Ubuntu Touch 24.04-2.0 call for testing

peat_psuwit

Hello everyone.

We are pleased to announce that Ubuntu Touch 24.04-2.0 Beta is now available for testing! Ubuntu Touch 24.04-2.0 is slated for release on 13 July 2026. Before then, we need to make sure it's ready to go.

Notable features in this release are:

Updated browser engine for Morph Browser
Ubuntu Touch can now avoid notches and rounded corners
Screenshot editor

More info about these features are available on our blog (in the process of publishing).

Unfortunately, because of the system storage space limitation, we're unable to provide Ubuntu Touch 24.04-2.0 to all of currently supported devices. We have divided devices into 3 groups:

Devices we're confident will not have a problem with system storage space (or have the problem resolved). These devices are:

F(x)tec Pro1X
Fairphone 4
Fairphone 5
Lenovo Tab M10 HD 2nd Gen WiFi / LTE
Nothing Phone (1)
Sony Xperia X
Volla Phone
Volla Phone X
Volla Phone 22
Volla Phone X23
Volla Phone Quintus
Volla Phone Plinius
Volla Tablet
Rabbit R1
Xiaomi Poco X3
Zinwa Q25

To receive Ubuntu Touch 24.04-2.0 Beta on these devices, switch your device to Release Candidate channel, then run the following command in Terminal app or via ADB/SSH:

gsettings set io.ubuntu-touch.system-settings.update offer-development-release true

Afterwards, head to System Settings -> Updates, and you should be offered to upgrade to Ubuntu Touch 24.04-2.0 Beta.

Devices that are known not to work. These devices are:

Oneplus Nord N10 5G
OnePlus Nord N100
OnePlus 5
OnePlus 5T
OnePlus 6
OnePlus 6T
Fairphone 3 and 3+
Google Pixel 3a and 3a XL
Xiaomi Poco M2 Pro
Xiaomi Redmi Note 9 Pro (Global)
Xiaomi Redmi Note 9S/9 Pro (India)
Xiaomi Redmi Note 9 Pro Max

For these devices, we've stopped updates flowing into the daily channel to avoid bricking those devices. If you follow the above instructions while you're on 24.04-1.x Release Candidate channel, you won't be offered to upgrade to 24.04-2.x Beta. However, if you're on 24.04-1.x Daily channel, you may still be offered to upgrade to 24.04-2.x daily images. Do not upgrade, as 1.) this is the older image before we include the new Qt 6-based Morph Browser, and 2.) you will not be able to upgrade to the new daily image once it's available.

If your devices are in this list and you're already on 24.04-2.x Daily channel, I recommends you to use UBports Installer to downgrade to 24.04-1.x images and wait for your port to receive 24.04-2.x updates again. This can be done without losing data.

Devices that are not in either of the list above. We don't have enough information to determine if they'll work on 24.04-2.x, so we need testing from you. To do so, make sure you're on a spare device, then follow the same instructions above but switch to Daily channel instead of Release Candidate channel. The possible results are:

Your device upgrade successfully. In such case, congratulations, your device should be working with 24.04-2.x. Please report back to us, and we'll enable your device to receive 24.04-2.0 RC and 24.04-2.0, or if not possible in time, for 24.04-2.1 or subsequent releases.
Your device fails to upgrade. In such case, please use UBports Installer to restore 24.04-1.x on your device, and then also report to us to disable updates to these devices too.

I know that these instructions are long and unwieldy, but this is due to the special transition that needs to happen for the inclusion of Qt 6-based Morph Browser with upgraded Chromium. We truly appreciate all testing. Please don't hesitate to reply below with any questions you have.

lsitongia

If our phone is on list 2., how will we know when the new 2.0 is available? By staying on the 1.x RC channel? I’ve been assuming that the upgrade to 2.x will require a reinstall using the installer with a wipe because the partition size changes.

Vlad Nirky

@lsitongia
Even if you need to change partition size, you won't have to do a wipe, just partionning option checked based on my previous tests.

alagirialagiri

@peat_psuwit Redmi note 9 (merlin) is not updating to 24.04-2.0 beta.Poco x3 updated to beta. I do not know why merlin -android 11 device disabled from updating.Poco x3 Surya updated successfully-android 10 device.miatoll devices waiting are android 10 devices..It can be enabled ,I think so. Thank you.

