I'm experimenting with GPIO interrupts on my RockPro64. I used the "Watching buttons" example from here: https://www.npmjs.com/package/epoll, but I changed the pin number to 156 (GPIO4_D4, pin 31 on the header).

The hardware is as follows: there's a mechanical switch between the supply (a buck converter with 3V output) and GPIO4_D4 and a 10k pull-down resistor between GPIO4_D4 and ground.

My issue is that when the button is released, the script just constantly spits out "released" (falling edge) events as fast as it can. When I close the switch, I get a couple of rising edge events, then a few falling edge events and then again a few rising edges. Then rising edge events pop up occasionally while the switch is still closed. I also found out that if I connect GPIO4_D4 directly to ground (with the switch open), the falling edge interrupts aren't emitted as frequently.

I'm aware of the fact that mechanical switches have contact bouncing, but is it normal that the events are repeated several times? Has anyone made a working hardware and software setup to detect interrupts with RockPro64? I would appreciate if you share your experiences Thanks!

Hi all.
I'v made a review video about the PineBook Pro.



I'm very happy with the PBP. Perfect device for me.

Here all the info I gathered. Greetings, NicoD

Haven't had a shipment notification I paid for courier delivery to the UK when will my order be sent and will I get notification it's on its way?

So we have two pinephones, same version, one works with our cell service provider without too many complications, and the other one will not work No matter what we do. Thoughts? We got mine running on Arch with Puretalk. We may try his at some point in another provider. But it is just so odd that his Will not work with Arch/Puretalk and mine does.......

Thanks in advance.

Hi,

Does anyone know when replacement board for pinebook pro will be avaliable in the store?

Maybe someone has one and can sell it ?

Hey everyone! Wasn't sure if anyone had encountered this issue. Spent some time searching the forums for issues powering on their device and incurred endless threads of battery performance issues instead.

I just received my new PinePhone Convergence model. I plugged it in to charge it and let it sit. When I plugged it in, the LED turned red, then yellow, and eventually the screen blinked on and off and the device seemed to power down again. I figured it needed time to charge and let it sit for an hour.

Unfortunately it's still happening exactly the same. The boot loop has stopped but the same sequence occurs after holding the Power button.

My PinePhone doesn't get to a boot screen even and it's been charging for over an hour now- It's like DOA but was wondering what kind of help I might find here.

plasma development branch. After flashing the most recent image 2 days ago, the phone will no longer make or receive calls or send SMS. It's odd, because prior to that, it was working more or less normally (except for the usual intermittent lose-the-modem flakiness). Although the indicator shows bars and says I am connected to the cellular network, it remains inaccessible. Updated as of 10 minutes ago, same problem. Rebooting does not help.

I've tried restarting ofonoctl, with no change in behavior. Any suggestions that could work me out of this?

Thanks.

Hi, I looked everywhere, but it seems that the SIM pin could not be changed in plasma-mobile itself?

Codes like **4* ............. in the dialer have also no function and threw errors only

Hi,


I have Pinebook Pro connected to LG 27UD88-W monitor via USB-C to DisplayPort cable. I'm running Manjaro ARM 21.06 (Linux kernel 5.12) with Sway WM. The problem is that I can't run 4K @ 30Hz properly (right 1/3 of the screen is distorted). FullHD (1920 x 1080) and WQHD (2560 x 1440) works just fine. I have also tested X11 based Linux distros and the issue is the same. Anybody had luck to run 4K @ 30Hz video output on the external monitor?





This is the similiar thread, but it is closed.




I will be more than happy to provide more details if necessary.

Hi,

on my PP with arch/plasma-mobile after a reboot the systems give me a notification that due of an update a restart is required.

Have done all updates in the shell and Discover. Of course rebooted several times. But the notification pups up after every new boot.

Any hints for me?