<![CDATA[PINE64 - General Discussion on PinePhone]]> https://forum.pine64.org/ Sat, 16 May 2026 02:04:38 +0000 MyBB <![CDATA[keyboard and docking pad]]> https://forum.pine64.org/showthread.php?tid=20192 Sun, 15 Feb 2026 14:41:29 +0000 wigan]]> https://forum.pine64.org/showthread.php?tid=20192 vmlinuz-6.1-sunxi64

Docking bar doesn't work w/ the fon in the keyboard (connected to the pinefon
USB-C port).  The keyboard manual says (in four languages)...

  When coupled w/ the keyboard the pinefone's USB-C is to be used 'solely' for
  data and peripherials.

I take the docking bar to be a peripherial.  I've read through the relevant
material w/o finding a way through.

  Firmware:  https://xnux.eu/pinephone-keyboard/
  Firmware repository: https://xff.cz/git/pinephone-keyboard/
  FAQ:  https://xnux.eu/pinephone-keyboard/faq.html

Would like to hear from anyone who has this working.

-ludy-]]> vmlinuz-6.1-sunxi64

Docking bar doesn't work w/ the fon in the keyboard (connected to the pinefon
USB-C port).  The keyboard manual says (in four languages)...

  When coupled w/ the keyboard the pinefone's USB-C is to be used 'solely' for
  data and peripherials.

I take the docking bar to be a peripherial.  I've read through the relevant
material w/o finding a way through.

  Firmware:  https://xnux.eu/pinephone-keyboard/
  Firmware repository: https://xff.cz/git/pinephone-keyboard/
  FAQ:  https://xnux.eu/pinephone-keyboard/faq.html

Would like to hear from anyone who has this working.

-ludy-]]> <![CDATA[Faster OS test deployments - Faster UART?]]> https://forum.pine64.org/showthread.php?tid=20190 Wed, 11 Feb 2026 12:30:42 +0000 WhiteHexagon]]> https://forum.pine64.org/showthread.php?tid=20190

The UART seems to default to 115,200 (from u-boot?) and is working fine with my serial USB adapter.  However this baud rate is going to be too slow for my 10MB debug builds.

So I wanted to try 1.5Mbps with the UART divisor of 0x1, but it doesnt seem to work (using linux util 'screen' but also tried my own Zig UART code).

My question is, how do I set the APB2 clock dividers and UART0 divider to match any of the standard baud rates please? and is there a limit on UART0?  I seem to recall a limit elsewhere related to the modem, but I cant find the details now.

Also, from what I brute forced so far, it seems like I can only approximate other baud settings?  In fact the default UART divider of 0xd seems to also be an approximation?  Is that the best I can do here?

Alternative would be to get the USB port working, but I think that might be quite a bit more challenging...]]>

The UART seems to default to 115,200 (from u-boot?) and is working fine with my serial USB adapter.  However this baud rate is going to be too slow for my 10MB debug builds.

So I wanted to try 1.5Mbps with the UART divisor of 0x1, but it doesnt seem to work (using linux util 'screen' but also tried my own Zig UART code).

My question is, how do I set the APB2 clock dividers and UART0 divider to match any of the standard baud rates please? and is there a limit on UART0?  I seem to recall a limit elsewhere related to the modem, but I cant find the details now.

Also, from what I brute forced so far, it seems like I can only approximate other baud settings?  In fact the default UART divider of 0xd seems to also be an approximation?  Is that the best I can do here?

Alternative would be to get the USB port working, but I think that might be quite a bit more challenging...]]> <![CDATA[best setup to run waydroid with discord + instagram]]> https://forum.pine64.org/showthread.php?tid=20180 Sun, 01 Feb 2026 19:41:26 +0000 dustfinger]]> https://forum.pine64.org/showthread.php?tid=20180
I am interested in knowing if anyone has been able to run Instagram or discord apps using waydroid (or alternative setups) on the pinephone with stable performance. I am also interested in knowing if anyone has been able to run any youtube app with stable performance. 

