keeping the pilotlight lit, normally when listening to an audiobook or music playlist the Pinephone locks it's screen after a minute and suspends the OS after a few more minutes as set by the user.
This suspend action makes it possible to carry a pinephone all day ready ro receive incoming telephone calls and still have battery if the phone is not used for more than 45min to an hour a day.
Every time the system suspends the audio stream is killed, even after wakeup most of the time the audio playback app needs to be killed and restarted for it to output audio.
I want a way to keep a tightly controlled and minimized audio app running while using minimal CPU waste power, and without the bloat of the system processes.
I only want the pilotlight lit, not the whole furnace.

I have several ideas that might be able to be implemented with only scripts, but I will need a LOT of help making this work if I run into bugs.
The idea works like this:
1- when an audio app is running we get the audio pause/skip controls on the lockscreen, there are already processes which load when audio is started
2- when audio mode is detected a special suspend mode is activated or enabled
   A- an exception is made to the suspend mode script, perhaps an alternate suspend mode
       a- the process running the audio is moved to one awake cpu core and the lowest voltage and mhz possible is engaged, only enough to allow for the audio stream to continue
       b- if possible audio is buffered into hardware audio acceleration chip and even the audio app CPU is suspended until 10-20 sec before the buffer runs out,
       c- buffer refills, suspend special audio process, repeating
    B- when system is taken out of suspend the audio app and special settings for single CPU are ended

An alternative would be to add an audio buffer playback system to the programs running on the modem module, perhaps a virtual serial audio device fed over the data connection line.  The modem module has its own Android based no-GUI OS, memory, and CPU, it is always awake and waiting for incoming calls and texts, which results in it sending a de-suspend command to the Pinephone, as running its own OS processes.

Currently unless there is USB power in the Pinephone pro can get at most around two hours of audio playback even though the the screen is dark and locked as all processes continue to run at full power.

Can anyone who has successfully built Megapixels in Mobian for the PPpro please post the contents of their /usr/share/megapixels/config/pine64/pinephone-pro.ini file?
Since this build of Mobian sid has libcamera I am guessing there is a good chance of megapixels working once I add this required file.
thanks!

Why is it Braxman is able to sell a similar, and better phone with a stable Linux and Android OS for only $300 at a profit, but Pine64 with their "but we're a non-profit!" cannot?


https://www.indiegogo.com/projects/brax3...artphone#/

Hello,

Currently in the process of installing a HES-sensor on my Pinecil (V2).

I am trying to find a good stand which incorporates magnet(s) required for the HES-sensor to work.

I've found this when searching online:
https://www.printables.com/model/770103-...ri?lang=de

Anyone else has any other suggestions?

Thanks!

With Mobian Sid we get a working libcamera so we can pipewire the sensors to the camera app.
Unlike Megapixels, which doesn't work yet on PPpro(some have succeeded in compiling in trixie), the system Camera app doesn't have a built-in QR reader.
It is a bit of a kludge but installing qtqr (it is a desktop package and needs scaling in Mobile Settings to work correctly, bring reading glasses)

Recently upgraded my PPP to Mobian Trixie, and it is a major improvement. However under Plasma-Mobile the task switcher just brings up a black screen. You can use it "blind" but I was curious if anyone on this forum has the same issue or knows what it could be.

I am going to file a bug report upstream with plasma-mobile.

Also wanted to report that KDE Plasma-Mobile is SUPER snappy and feels really good on the PPP. I have been daily driving it under `stable/bookworm` for the past few months, and moving to Trixie feels like I just bought a new phone

Keyboard issue
https://forum.armbian.com/topic/47099-ke...are-issue/

Is there any chance to check if the keyboard failure is hardware or software related?

The keyboard stopped working correctly when computer was in the drawer. There was no possibility for any physical damage to the keyboard.

Can I solve the issue by myself or do I need to buy the new keyboard or use my Pinebook pro as a coaster only.

Thanks.

*UPDATE*

On top of keyboard issue - I solved it by buying external usb keyboard.

*I cannot power up my trashy laptop i.e. PBP.*

1a. battery disconnected, I used bypass cables.

eMMC with Armbian

Hello all, 
I've been distro hopping on my ppp for a little while now. And I am trying to figure out which os I should settle down on, to use for a daily driver. So far everything I need to work has not all worked out of the box on any os, which is to be expected obviously. And based on other's experience I am fairly confident that I can get most, if not all, of the main things I want, to work. However, this will obviously take time and effort, and the question is 'which os do I focus on getting working?' So I thought I would ask the community for advice/personal experience. If ya'll could take the time to let me know: 1. if you daily drive a ppp, 2. what os you use, 3. what desktop interface you use, 4. what do you have working (eg camera, calls, sms...) and 5 maybe just some simple tips that might be helpfull. I would be extremely grateful.
The main things I would like to work (listed in order of priority) are: sms, calls, mms, gps, camera (to some extent at least), and usb-otg. I would definitely prefer plasma mobile above posh, but if I cannot get everything working on plasma then posh is the next best. 
Thank you in advance!

I got my PinePhone and I have been trying to call with people, but it seems like the earpiece is just too quiet and low quality because I cannot understand a lot of what the person at the other end says and also it sometimes sounds like those low bitrate chinese toy phones. I don't know if this is an issue with my distro or hardware but it is pretty annoying. I use ArchLinux with Phosh, I found the image from the official Pine64 software releases page.

In one of the recent Manjaro system updates TLP was mentioned as an option to power-profiles-daemon to manage battery life for the Pinebook Pro.

On the Pinebook Pro the TLP power management gives subjectively better battery performance over power-profiles-daemon. Especially sleep lasts over night without problems. My PBP is one of the earliest (second batch, I believe) and yet with TLP the battery performance is great.

The downside is that the PBP user interface feels slightly more sluggish in KDE Plasma. Everything seems to be a bit slower than it used to be. This might be different in a simpler (tiling) window manager. The TLP documentation mentions that their power management suits light users best (writing, etc).
However, the battery performance feels much improved.

If you are interested:

## Install TLP