@rdfrs thats because apparmor rules (waiting for fix to trickle down to stable releases ask @Fuseteam he knows about this better then me)
confinment is mostly done, not a priority though because it will not raise security as much as you think only make it clearer to you the user what i am doing on you're phone, which granted is a very good reason and is why im working on it. (there is a branch with confinement implemented im just waiting until it won't break the app to use)
@lduboeuf Thanks a lot for the suggestions. That's interesting to hear that the nuntium restart command should be the same as rebooting. It happened often enough that I feel confident saying a reboot didn't happen.
Now that I've heard your idea about booting I wonder if the trigger that would cause the issue was reboots all along. I'd be disappointed with myself for not making that connection, but it's definitely possible.
I don't have this issue anymore, it occurred both on a previous phone (Oneplus 5T) and with a different cell provider (not sure which change fixed it), but I'll try swapping my SIM into that broken old phone and see if I can reproduce it just to see.
As ever, thanks so much for your work on MMS and for the help!
@wally Bienvenue , as stated , newbie to phone and UT,
ok ,checking 3G is showing receiving and making a call, i guess you are right !! it does switch from L to 3G here too , so , learning here .
@jezek said in Ubuntu Touch Q&A 174 call for questions:
Could you elaborate on this? https://www.salesiancollege.in/eu-enforces-android-bootloader-restrictions-from-august-1/
Probably untrue: https://xiaomitime.com/dont-panic-eu-isnt-ending-bootloader-unlocks-soon-59697/
@Simmonz Interesting. Have you tried contacting our Volla mates in their forum? There should be a more straightforward way of doing that. One of the benefits of such phones is that, since they have total control of the drivers, one can unlock the bootloader and lock it again after installing UT. Cheers.
@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.
@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
Don't suppose anyone has the vendor blobs for android 12.1/lineage 19.1 extracted already? I'm trying a build myself and it's at the point where it wants them but I've been struggling a bit to extract them from the payload image I have. Checked the muppet but they don't have 19.1 .
@stanwood said in Call for testing: Ubuntu Touch 20.04 OTA-10:
So, how will the update be rolled out to users on the stable channel? (OTA-9). Will they first receive the update to 20.04 OTA-10, then immediately afterwards the update to 24.04-1.0? Or will they have the choice between the 20.04 OTA update and the 24.04-1.0 update?
I must admit that I myself am a bit lost in all this
20.04 OTA-9 users will first receive 20.04 OTA-10 as an usual update. After that, they'll be offered an upgrade to 24.04-1.0. Users can choose whether to upgrade or not.
I'll try to make this more clear in our release announcement blog.
@Simmonz I have moved your topic so that it is more clear to everyone what device you have. That was relevant for your question, but you did not specify it at the start.
@smoore100 You may have to look at installing the minimum Android version requirement before going to UT. You can check with the Volla guys which one is required before upgrading to UT. Cheers.
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]