Looking at the list of supported devices, most of them only have 4GB. I thought this is because UT doesn't need many resources, less than Android.
But what you imply would mean, that hardly any of these phones runs UT smoothly...?
Then I wonder why there have been hardly more than three devices with 6GB or more been ported...? Of which only one is not a community port.
And especially the recommended devices have mostly 4GB. Why would they do that knowing the devices are hardly suitable to run that OS?
That confuses me, since I thought I only have to wait a bit for the software to become better...

Maybe I got some Volla Phones for sale now...

@linuxlion It would seem both of us were going about this the wrong way.

On the login page (you would need to log out of the forum first to see it) there is a Forgotten password link. Here is the direct link: https://forums.ubports.com/reset

@AppLee thanks very much

@justsoup
Yes, I guess this is a good summary.

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,

My guess is that something crashes when this happens and probably not really related to out of memory issues. Perhaps Mir, Qtmir, or whatever 😄

Sadly it seems to be really hard to replicate and investigate. I've observed similar issue on my FP4 and Xperia X.

Any Gigaset device is not officially supported by us. There have been many discussions on here about that. Some have got UT running on Gigaset devices but you need to be careful.

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.