I just wanted to share how I got my PPPro booting after the battery was fully drained (just after I received my phone). I saw there are already some Threads (e.g. #15896) which describe this issue. However, I wanted to share some additional debugging instructions for reference. These instructions will help ascertaining if the phone enters Maskrom mode correctly (precondition for charging the drained battery). The actual instructions that helped me solving my issue are described in the blue box of the Installation instructions in the PPPro wiki.


Behavior: The phone does not boot (neither does it charge)

Fix: Instructions how to charge the PPPro if the battery is fully drained (quoted from the wiki):

Quote:If the battery is fully drained U-Boot might fail to boot any installed operating system on the eMMC and microSD card due to a bug.
If that's the case please start your phone in Maskrom mode and let it charge in that for a few hours. To do that:

• Remove any microSD card from the phone
  
• Hold the "RE" button underneath the back cover of your Explorer Edition (or shorting the bypass contact points on the Developer Edition)
  
• Connect the phone to an USB port of a computer, while still holding the button
  
• Check if the phone in Maskrom mode appears in the output of the Linux command lsusb on the computer (if the device disappears again please use a different cable)
  
• Let the phone charge for multiple hours
  

Note: If that didn't work, try to remove the battery and the USB cable and hold the power button for a few seconds and then insert the battery again, before retrying the procedure.

1. In the first terminal window I watched the lsusb output, while connecting the PPPro with the RE button pressed. The device showed up on the USB bus:
   
   Code:

   $ watch lsusb
...
Bus 001 Device 011: ID 2207:330c
...
2. In a second terminal window I concurrently observed the dmesg output, while connecting the PPPro. Here, the PPPro was showing up on the USB port as well:
   
   Code:

   $ tail -f /var/log/{messages,kernel,dmesg,syslog}
...
Feb  2 13:19:15 <HOSTNAME> kernel: [148427.240994] usb 1-1.2: new high-speed USB device number 11 using ehci-pci
Feb  2 13:19:15 <HOSTNAME> kernel: [148427.350785] usb 1-1.2: New USB device found, idVendor=2207, idProduct=330c
Feb  2 13:19:15 <HOSTNAME> kernel: [148427.350791] usb 1-1.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb  2 13:19:15 <HOSTNAME> mtp-probe: checking bus 1, device 11: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2"
Feb  2 13:19:15 <HOSTNAME> mtp-probe: bus: 1, device: 11 was not an MTP device
Feb  2 13:19:15 <HOSTNAME> upowerd[2113]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2
...
   
   

My keyboard has stopped working.  When there is a text entry in an app the keyboard does not open.  That leaves you dead in the water.  You can't work with terminal to make any corrections.  I am running off system memory; not an sd card.  Working reasonably well with keyboard til now.

Have restarted several times and also just shutdown and then restarted.  No changes.

What does the RE button do?  Could that help.

tom kosvic

I installed caffeine with
yal -S caffeine
The icon is on the screen but does not work
In the last release it works but from the windows down with
with other controls

I’m on Day 2. The phone works though not very cleanly (Mint Mobile) but I have no other audio - no YouTube in browser, no radio in Shortwave, no sound in cnn clips. It’s not muted and Settings aren’t helpful. Advice? Maybe some CLI commands?

Placing a calll in "Phone" or "Phonebook" now kills the phone completely to a black screen immediately.  Reboot is necessary.

When I first got phone and got it to boot, I tested Phone and it worked fine.  I use Consumer Cellular sim card.  This worked fine on previous PP.  Cellular network in settings shows sim card operating properly.  Initial calls worked fine.

Since these initial tests of phone,  I have done a major system upgrade with pacman.  I have also added a contact list to Phonebook using kdeconnect.

I am thinking of undoing the upgrade (approx 390 packages) to see if phone comes back.

Also, perhaps reinstalling phone and phonebook if I can find the file names.

Anyone have any further ideas?

Perhaps reset the RE switch which I don't know what it really does, then reboot????  Gotta get back to where I was.

thanks,       tom kosvic

I am finding that it is necesary to conect ppp to a charger connected to 120v to increase the battery charge.  Connecting to pc with USB (even USB C) does not seem to provide enough power to increase the indicated battery charge.  And this was with an inactive phone.

I had ppp connected by usb to pc and I was having a hard time getting anything to boot and if booted wouldn't stay booted.  I finally noticed that the battery charge was near zero.  What I had been blaming as software failures was likely caused by insufficient battery charge.  This was after leaving phone connected to pc through usb overnight.

Upon connecting to charger the battery charge increased to 98% in just an hour or so even with active things going on with the phone.  The software problems have basically gone away. 

tom kosvic

I have a new pine64 and once unpackaged, removed battery plastic, attempted to power on. Only red/orange indicator appears, black screen. Inserted micro sd with mobian image and got a green indicator but still black screen.
Would really love to get this bad-boy up and running! Thanks!

Wish to move at least contacts file to PPP.

I tried jumpdrive (pp version) on an sd card and nothing.  My linux pc file managers do not even see the PPP

Anyone have a breakthrough?

tom Kosvic

Mostly no one care about Android on the PPP but would by nice to have the source of the factory AOSP image. Is there anything? (:

Thanks in advance

FYI, chatty v0.6 rolled in to Bookworm this morning.  This includes some big and important updates to - hopefully - make MMS work properly (among other stuff).  The Pinephone might finally become my "daily driver".