Pinephone received yesterday. Ran it through basic phone and web browser functionality tests.
This phone is apha not beta.
Access to voice and data dropped multiple times.
PO resets and battery removal and replacement to clear.
Other basic functionality such as camera would require a complete overhaul of both SW and HW to even get to minimal functionality . 
Will try to get this not ready for prime time phone returned for refund.

So I'm still playing with my Zig toy OS for PinePhone, and I reached the point where I can draw on screen the A53 CPU core temperature   

Does anyone know what temperatures I need to set for the alarm/shutdown limits please?  It seems to get hot quite fast, although that is probably my code  

I guess I should consider the GPU sensors too, but since I am streaming a framebuffer direct to LCD, I doubt they are doing much temperature wise.

So I'm having trouble with my Pinephone which only worked properly for a day and I'm trying to work out which part I need to replace. Today, I remembered that I had the hub that has HDMI output so I tried booting it with that connected with both the regular install (the preloaded plasma) and the jumpdrive SD card. Neither gave me HDMI output. So the question is, is it supposed to work from boot, which would point to the mainboard being the issue - or not, in which case, I'm still up in the air.

Just to forestall the obvious questions, the phone *is* technically booting. I can see output on the serial console, it gets a DHCP address etc, I just don't get any kind of display on the screen (though the backlight does come on). I don't *think* it's the software (though I'd be happy to be proven wrong) so I think it comes down to the mainboard or the display. I'd be happy to pay for either but don't want to shotgun things.

This is a proposal for a guide to upgrade to Forky(Mobian testing) from Trixie(the previous testing release)
This has now been tested!!! it worked for me on my PPpro.
https://blog.mobian.org/posts/2025/10/ne...ting-keys/
It seems there are errors but we can fix these.

I will first recommend everyone with disk space use the tow-boot blue light special bulk storage mode and save the / of your PP or PPp to your computer, this will take a while to do but even if encryptde is pretty easy, in my ubuntu derivitave OS the GUI asked if I wanted to decrypt the volume, entered password, and I had access to my root.  A alternative is to use a USB mass storage device over an adapter or a big SD card to save your root or at least your /home.

below is form the guide linked above with some lined out do-not instructions and my edits in green 
_______________________________________________________________

1. keep your device plugged to a power source: such an upgrade can be a rather long process, you don’t want to run out of battery half-way there!
   
2. backup all your personal data
   
3. really, we mean it: backup all your personal data!
   
4. install
   
   Code:

   sudo apt install openssh-server
   and execute the entire upgrade process over SSH (and preferrably using
   
   Code:

   sudo apt install screen
   or a similar tool, so the upgrade can carry on even if the network connection is lost)
   
5. ensure your Trixie installation is fully up-to-date; as the GPG key we use for signing the package repository has expired since the Bookworm release, you’ll probably need to run
   
   Code:

   sudo apt update && sudo apt dist-upgrade
   at least twice: the first time it will update the Mobian keyring package, the second invocation will pull in the latest updates for Mobian-specific packages
   reboot,
   
6. then edit both 
   
   Code:

   sudo vi /etc/apt/sources.list.d/debian.sources
   and
   
   Code:

   sudo vi /etc/apt/sources.list.d/mobian.sources
   , replacing all occurences of trixie with forky in both files; forky
   
7. (not sure this step is required in trixie to forky)you should then stop the
   
   Code:

   sudo service greetd stop
   service (this will stop all running graphical applications, and is why SSH is needed!) and run
   
   Code:

   sudo apt update && sudo apt dist-upgrade
   once again
   
8. (trixie to forky I didn't need this as only 2 packages were removed non-mobian both)write down the list of packages removed by
   
   Code:

   sudo apt dist-upgrade
   which start with
   
   Code:

   mobian-
   as those will have to be reinstalled later on to restore full functionality of your device; please note that some packages have been renamed/replaced in Trixie, so it can be expected to see e.g.
   
   Code:

   phog
   or
   
   Code:

   pinephonepro-tweaks
   in the list of removed packages
   
9. reinstall all
   
   Code:

   mobian-*
   packages removed in the previous step; this will remove
   
   Code:

   pulseaudio
   from the system, which is to be expected as Mobian now relies on (and mandates the use of) PipeWire(already done in the trixie upgrade form bookworm)
   
10. run
    
    Code:

    sudo apt autoremove
    to clean up unneeded packages
    

I amusing the latest Mobian trixie on my PPpro, slightly modified with an older kernel as this seems toavoid the non-working wake button issue. https://forum.pine64.org/showthread.php?tid=19940

My issue is that unless I run the caffeine toggled on my phone falls into a suspend coma nad no charge cable, phone call, or wake button brings it back.  If the indicator LED was blinking it will continue,it might have even been one case where an audiobook was running and I couldnt get it back thoug that might be the intermittent non function of the wake/sleep button in the OS(holding still triggers a shutdown).

I do NOT have a serial cable to get the logs right at the fall into suspend coma.

I managed to bugger up the boot configuration of my pinetab-V. At first, only a blank screen would come up, and it wouldn't even boot into the sdcard, but this much is fixed. 

Now, I want it to boot from the EMMC, which it doesn't do. Luo provides an u-boot update script in the GitHub releases for updating the bootloader, but I do not believe this tool is suited from rescuing the boot of a broken system. 

I will review the starfive documentation on booting, but if someone has experienced a similar issue, assistance would be appreciated. I have some critical projects going on I must dedicate my entire attention to, and cannot afford to tinker as I usually do.

Hello all,

Short version.

Is there a current satisfactory working platform for my dusty pinephone?



Longer version, old timer who lives in the past,I gave up on phones in total for a good while, picked up a pay as you go flipper from wally world a couple months back and was wondering if I should try to rehome the sim to my pinephone?

Looking for advice and links if applicable, been awhile so pretty much back at noob status, please type slowly and with pictures   


Thanks in advance

"Remember, it's not an adventure if part of it doesn't suck!"

I just moved my Rockpro64 from a 128GB emmc to a 256GB emmc, and I remembered everything except one thing: Updating /etc/fstab to use different UUIDs before swapping the emmcs. So it wouldn't finish booting. I attach the serial console, figure out what the problem is, and the question is, how do you fix it without using anything else?

I was in U-Boot to begin with, so we want to get to the initramfs where we have lvm tools. We have commands like 'fatls mmc 0:1' to look around. (List files on a FAT-formatted filesystem, emmc interface, device 0, partition 1)

https://docs.u-boot.org/en/stable/usage/index.html
https://docs.u-boot.org/en/stable/usage/cmd/booti.html

Hi everyone,
I recently got a Pinecil V2 and I’m wondering what’s the most stable firmware version to use right now. I saw some people mention IronOS builds from GitHub, but I’m not sure which one is currently recommended.
If there’s a safe way to roll back firmware if something goes wrong during the update?
Thanks in advance!

Hi!
Very satisfied user of this device. The stock arch danctnix os is a joy to use both in tablet mode and with keyboard.
My only issue is with updates. They always seem to stop after a while. The usual