In this article we’ll boot a tiny bit of Apache NuttX RTOS on the Star64 64-bit RISC-V Single-Board Computer. (Based on StarFive JH7110 SoC)

(1) Migrate NuttX RTOS from QEMU Emulator to Star64
(2) Print to the Serial Console in RISC-V Assembly
(3) Trick U-Boot Bootloader into thinking we’re Linux
(4) Downgrade from Machine to Supervisor Privilege Level
(5) Helped by OpenSBI Supervisor Interface

Check out the article:

Apache NuttX RTOS on RISC-V: Star64 JH7110 SBC

Pipewire lets me use the new snapshot camera app. Yay! That's about where the fun ends.

For those considering a switch to pipewire, it looks like it gets a camera working, but neither of my smart speakers work even on the latest master of pipewire and they both worked fine with pulseaudio: https://gitlab.freedesktop.org/pipewire/...ssues/3340 , https://gitlab.freedesktop.org/pipewire/...ssues/3210

And unfortunately the call audio does seem very messed up on the latest master :/


The audio routing on this is a mess and it seems like pipewire doesn't like it. For example, it does not switch correctly to the earpiece when placing a call and there tends to be distortion that I did not have in pulse.

If I can't get that to work reliably I'll have to switch back and give up the convenient camera...

My solution for now is to place a call to 804-222-1111 each boot to initialize the call audio pipeline, toggle speakerphone a few times until the audio comes out of the earpiece (speakerphone is always horribly distorted). The first call will not switch to the earpiece and the audio will be bad. In the second call, the echo test will be horribly distorted. To make sure people can hear me, I need to call a third time to confirm that the audio comes out of the earpiece and I am audible from the echo test.

With pulseaudio, the call pipeline just worked most of the time, though barely. This seems to break it. And with pipewire and bluetooth headphones or an airplay device (even though those don't work, even if they're present in the graph), it will just never work.

I'm not sure if this is an issue with the UCM audio routing on the PPP or with pipewire and have no idea where to file it, but it's a huge usability problem!

Suggestions welcome. I am running Manjaro ARM with Phosh and the latest updates.

The title sounds negative but I say it with humor. Just to set my expectations, I'm currently using an F1 Orchid by Sunbeam Wireless. It's a flip phone and my phone before that was a iPhone 12 Mini. So I've already gone through the stage of losing essentially all smartphone functionality and on top of that, because the flip phone I use is from a niche manufacturer, I've even experienced the joys of carrier whitelists. So really, the only expectation I have is that the PPP function as a phone. I need it to be able to consistently receive calls and SMS/MMS whether suspended or not. Any particular US carrier recommended for best compatibility? Which OS/DE is most recommended currently for my purposes? I've looked at past threads but none seem current or answer the questions I have. My plan was to use pmOS with KDE as my ideal scenario but I could get used to GNOME or Phosh if needed. I plan on flashing the FOSS firmware for the modem as reports seem to indicate it improves the experience.

How is the software development progressing and where can I contribute monetarily? I looked at pmOS but they aren't interested in such donations.

the default sms app, ie chats v0.7.3, seems very limited, eg I can't forward an sms to my email. I searched for an alternative but nothing jumps out, in fact i can't even find any info at all about the chats app. Can someone recommend an alternative or otherwise explain how to get around such limitations. thanks

Iv'e had many problems with my pine tab 2 the latest I cannot get a handle on it will not boot any farther this is what I'm seeing
[    0.000000] clk: failed to reparent gpll to clk_rtc32k_frac: -22 
does anyone have any ideas? at this point it no longer powers up it is a hardware problem and pine64 keeps insisting its software .
july 13 2023

The staff from Pine partially managed to help me with troubleshooting but I went to a busy period and postponed fixing this problem. Here's how the problem evolved:


1. I just received my pine book pro and it just doesn't start up. I've searched YouTube for some troubleshooting and I think it's some switch I have to change at the RAM slot. I opened up the whole thing and made some photos if this could help you. How to solve this problem?

2. I readjusted my EMMC and switch in on position and now it starts so it's powered because the green light is on but unfortunately the screen remains black. What should I do?

Based on the answers I got from the Pinebook team I guess my eMMC is empty. Can I use some kind of app to install Manjaro directly on the flash memory or do I have to use a stick to boot from it. I'm a newbie so please tell me exactly what I have to do.

since last update or so, the screen is not so bright, but the brightness slider is locked to maximum. Gone are the days when screen would get dark after a restart. Now it is always maximum but this maximum is quite dim so I dnont like it much. Bug or feature?

Me and my wife bought Pine Time watches (the water proof ones) about half a year ago. We are both running InfiniTime 1.10. Her watch has more than a week of battery life while mine runs out after 4 hours. Disabling Bluetooth adds another hour.

What could be wrong with my watch? What can I do about it? Is it possible to send the watch back and get a replacement?

My pinephone64 no longer finds any wi-fi signals using Aarch or PostmarketOS. There are multiple signals found on my notebook. It's still under warranty. Where do I go to start the repair process?

Upon arrival my pine tab 2 didn't boot.  So I flashed a SD card and tried booting via the UART adapter. I get the following message when using screen:

mmc1: error -110 whilst initializing mmc card

I've used probably 4 different SD cards. 

The screen comes on but nothing displays. Any help would be appreciated. Thanks!