@poVoq Unfortunately, that's very dependent on the device, I can do it with my OP5 and my Sennheiser BT headphones

I added Sudo to the Apt statements in .gitlab-ci.yml. I also added systempart=/dev/mapper/system to the deviceinfo file. For this part, https://lucaweiss.eu/post/2023-03-30-retrofit-dynamic-partition/ I'm trying to figure out where to add this on github. The code on github is referencing a number of other githubs by "clone." I'm trying to untangle it to get a since of what happens when and where. I want to make sure I'm not missing anything.

Indeed, this is a general issue with 20.04 OTA-9, and is not related to VollaX. Some apps fail to update. I guess that there's something regarding with 24.04 compatibility layer... For now I ignore those updates, and will wait for the next OTA-10 / 24.04-1.0 to update them again. [image: 1757793889979-photo_2025-09-13_22-02-17.jpg]

@arubislander said in Trying out UT on Pixel 3a XL for review article: Opening an issue about it on the Installer's issue tracker will keep the info from getting lost. Done! https://github.com/ubports/ubports-installer/issues/4177

@Opolork thank you

@ChromiumOS-Guy Option 5 without the fur and thanks for your work.

@ MrT10001 I’ll wear that badge proudly. @ johndoe Thanks for the advice. I’ll keep it in mind and won’t change anything. @ liam Sorry to hear that. I’m really not an expert. So I can’t understand the issue you experienced with the battery and Postmarket on your device. Perhaps you should try again some time with UT? (Possibly a real expert should say something to that suggestion) With me the installer showed some flaws. I was absolutely not sure about how successful the install would be since it didn’t show anything like “Congratulations! Ubuntu Touch is now installed.” The final screen just showed that formatting was still at work. I could only see on the mobile itself that it was possible to start UT (since there was a reboot and I was asked to define a passkey) and that the amount of free space on the device was big enough to believe that everything was more or less OK. Hope you can still use your device somehow.

@RJDan hmm, i may be able to do something about syncing passwords, but it would require cooperation from the UT development team. no promises though I already have my plate full with the upcoming rewrite of uWolf for Noble and NixManager plugin for lss (which i'm waiting on a test device so i can start working on the UI)

@MrT10001 I did not use trwp just local update. But I did get it to go. I reset the phone, used the zip from the XDA link you put, then used a different computer with a fresh ubuntu install, flash UB24 from there it booted into recovery, I then flashed UB20 from the installer and was able to update to 24. Not sure why that worked but it did. Thank you for helping. EDIT so I posted that while it was updating to 24.0 and it rebooted right back to recovery and that was it, I was able to re flash 20.0. So I assume 24.0 just does not work on the 6t as of yet, which is cool since it is still new.

@lduboeuf Running /usr/share/ofono/scripts/get-tech-preference outputs Technology preference: nr. Running /usr/share/ofono/scripts/get-serving-cell-info tells me Radio Access Technology = lte, but I don't know if that helps

My preferred method is when out and about, to open a draft email on whatever email client/web interface on my UT smartphone I use and add to it but not send it. Then later when I open my emails on my home PC, the notes are there.

its working since todays update to version 3.1.3

The Signal gateway for XMPP is also working again, in case someone prefers that.

@johndoe said in using Ubuntu Touch as o/s for IoT devices with RPi/Rockchip: A specific mobile DE, you could also look into, is Phosh. But it will probably not work with your remote access software. Whereas Lomiri is known to work with VNC at least. And it is in the debian repo's as @Vlad-Nirky already mentioned.

@RJDan provide us with important applications that can be easily installed (one-click in the store), are safe (not random code from a random stranger with a random license), and have all the essential functionalities. I am willing to pay some money, let's say for fully functional Firefox, fully functional MS Teams, Slack, Spotify,... but mainly, they should not be outdated or unupdated, and the microphone, camera, keyboard, and clipboard should work. I know it sounds like a lot, but theoretically, it could just be an integration of Snap/Flatpak into the store. but that no bug bounty, that is more like fundraising

@oldpaint said in gcc 9.4 compiler in docker images: I thought I would start with the Botan library so I ran the command 'clickable build --libs --verbose' and that provoked a download of the correct docker container for my phone, arm64. I can't seem to provoke a download for the desktop docker container, amd64. I tried 'clickable desktop ...' but no joy. You could try 'CLICKABLE_ARCH=amd64 clickable build --libs --verbose' or 'clickable build --arch amd64 --libs --verbose' in order to specify the architecture. Your architecture should also be defined in your manifest.json file. (The app template should provide a manifest.json file by default. It is maybe under data/. You can read about it here: https://clickable-ut.dev/en/latest/usage.html ) The architecture will probably be whatever architecture is specified when executing clickable (likely arm64 by default).

@wally Does shows L when calling , here..not LTE .

A puzzling issue is that when I see the prompt 'waydroid is stopped' in the UT command line, Waydroid is actually running, and operations within its system GUI appear to be functioning normally.

@arubislander said in unknown filesystem type 'overlay'.: @dafeihong you probably want to run those tools in a LXD container. Try searching for LXD on Ubuntu Touch in the forum. Thank you very much. It sounds like the container solution I need. I'll go check its support for these tools.

@lduboeuf Well, I didn't try to reset the APN, I am scared that nothing works afterwards. I will try the terminal command proposed by Wally (I hope this won't have bad effects on SMS) and if nothing changes, maybe I will try to reset the APN. I won't try a reinstallation, I am not expert enough of UBports (that's why I bought this second-hand smartphone with UT already installed). If I cannot succeed in fixing the problem, well, my daughter will live without MMS (but it's a pity because this is our only way to exchange pictures during the week when she is on boarding school).