Hi Everyone,

I received my new Pinephone yesterday and was very impressed with the build quality.  despite watching the videos, I was really expecting something more brick-like and not the nice form factor it arrived in.  The OS experience is pretty similar to what I had seen in the videos.  Its very early days and needs some work.

This is where my questions come in.  I'm not very good at coding so can't really be of use there.  However, is there any testing that I could be doing that would help the project?  I get that it's not ready as a daily driver but I want to help this succeed and want to know how I can help out.

Second questions is around donating.  I know that Ubports has a donations page and I plan on doing something there.  Is there something similar for Pine64?

Thank you!

Jmasters

One of my major annoyances with the PBP right now is that sound doesn't work after deep sleep.

I'm using Ubuntu 20.04, the 5.7 kernel from Manjaro/tsys with the hwaccel patches, and the BSP uboot (as the mainline uboot/ATF don't support deep sleep yet, and I consider this an important feature).  If you're following along, you're on your own if you're doing something different.

Coming out of deep sleep, the system simply doesn't have sound.  If you run the proper incantations, and things aren't using the sound devices, you can, with a bit of fiddling, get sound working again.

Experimentally, playing with modules, I traced the issue down to module snd_soc_es8316 - coded up here: https://gitlab.manjaro.org/tsys/linux-pi...s/es8316.c

Compare this with, say, the es8328 file: https://gitlab.manjaro.org/tsys/linux-pi...s/es8328.c

You'll notice, if you look in the ops struct, that there's a suspend and resume function in the 8328 codec - but NOT in the 8316 codec!

My theory is that the reason there's no sound after deep sleep is because the 8316 driver simply doesn't know how to properly reset the codec after sleep.  When the module is re-inserted, the device is re-initialized, which is why sound comes back - but there's no need to do this, if the module can simply perform the proper actions on resume.  Right?

Let's implement that set of functions and try it out!

Hi.
I received this message:
EPERM: Operation not permitted, open '/dev/rdisk3'
Any ideas what to here?
Thanks
Ilan

Hi everyone.  Just wondering if anyone has any experience in having a PineTime watch delivered to Canada.  Trying to determine what the import taxes or duty might be for delivery to Canada.

Thanks in advance!

support for slarm64 for Pinebook Pro (aarch64 unofficial port slackware)

the system can be assembled as armhf and aarch64, assemblies are made under aarch64

links:

Hey guys - I feel like the laptop is super slow even if it is just opening a browser. CPU spikes up to 85%-95% just to load. I can't imagine 4GB ram and 5GB of swap is still that slow even at the beginning of starting up the laptop.

Anyone is having problem with this or is it just Manjaro i3 that is causing it?

It's about $15.

One thing I'm seeing, fairly consistently, is problems on the forum that are borderline impossible to troubleshoot without serial output.

Due to how the PBP brings up the display, it has to get quite far into the boot process before you'll see anything beyond the status LED.  Troubleshooting "LED comes on, nothing else happens" without the serial output is both challenging and frustrating.

With the serial output from the various stages of boot firmware and potentially early kernel, troubleshooting becomes very straightforward, because all the stages are fairly verbose and tell you what's wrong if they can't proceed.

Also, given the boot ROM's rather odd preference to pull firmware from the eMMC before searching the SD card, a corrupt eMMC will easily prevent the system from booting, and it's quite annoying to correct.

With a UART and the USB eMMC adapter, both of these problem classes become radically easier to troubleshoot and fix.

So buy (or build) the proper adapters.  Please.  It's still very much beta, rough around the edges hardware in early boot, and it would be really nice to be able to be more helpful.

I am trying to put some music/podcasts on my PinePhone running Ubuntu Touch and noticed that when I plug my PinePhone into my laptop using the cord sent with the phone, the phone starts charging but I can't see the phone in the file manager and running "fdisk -l" I also don't see the phone. Anyone else having a similar issue or know a workaround? I am running Linux Mint on my computer for what it's worth.

The A72 and A53 core are each (according to Rockchip) optimized for, respectively, high-performance and low power.
How does our system (linux kernel maybe?) choose which processes to put into which core?

For example, if I'm running a single thread process that occupies 100% of one single core, I would like the system to choose the high-performance core in order to complete the task faster, rather than choosing the low power core to save power.

Do we (end users) have any control over this? Should we?

Hey group,

Switched my CE over to Mobian and i'm quite impressed by Phosh and by the Mobian underpinnings so well done. 

Quick question, if I install the nightly and run an apt upgrade, will this pull down the latest changes upstream from the mobian project? Or will it just upgrade the base Bullseye packages? Are there repos set up for Mobian yet is essentially my question.

Thanks!