Aside from the proprietary apps, I would also love to hear from anyone using alternative opensource apps? I know some projects exist for discord, such as WebCord, ArmCord and maybe there are more projects like those some of you have had success with and would like to share.

Please also share what OS + mobile shell combination you are using and anything else you can think of that was important for performance and stability.

cheers!

dustfinger]]>
I am interested in knowing if anyone has been able to run Instagram or discord apps using waydroid (or alternative setups) on the pinephone with stable performance. I am also interested in knowing if anyone has been able to run any youtube app with stable performance. 

Aside from the proprietary apps, I would also love to hear from anyone using alternative opensource apps? I know some projects exist for discord, such as WebCord, ArmCord and maybe there are more projects like those some of you have had success with and would like to share.

Please also share what OS + mobile shell combination you are using and anything else you can think of that was important for performance and stability.

cheers!

dustfinger]]> <![CDATA[Bare Metal OS]]> https://forum.pine64.org/showthread.php?tid=20170 Fri, 16 Jan 2026 12:17:53 +0000 WhiteHexagon]]> https://forum.pine64.org/showthread.php?tid=20170   

Anyway, I'm almost at the point where I can add some basic Apps, and then I'll have to think about distribution to a couple of colleagues for testing.

First I need to ensure my OS can only boot on the PinePhone v1.2b, since that is the only device I have for development.  Does anyone know if there there is a version string somewhere within the hardware?

The other unknown is U-Boot.  It seems to do a lot of the hardware configuration before it reaches my kernel code, and I am a little concerned that people might be running different versions from me (U-Boot 2020.07).  Currently I'm running from SD card, but maybe the boot process/chain is different once I figure out how to install my kernal onto the eMMC?

Do we know how many v1.2b devices were sold? and how long they will stay in production?  Since that obviously limits the scope of my project.  The device I have is continually out-of-stock, maybe already discontinued?  And the expensive model is currently $270, which is a bit of a worry when I see android 14 phones going for 79eur.  Are the PinePhones still selling?

Anyway, whatever becomes of this project, I wanted to thank the community for their support over the past 2 years.  It's a shame I didnt discover the PP sooner!  I was hoping to add LORA and Keyboard case support next, but just discovered they are no longer available Sad]]>   

Anyway, I'm almost at the point where I can add some basic Apps, and then I'll have to think about distribution to a couple of colleagues for testing.

First I need to ensure my OS can only boot on the PinePhone v1.2b, since that is the only device I have for development.  Does anyone know if there there is a version string somewhere within the hardware?

The other unknown is U-Boot.  It seems to do a lot of the hardware configuration before it reaches my kernel code, and I am a little concerned that people might be running different versions from me (U-Boot 2020.07).  Currently I'm running from SD card, but maybe the boot process/chain is different once I figure out how to install my kernal onto the eMMC?

Do we know how many v1.2b devices were sold? and how long they will stay in production?  Since that obviously limits the scope of my project.  The device I have is continually out-of-stock, maybe already discontinued?  And the expensive model is currently $270, which is a bit of a worry when I see android 14 phones going for 79eur.  Are the PinePhones still selling?

Anyway, whatever becomes of this project, I wanted to thank the community for their support over the past 2 years.  It's a shame I didnt discover the PP sooner!  I was hoping to add LORA and Keyboard case support next, but just discovered they are no longer available Sad]]> <![CDATA[Rockchip gets DMCA'ed on media acceleration]]> https://forum.pine64.org/showthread.php?tid=20156 Mon, 05 Jan 2026 13:33:33 +0000 biketool]]> https://forum.pine64.org/showthread.php?tid=20156 https://github.com/rockchip-linux/mpp
looks like the other repos are up and only media acceleration is DCMA'ed.
https://hackaday.com/2026/01/05/github-d...a-request/
though someone could just fork and re-license correctly I think...]]> https://github.com/rockchip-linux/mpp
looks like the other repos are up and only media acceleration is DCMA'ed.
https://hackaday.com/2026/01/05/github-d...a-request/
though someone could just fork and re-license correctly I think...]]> <![CDATA[Power up a 2nd core?]]> https://forum.pine64.org/showthread.php?tid=20148 Thu, 01 Jan 2026 12:29:45 +0000 WhiteHexagon]]> https://forum.pine64.org/showthread.php?tid=20148 ]]> ]]> <![CDATA[beep - playing PCM samples on PinePhone?]]> https://forum.pine64.org/showthread.php?tid=20105 Thu, 04 Dec 2025 14:07:53 +0000 WhiteHexagon]]> https://forum.pine64.org/showthread.php?tid=20105

