What is the state of the keyboard and its power management/capacity reporting for you guys?

On my original PinePhone everything works fine, it reports the capacity, the buttons work (short press, double press and long press) but on the PinePhone Pro it's a completely different story. The power button powers the phone and then it's all downhill from there. It does not report the battery capacity at all, the power button works when it feels like it (having to long press multiple times to try and stop it from charging the phone so I can turn it off). I should mention that typing on it works flawlessly.

Is anyone else having these issues?

debian bullseye
setup: 32Gb SD-Card for the debian-installer
32 GB emmc for the OS

tried the official debian iso via usb-stick. The problem is known since 2020. The iso wants to boot with grub and this - of course - fails due to EFI.
OK did the debian-installer on SD-Card and installed on emmc.

Result: rockpro is not booting any more and the white led is flashing.
Recloned the debian-installer on the sd-card again ... same result
removed the emmc - same result
inserted the previously working armbian emmc - same result.

I am confused!
Futhermore, the rockpro64 wiki did not feed me with informations about the default LED-Status.

Thanks for input...

I still have 2 kickstarter pine64 (2Gbg) boards.
One one of them I have mounted a small self adhesive cooling block on the processor.

Is it possible to connect a salvaged ventilator to the board ?
It has 4 wires, but 5 pins to connect to:
Image: https://imgur.com/k2lOsQx

Ventilator model: nidec Ta225DCM

Hi, does anyone know how to change the functionality of button presses on standard 3.5mm jack devices?

I have some headphones with a volume up/down and play/pause buttons that all work as expected. What I want to do is to copy the behavior on android of enabling a double or triple press of the play/pause button to skip forward or back in what I'm listening to. This alone would turn it into a real daily driver for me

Hello!  

What is the best configuration for Mint for the APN/MMS settings?  I haven't had much luck as of yet. 

Also, 

Is MMS integrated in bookworm or must it be installed?

Hello.

Do you sell a ready-made housing for the PineCube camera?
If yes, where can you buy it?
Thanks.

Hello.
Is it possible to view examples of video surveillance recordings through the PineCube camera?
Day, night (with IR illumination)?
Thanks.

Hello.
What is the operating temperature of the PineCube?
Can PineCube be used between -30 and +30 degrees Celsius?

Is there a straightforward solution to read and write files on a PinePhone from a PC? In Windows 10 it is so easy to have a network shared folder. I am ready to change to a Ubuntu PC for this purpose. From a PC (Ubuntu/Windows), can I read and write to a PinePhone shared folder according to this instruction:

https://www.youtube.com/watch?v=X-PSSd-U610

Hi,

I've spent more than two months(!) trying to find out what causes Linux Kernel OOPs that seem to be triggered by big writes to mounted ext4 filesystems. My quest began while trying to boot from SPI and run Armbian with rootfs on eMMC. I tried two different eMMC modules and all the Rockpro64 Linux images that I could find. I burnt a lot of midnight oil trawling the Internet for solutions, but found none...

Most of the Linuix images that I've tried work fine booting from SPI using the latest u-boot running Linux (Armbian, Debian, Ayufan) with rootfs on SD, but crash badly when either installing them to eMMC from SD or running them from eMMC and e.g. installing a big package like OMV.

Watching "htop" during installation of a 'large' package, I can see that the OOPs seem to occur when the filesystem buffers hit a high-water mark and this could be mitigated by mounting ext4 filesystems in 'sync' mode. I've done a lot of testing and now I have a stable OMV6 running under an Armbian image I compiled myself from source, and ext4 filesystems mounted in 'sync' mode: I only have occasional OOPs during heavy i/o to an ext4 filesystem mounted on an "md" raid consisting of two 1TB SATA disks connected to a 2-port Adaptec PCI-e controller.

Using 'sync' mode degrades performance, and could wear out SSD's, so it's only useful as a temporary work-around. The real problem is how to prevent the ext4 FS buffers from overflowing available memory. I suspect, but have no proof, that this is caused by the Linux 'optimistic' memory allocator oversubscribing memory and getting caught-out by the actual usage overflowing available physically memory.

I don't have a deep enough knowledge of the Linux kernel to investigate the problem, but maybe someone else reading this message does, but what I do know, is that the problem is NOT a device driver issue, because direct device access (e.g. using "dd") does not trigger an OOPs. This is not a hardware fault on my particular Rockpro64 board or eMMC module because FreeBSD installs and runs fine on SD or eMMC on the same system.

I'd be interested to read other people's experiences of using the Rockpro64 with OMV6 under Armbian.

Bye,

  Tony Travis.

Attached Files

Thumbnail(s)