When I receive and answer a call, the audio switches to the earpiece. When I hangup the call, the audio won't switch back to speaker. I can't even switch it back using the settings. The only solution is to restart the phone.

Is this a known issue? If not, where would I even report it?

Hi

sorry, just copied and modified the thread title.

How can I tell what the hardware version/revision of a rock64 is?

Running Linux. The Wiki has nothing, /proc has nothing, and even dmesg has nothing whatsoever.

Maybe if any hardware differences were known, the dmesg output could point to what hardware version/revision it is.

v1 vs v2 vs v3, or rev2, or rev3?

thanks

I booted up my beta edition pinephone this morning, and everything on screen is half the size it was yesterday. Icons are tiny, text is tiny, everything is hard to see.  

I restarted it, this time without having the docking bar plugged in, and everything was back to normal size.  It looks like booting with the docking bar plugged in is what caused that?  

Does anyone know what happened, and how to do/undo that without rebooting? I looked in the settings, but can't yet find anything that applies.

Hello,

So i've dusted of my old pinetime dev kit. Beforte the infinitime 0.7 firmware. Just the closed source firmware.

Here is my plan. Will it work or will it brick?

-> Flash new bootloader with BLE with the DaFlasher App
Like described on the WaspOS tutorial*:
1) flash 'hacked'
2) flash 'dafit..'
3) and then?

The documantation says flash 'bootloader-daflasher.zip'. But i can't find that file anywhere.
I think that, finishing stages 1 and 2 will give me a 'unlocked' pinetime. And i can flash the waspos 4.1 firmware. 
? Is this correct?

Or can i then follow the infinitime instructions**
1) flash inifitime 1.x
2) flash bootloader
3) flash recovery

I expect that i have to flash a wasp/infinitime bootloader first. That 'bootloader-daflasher' that seems missing..

Help appreciated!

*Installation Guide — WASP-OS documentation
**InfiniTime/gettingStarted-1.0.md at 1.2.0 · JF002/InfiniTime · GitHub

Just installed the edge build here - edge/pine64-pinephone/phosh/20210630-0055 - postmarketOS // Official Images - and I can't find out what the default pin is!

Why release this and give nobody the default pin!? And don't tell me it's in there because I've already tried it!

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!