This is what I have so far:

LINEOUT to Speaker goes via component U800, audio amplifier, and link expired in the component list.  but seems to have an interesting connection to NAND. (PA-SHDN)

[edit: ignore this paragraph, I got AC_PR working!]    AC_PR Configuration Register mentioned (p362), but not sure of it's register address or usage, it mentions PRCM but doesnt explain how.  It seems I'll need this for access to : 0x05 LINEOUT Control Register, and maybe to un-mute the MIX channels.   [Edit: I found more information in the A80 manual Smile  it looks like R_PRCM is at 0x01F01400 in the A64,but still not clear where this AC+PR register is located.]

Looking at the data path diagram (page 280).  It looks like I should be able to send PCM over I2S, but sounds like there is a mode that reads direct from RAM?

As you can hear, I'm a bit lost down the rabbit hole at the moment!]]>

This is what I have so far:

LINEOUT to Speaker goes via component U800, audio amplifier, and link expired in the component list.  but seems to have an interesting connection to NAND. (PA-SHDN)

[edit: ignore this paragraph, I got AC_PR working!]    AC_PR Configuration Register mentioned (p362), but not sure of it's register address or usage, it mentions PRCM but doesnt explain how.  It seems I'll need this for access to : 0x05 LINEOUT Control Register, and maybe to un-mute the MIX channels.   [Edit: I found more information in the A80 manual Smile  it looks like R_PRCM is at 0x01F01400 in the A64,but still not clear where this AC+PR register is located.]

Looking at the data path diagram (page 280).  It looks like I should be able to send PCM over I2S, but sounds like there is a mode that reads direct from RAM?

As you can hear, I'm a bit lost down the rabbit hole at the moment!]]> <![CDATA[60fps display updates possible without GPU?]]> https://forum.pine64.org/showthread.php?tid=20101 Tue, 02 Dec 2025 20:56:39 +0000 WhiteHexagon]]> https://forum.pine64.org/showthread.php?tid=20101  

All good fun, but my 'clear screen' functionality is super slow.  I'm guessing at .25s, slow enough to see the progress.  This is using a framebuffer approach i.e. no GPU, and a memset to do the clear.  But I also tried a direct arm assembly loop, and looks the same.

I dont have enough experience with the PinePhone to know if this is to be expected? or an anomaly in my approach.  I was expecting to be able to easily do 60fps with plenty of spare cycles to run my apps.]]>  

All good fun, but my 'clear screen' functionality is super slow.  I'm guessing at .25s, slow enough to see the progress.  This is using a framebuffer approach i.e. no GPU, and a memset to do the clear.  But I also tried a direct arm assembly loop, and looks the same.

I dont have enough experience with the PinePhone to know if this is to be expected? or an anomaly in my approach.  I was expecting to be able to easily do 60fps with plenty of spare cycles to run my apps.]]> <![CDATA[PinePhone sensors - Gyroscope power]]> https://forum.pine64.org/showthread.php?tid=20092 Thu, 27 Nov 2025 21:28:55 +0000 WhiteHexagon]]> https://forum.pine64.org/showthread.php?tid=20092   Although the sensor seems to be always powered on, which kinda makes sense, but I somehow expected a GPIO pin for switching it off.  

Now I am looking at the gyroscope, wow it looks complicated Smile and I am kinda glad to see the secondary I2C fusion? lines are not connected.

