Hi all,

I'm analyzing boot log from journalctl.

I have found regulator error. Is it possible to fix it ?

Hi there!

Just tinkering with the Ox64, I see there is not much of noise here about it. Might a sub heat it a little?

Also, while linux drivers for it are released, any guidance on how to use the gpio commands?


Regards

I removed Pulseaudio and set Pipewire. Sounds work well but the phone
Receive well but with my voice to the other telephone sends a strong noise
Can this be corrected and how?. It is curious that when purge Pulseaudio
automatically loads pipewire. The gnome-sound-recorder is also caput(spoiled)

Hello all,

I recently noticed that the green light on the back of my pinetime is stuck on, and seems to be draining the battery much quicker than normal.  Is there something I can do to fix this, or could it be some sort of hardware problem?  I tried holding the button to restart it, then starting and stopping the heart rate monitoring (although it never got a fix on my heart rate for some reason in the few minutes I tried it), and then reflashing the most recent version of infinitime.  None of those attempts fixed it.

Thanks in advance.

Hello!

A couple of days ago I wanted to try Postmarket OS again with my PP Pro, which I'm not using regularily. I flashed the latest image on the Sd card.

Since then I wasn't able to boot the phone again, no LED blinking, no vibration, nothing. First I thought I might have drained the battery.

So I tried the procedure mentioned here: https://wiki.pine64.org/wiki/PinePhone_P...ly_drained and charged the phone the whole night. Without success. 
It's not the battery as the battery works in my Pinephone.

What I already know:
- The image on the SD Card is fine
- The battery is working and charged
- none of the helpful procedure are working (i.e. holding volume up while powering the phone or try to bypass the emmc while booting up)
- there is the pre-installed image on the emmc (which isn't booting either)

What is strange:
As soon as I plug in the phone on my computer, it is shown in "mask rom mode" ("ID 2207:330c Fuzhou Rockchip Electronics Company RK3399 in Mask ROM mode") which shouldn't be the case if I'm not following the explicit procedure, right?

Anyone any idea?

Additional Information:
- Unfortunately I'm not sure which Bootloader is installed on the device. I ordered my PP Pro in March '22, but I believe I installed a different bootloader...
- I created the postmarket os image with pmbootstrap, using my laptop with fedora workstation. The image was written on the sd card with dd

Last week we ran Apache NuttX Real-Time Operating System (RTOS) on Unicorn Emulator, and we hit a baffling Arm64 Exception in the emulator. In this article we’ll create some tools to troubleshoot the exception…

1.  Render the Dynamic Call Graph for Apache NuttX RTOS, to understand how it boots

2.  Make it Clickable, so we can browse the NuttX Source Code as we explore the Call Graph

3.  We’ll use a Block Execution Hook in Unicorn Emulator to generate the Call Graph with Rust

4.  And call the Rust Libraries addr2line and gimli to map the Code Addresses to NuttX Kernel Functions

5.  Thanks to the (Clickable) Call Graph, we’ll describe the complete Boot Sequence of NuttX RTOS on PinePhone

6.  And explain how we might do Automated Daily Build and Test for NuttX on PinePhone

(Clickable) Call Graph for Apache NuttX Real-Time Operating System

I would like to reinstall arch with fde via the installer, but it seems to not be working anymore. Is there a fix or a way to do it?

I installed a sloppy porting version, but it is very beautiful. It comes from: [b]https://cloud.189.cn/t/u6BrQbZVnuum[/b]  （Access code  5feb）
I would like to make a DEEPIN OS image based on this, but I will not transplant it,
I hope people with this technology can complete this mission.

Every time my Rock64 boots, I get an error about the Superblock last mount time is in the future. As I don't have a working hardware clock, this happens on every boot, force an fsck and adding to the boot time. When searching for this error, most of the recommendations are to fix the clock, but that isn't really feasible on a device that doesn't have one. Seeing as this check happens before mounting the filesystem, a solution like fake-hwclock isn't likely to be useful either. I can't be the only one with this problem...

Hi all,

For pinebud users out there, how is the voice quality when making calls with these? Is the open firmware any better than the default one that ships in this regard?

Thanks!