PINE64 - PinePhone Pro Hardware

Looking for engineer for customized project MVP based on PPP

Mon, 06 Apr 2026 14:44:41 +0000

Hello, everyone! I’m looking for engineer for customized PPP. I need to create an MVP based on PPP. I need to create a physical qwerty keyboard, replace display with touch screen with a smaller more. Replace the cameras. Anybody can help with it?

If your USB-C port is flakey...

Tue, 24 Mar 2026 20:25:41 +0000

I was having problems with my Pinephone's USB-C charging port. I tried a few different cables but they were all making intermittent connections, if the phone was moved around at all power could be lost and then would reconnect making the phone boot up.

I do have a spare USB board but before doing surgery on the phone I sprayed some DeoxIT contact cleaner into the port and plugged/unplugged a USB cable several times. After doing this the port is working fine! Even directly wiggling the connector doesn't break the connection.

The Pinephone's USB port is open to dirt and debris and over the years apparently enough got in there to affect the connection. So if you're having problems with your USB connection this is something to try before swapping out the board.

*** EDIT *** Oops, I meant to post this in the regular Pinephone board, not the Pro board! Though I expect this info applies to both models.

performance wise which iphone does the pinephone pro compare to?

Wed, 14 Jan 2026 09:45:55 +0000

A pinephone pro having adequate software support in terms of hardware performance which iphone or android phone would the pinephone pro compare to?
Thank you.

Selling Explorer Edition Unit

Mon, 22 Dec 2025 13:38:38 +0000

Hi there,

If any one is looking for an Explorer Edition I have one for sale here: https://www.ebay.co.uk/itm/267520057218

I have been unable to get sound working during calls since I changed the motherboard out leaving me frustrated, so it's available to anyone else who would liketo tinker with it.

Kind regards,
David

No phone call audio, logs posted, modem can't init audio?

Tue, 02 Dec 2025 16:54:30 +0000

firstly the earpiece hardware works fine, I can play audio through it.

I replaced the mainboard on my PPpro and at some point early on I lost the ability to hear or send audio on a telephone call.

Follow down the thread to see the Quectel EG25 modem's dmsg failing to create the audio device

I flashed themodemdistro firmware 8.0 via ./flashall and then ADSP V 01.003.01.003 and then DSP V 01.002.01.002
https://github.com/the-modem-distro/pine...LASHING.md
did both several times over the last days.
incoming and outgoing calls no luck; 2g, 3g, 4g
interesting ringtone doesn't work either

I have been flashing various images testing, I have flashed an image of the final from my old main board where phone audio mostly worked. I have been writing my old /home onto the new installs once I have them installed but I do a phone test first.

Rebooting as well as shutdown, rest, boot doesn't work either.

Data works, SMS works, DIalling works receiving works, just no audio except that 4g fails to make/take a call as usual which will be a problem once 2g and 3g shut down.

the audio line alsa/pipewire stuff gets complicated I am nut sure what to look for in the modem's dmsg

I am probably missing an obvious mistake, embarrass me please by showing me my error!

(edit)moved to ADSB 30.004 and 4g seems to be work, but that is always temporary, not the real problem of this post anyways
(edit2) I even rewrote the EFS https://themodemdistro.com/efs_recovery makes calls no audio in/out

no SD boot on replacement PPpro board, loads CN android

Sun, 30 Nov 2025 10:26:05 +0000

I just received my replacement Pinephonepro system board.
I had a tow-boot bootable SD ready to begin the process but the phone now loads a Rockchip splash and then boots into Chinese Android.
It also doesn't auto-boot when plugged into power, it just charges as it is an android.
How can I force this to bootfrom SD?
I wonder if this requires ADB commands?
I also wonder if the board requires ADB unlocking now as it is loaded with android...
I do not dread/write/speak Chinese so I have no idea how to get into dev mode.

A side problem is the main camera socket keeps popping off from the new board, I tried adding a paper shim to push it down via pressure form the plastic enclosure when screwed down. I wonder if it is broke and I need to spend $30 replacing the camera.
it also seems that the proximity detector is not fully pushed into its place as I can see the notification LED, this probably just needs to be opened and pushed down or remove the shim from the main camera.

(edit)
https://wiki.radxa.com/Rock/SD_booting
this is for rockchip not sure if it will do anything useful for me, I want to be careful that I dont do more damage.
This just seems to be a windoze SD card writer app which can flip the bootable bit

per the dev boards(r-pi like boards) stuff here https://wiki.radxa.com/Rock/dual_boot
You can flash over those board's /recovery partition, if I could get that much access from my phone

For now this might as well be bricked unless I reinsert the broken board that cant use hibernate mode and cant boot without a good smack(detached RF shield), I wonder if I can interfere with anything to force a SD boot using the serial cable?

slight bumps causing phone to turn off.

Tue, 11 Nov 2025 19:16:54 +0000