messayisto

@peat_psuwit Thanks for this amazing work!
One Question: is there an easy way to go back to -24.04-1.x just in case the update fails?
On Xperia X Morph shows no websites.

klh

@alagirialagiri the Android version doesn't matter here.

miatoll is on the second list for a reason - it turned out to be broken last minute and had to be disabled, the number of variants meant it took a while to verify - it will also most likely go in the RC.

merlin was updated too late to make the cut for beta, it will have to wait for RC. You can try the instructions as this device is not on either of the lists:

@peat_psuwit said:

Devices that are not in either of the list above. We don't have enough information to determine if they'll work on 24.04-2.x, so we need testing from you. To do so, make sure you're on a spare device, then follow the same instructions above but switch to Daily channel instead of Release Candidate channel. The possible results are:

Your device upgrade successfully. In such case, congratulations, your device should be working with 24.04-2.x. Please report back to us, and we'll enable your device to receive 24.04-2.0 RC and 24.04-2.0, or if not possible in time, for 24.04-2.1 or subsequent releases.

Your device fails to upgrade. In such case, please use UBports Installer to restore 24.04-1.x on your device, and then also report to us to disable updates to these devices too.

klh

@messayisto Use the installer, make sure none of the checkboxes are selected and install 24.04-1.x

messayisto

@klh thanks!

lsitongia

Okay, I am going to run 1.x RC on my OnePlus N10, run the gsettings command as above, and wait for notification that 2.x is available.

pparent

@lsitongia

Unfortunately I cannot really test now because my testing device is Oneplus Nord N10 5G, and I can't risk my daily driver at the moment.

My concern is about XWayland apps, is there still the problem of OSK not showing up on these apps ? (uWolf, uFirefox, Chromium for UT, Signal UT, Whatsnew, Min Browser, Rocket.chat)? I say that because I could test previous revisions of 24.04-2.x on my device and those app could not access the OSK anymore. Other people reported the same.

Can any one report the current status of these apps? Has it improved or is it still the same?

( I feel it would be a shame to loose usage of these apps with upgrade to 24.04-2.x, they are currently indispensable to my personal daily usage on my volaphone 22 ).

Thank you!

klh

@pparent have you reported the issue anywhere? Not sure if anyone worked on that. Did this testing result in any logs or anything that could point us to a cause? Are these apps still using my immodules.cache hack from back in xenial?

messayisto

@pparent On my xperia X neither Min Browser nor uWolf are working. Min Broeser is crashing after it st
arted, Uwolf has no keyboard. I am a bit surprised that this beta came out today, because Morph itsself is not working, too. Well, its a beta...

pparent

@messayisto said:

Min Broeser is crashing after it st

This is normal I will realease very soon (possibly tomorow) a new version that will not crash with 24.04-2.x, this is another bug that I can and will fix easily, that should currently only impact Min and Rocket.Chat .

The real problem is the OSK, I guess if it does not work with uWolf, it is the same with Signal UT or Whatsnew

Thank's

@pparent have you reported the issue anywhere? Not sure if anyone worked on that. Did this testing result in >any logs or anything that could point us to a cause? Are these apps still using my immodules.cache hack from >back in xenial?

I did not open an issue, because I did not have the time to really dig. But some users did report me the issue about my apps.

But I remember we discussed with @gpatel-fr about this issue on this forum, and I think he had an hypothesis about a commit that might have provoked it, but I did not have the time to dig. I will try to find again this topic!

@klh said:

Are these apps still using my immodules.cache hack from back in xenial?

Possibly yes. My apps are indeed using a immodules.cache file in GTK_IM_MODULE_FILE to point to the maliit-inputcontext-gtk library path form the app. Its probable that the other apps from other authors do the same.

Edit:

@gpatel-fr said:

this could be linked to this change:

https://gitlab.com/ubports/development/core/packaging/maliit-framework/-/commit/6bd655621fea66af7b9bb3a477b9de072b4939db

if it is, you may find warnings such as 'Application attempted to activate itself without focus' in the journal.

https://forums.ubports.com/post/93101