If I have the front camera disabled then Megapixels wont start. Is there any workaround for this?

Back when I was running Manjaro ARM w/ Phosh Beta 4 or 5, I first experienced a problem whereby my screen would lock, and I would find myself in an infinite loop of entering passcode, and returning to the lock-screen.

I recently did a complete reinstall of the OS to Beta 11. After a week or so, the problem of screen-locking seems to be back, but intermittently.

Has anyone else experienced this problem? What might be causing it? And if it's a known bug, is somebody working on it?

once more my pinephone had come to that sweet spot where after a recent update the battery consumption improved noticeably. The cellular modem (and therefore mobile data still dropped off and disappeared from time to time)  Alas, after june 30th upgrade (uname -a tells me it's the May 31, 2021's 5.10 kernel), my trusted and essential usb tethering stopped working. I get that perhaps not many people need this option, but at this moment in time i urgently need that function to be solid. i don't need encryption. (Last time i had this issue after upgrading to 5.11 kernel.. and i had to reinstall.)Can someone walk me through how to back track without re-installing? Thank you!

I've read a bit about Pinephone's challenges in getting the device all open-source hardware ...

https://www.pine64.org/2020/01/24/settin...nceptions/
https://forum.pine64.org/showthread.php?tid=12105
https://deninet.com/blog/2020/02/16/pine...smartphone

... What threats do these weaknesses facilitate? I have read the IME problem on most computers even allow remote hacking, as well as who knows what data theft to the (small) memory. Do the Pinephone closedsource parts allow similar types of distant threats (people can hack it over the internet)? Do they allow a way to open or access files bypassing the OSs fulldisk encryption? Or can they be exploited in some other ways?

(full support to PinePhone's workers and hope they continue on their worthy path)

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.