Hi, My ppp started being super sensitive to any bumps, or too much pressure on it and I don't know why. if i slightly bump it or barely tap it against something it will immediately stop working and the screen will go blank, I don't think it's completely off because the screen, though black, still is slightly back lit. I've also found that if i even squeeze the phone slightly it does the same thing. I then have to turn it off, and then back on, which is not easy. I have to pop the battery out and back in, shake it, and sometimes tap on the back of it while holding the power button to get it to come back on, and then more often than not, it starts to boot, and then gets stuck, and I have to repeat the process until it turns back on. im not sure what happened to cause this, I thought at first the battery was not making good contact with the terminals in the phone, but that isnt it. its like something is loose but im not sure where to begin in fixing it, has anyone else had this issue? are there any suggestions? Any help will be very much appreciated as my ppp is pretty much completely unusable right now. Thanks!

Pinephone pro stuck while booting

Sat, 16 Aug 2025 17:35:48 +0000

So i have a pinephone pro and i have tried every thing provided here https://forum.pine64.org/showthread.php?tid=18216 and gotten assistanve on discord which still did not help. Ive charged for approximately 10 hours on Maskrom, tried using a sd card, flashed directly to EMMC, attempted to reinstall Towboot, Used a gui tool and dd, and still it will not work. Whenever i turn it on with a working os installed it will flash red then yellow then stay stuck, the screen wont even show anything. If i try without an os on the phone it reboots as the it knows there no os installed. Sometimes too when i turn it on it will stay red and just vibrate as soon as it is turned on. It will not even boot to an SD card if i use either the RE button or the volume down button. I can however boot into mass storage mode by holding volume up and connect it to the computer, im not sure how much this can help but if anyone can help pls do.

touchscreeh doesn't accept input

Tue, 10 Jun 2025 05:55:52 +0000

The original problem started with an upgrade in April 2025 that installed 600 packages on my PPP, which failed to complete. I reran the the upgrade, which ended up completing, but it failed to boot. I saw several "core" files in the root dir. So, I decided to install from a new img.

Installing mobian phosh (mobian-rockchip-phosh-20250525.img.xz).

I installed the new OS image on my PPP using the suggested method (dd). I placed the installation img file on a micro sdcard which had that same OS on it. I installed that sdCard in my PPP and booted it.

I then used dd to transfer that img to the eMMC per instructions.

Code:
dd if=IMAGE.img of=/dev/mmcblk2 bs=1M status=progress conv=fsync

I rebooted the PPP.

All was well, the system was working. I installed some software. After a few days, I decided to upgrade the system. After rebooting the touchscreen would not accept input. The login screen would appear, but would not respond to my touch. I plugged in a usb mouse via a pine64 usb multi port hub. The mouse pointer appeared and I could login.

I tried booting the micro sdCard, but was confronted with the same situation.

I decided to go to an earlier img (20250618). After installation it booted fine, but would not respond to my touch. I tried booting from an arch img (20241223) on an sdCard. Still, touch did not work.

First, I'd like to know if anyone else is experiencing this issue. And, if so, have they found a solution for it.

Second, if no one has experienced this, does anyone have a clue as how to go about debugging the problem?

Thanks for any help.

RTKLIB PinePhone Pro GPS

Thu, 01 May 2025 19:16:09 +0000

Hello all,

I want to use my PinePhone Pro as a rover in a RTKLIB setup. Todo so, I have some questions:

1. Is it correct, that the Pinephone Pro GPS sensor can provide GPS raw data?
2. If yes, what is the format? In RTKLIB I can select rtcm2, rtcm3, oem4, oem3, ubx, ss2, hemis, skytraq, gw10, javad, sp3
3. On mobian the device should be ttyUSB1, correct? I have configured it with baudrate 115200. There are 2 additional options in RTKLIB inpstr-path config: 8:n:1:off Does anyone know, what does that mean and if it is correct for the PinePhone Pro?

By the way: What GPS chip is used in the phone?

Are there plannes to create a new and more powerfull PinePhone Pro?

Mon, 07 Apr 2025 07:22:12 +0000

Hello,
iam pretty interested in the PinePhone Pro and really like the concept. But sadly, 4Gib RAM and the RK3399S are just too week for todays use. Now my question is if there are plannes to bring out a new version with more ram (like 8Gib or so) and a better chip (Like the RK3588), or to bring just a new mainboard with upgraded parts that can be swapped out.
Thank you for your help

At what voltage is the battery fully drained?

Tue, 01 Apr 2025 13:44:03 +0000

I'm wondering, what is the minimum battery voltage the PPP can run at before having to shutdown? Or in other words, what should the battery's voltage be when the installed OS says it's at 0% charge?
Thanks in advance, ethical_haquer

PinePhone Pro disable Volume Buttons when malfunctioning

Wed, 12 Mar 2025 23:51:19 +0000

Hi together,

here comes a solution for a problem I had with the PinePhone Pro, hoping that it helps someone else. When I started installing different distributions, there was the same problem all over again. The volume buttons were randomly sending signals to the phone although I didn't press them, constantly changing the volume. This was very annoying as the pop-up message interrupted anything I wanted to do on the phone. After some research I found the following work around. Tested it on Arch with Phosh and on Manjaro with Plasma Mobile, but should work on other distros too. The solution works by unbinding the volume keys from the driver. The volume keys will stop working then, but the power key can still be used normally. Up to now I didn't miss the volume keys, as it can easily be adjusted in the settings. You can find more information about driver unbinding in this article: https://lwn.net/Articles/143397/