But here again it seems to be always powered on? (based on schematic), and I recall from my early iOS days, that gyroscopes can waste some power when always on.  Did I miss something?]]>   Although the sensor seems to be always powered on, which kinda makes sense, but I somehow expected a GPIO pin for switching it off.  

Now I am looking at the gyroscope, wow it looks complicated Smile and I am kinda glad to see the secondary I2C fusion? lines are not connected.

But here again it seems to be always powered on? (based on schematic), and I recall from my early iOS days, that gyroscopes can waste some power when always on.  Did I miss something?]]> <![CDATA[what is the point?]]> https://forum.pine64.org/showthread.php?tid=20091 Thu, 27 Nov 2025 08:56:16 +0000 vanja]]> https://forum.pine64.org/showthread.php?tid=20091 I've come across several daily driver users who eventually state things like
Oh, I don't care about buggy wifi, slow X, crashing Y or unstable Z because I use it only for: calls, sms, contacts.
Oh, who cares about battery life, i keep it powered off most of the day etc..

my question is, what is the point of having a linux phone when use case is dumb phone features only? Why not just use some dumb nokia that runs for 7 days on a battery and call it a day? also same privacy level on those devices...

I think the cold truth is, because its too slow and unstable to do anything else then calls and sms with it, but then the loop goes back to the beginning, what is the point..]]> I've come across several daily driver users who eventually state things like
Oh, I don't care about buggy wifi, slow X, crashing Y or unstable Z because I use it only for: calls, sms, contacts.
Oh, who cares about battery life, i keep it powered off most of the day etc..

my question is, what is the point of having a linux phone when use case is dumb phone features only? Why not just use some dumb nokia that runs for 7 days on a battery and call it a day? also same privacy level on those devices...

I think the cold truth is, because its too slow and unstable to do anything else then calls and sms with it, but then the loop goes back to the beginning, what is the point..]]> <![CDATA[Light Sensor / Proximity Sensor on PinePhone?]]> https://forum.pine64.org/showthread.php?tid=20085 Tue, 18 Nov 2025 14:41:19 +0000 WhiteHexagon]]> https://forum.pine64.org/showthread.php?tid=20085   Can anyone confirm which chip I am trying to talk to on the PinePhone Beta v1.2b please?]]>   Can anyone confirm which chip I am trying to talk to on the PinePhone Beta v1.2b please?]]> <![CDATA[What is wrong with the Mobian signature key?]]> https://forum.pine64.org/showthread.php?tid=20070 Sat, 08 Nov 2025 11:13:40 +0000 Mahgue]]> https://forum.pine64.org/showthread.php?tid=20070 https://images.mobian.org/sunxi/ and failed to verify the signature.


Code:
LANGUAGE=en gpg --verify mobian-sunxi-plasma-mobile-13.0.sha256sums.sig mobian-sunxi-plasma-mobile-13.0.sha256sums
gpg: Signature made Mo 13 Okt 2025 10:55:36 CEST
gpg:                using RSA key 782C6C58B583FE966CEE44EBF8BDAB78BEE246C2
gpg:                issuer "admin+images@mobian.org"
gpg: Can't check signature: No public key
It seems to be signed with a key as mentioned in https://blog.mobian.org/posts/2025/10/ne...ting-keys/ but I can not get this key from any server.

https://wiki.debian.org/Mobian/Verify still mentions:

Code:
gpg --keyserver pgp.mit.edu ...
which seems to be down since 2023. But trying keyring.debian.org, keys.openpgp.org, keyserver.ubuntu.com, pool.sks-keyservers.net fails too.

Where do I get the key to verify the latest Mobian images for PinePhone (sunxi)?]]> https://images.mobian.org/sunxi/ and failed to verify the signature.


