I think TELEports is very decent.

@nogoogle There is an odd issue with the PP not sure of PPP where if the device has a sim pin when you set up the phone it causes issues. If the sim has no pin all works fine. I found this out by trying each way. You might find out more by going to the Pine 64 group on Telegram https://t.me/utonpine Another similat issue is that the APN settings "green" switch does not stay on either,

Update: I found the solution. At least when using command line programs like mplayer. UBports on the PonePhone seems to default to trying to use PulseAudio, which doesn't work. It needs to be using ALSA, but the regular user account selects the wrong ALSA device by default. For some reason the root user gets the right device. I used the "aplay -l" command to get a list of local audio devices: $ aplay -l card 0: PinePhone card 1: sun9ihdmi It seems the regular user is selecting card 1 when it needs to be selecting card 0. So to play audio with mplayer (or other audio players) I need to manually specify card 0. With mplayer that looks like this: mplayer -ao alsa:device=hw=0 audio-file.mp3 I'm currently looking for a way to make this selection permanent and consistent for all audio players, but for now I can at least funnel audio through mplayer on my PinePhone.

@etdoughe Thank you for the link. I now can transfer data via usb using the recovery mode ;). Although I would prefer a OTA-26 release which fixes the usb issue ... or at least a patch or something, but you can't have everything ;).

@BarryT have you seen this post?

Yes, the firewall stays active after rebooting. I've also checked if the firewall was perhaps circumvented by looking at the NAT log of my router. No entry, so it seems to work. Another idea might be: If you, say, currently need Cloudflare for surfing the net, then you could enable just these IP ranges by making a separate text file and running this command: while read line; do sudo ufw allow out from any to $line; done < ip-ranges-cloudflare.txt I only changed in the first script "deny" to "allow". These would be the IP ranges: 173.245.48.0/20 103.21.244.0/22 103.22.200.0/22 103.31.4.0/22 141.101.64.0/18 108.162.192.0/18 190.93.240.0/20 188.114.96.0/20 197.234.240.0/22 198.41.128.0/17 162.158.0.0/15 104.16.0.0/13 104.24.0.0/14 172.64.0.0/13 131.0.72.0/22 2400:cb00::/32 2606:4700::/32 2803:f800::/32 2405:b500::/32 2405:8100::/32 2a06:98c0::/29 2c0f:f248::/32

#1: 12/24hr clock does indeed seem linked to system display language as Luksus wondered. It'd be nice to be able to change this independently, I agree. But maybe pretty minor in the scheme of things, and the folks doing development have a lot of important work going on. I'm able to set mine to British English, which is close enough to Canadian English, and gets me a 24hr clock. #3: It's hit and miss for me too on whether apps where I've disabled app suspension work when the phone's locked. On my Oneplus 5T when I shut the screen off, audio playing in Morph cuts out, as do voice calls over Jitsi, but Podbird keeps playing and normal phone calls work fine. Recorder keeps playing on playback mode, but will stop recording.

@arubislander Thanks for the fast answer!

Found it: jounalctl | grep -i ufw

Firefox has been packaged with click already https://gitlab.com/debclick/uFirefox/. Last commit was 4 months ago and it works. There are some minor issues, (with workarounds), like keyboard sometimes not opening, and to scroll by touch you have to install the "scroll anywhere" extension.

@ceric You can wait, but don't get your hopes up. Chances are slim this device will be brought up to Focal.

@CiberSheep openssl ciphers | grep -i 256.gcm does reveal that there are several AES 256 GCM ciphers installed on Ubuntu Touch 20.04. But not having ever used ProtonVPN, I do not know if the right one is in the list.

All right, thanks for that viewpoint. I never saw it like that. I'll keep my badge of honour then!

@domubpkm thanks for that. I'll close this then and wait.

@MrT10001 We can also add OnePlus Nord N10 5G and OnePlus Nord N100?

@sven The error message I pasted above tells about a missing image. And at this time, as I learned, the installer was only partially flashing critical firmware partitions so if you came from android 12+ it would leave you with a brick... This is fixed now, the Installer does a correct flash now.

I wanted this too but so far I haven't found a way even with a code. For now, you can only use the lock option from the system indicator but it won't turn off the screen, just lock.