And it is working for me. Thank you from me as well. This work is much appreciated.

@ChromiumOS-Guy No rush of course but can you say a few words about noble? I don't see any commits relating to it yet, so I assume a real wayland port is not done yet? Do we know if the current state still works on noble? Thanks.

@wally next it happen for you before restarting the service, could you give the output off: systemctl status --user nuntium.service ?

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

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

By following the method mentioned above, the GPS can be turned on.

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

Hi @Rondarius. Thanks, but that's overkill for my use case.

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]

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

@Wheeling-Pigeon Indeed. And either 9S/Pro/India...All share the same motherboard hardware&firmware + same built image...

@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

@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

@atarilinux said in VoLTE Implementation For Google Pixel 3a/3a XL: @Eric-H What you have stated above is correct to the best of my knowledge. Here is the other part from the QA call: *Source Material - Not Image *Information on image build process, but not how to install it *Built on top of latest Android 12.1 version for the Google Pixel 3a, but build not completed So....it looks like we need to: Finish the build (This part is the least specific. Finish what? This is the main issue due to it not being specific. Maybe it is only the retro-fitted partition issue? A lot of data may need to be checked to see what is complete. Here is the bottleneck in completing development.) ...snip... I think this, at the very least, is what you're running into. For one thing, the LLVMgold library isn't referenced correctly by the build system. I was able to correct that but my make skills are simplistic and old and rusty. Am currently looking at a problem with the device tree.

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

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