@Moem up to you. I did wrote the underlying queries to all this (and the whole process took days and two month of tokens value on claude ai), red them all more than once, and checked, then refined, over and over. This all ai thing starts sounding like a strange discrimination on a tool that is nothing but a tool, and as with any tool its value is defined by its user and not of itself (the old guns dont kill argument). But anyway, that is not the place for this. If you dont want to read, dont. You dont need to inform me about it, its solely up to you. I dont need to point this out to you either, but I did, and you informed, so it is that. Just pointing things out around

@arubislander no ideia! It is what appears! I checked the data in the phone and it is the correct one.

@undrwater the thing is Ubuntu Touch is a left, top OS. It would ideal is developers follow the Human Interface Guidelines and stop pushing bottom controls into apps. And again, there is no «global back» concept because we have the app spread to switch from app to app. And the launcher to launch apps. Of course there's an in-app back, end it is on the top left corner.

Reporting back for future generations, I think I've found the issue. I was retracing my steps and found this: When installing postmarketOS there is a device specific instructionto run "fastboot oem uart enable" command. So I tried to run "fastboot oem uart disable" and then flash UT. So far working like a charm. Did a switch off, did a restart and all works as I'd expect it - also with Libertine set up.

@PhAndersson @gpatel-fr So the fix is in 1.3 daily. Wait 1.3 candidate to test. Thanks.

@pparent lol reminds me of a ancient proverb i just made up ....."isolation is good until one dies of loneliness" ...

@developerbayman said: @pparent this is good to know basically 99% of all my stuff is on qt6 i would hate to have to refactor back to qt5 Anyway this is only a question of time before Qt6 gets integrated in the system and become the standard for app development. Now to publish a Qt6 app to the openstore you have to bundle the whole Qt6 library with you're app which might be a bit heavy, be soon this should not be a problem anymore.

On my home wifi I have no issues, so just playing around with the phone now. It's very smooth and responsive. Wonder how it will work with my SIM here in Japan.

I tried with another display, it works! It seems, for some odd reason, my main display is the cause. Thank you all for help! P.S.: It's really cool to have this working, so I can now make FP5 my main device. Ubports is such a great project, after leaving Windows to Manjaro, I now can leave the Google ecosystem too and gain back control of my hardware. Just to mention, waydroid works as well very nice. Not everything is perfect (I have issue with bluetooth), but what it offers, is good enough for me, I can live with the workarounds for the rest, until things are fully working sometime in the future (hopefully).

@oldbutndy im actually shaving like .....idk ..500 yaks? ...lol im slowing porting my entire pylinux software suite to UT with a few extras like this ....a aethersx2 ps2 emulator snes9x maybe retroarch if nobody did that one already? ....im gonna do alot of esp32 and meshtastic stuff ...i mean the sky is the limit ....health and money permitting

@Martin230799 check NetworkManager is enabled make sure this file looks like this: phablet@ubuntu-phablet:~$ cat /etc/NetworkManager/NetworkManager.conf [main] plugins=ifupdown,keyfile [ifupdown] managed=true [device] wifi.scan-rand-mac-address=no if ifupdown managed is false, networkmanager is not managing the network interfaces. in my case it somehow works with it being false but that is most certianly some kind of bug, it should be true.

@Moem @MarcelloTogg I went and checked all three links provided. The roadmap (ubports DOT com/lomiri-roadmap) covers Lomiri's packaging journey into Debian — historical milestones since 2020 and two vague estimates for Lomiri on Debian desktop. There is no roadmap for Ubuntu Touch itself. No page that says "here is where the OS stands, here is what we are working toward." It does not exist. The blog is a reverse-chronological archive of Q&A transcripts and release announcements. Valuable if you have time to read 185 biweekly sessions and synthesize them yourself. Not a summary. To their credit, the transcripts are detailed — but that is raw material, not communication aimed at regular users asking exactly your question. The GitLab activity feed is raw commits. No context, no narrative, not useful to anyone who is not already a developer on the project. Your question is reasonable. "Where are things and where are they headed?" is the most natural thing a user could ask. The honest answer is that there is no concise, maintained answer to that question available anywhere on ubports DOT com right now. That is not a criticism of the developers — maintaining documentation alongside the actual work is genuinely hard with a small volunteer team. But pointing someone toward those three links as if they answer your question is not accurate. I spent several months reading through the Q&A archives and forum history to piece together the picture myself. The short version is in a post I linked earlier in this thread — not because I want to be negative, but because I think you deserved an actual answer.

@developerbayman You may be interested in my recent post on the matter. Tldr there are projects who already ditched hallium years ago, basically ALL other mobile linux projects. For ubtouch flavored mobile distro, you may be more interested in lomiry on debian.

@oldbutndy said: I thought sm-xcx was updating details on specific device pages They are. That means updating the already existing text, not adding new sentences.

This will not be possible as a confined app. You will need a background service that listen to incoming sms and forward it. I'm not sure if such app can be allowed in the openstore, but here is a few things to know. First create your background service, it could be in standard python if you are familiar with. Ofono is the service that emit notifications when new incoming sms, it uses dbus. api can be found here: https://github.com/rilmodem/ofono/blob/master/doc/messagemanager-api.txt (old repository but sending and receiving sms still like that ) AI can help you with a minimal script. then when your service seems to work, you have to create all the plumbery to install/remove/run it, you can find an example with battery-saver app: https://gitlab.com/lduboeuf/battery-saver/

@Shriharsh-Kulthe It is an old phone (with the micro USB port) and the fact it updated to Noble may indicate further work may be done. It is not a common device though and I did use it for my main UT device for a while.

@grenudi Thanks for linking that thread, though I've not had time to read it fully now. I am aware of the Halium approach vs. the mainline Linux approach, and I am somewhat (at least superficially) familiar with the downsides and upsides of each. I will try to read it in its entirety during the week to gain more insights. I am mostly interested in a mainline distro on my phone, but my plan with this second hand device is to familiarize myself with all possibilities available that will run on my device. postmarketOS is what I plan to try after Ubuntu Touch. I've been quite stoked about the recent progress posts on Mastadon by Luca Weiss (and his FOSDEM talk) on getting stuff like the camera and the battery gauge working. I understand these things are not trivial with the locked down mobile chipsets, even for someone directly employed at Fairphone. I'm testing them out in this order in hope of being able to contribute over longer time to testing stuff for postmarketOS.

Hilfe auf Deutsch gibt es hier: https://t.me/UBports_Deutsch

@arubislander i am in Portugal. By law all ISP block some IPs. Which IP is used for the installation? I can check it.

@Moem You are welcome, hopefully this can help with your issue