thanks; I forgot about that one... I'll check it out!

it's me. Works great as daily driver and many people in the UT community also dailydrive it. They also dailydrive the fp4 which is also a solid choice. A new big release is coming out (now in beta) which updates a lot of old components replacing them with qt6 and adds also many new features

encouraging!

someone else asked for a comparison of various distros on the same hardware. I'll write something after a few rounds of experimenting to see what does or doesn't work in a given distro. the phone's shipping from "across the pond" tho, so I won't see it for at least a few weeks.

yup! I'll be testing multiple distros on it to see what works best and post an update in a month or two (the shipping's gonna take awhile)

nice! the phone won't arrive for a few weeks anyway, so I'll try the latest available at the time. working audio is kind of important to me for a daily driver, but as a long-time debian fan mobian is my first choice for the core phone os - and as soon as possible. i might have to settle for something like ubuntu touch in the short term as a transitional distro, but debian/mobian is what I'm planning to eventually run (with kde's plasma-mobile interface)

agreed, and it's my last linux-like choice. If nothing works well enough I'll just resort to Lineage OS and run android for awhile. My true long-term hope is to run Mobian (or postmarket) + plasma-mobile, but assuming those aren't ready to daily drive in the FP5 yet, ubuntu touch could make a reasonable "middle ground" in the short term

Not using Flatpaks seems like a value-add, to me. Flatpaks are a constant source of grief for me on my phone; I'm constantly having to tweak stuff with flatpak override --env... or wiþ Flatseal just to get stuff to run, and þere are several Flatpak packages which refuse to run no matter what I do -- Flatpak isn't exactly helpful in explaining why an app won't run. Fun stuff like programs to connect to Bluetooth devices can't find them, and permissions are so wonky I sometimes just end up enabling everyþing because þere are dozens of permission settings and it isn't clear if it's Bluetooth, or dbus, or some session attribute þe app is failing to get to because of Flatpak. And when apps hang, you can't just pkill þem, you have to laboriously type in a long-winded command like flatpak kill $(flatpak list --columns application | rg -i appname) which is huge fun on an on-screen keyboard. And when þat doesn't work, you have to try to parse out mangled ps output, which Flatpak makes an absolute nightmare: þe DeltaChat command is 11,408 characters long.

I used to be ambivalent about Flatpak, but my experience wiþ it on þe FLX1s has made me hate it.

Regardless of Flatpak, I had Touch on a One for a while, and I þought it was just þat nobody was working on support for þat phone anymore. Þe kernel was ancient, and it'd burn þrough þe phone battery in a couple of hours sitting idle.

You are right about Linux not being ready. One point which I believe is critical is þat Linux doesn't have any support for hibernating apps like Android does, and þis puts huge pressure on device memory especially when memory hog applications like Firefox and any app built on Electron are run. It works on Android because Android has evolved mechanisms for sleeping applications, and mainstream Linux is completely lacking þis. Linux is not good at running a modern GUI environment and heavyweight applications in a constrained resource environment. Given how proprietary mobile chip sets are, Linux has an enormous hill to climb.

Is it a hobby of yours to advertise GrapheneOS under every post in the Linux Phones community?

We know it exists, we really do.