We’re in the super-early stage of porting Apache NuttX Real-Time Operating System (RTOS) to the Star64 64-bit RISC-V SBC. (Based on StarFive JH7110 SoC)

In this article we’ll talk about the interesting things that we learnt about RISC-V and Star64 JH7110…

(1) What are RISC-V Privilege Levels
    (And why they make NuttX a little more complicated)

(2) What is NuttX Kernel Mode
    (And how it differs from Flat Mode)

(3) All about JH7110’s UART Registers
    (And how they are different from other 16550 UARTs)

(4) Why (naively) porting NuttX from QEMU to Star64 might become really challenging!
    (Thankfully we have the LiteX Arty-A7 and PolarFire Icicle ports)

https://lupyuen.codeberg.page/articles/privilege.html

So... is anyone selling a proper (fully compatible) serial console cable for the Pinebook pro ?

My impression from reading older threads is that 3.0V is ideal, 3.3V usually works, and 5.0V (which the Pine64 store was selling as PBP compatible) is unreliable.

Have any stores stepped up to sell proper cables for this?

Does everyone just have to solder their own cables together?

I want to experiment with alternative bootloaders and maybe firmwares, and it sounds like a serial console would be essential for when things inevitably go wrong.

I ran top to see what process are running on background and notice fwupd is contantly eating 25% of the cpu:
4136 1 root R 52056 2% 3 25% /usr/libexec/fwupd/fwupd

How to fix it? My phone running hotter than usual because of it.

$ sudo apk add powersupply
[sudo] password for user:
ERROR: unable to select packages:
powersupply (no such package):
required by: world[powersupply]

No, it doesn't exist yet. I'm just pitching an idea.

What if the Pinebook Pro was upgraded to 8 gigs of memory with an upgraded CPU. Maybe something like the Quartz64 spec.

And it was offered in a few colors, maybe adding white and grey to the current black.

Everything else could stay the same. I'm happy with the keyboard, trackpad, peripherals, and monitor.

And it cost maybe $350-$375.

I would buy it.

What other competition exists at that price that is ARM based?

I have no idea what is involved in making a laptop though, so maybe I'm way off base.

my pinephone can not send sms messages through spacebar but can recieve them and phone calls,
it's running Arch Linux and KDE mobile.

What do I do?
I tried out Ubuntu touch and could send messages with it's built in sms app,
the only problem with that linux disto is I couldn't install packages.

For whatever reason manjaro doesn't boot my on phone anymore just one day decided not to boot and instead get stuck in that annoying boot loop with the vibration going off every 8 seconds.

Hello there, newbie here!

I have the Pinephone in the 3 GB Version with the Keyboard case, using it as a PDA with Gnome 3 (NOT phosh) as the DE, modem disabled via hardware switch.
Software works great, Performance as expected and battery time in combination with the battery case no problem in active use. However, in suspend, the battery consumption stays unreasonably high, draining battery of phone and case in around 24 hours, thats more than 1 Watt in suspend to RAM.

I've tried around a lot by now, but I've hit a wall here and wanted to ask if there are similar problems and workarounds.

First, the suspend is triggered via systemd, so the /etc/systemd/sleep.conf is used. I've set the SuspendState to mem, drain remains high. The drain is even higher when set to standby or freeze, although not much. Gnome 3 uses systemd for this, I've tested it by setting hibernate settings into the suspendvariables with the expected outcome.

So forward to the logs. Journalctl says

Hello,
I have been using my pinephone for around 2,5 years now. Have tested mobian, arch, pmos and lineage. I like the mobian/debian culture and used it a lot for those reasons, arch is kind of my favorite because it's very snappy and the battery seems to last longer than mobian and pmos. Last week I gave a new try to pmos and looks amazing, I don't remember seing the ram usage and average load the other times I used pmos...it's so amazing, average load around 0.20 when idle...mobian always higher than 1.00, ram usage around 600mb, mobian and arch much more like 1,4GB on average....the only downpoint so far in my experience with pmos is the battery life, it seems to get warmer than arch. Mobian is good and stable(I was using trixie lately) but very hungry on resources and battery disaster.
What are you experiences and thoughts?

Hello all, I'm curious as to whether anyone has been able to use an optical drive such as a USB DVD drive with a Pinephone or Pinephone Pro?

My use case is - my preferred way to acquire music is to buy a CD. I would like to set up a Pinephone as a one-stop shop for listening and ripping CDs. I have been able to do this before with a Samsung Galaxy S20 5G under Android.

My Pinephone running Postmarket OS recognizes USBdevices and can also run with a Nexdock. It can read flash drives too. If I use an optical drive, including powered variants, it shows under lsusb but not fdisk -l.

Before I go down a complete rabbit hole trying to get this to work, I wanted to ask if anyone had used this setup with any success? Or if it works on a Pinephone Pro I can upgrade. I'm wondering if the hardware supports it but there's something missing at the Linux kernel level, or need certain drivers.

Happy to post logs etc. but mainly wondering if anyone else has made this setup work previously?

Hoping someone here can aggregate the info on the bes2600 wifi/bluetooth driver in development and offer a step by step set of instructions to at the very least, download the  from gitlab and get it compiled. Currently, as of kernel version 6.4.2 it does not build using 'make.'

There is some info about applying a patch, but the info is presented in such a way that the newbie (who just bought the device and wants to download a driver) could do it.

a note for the Devs: please provide setup and install info of the driver that is free from insider jargon and assumptions. Yes, I know it is a development release tablet, but that doesn't mean that everyone knows how to patch a file (what file?) to get a kernel module to build with make.