Flashing rk2aw to the PinePhonePro

#https://xff.cz/kernels/

Updating to Biktorgj from 0.7.2 to 0.8.0

#https://themodemdistro.com/docs
#https://github.com/the-modem-distro/pinephone_modem_sdk/releases/tag/0.8.0

START EDIT: 
Clean up and adding Mobian steps.
OS: DanctNIX Arch with Phosh fully updated
OS: Mobian fully updated
EG25 Firmware: Biktorgj 0.8.0
ADSP Version: 01.003

This uses PipeWire, Not PulsaAudio

DanctNIX Arch with Phosh
pipewire-alsa is required to get call audio.

I'm trying to reinstall some stuff after distro hopping and when I try to install firefox, I get the following error.

Hello, i'm searching for a Way to connect my 3 Pin Fan to the Euler Pins or other.

The PI2 Pins are not useable. 

Greetings

Breacher

The biggest block to daily driving both the Pinephone and Pinephone pro is battery life.  I am not an expert but it appears to me that except for Clapper video app few if any parts of the UI or web browser take proper advantage of the GPU and therefore have to force the graphics through the CPU which is a large part of the total unusual electricity budget of the pinephone family devices.
On the Nokia N900, which was sold loaded with Maemo5 Linux, the GPU was accessed via a hardware abstraction layer(HAL) every time openGL was called, individual apps did not have to be optimized, the major exception were graphic intensive games including the rich(for the time) library imported from Palm/WebOS which was possible because the last gen of Palm devices used the same kernel and GPU as the N900/Maemo5 so were very specifically targeted directly to the GPU silicon for best performance.
The N900 was average battery life for an early(2009) smartphone we could do several hours of GPS guided navigation, web surfing, or playing graphic intensive games like tuxcart, N64 games via muppen64, or X-Plane imported from WebOS games. I do not remember watching the battery % drop at least 5% for every unluck and 1-2% per minute of unlocked screen eve though the N900 had a 1200mA/H vs the  PP/PPP with a 3000mA/H battery.

Hi,

We recently purchased the tablet. It was working fine, but now isn't turning on at all...

Need technical support please...

Hey everyone,

Im looking for some advice on which Pine64 board would be best for my latest project. I am planning to build a small home automation system that integrates with sensors (temperature, humidity, motion, etc.) and controls some basic devices around the house (lights, fans, etc.).

I've been looking at the different Pine64 boards available, but I am not entirely sure which one would be the best fit for this project. I need something that’s fairly easy to set up, has good GPIO options, and can handle running multiple sensors and devices at the same time without any performance issues.

And for the same I have been through these articles/resources https://forum.pine64.org/showthread.php?tid=18116 Generative AI Tutorial that are quite informative. But I’d love to hear more from the community member.

Also, I’d appreciate any tips on getting started with the software side. I am thinking about using Home Assistant, but I’m open to suggestions if there’s a better option.

Thanks in advance for any recommendations or experiences you can share.

Best Regards

(The fix for disfunctional but flashable after firmware load in newer EC25 modems PPP and maybe newer PPs is described here https://themodemdistro.com/efs_recovery )

The process for installing the firmware on my old pinephone was pretty easy; download, unzip, and run flashall then follow instructions to flash the NON-HLOS.ubi 
https://github.com/the-modem-distro/pine...LASHING.md
I never encountered any problems.

I got a replacement upgrading to PPpro; mostly the same modem (uses nano vs micro-SIM); the behavior after flashing is very different.  
After running flashall utility and the NON-HLOS.ubi(ADSP) successfully the modem reboots but has the slash through the signal-bars symbol and no longer works for telephony and GPS though shows as a quectel modem on lsusb.  I managed to spend a few evening hours a few weeks ago flashing between the upgraded firmware and the stock quectel_eg25_recovery and firehose flashing utility, and every ADSP found on the git; I gave up and let the PPpro sit until the next day with the battery out.  For no reason I know of the modem was working at bootup of the PPpro where it had not the night before.

After having modem audio problems likely related to Mobian unstable updates I tried flashing the modem to a different more stable ADSP thinking it was the full shutdown vs hot-rebooting(no full shutdown/power-down for modem) that was my previous problem.  

As I am sure others have experienced this problem.
What is the best way to debug a 'stuck' modem that does partly boot, can be flashed, but will not connect to the network or give a GPS ttyusb interface beyond trying flashing the stock firmware?  Once fixed I will try to document it as best I can for the wiki.

I have an account which I registered using protonmail(biketool), unfortunately the code to recover my account doesn't arrive in my inbox nor spam folder.
I registered this account(biketool2) and the confirmation dlso did NOT arrive in my protonmail inbox/spam.
I suppose I could register a third account but my first account biketool has maybe seven years history.