Updated on 14.10.2023

Short background so you can understands the starting points
I prefer myself as a skilled end user of mobile linux - so I am not developer (what ever that means in 2023) but I understand little bit about something.
I have been daily driving* mobile linux for many years. I have been also using linux as desktop machines as long as I remember.
*Really daily driving so if you have never used mobile linux before please note that your experience might be very much different than mine

This review talks
Mostly about Phosh because it is currently the most stable and easiest DE to operate out of the box. Some things are similar with other DE's but I have not tried them so intense.
Mostly about PPP as a phone - because after all it is Pinephone Pro .

Let's start with what I think is the last thing that gets in the way of daily driving PPP:
There are some callaudio issues which are not solved yet and for me it is show stopper. Reported issues:
https://gitlab.com/postmarketOS/pmaports/-/issues/2016
https://gitlab.com/pine64-org/pine64-als...-/issues/5
https://gitlab.com/pine64-org/pine64-als...requests/9
+
if you turn wifi/bluetooth killswitch off (as in you kill wifi/bluetooth) callaudio will suspend in seconds and makes calling impossible. Megi has all ready fixed this but the fix is not yet landed to distros.

How to achieve stable phone state? (excluding callaudio)
I never get any phone calls trough to suspended PPP if I was not using Biktorgjs firmware and all recommended settings - I really love it but because carriers work so differently it is hard to recommend it without any conditions. For me PP or PPP would not be a reliable phone without Biktorgjs awesome work.
https://github.com/the-modem-distro/pinephone_modem_sdk
postmarketOS and danct arch where the two distros where all phone functions did work. With all others I did face some issues.
To have more working callaudio I suggest to use pulseaudio instead of pipewire-pulse and wireplumber (in my testing wireplumber will cause lot of failures when routing callaudio and that combined with the above issues is pain) - this has downside for camera usage but which one do you want to choose?
Also to use PPP as a phone you sure want to make sure you have battery when you need it - so key is to suspend as fast as possible and as much as possible.

I daily drived Pinephone Pro for a few weeks - how did it go?
I charge my PPP as full as it gets in the evening. Then it rests next to me until morning (on suspend without charger) and wakes me up - I do have backup alarm clock because Pinephone did freeze few times but I have not seen it with PPP. (With pmos alarm clock works out of the box)
After 8-10 hours of suspend my PPP has something like 80% battery.
I go to work and I use PPP as my work phone - I answer calls and send messages trough it.
After week of intense daily driving I have 0 failed calls and 0 failed sms/mms (I monitor them trough my carrier platform).
I have also dock and display so I can plug PPP to dock and use it as a computer - and it just works!
For me biggest difference to PP is that "convergence connection to external display" is stable as f*ck - PP was more proof of concept and really terrible to use (at least it feels like this after I have used PPP).
When my PPP is in dock it will at the same time be in charger - don't use dock with external display without charger because your battery will die like in 15-30 minutes.
I am usually at work for like 10 hours and when I get home in the evening I still have 30-50% battery.
If I have been using dock it will have charged the phone - yes. But if I have not used the dock my phone have been suspended most of the time and the battery is about in the same level.

What I am really happy about?
Finally I have true convergence linux phone which I can reliable use as a phone also.
Pinephone Pro is as fast as phone needs to be -> yes I would love to have even faster phone but this is enough so I can show it to my friend and say test it and he/she might even like it.

What are the cons?
Pinephone Pro is not device where you watch Youtube videos or play mobile games - it will drain your battery.
You can't do any intensive stuff when docked because phone gets really hot - but hey it's phone not super pc.

What does not work (or works only as proof of concept)
Mostly familiar things from OG PP:
camera (but I think in a "near future" libcamera will bring lot lot of evolve to this)
speaker on calls (see the issue links above)
internet notifications when suspended

For who I recommend PPP?
You can live without constant phone browsing when you are on the road
In your regular day you have opportunity to charge phone in cycles of 10 hours
You don't need internet (email etc.) notifications asap
You have linux end user knowledge or the desire to learn for yourself
You don't except that everything works out of the box (because it does not you have to settle for compromises in many things)

