I recently got my sopine modules and my clusterboard only to notice that the network is not working. So I searched the forums and found a way to conveniently build an Armbian-Image which has the network fix applied (using Ubuntu):

I tested this with the current Armbian Focal release.

Thanks to @AZClusterboard  who made an initial guide on how to setup the clusterboard which gave me confidence to buy my own cluster!

Step [b]Overview:[/b]

1. Download current Armbian Focal release
   
2. Mount the Image to make modifications
   
3. Make changes to the .dtb file (allwinner network fix)
   
4. Write the changed Image to as many sopines as you wish
   
5. (Give each sopine a unique hostname by hand)
   

https://github.com/syonyk/pinebookpro

I've created two halfway helpful utility scripts that are useful enough to share generally. They should work with any Linux, though I've only tested them on Ubuntu 20.04/mainline kernel 5.7.

The first is cpu-set.sh - which allows you to, as root, quickly toggle between all CPUs, big CPUs, little CPUs, see the status of the CPU, and set the governor across all the cores (the cpufreq-utils don't seem to get all the cores properly). Really, you shouldn't have to do much more than powersave, performance, or schedutil. I've not seen much power savings by turning cores off, but if you want to do hardware accelerated KVM work, you'll need to disable the little cores - they don't seem to support the hardware virtualization properly.

The second is pbp-status.sh - which shows the CPU status, temperature, and some basic battery stats (voltage, current, watts). Most of the battery stats will be zero while charging, as the only one you get out is the voltage. This doesn't need root.

This website https://xnux.eu/devices/pine64-pinephone...-pinephone states:

Quote:It's not fixable in SW, other than via a manual selection of power and data roles by the user.

Hi, 

I issued an

Hi all,

I tried the dark theme by:

Every time I press a call, I and the person I am talking to hear loud static noises. It sounds a bit like a radio and it's very hard to understand each other.

Is this normal or a specific hardware problem.

Thanks

Any new info on when I would be able to order a pinephone? thx...

When I go to System Settings > Accounts > Nextcloud, I get an endlessly spinning circle to the right but nothing ever happens. Has anyone else been able to setup a Nextcloud account or any other account? I just tried and none of the account options work. Just spins forever.

Before replacing the battery, internet and texting were working on Verizon's network (I hadn't tried making a call). After the 3500mAh replacement[0] the bottom half of the screen started flickering. I immediately turned the phone off and put the stock battery in, but now I don't seem to have any cellular network access (though the phone can see my SIM card). I've already double checked that it wasn't a result of me accidentally flipping the kill-switches when I did the swap. I recognise that this was the result of me playing with fire to see what would happen, and while I'm open to advice I'm sort of assuming I'll need to wait for more main boards to come available -- replacing the modem specifically is probably above of my level of solder competency. I just wanted to warn anybody googling for pinephone battery upgrade information related to v1.2 CE that my personal experience is 3500mAh kills modems.

[0]: https://www.amazon.com/6-7-8-Battery-Cas...07F7R4HLM/

Upgraded from PinePhone Devel Image #52 to #58 this morning over OTA, rebooted and now have an utterly unresponsive touchscreen

It boots up fine, Volume Up and Down buttons and Power button work (as evidenced by OSD responses) and I can still ssh in, but touchscreen not working.

If I revert back to Image #52, touchscreen works again - OTA update to #58 breaks it again. I see from System Image Changes page (https://ci.ubports.com/job/rootfs/job/ro...ge/changes) that #58 and #59 have not changed since #57, so assuming this is a #57 problem?