One year ago we started porting Apache NuttX RTOS (Real-Time Operating System) to PinePhone. Let’s look back and talk about…

1. The Features that we’ve implemented
2. Our Plans for the future
3. Why we might move to a RISC-V Tablet!

Check out the article here...

NuttX RTOS for PinePhone: The First Year

Adding  U_BOOT_PARAMETERS="ipv6.disable=1"   to /etc/default/u-boot        and run  u-boot-update use to work before tow boot.   What is the new methodology to pass  ipv6.disable=1 to kernel ?

Running Manjaro Phosh Beta ver 33 on PP Beta, I'd like to install and switch to an xfce desktop. Would that be a simple pacman install of all things xfce, or would I need to find a non-Phosh OS and start from there?

Thanks.

The Phosh Web app has a memory leak when playing YouTube video, bogging down functionality after a while. Closing the app is necessary to recover usability of Phosh. But the Angelfish app on Plasma no longer has this problem.

The Megapixel app has lost its auto exposure ability. It is now necessary to adjust exposure using the shutter speed or iso controls.

My modifications to the Megapixel configuration files, published here before, are still needed.

Today is Monday, June 19, 2023. It has been a while, but the update on the unstable branch of Manjaro Plasma is not usable today. Some sort of restart of the Plasma service is needed after recovery from the session locking malfunction.

I would like to increase the volume (over 20 dB louder) when I receive a text message, but leave the phone notifcation
volume alone.  I do not see how I can do this in the setting (if possible, I must be blind - please tell me how).

So now, I want to increase the ringtones for message notification.  Where is it?

I already noticed

/usr/share/sounds/gnome/default/alerts/click.ogg
/usr/share/sounds/gnome/default/alerts/string.ogg
/usr/share/sounds/gnome/default/alerts/swing.ogg
/usr/share/sounds/gnome/default/alerts/hum.ogg

and increased the volume.  But these files do not get used for text notification (if they can, I must be blind - please
tell me how).  Instead I hear a  soft buzz whenever I receive a text.  Where is it?  I already searched for all the wav,
mp3, ogg, au, and raw files.

Fyi, I have the 32GB community edition Pinephone which was recently discontinued.  And postmarketOS v22.12 (haven't
update to newer version yet).

Thank in advanced for any help/tip.

Sheng-Chieh

I've noticed and been trying to debug an issue with the pinephone(pro)'s modem not reading sim cards properly, and I think I know what is happening, but not how to fix it, at all.

Disclaimer: I know jack-shit abt cellular modems and sim cards, so this is just a hypothesis from trial and error of swapping the sim card around.



The Issue:

A sim card that once worked perfectly can no longer make or receive calls in the Pinephone Pro on Mobian.



What I think is Happening:

When you get a nice shiny new pre-paid sim card and put it into your phone, it gets a tiny amount of info written to it, like the network provider, the phone's IMEI, etc.
I swapped the sim to my iphone once for a bit, which worked fine for everything from calls to texting and interwebs.
I than swapped the sim back to the Pinephone Pro, and I believe that the sim now has a new set of information on it that the Pinephone Pro's Modem doesn't fully undertsand.
The Pinephone's Modem now believes that the Mint Mobile sim card is in fact a T-Mobile sim card, and refuses to let me tell it otherwise and set the network to Mint.
It randomly alternates from displaying the network as 'T-Mobile' and 'Cellular' now.



Potential solutions(?):

Force the modem to wipe and re-write the sim card with fresh information every time it is re-inserted into the phone?
Is anyone else experiencing a similar bug?
Have you figured out a solution?

The pinetab2 is set to stop you from logging in for 10 minutes if you mess up your password 3 times in a row.  Here is how to turn this off.

There is a file called  /run/faillock/<your login name>.  It is an empty file. Its presence causes this behaviour. You can  delete the file (use sudo) and that stops the 10 minute lockout.  No reboot needed.

FYI:  According to this page KDE Bugs Org this error you get when opening Discover is fixed in KDE Plasma Version 5.27.6.  My Pinetab2 is currently on 5.27.5.  Looking forward to 5.27.6