First open a terminal and issue the following command to stop the nuisance:

Code:
sudo echo -n "adc-keys" > /sys/bus/platform/drivers/adc_keys/unbind

Now to permanently deactivate the volume keys on startup we can create a systemd-service.
All of the following code-snippets should be executed as root-user.
First create the shell-script, for example in /opt or wherever you like to have it:

Code:
cat > /opt/unbind-adc-keys.sh << EOF

#!/bin/bash

echo -n "adc-keys" > /sys/bus/platform/drivers/adc_keys/unbind

exit 0

EOF

Don't forget to give execute permissions:

Code:
chmod a+x /opt/unbind-adc-keys.sh

Now create the systemd service unit:

Code:
cat > /etc/systemd/system/unbind-adc-keys.service << EOF

[Unit]

Description=Unbinds the Volume Keys on startup

[Service]

ExecStart=/bin/bash /opt/unbind-adc-keys.sh

[Install]

WantedBy=mulit-user.target

EOF

Now enable the service unit:

Code:
systemctl enable unbind-adc-keys.service

From now on the volume keys should be disabled from startup and you can again enjoy your PPP :-)

PPP, PP, PBP, and Accessories For Sale

Fri, 14 Feb 2025 09:58:32 +0000

Offering my Pinephone Pro Explorer Edition + Soft TPU Protective Case + USB-C Docking Bar + Extra Tempered Glass Screen Protector, Pinephone Braveheart Edition w/VCONN mod + Soft TPU Protective Case, and Pinebook Pro + Barrel Plug Charger.

Reason for sale - I bought this hardware years ago and I have barely used it since.
Ships from - Mexico.
Condition - Pinebook Pro is like new, Pinephones are lightly used.

Minimum asking prices (shipping not included):

PinePhone Pro + Accessories = $250 (SOLD!)
PinePhone + Accessories = $50
Pinebook Pro = $120

Items can be sold separately. If I receive multiple offers, I will go with the best offer.

Reply or DM for more info.

BOOT ERROR: Failure to read device ID

Fri, 10 Jan 2025 11:38:17 +0000

Hello,

I have a Pinephone Pro device. It is one of the early models with the microSIM slot.

Note: If I do not have a hardware problem, I will repost this thread in one of the other PPP form categories.

The device has tow-boot installed with Mobian (Bookworm) for the operating system, which worked quite well for me (only problems were poor battery life and inability to switch between external speaker and phone speaker without a reboot).

Mobian is installed on the internal eMMC storage. The microSD for extra storage is empty (not used).

The battery drained fully and upon recharge the PPP booted to this error message.

Quote:[1.260681] dw-abp-uart ff180000.serial: Failed to creat device link (0x180) with 0-001c
[1312821] dw-abp-uart ff180000.serial: Failed to creat device link (0x180) with 0-001c
[2.094416] OF: graph no port node found in /i2c@ff3d0000/typec-portc@22
[3.269239] pinephone-keyboard 5-0015: Failed to read device ID: -6

The "pinephone-keyboard 5-0015: Failed to read device ID: -6" error is mentioned in this forum thread titled The Case of the Vanishing EMMC; however, I do not have the knowledge to confirm from the thread that the root cause is an inoperable hardware.

The pinephone-keyboard 5-0015: Failed to read device ID: -6" error is also mentioned at this git-hub thread two-boot installed on PPP/ EE. USB mode works, but can't boot from SD; however, I cannot decifer the fix.

I followed the directions to revive a PPP with a fully drained battery described at Troubleshooting; however, this did not restore the ability to boot.

I did a reinstall of Mobian to the eMMC storage and on boot up, the same boot error message appears...

Quote:[1.260681] dw-abp-uart ff180000.serial: Failed to creat device link (0x180) with 0-001c
[1312821] dw-abp-uart ff180000.serial: Failed to creat device link (0x180) with 0-001c
[2.094416] OF: graph no port node found in /i2c@ff3d0000/typec-portc@22
[3.269239] pinephone-keyboard 5-0015: Failed to read device ID: -6

I did a reinstall of Mobian to an sdcard and on boot up, the boot error message is...

Quote:[1.259126] dw-abp-uart ff180000.serial: Failed to creat device link (0x180) with 0-001c
[1308292] dw-abp-uart ff180000.serial: Failed to creat device link (0x180) with 0-001c
[1.460453] mmc1: tuning execution failed: -5
[1.465354] mmc1: error -5 whilst initialising SD card
[1.592567] mmc1: tuning execution failed: -5
[2.077685] OF: graph no port node found in /i2c@ff3d0000/typec-portc@22
[3.269239] pinephone-keyboard 5-0015: Failed to read device ID: -6

Is there sufficient information above to diagnose the root cause is hardware related?

Is the root cause a busted eMMC device, pinephone-keyboard, or something else?

If the root cause is hardware, what is the replacement?

Any help and advice is greatly appreciated.

DrH