And here a little success story on combining the Clickable Snap & the Docker Snap, allowing to build AND test a click package directly on the device (in this case a JingPad). Photo courtesy of Sander: [image: 1762635258156-photo_2025-11-05_21-28-47-resized.jpg]

but sharing about overall experience, I'm really happy with FP5. It works flawlessly with my 4k monitor and docking station. I can just plug it and use from mouse/keyboard/monitor. That's just awesome. FP4 was probably working similarly with FHD but I don't have any low resolution screen anymore, so I never tested it (I just can confirm that it couldn't drive 4k resolution). I just hope FP7 will have fully fictional USB-C again (as FP6 allows only charging, no docking capabilities!!!)

@Linuxlite76 In my experience this issue is device dependant, port dependant and different in rc, stable and daily channel sometimes, so its a liitle guess and hit

I think for fast typers UT's keyboard definitely would feel slower and I guess it also depends on the device and port. There are optimizations and improvements that can be done. At the moment, autocorrect isn't recommended because it kinda suck You can still use word suggestions though which can be helpful.

@gpatel-fr yep you were right, going down to the specific projects helped. Thanks once again

@bestenaizena No problem. Helping one another is what this forum is all about.

@RJDan Oh okay. I guess you're on Noble and only the Essentials version is available for now The full version is available from the repo but it will be released in Ambot soon

@k.nacke Just installed UT. The issue with this is that waydroid, just doesnt work. I got it to setup, but It spams about sensor not found. I left it for a good 30 minutes, but, it could not recover from that. apart from that, the only other issue I could see is that the back camera is very cloudy and any photos is barely understandable. Apart from that, the UT itself is great and working minus the videos which you addressed. I am open for more testing, please feel free to push a development update. thanks a lot though.

I've been having some issues using Libertine running apps and searched the forum. It seems some others are also having issues setting up a proper Libertine container on the Google Pixel 3a. I'm placing a link to here. https://forums.ubports.com/topic/11232/unable-to-create-libertine-container

from what im reading its asking me to build package sources like indicator-network and i think that is needed because i ran lomiri once i got the setup no apps worked and when i restarted it failed to run so what do i need to b

@fake-alex So what's the plan... are you offering to send these devices to people who want to try to make a port for them? Developers need to have the device in hands.

@sixwheeledbeast To use UT, you must never relock the bootloader

@Carlos said in Call for testing: Ubuntu Touch 24.04-1.1: This weekend I updated my Vollaphone22 from 24.04-1.0 to 24.04-1.1 and screen starts blinking on boot before the logo Ubuntu appears. With installer reinstalled 24.04-1.1 without wiping data and everything I use every day starts working normally until I found a serious bug on calls. Yesterday a friend calls me, I answered the call but no sound from other side. My friend repeated calling me and all answering was no sound. With other phone at hand I search the source of the error and found the Vollaphone22 was the culprit. How to reproduce is like this, make a call to other phone, wait that the other side answer the call, talk to test that audio is ok, wait that the other phone hang the call, now if you repeat process there is no sound if answered the call. Only rebooting Vollaphone works again, untill other phone terminates the call first and error returns. This error does not happens on version 20.04 stable. Thank you for the report. We're looking into this issue and will delay Ubuntu Touch 24.04-1.1 until we have this issue figure out. @mjosenhans said in Call for testing: Ubuntu Touch 24.04-1.1: I yesterday installed on my volla phone 22 Ubport 24.04-1.1 RC1 via RC channel. I had problems with incoming and outgoing voice calls without any voice being heard in both directions. Thus I reinstalled 24.04-1.x stable via stable channel. However instead of running the again the 24.04.1 software from stable, the phone is now in a reset loop. It shows the volla screen, then a black screen via backlight on, then a black screen with backling off and then again the volla screen. And so on. When going into boot loader, I was able to start the recovery mode, however it did not change, it is still in boot loop. Ubports installer is not finding the phone too. What can I do? I plan tomorrow to go to the phone service shop in berlin, which provides volla service and try to reflash the phone. We're sorry that this happen. Please try the following: Boot to bootloader by pressing Volume Up + Power (or Volume Up + plugging cable), then select "Enter fastboot menu". Do not enter recovery. Starts UBports Installer, then manually select "Volla Phone 22" (the Installer currently cannot auto-detect device model in bootloader mode). Select "24.04-1.x Stable" channel and ensure "Bootstrap" option is checked. Leave "Wipe Userdata" unchecked. Follow further instructions from the Installer.

Even better news: The wipe won't be needed. Existing v1 policies continue working and should even be compatible with Waydroid once they're stored in the filesystem keyring. Even if they're not, that's not a blocker for v2 to land early, as existing users can enjoy their devices with the same feature set as before. I'll go ahead and merge this.

@FixOne Very cool.

@RJDan Not while using encryption, because all the info needed for the functions you care about are inaccessible until after your home folder is decrypted.

I have a FP4 and currently everything seems to work: data roaming abroad works calls / sms work wifi/hotspot/vpn works usb-c headset works (Sennheiser Momentum 4) with better volume control than on bluetooth (playback stopped when unplugging as well)