Code:
LANGUAGE=en gpg --verify mobian-sunxi-plasma-mobile-13.0.sha256sums.sig mobian-sunxi-plasma-mobile-13.0.sha256sums
gpg: Signature made Mo 13 Okt 2025 10:55:36 CEST
gpg:                using RSA key 782C6C58B583FE966CEE44EBF8BDAB78BEE246C2
gpg:                issuer "admin+images@mobian.org"
gpg: Can't check signature: No public key
It seems to be signed with a key as mentioned in https://blog.mobian.org/posts/2025/10/ne...ting-keys/ but I can not get this key from any server.

https://wiki.debian.org/Mobian/Verify still mentions:

Code:
gpg --keyserver pgp.mit.edu ...
which seems to be down since 2023. But trying keyring.debian.org, keys.openpgp.org, keyserver.ubuntu.com, pool.sks-keyservers.net fails too.

Where do I get the key to verify the latest Mobian images for PinePhone (sunxi)?]]> <![CDATA[compass pdf link expired: VTC AF8133J help]]> https://forum.pine64.org/showthread.php?tid=20069 Thu, 06 Nov 2025 20:15:03 +0000 WhiteHexagon]]> https://forum.pine64.org/showthread.php?tid=20069

But I dont have the I2C address, and the documentation linked from the component page on the wiki has expired.  Can anyone shed some light on this please.  A good start would be the I2C address, but a copy of the data sheet would be best please.  I am unable to decode linux source tree structure to find this.

Also, are the PinePhone sensors always powered, since DLD01 seems to be used everywhere.  For the LCD and touch I had to switch on some pio pins, but I dont see that on schematics, only EINT pins.  Iḿ worried about power usage from unused sensors.
I am used to following   amazing tutorials, but I think he focuses more on new devices and didnt cover the sensors Sad]]>

But I dont have the I2C address, and the documentation linked from the component page on the wiki has expired.  Can anyone shed some light on this please.  A good start would be the I2C address, but a copy of the data sheet would be best please.  I am unable to decode linux source tree structure to find this.

Also, are the PinePhone sensors always powered, since DLD01 seems to be used everywhere.  For the LCD and touch I had to switch on some pio pins, but I dont see that on schematics, only EINT pins.  Iḿ worried about power usage from unused sensors.
I am used to following   amazing tutorials, but I think he focuses more on new devices and didnt cover the sensors Sad]]> <![CDATA[Wake up Call]]> https://forum.pine64.org/showthread.php?tid=20061 Sun, 02 Nov 2025 18:37:29 +0000 walter1950]]> https://forum.pine64.org/showthread.php?tid=20061
https://medium.com/@mathias-steiner/mobi...9dd60aee42

Ciao
Walter]]>
https://medium.com/@mathias-steiner/mobi...9dd60aee42

Ciao
Walter]]> <![CDATA[Slashdot re:Cellbright (PP and PPpro are always resistant by design)]]> https://forum.pine64.org/showthread.php?tid=20059 Fri, 31 Oct 2025 10:15:43 +0000 biketool]]> https://forum.pine64.org/showthread.php?tid=20059 https://yro.slashdot.org/story/25/10/31/...ng-details

"Someone recently managed to get on a Microsoft Teams call with representatives from phone hacking company Cellebrite, and then leaked a screenshot of the company's capabilities against many Google Pixel phones,"

"The Support Matrix also shows Cellebrite's capabilities against Pixel devices running GrapheneOS, with some differences between phones running that operating system and stock Android. Cellebrite does support, for example, Pixel 9 devices BFU. Meanwhile the screenshot indicates Cellebrite cannot unlock Pixel 9 devices running GrapheneOS BFU."]]> https://yro.slashdot.org/story/25/10/31/...ng-details

"Someone recently managed to get on a Microsoft Teams call with representatives from phone hacking company Cellebrite, and then leaked a screenshot of the company's capabilities against many Google Pixel phones,"

"The Support Matrix also shows Cellebrite's capabilities against Pixel devices running GrapheneOS, with some differences between phones running that operating system and stock Android. Cellebrite does support, for example, Pixel 9 devices BFU. Meanwhile the screenshot indicates Cellebrite cannot unlock Pixel 9 devices running GrapheneOS BFU."]]>