Hi all,

I'm analyzing boot log from journalctl.

I have found regulator error. Is it possible to fix it ?

Hi there!

Just tinkering with the Ox64, I see there is not much of noise here about it. Might a sub heat it a little?

Also, while linux drivers for it are released, any guidance on how to use the gpio commands?


Regards

I removed Pulseaudio and set Pipewire. Sounds work well but the phone
Receive well but with my voice to the other telephone sends a strong noise
Can this be corrected and how?. It is curious that when purge Pulseaudio
automatically loads pipewire. The gnome-sound-recorder is also caput(spoiled)

Hello all,

I recently noticed that the green light on the back of my pinetime is stuck on, and seems to be draining the battery much quicker than normal.  Is there something I can do to fix this, or could it be some sort of hardware problem?  I tried holding the button to restart it, then starting and stopping the heart rate monitoring (although it never got a fix on my heart rate for some reason in the few minutes I tried it), and then reflashing the most recent version of infinitime.  None of those attempts fixed it.

Thanks in advance.

Hello!

A couple of days ago I wanted to try Postmarket OS again with my PP Pro, which I'm not using regularily. I flashed the latest image on the Sd card.

Since then I wasn't able to boot the phone again, no LED blinking, no vibration, nothing. First I thought I might have drained the battery.

So I tried the procedure mentioned here: https://wiki.pine64.org/wiki/PinePhone_P...ly_drained and charged the phone the whole night. Without success. 
It's not the battery as the battery works in my Pinephone.

What I already know:
- The image on the SD Card is fine
- The battery is working and charged
- none of the helpful procedure are working (i.e. holding volume up while powering the phone or try to bypass the emmc while booting up)
- there is the pre-installed image on the emmc (which isn't booting either)

What is strange:
As soon as I plug in the phone on my computer, it is shown in "mask rom mode" ("ID 2207:330c Fuzhou Rockchip Electronics Company RK3399 in Mask ROM mode") which shouldn't be the case if I'm not following the explicit procedure, right?

Anyone any idea?

Additional Information:
- Unfortunately I'm not sure which Bootloader is installed on the device. I ordered my PP Pro in March '22, but I believe I installed a different bootloader...
- I created the postmarket os image with pmbootstrap, using my laptop with fedora workstation. The image was written on the sd card with dd

Last week we ran Apache NuttX Real-Time Operating System (RTOS) on Unicorn Emulator, and we hit a baffling Arm64 Exception in the emulator. In this article we’ll create some tools to troubleshoot the exception…

1.  Render the Dynamic Call Graph for Apache NuttX RTOS, to understand how it boots

2.  Make it Clickable, so we can browse the NuttX Source Code as we explore the Call Graph

3.  We’ll use a Block Execution Hook in Unicorn Emulator to generate the Call Graph with Rust

4.  And call the Rust Libraries addr2line and gimli to map the Code Addresses to NuttX Kernel Functions

5.  Thanks to the (Clickable) Call Graph, we’ll describe the complete Boot Sequence of NuttX RTOS on PinePhone

6.  And explain how we might do Automated Daily Build and Test for NuttX on PinePhone

(Clickable) Call Graph for Apache NuttX Real-Time Operating System

I would like to reinstall arch with fde via the installer, but it seems to not be working anymore. Is there a fix or a way to do it?

I installed a sloppy porting version, but it is very beautiful. It comes from: [b]https://cloud.189.cn/t/u6BrQbZVnuum[/b]  （Access code  5feb）
I would like to make a DEEPIN OS image based on this, but I will not transplant it,
I hope people with this technology can complete this mission.

Every time my Rock64 boots, I get an error about the Superblock last mount time is in the future. As I don't have a working hardware clock, this happens on every boot, force an fsck and adding to the boot time. When searching for this error, most of the recommendations are to fix the clock, but that isn't really feasible on a device that doesn't have one. Seeing as this check happens before mounting the filesystem, a solution like fake-hwclock isn't likely to be useful either. I can't be the only one with this problem...