@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

@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.

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

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]

@domubpkm Thanks for the info! calls are my biggest issue, they just keep calling all day every day.

@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

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

@MrRoughwood Yeah, keep on checking different settings. I've done the same when I was trying to figure out my battery drain issue. It needs an overnight test so it takes a long time

@Amarurtuuq I have no idea what is happening. I would try to reset the APN config again and recreates manually if needed. Or maybe just needed a reinstallation ?

@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).

@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.

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

@MrT10001 I genuinely cannot believe that fixed it, thank you! It cruised through the process this time, and UT is now installed

@ChromiumOS-Guy Hello and many thanks for the work! For me (from favorite to appreciated): Option 5 - Option 4 - Option 3

@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.

@Simmonz Hi there, mate. Was the bootloader unlocked when you attempted the downgrade?

I couldn't really leave it, so I just tried again, and now it worked? I did: Double Checked: Android is version 11 (Build fp4.fp4k.a.179.20230116 $ fastboot flashing unlock FAILED (remote: ' Device already : unlocked!') fastboot: error: Command failed $ fastboot flashing unlock_critical FAILED (remote: ' Device already : unlocked!') fastboot: error: Command failed Checked All three boxes (Including User Wipe)... Maybe you were right, Luksus (and thanks!), that I somehow missed the first check box, but alas, I'm a happy camper.. Regards Grisen

@poVoq I just tried now with the apk pure Revolut install. It installs but immediately says the device is not secure and will not start.

@poVoq No, sorry. Only A14.

Not the only one. I was also surprised plugging in my usb-c headphones did nothing. Generally it should be noted that this is about headphones with an usb dac. There are also adapters and headphones that pass through analog audio over the usb-c connectors, and those apparently work. These are the open issues that have been reported so far: https://gitlab.com/ubports/development/core/packaging/usb-moded/-/issues/6 https://gitlab.com/ubports/development/ubuntu-touch/-/issues/1912 https://gitlab.com/ubports/porting/reference-device-ports/halium13/volla-phone-quintus/volla-algiz/-/issues/3