I'm happy to announce that, after much anticipation, Ubuntu Touch 24.04-1.0 is scheduled to be released on 24 September 2025.

Currently, the schedule looks like this:

Date	Event
31 July 2025	Platform stability freeze, 24.04-1.0 Beta 1
14 August 2025	String freeze
28 August 2025	Branch off, 24.04-1.0 Beta 2
11 September 2025	Final freeze, 24.04-1.0 RC
24 September 2025	Release version 24.04-1.0

(See the explanation of the freezes here: https://cpad.ubports.com/sheet/#/2/sheet/view/z44Rl7-Ba5mzHRYXXuk-9l8ZweVF-+v5X30JnZw7bPw/)

We're still a number of things left to do before we can release 24.04-1.0 to all users. However, at this point, we feel confident enough to define a finish line, especially given that Canonical has ended standard support for Ubuntu 20.04.

App developers: you'll soon be able to submit applications built against 24.04-1.x to OpenStore

As part of 24.04-1.0 Beta 1 release, we'll also declare ubuntu-touch-24.04-1.x Click frameworks as stable. Applications built against 24.04-1.x will be allowed to use APIs introduced in Qt 5.15, paving a way to Qt 6 migration in the future.

We're working to make sure apps built against 24.04-1.x can be published on OpenStore. This should happen by 31 July.

Apologize for the late update this time. Let's get into it:

For everyone: the next Ubuntu Touch release will be called 24.04-1.0

You'll notice that this status update has a different headline format. After a discussion with UBports Foundation Board of Trustee (BoT) and with the community in general, we've decided on naming the next Ubuntu Touch release based on Ubuntu 24.04 as "Ubuntu Touch 24.04-1.0". 24.04 signifies the base Ubuntu version we're based on, and 1.0 represents whether it's a major upgrade or it's a minor update.

For now, the system-image channel will still be called utnext/{arch}/{hybris|android9plus|mainline}/daily. We will provide more updates on system-image channel in the future.

For app developers: it's now possible to build against Ubuntu Touch 24.04-1.x

Finalizing on versioning scheme means we're now able to finalize the name of Click framework. The new framework is called ubuntu-touch-24.04-1.x, with -qml variant for QML-only applications and -papi for applications without QML part. Due to the limitation of the Click file format, the AppArmor policy version is 2404.1.

Support in Clickable has been added in the recently released version 8.3.0. This means that if you specify the correct framework and AppArmor policy version, Clickable will choose the correct Docker image by itself and will produce Click packages compatible with 24.04-1.x series.

Open-Store will not yet accept applications built against Ubuntu Touch 24.04-1.x, as the framework is not quite stable yet. However, it's stable enough for developers to compile and test their applications against newer versions of libraries (such as Qt 5.15) available in Ubuntu Touch 24.04-1.x.

We intend to maintain full app compatibility between minor updates, but the same can't be said on major upgrade even when we stay on the same Ubuntu version. However, in practice the app compatibility on the same Ubuntu base version should be possible, and we'll try to maintain backwards compatibility where it makes sense.

For app developers: Ubuntu Touch 24.04-1.x will support apps built against Ubuntu Touch 20.04

Related to my last point, it turns out that it's relatively easy to maintain compatibility with apps built against Ubuntu Touch 20.04, with only a couple of compatibility libraries added to Ubuntu Touch 24.04-1.x. So, we've decided to maintain compatibility with applications which use ubuntu-sdk-20.04 framework and its variants.

This applies to most phones which has a modern 64-bit ARM processor (this applies to all devices which we currently have stable releases of Ubuntu Touch 20.04). On older phones with 32-bit ARM processor, due to a large-scale transition in Ubuntu and Debian (64-bit time_t transition), this is not possible, and compatibility will be limited to QML-only apps which use -qml variant of framework.

Status of Ubuntu Touch 24.04-1.x

At the moment, a few key items still has to be done, including but not limited to:

• Fix MMS and contacts/calendar sync.
• Re-test push notification and hotspot to ensure they actually work.
• Re-building our core applications against the new framework.
• Update our artworks to go with the new Ubuntu icon, introduced at part of Ubuntu 22.04.
• A more streamlined mechanism to upgrade Ubuntu Touch major releases.
• Infrastructure-side work to support the new Ubuntu Touch release scheme.

We still need help in many of these items. If you're interested in lending hands, please reach us on our Telegram group.

We're going to release Ubuntu Touch 20.04 OTA-7 earlier than schedule to fix a number of security issues affecting Pulseaudio, our audio server. One of the issue affects privacy of Ubuntu Touch users, and thus we've decided to release an out-of-schedule update.

The issues are as follow:

• Confined applications can remove the Trust Store permission system module from Pulseaudio, allowing such applications to access the phone's microphone without user knowing, amongst a number of privileged actions.
• Confined applications are able to crash Pulseaudio by performing a volume control on a specific virtual device when a Bluetooth headset is connected.

Both of the issues are specific to the way Ubuntu Touch patches and uses Pulseaudio. However, the second issue has a potential to affect some Ubuntu 16.04 installations running non-default configuration (newer versions are not affected). As such, we've coordinated with Canonical on the timing before making this announcement.

Due to the way our release pipeline works, Ubuntu Touch 20.04 OTA-7 will also contain a number of fixes which are not related to the aforementioned issues. Thus, we'll release an RC for 20.04 OTA-7 in upcoming days and we'll announce a call-for-testing. We plan to release Ubuntu Touch 20.04 OTA-7 on Friday 29 November 2024.

Updated: Ubuntu Touch 20.04 OTA-7 RC is out, which should have version 2024-W47. Please take some time to switch your spare/development phone to the 20.04 RC channel and test this OTA.

Update: Ubuntu Touch 20.04 OTA-7 is released. Thank you everyone involved in testing.

In the Board of Trustees meeting on 4th February, I've brought the release version numbering up as a discussion topic. The attendees considered the comments on this post and have agreed that it's important to still reference Ubuntu version in our versioning scheme, while it would be beneficial development-wise to have a major-minor release system in place.

As such, we've come up with a versioning scheme of "Ubuntu Touch [Ubuntu version]-[release version]" (a variant of option 3). For example, the next version of Ubuntu Touch would be referred to as "Ubuntu Touch 24.04-1.0".

We believe this versioning scheme is both understandable and practical.

I just realize that there has been a lack of a long-form communication from the Ubuntu base upgrade side, which causes some frictions and confusions when trying to contribute to Ubuntu Touch during this transition period. This post aims to provide status updates and information that I think everyone has to know.

Name changes for Noble-based images

Due to some confusion in the word devel which has been used differently before, I've decided to rename the word devel that is used in various places to just next or utnext. In practice, this means:

• The image name from the rootfs job will be in the format of e.g. ubuntu-touch-android9plus-rootfs-next-arm64.tar.gz
• The system-image channel for testing out Noble-based is now called utnext/arm64/android9plus/daily. Note that we've set up redirection in place, so if you're already on the old channel, you'll automatically be redirected to this new name.
• The Clickable images (which we're still working on) will be available under the version next.

The name next is chosen to represent that this will become the "next" major release of Ubuntu Touch. When we enters the phase where we stabilize the release, we'll produce another set of channels, rootfs and Clickable images with the release number (which is yet to be finalized).

Status of Noble-based Ubuntu Touch

Since the last time I made a forum post, the following features has become usable:

• Web Browser
• Media Playback
• Sensor

This may seem not much, but more features are already in the code review phase. It could even be possible that we'll have the image in the state ready for wider testing before the Chrismas. We'll see...

Please be careful when submitting changes to core applications

Mike Gabriel and his team is currently working to package up a number of UT/Lomiri core applications for Debian, making them available on a more up-to-date OS with newer Qt compared to Ubuntu 20.04 our current images are based on. Meanwhile, our Noble-based Ubuntu Touch image is start to be more usable. Both of these expose our applications to new warnings which has not appeared before on Ubuntu Touch 20.04 with Qt 5.12.

However, in many cases, the only way to solve those warnings is to migrate the code to the new syntax. Syntax which is not compatible with Qt 5.12. In particular, those syntax changes include:

• Using function onFoo () { } form for Connection { } component.
• Setting restoreMode property of Binding { } component.

Since we've not make a separated branch for 20.04 just yet (and we can't do so because Clickable support for Noble-based Ubuntu Touch is not available yet), please don't introduce those changes into our core application repositories (more specifically, repositories under "ubports/development/apps" GitLab group). We've yet to decided if we need a separated branch for Ubuntu Touch 20.04 compatibility, but personally I would prefer that we don't need one.

Also, please be reminded that these applications are first and foremost core applications for Ubuntu Touch. When submitting changes for them, please be mindful of this fact. When reviewing changes, please think of a possible breakage on phone (and wrt. Click packaging). Preferably test them on a phone first if the change seems big.

Side note: we're planing to ship an environment variable drop-in file to silence deprecation warnings for the 2 syntax changes above. This should ease your eyes when reading through the log on the device.

Heads up for porters: please drop touch.pa overlay if possible

We expect ports that are available on Ubuntu Touch 20.04 to require only minimal changes in order to run on Noble-based Ubuntu Touch (unlike the 16.04 -> 20.04 transition). We've yet to finalize all changes that will be required. However, one change is certain: touch.pa will have to be updated, or be dropped if possible.

This is due to how a newer Pulseaudio changes how it handles Bluetooth audio, requiring us to update the configuration for the Bluetooth module. However, if touch.pa file is overlaid from ports, the old configuration would be used, preventing voice call over Bluetooth headset to work properly.

If your port requires overlaying touch.pa to hard-code the API level of pulseaudio-module-droid to 30, then you'll be glad to know that it will no longer required when MR at [1] is merged, as it will now happen automatically when required. If, however, your port requires overlaying touch.pa to specify quirks to pulseaudio-module-droid, we'll soon provide a way to specify this quirk without overlaying touch.pa. And if you need to overlay touch.pa for other reasons, please tell us so that we can understand your need better.

[1]: https://gitlab.com/ubports/development/core/hybris-support/pulseaudio-module-droid-discover/-/merge_requests/6

Another thing that might require special consideration is that, if your port overlays binary files (which we would not recommend, for security update reason and other reasons), please make sure that your overlaid binary can be executed on Noble-based images, as not every library retains its interface and/or soname.

Heads-up for app developers: you'll need to re-build your app

Due to changes in Ubuntu 24.04, we cannot guarantee that every application built against Ubuntu Touch 20.04 will run on Noble-based Ubuntu Touch. As such, we'll enforce it through Click's framework system that every native applications must be re-built against the next Ubuntu Touch version.

However, we've not finalized how the Clickable support for the new release scheme will look like. So you can't quite do that just yet. Sorry for the delay.

Meanwhile, if your application is QML-only, and the Click package declare this fact through Click framework (i.e. by using ubuntu-sdk-20.04-qml framework), your application should work as-is without any change. However, due to a shortcoming in Clickable, you might not be able to do that just yet. Please follow issue at [2] to see if this has been solved.

[2]: https://gitlab.com/clickable/clickable/-/issues/444

---

Phew! That's a lot of stuffs. I didn't expect it to be this long when I first decided to sit down and start writing this up. But here we are.

If you still have any question, feel free to reply to this post or to ping me on Telegram in the "UBports Development" channel. I'll try to answer as much as I can.

Status of Noble-based Ubuntu Touch (UTNext)

Since the last time I made a forum post, the following features has become usable:

• GPS
• NFC
• Phone call & SMS
  • Note that MMS is blocked until very recently. We'll have to recheck if it has been fixed or not.
• Camera, include picture and video recording.

Progress is a bit slower than we expected. But we still are progressing nicely.

For app developers: it's now possible to build & test your apps against UTNext

After a long await, you can now start attempting to rebuild your app against Noble-based UTNext. This should allow you to test whether your app has any problem with the Noble-based images, especially if the app was unable to start on them before due to shared library changes.

For now, you'll need to get a nightly build of Clickable. After that, specify ubuntu-touch-next-internal as the framework inside clickable.yaml and specify policy_version of the AppArmor profile to 9999. You may also also have to make sure your manifest.json specifies @CLICK_FRAMEWORK@ in the framework field so that the correct version is filled in automatically by Clickable (sadly a similar mechanism doesn't exist yet for AppArmor policy - see this issue). When building, you'll have to specify --accept-review-errors for now, as click-reviewer-tools has not been updated.

ubuntu-touch-next-internal is a framework which corresponds to the on-going development of UTNext. The -internal part indicates that there is no formal "contract" for this framework. In other words, we don't guarantee forward- and backward- compatibility with any past and future Ubuntu Touch versions. The framework is intended for testing only and is not intended to be published to the Open Store; you'll have to switch to the final framework when it's available.

Due to delays and ongoing discussions, we at the core team are still unable to settle on what versioning scheme and what version number we will use for the next Ubuntu Touch release, and subsequently as the final framework name. We'll have a separated post discussing this in more details and allow you to chime in. We're sorry for this; as soon as we're able to finalize this detail, we'll provide an update to you.

Update: please see a separated post for a discussion around version number: https://forums.ubports.com/post/84517

For porters: it's now possible to drop touch.pa overlay (for UTNext, at least) now possible on both UTNext and 20.04

If your port is one of the port which has to overlay /etc/pulse/touch.pa to provide additional arguments to pulseaudio-module-droid-discover or pulseaudio-modules-droid-card-<API>, it's now possible to instead provide extra arguments using an Deviceinfo property. The property is called PulseaudioModulesDroid_ExtraCardArgs [1] and accept all arguments which you may add to pulseaudio-modules-droid-card-<API>. For example, you can put this in your Deviceinfo overlay to set sampling rate of your device's audio chip:

  PulseaudioModulesDroid_ExtraCardArgs: "rate=48000"

Combined with a change which allow you not to hard-code API level, it should now be possible to drop touch.pa overlay entirely. This feature is now merged into UTNext and 20.04, so you'll be able to share your device tarball between 20.04 and UTNext.

[1]: In case you're wondering, yes, there are PulseaudioModulesDroid_ExtraGlueArgs and PulseaudioModulesDroid_ExtraHidlArgs as well. However, I believe you won't need them.

We've just released the RC image for the Ubuntu Touch 20.04 OTA-9, which should have version 2025-W21 or newer. Please take some time to switch your spare/development phone to the 20.04 RC channel and test this OTA.

Ubuntu Touch 20.04 OTA-9 is a maintenance release with only a minimal number of changes. That said, we still have a number of changes in this OTA. We would love an extra attention to the following areas:

• Basic phone functionality (call, SMS, MMS and cellular data)
  • In particular, if your carrier supports VoLTE and you're using newer Volla phones (X23 and newer). This release include fixes which make VoLTE work on more carriers, which may introduce compatibility issues.
• If your device has an LED, please see if it works correctly.
• Whether Emojis show up correctly. (Not all of newer ones work, but the number should improve).
• Whether Waydroid works.

Please note that only critical and security fixes will be able to enter Ubuntu Touch 20.04 OTA-9 as this point. Normal bug fixes and new features will need to wait for our next release. Please do not discuss normal bug fixes and new features here.

Ubuntu Touch 20.04 OTA-9 is expected to be released on 3 June 2025. We appreciate all testing we will receive.

---

Update 28 May 13:20 UTC: a new RC has been published. Changes include a fix for Waydroid startup race condition, an APN config update for 1&1 (a carrier in Germany), and additional security fixes from Ubuntu upstream.

New system-image channel name: 24.04-1.x/arm64/{hybris,android9plus}/daily

A couple weeks ago, I've done another migration to change, amongst other things. system-image channel name. The new channels are now called 24.04-1.x/arm64/{hybris,android9plus}/daily, with utnext/arm64/{hybris,android9plus}/daily becoming the alias of the former.

The change is made to streamline the process when the development release (e.g. 24.04-1.x) enters a stabilization phase. Devices receiving updates from the old channel name will not see a significant change.

Once 24.04-1.x enters a stabilization phase, utnext/arm64/{hybris,android9plus}/daily will become the aliases of the next release of Ubuntu Touch (e.g. 24.04-2.x).

Status of Ubuntu Touch 24.04-1.x

Notable progresses in the past 2 months are:

• The new logo of Ubuntu Touch has been finalized, and is now used in the boot screen and (soon) in System Settings app.

• Calendar syncing is now working again after fixing underlying issues in libraries we depend on. (MR: 1, 2)
• The problem of ADB session being closed after a few minutes has been fixed. (MR)

GitLab label & milestone cleanup, and new GitLab issue board for 24.04-1.0

A few weeks ago, I've finally got a chance to sit down and re-organize issue labels, milestones and issue boards. As a result we now have an issue board for UT 24.04-1.0 which should help showing what's left in order to have 24.04-1.0 out of the door.

As you can see, there are still a number of issues on the board that would love some help. Please join our development Telegram group and talk to us if you're interested in one of the issues on the board.

Update 18 November 2025

• Ubuntu Touch 24.04-1.1 RC 2 is now available for testing. This release fixes:
  • Issues with voice calls on Volla Phone 22.
  • Crash in Messaging app when attempting to play an attached video or audio.
  • Sending SMS on some VoLTE-enabled devices.

The new release date for Ubuntu Touch 24.04-1.1 is 25 November 2025.

• Due to a migration in Volla Phone 22's hardware abstraction layer (HAL), after receiving Ubuntu Touch 24.04-1.1 RC 1 or later (including daily channel), you will be unable to switch back to Ubuntu Touch 24.04-1.0 using UI. Please follow this instruction to use UBports Installer to re-install Ubuntu Touch 24.04-1.0.

• It is known that Sony Xperia X doesn't boot Ubuntu Touch 24.04-1.x images. This has been known since before 24.04-1.0 release, but due to administrative mistake, the list of device on our release announcement was not updated. The release announcement blog has since been updated. Due to its age, we're unable to guarantee if we'll be able to restore support for Sony Xperia X within 24.04-1.x releases or not. We're sorry for your inconvenience.

---

We've just released the RC image for Ubuntu Touch 24.04-1.1. Please take some time to switch your spare/development phone to the 24.04-1.x RC channel and test this update.

Ubuntu Touch 24.04-1.1 is a maintenance release of 24.04-1.x series. This release contains mostly bug fixes and small improvements. The notable ones are:

• Improved startup time on first boot after upgrading from Ubuntu Touch 20.04 series.
• Fix media scanning daemon getting stuck at 100% CPU usage, draining battery.
• Fix notification badges not appearing in the launcher for Phone and Messaging app.
• Fix applications e.g. TELEports unable to clear notifications before placing a new one.
• Fix incorrect calendar being shown in the pull-down (indicator) menu.
• Fix certain applications using embedded web browser crashing after attempting to use the browser.
• Fix Wi-Fi hotspot being broken on certain devices.
• Prevents deleted Wi-Fi or VPN connection re-appearing after reboot.
• General bug fixes and security updates.

To receive Ubuntu Touch 24.04-1.1 on a device running Ubuntu Touch 24.04-1.0, heads to System Settings -> Updates -> Update Settings -> Release Channel, then select "24.04-1.x Release candidate". Go back to the previous page, and then install the available update.

If your phone is running Ubuntu Touch 20.04 OTA-10, you can receive Ubuntu Touch 24.04-1.1 by first following the instructions above (but select "20.04 Release candidate" instead), then go to System Settings > Update again to upgrade to 24.04-1.1 RC.

Please note that only critical and security fixes will be able to enter Ubuntu Touch 24.04-1.1 as this point. Normal bug fixes and new features will need to wait for our next release. Please do not discuss normal bug fixes and new features here.

Ubuntu Touch 24.04-1.1 is expected to be released on 13 November 2025. We appreciate all testing we will receive.

---

At the same time, we've also released the RC image for Ubuntu Touch 20.04 OTA-11. We have a dedicated forum post. Note: please refrain from discussing Ubuntu Touch 20.04 OTA-11 in this post.

For those that are interested in development of Noble-based Ubuntu Touch, we've now published a new system-image channel devel/arm64/android9plus/daily, available on most devices which has 20.04 devel image [1]. You can switch to it using the following command:

sudo system-image-cli -v --progress=dots --switch=devel/arm64/android9plus/daily

The channel has actually been existed for some time. However, up until today images are available only on a handful of devices due to system-image server configuration limitation. Note that I haven't tested the images on devices other than a handful of devices I have, so please make sure you have a way to recover your phone before trying this.

Note that at the time of posting, the Noble-based images are still missing quite a number of functionalities. At the moment, the following features are either known to be not working, or is not tested but is likely not to be working:

• Web browser
• Media playback
• Camera
• Libertine
• Sensor
• Push notification
• Dialer, Messaging UI
• Hotspot

If you're interested in helping bringing up these features to Noble-based images, please ping me either here or on Telegram.

Do not install this image on your daily driving phone. Things will be broken. You have been warned.

[1]: more specifically, devices with 64-bit ARM architecture and Halium 9 or newer.

Update 18 November 2025 (2): Apologize for the mistake. We've published Ubuntu Touch 20.04 OTA-11 RC 2 to include a fix for sending SMS on some VoLTE-enabled devices.. The release date for Ubuntu Touch 20.04 OTA-11 is still 25 November 2025.

Update 18 November 2025: we're postponing the release of Ubuntu Touch 20.04 OTA-11 to 25 November 2025 to coincide with the release of Ubuntu Touch 24.04-1.1. This is due to a security fix which has to be released at the same time. We're sorry for your inconvenience.

Update 18 November 2025

• Ubuntu Touch 24.04-1.1 RC 2 is now available for testing. This release fixes:
  • Issues with voice calls on Volla Phone 22.
  • Crash in Messaging app when attempting to play an attached video or audio.
  • Sending SMS on some VoLTE-enabled devices.

The new release date for Ubuntu Touch 24.04-1.1 is 25 November 2025.

• Due to a migration in Volla Phone 22's hardware abstraction layer (HAL), after receiving Ubuntu Touch 24.04-1.1 RC 1 or later (including daily channel), you will be unable to switch back to Ubuntu Touch 24.04-1.0 using UI. Please follow this instruction to use UBports Installer to re-install Ubuntu Touch 24.04-1.0.

• It is known that Sony Xperia X doesn't boot Ubuntu Touch 24.04-1.x images. This has been known since before 24.04-1.0 release, but due to administrative mistake, the list of device on our release announcement was not updated. The release announcement blog has since been updated. Due to its age, we're unable to guarantee if we'll be able to restore support for Sony Xperia X within 24.04-1.x releases or not. We're sorry for your inconvenience.

@Charly said in Call for testing: Ubuntu Touch 24.04-1.1:

Hello forum,

Since 24.04-1.1 rc1 I noticed that my micro SD card is read only mounted. I use a Volla X23.

Is this issue known?

I'm unable to reproduce this issue. There's actually a number of reasons a storage could be mounted read-only; could you please try switching back to 24.04-1.x Stable channel and see if the issue goes away?

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

1. Boot to bootloader by pressing Volume Up + Power (or Volume Up + plugging cable), then select "Enter fastboot menu". Do not enter recovery.
2. Starts UBports Installer, then manually select "Volla Phone 22" (the Installer currently cannot auto-detect device model in bootloader mode).
3. Select "24.04-1.x Stable" channel and ensure "Bootstrap" option is checked. Leave "Wipe Userdata" unchecked.
4. Follow further instructions from the Installer.

@gpatel-fr said in Call for testing: Ubuntu Touch 24.04-1.1:

@peat_psuwit said in Call for testing: Ubuntu Touch 24.04-1.1:

send file journal.log?

attached.
Note that I know why there are deny messages for ntp servers. It's the firewall on my installation (not ufw - a site firewall) blocking ntp for devices on wifi (these devices can only ping and https/https)
journal.log

Thank you for the log. While it gives me some information, unfortunately this log does not show the issue being reproduced. I'm going to include some changes in 24.04-1.2 which should makes this happen less often, but I won't be able to guarantee that it actually fixes the issue.

Since you mentioned NTP being blocked on your local network, it's probably worth mentioning that we currently don't use date & time given by cellular towers; the only way we can automatically set date & time is through NTP over either Wi-Fi or mobile data. Although in your case, I suspect that systemd-timesyncd (NTP client) doesn't react well with changing network conditions, which is why disabling and re-enabling mobile data doesn't help.

@adorsaz said in Call for testing: Ubuntu Touch 24.04-1.1:

On a Fairphone 4, I've migrated from daily build (19th October) to this RC, I confirm I am still able to use VoLTE to make a call.

Although I cannot send SMS to recipient with phone number formated with my country prefix (+41).
I share log here with redacted recipient phone number:

sms_send.log

Edit: during the day I was able to receive VoLTE call and receive SMS.

We're going to land a change that could help with this in tomorrow's 24.04-1.x daily image. If possible, please switch to 24.04-1.x daily channel and see if you can now send an SMS. If this is successful, we're going to have another RC image.

@lk108 said in Call for testing: Ubuntu Touch 24.04-1.1:

In xenial and focal, the clearPersistent DBus method of com.Lomiri.Postal required the appid and the tag as a string. In 24.04-1.0, the tag(s) had to be passed as array of strings. Is it correct that this has been reverted and tags are passed as strings instead of an array of strings to clearPersistent?

That's sort-of correct. The change is "reverted" - more accurately, we made it so that the change seems to be reverted for applications which clear 1 tag at a time (which most applications do).

The full story is: originally, clearPersistent accepted not an appid and a tag, but an appid followed by an arbitrary amount of tags. Yes, for some reason, Canonical made the original clearPersistent accepts, for lack of better terms, "variadic arguments".

But this is very unusual in the DBus ecosystem. When we first migrated lomiri-push-service, a Go code, to the new DBus library (godbus/dbus), we didn't notice this weird pattern and assumed that the function accepted a list. Once we noticed this, we attempted to restore it, only to discover that it's not simple to support "variadic arguments" using godbus/dbus.

So we've decided on a compromise: we've discovered that, outside of our own code, most callers of clearPersistent pass only 1 tag to it. So, starting with 24.04-1.1, clearPersistent accepts exactly 1 appid and 1 tag, which should unbreak most unmodified applications. For those that actually pass multiple tags to clearPersistent, we now have clearPersistentList which accepts an appid followed by an array of tags.

"Technically", this DBus API is private and applications are supposed to use Lomiri.PushNotifications QML type. In practice, there are applications which need to call this DBus API from C++ or Rust. So we want to maintain compatibility where it makes sense.

This MR summarize the state of both functions in various versions of Ubuntu Touch, and also serves as an example on how one can support multiple versions of DBus methods.

Side note: I see in DeltaTouch codebase that you call QSysInfo::productVersion(). Please note that this function (currently) returns the version of the underlying Ubuntu version and not necessarily the version of Ubuntu Touch. With the new release scheme, we could have multiple Ubuntu Touch (major) versions be based on the same Ubuntu version. Please use other kinds of detections (such as what we outlined in the MR) instead.

@gpatel-fr said in Call for testing: Ubuntu Touch 24.04-1.1:

@peat_psuwit

Switched from 24.04.1 daily to RC on my newly installed FP5
Noticed 3 details:

1. the noise generated by keys, for example on unlocking the screen. Fixed it by going to settings and unsetting the option. Either the updated enabled the sound (and it's a bug) or the sound was enabled and it was not generated (in this case a bug was fixed)

Could you please elaborate on "noise" and "keys"?

2. no more hour from the network so I'm back in 1970. Tried to reboot, switched off and on the cellular data, no change

3. no more Store

I think that 3) comes from 2) in fact (the certificates for all sites are not yet valid)

There's some intricate interactions in the way clocks are managed on Qualcomm devices such as FP5. Could you please collect logs using the following command and send file journal.log?

sudo journalctl --boot \
    --identifier=systemd \
    --identifier=timekeeper \
    --identifier=systemd-timesyncd \
    >journal.log

@gpatel-fr said in Call for testing: Ubuntu Touch 24.04-1.1:

@peat_psuwit

automatic screen rotation does not work for me with RC (FP5)

In fairness, I have spent only 2 days with 24.04 stable and one day with 24.04 daily so I can't be 100% sure that rotation worked with daily. However I'm sure that it was working at least with stable.
I think that it was working with daily because it's something one notice very fast normally. And yes the setting 'rotation lock' is disabled and enabling/disabling it did not restore automatic screen rotation.

I did not look carefully in the sensor app at the gyroscope output so I'm not sure if something is wrong here - the changes are happening so fast that it's almost impossible to evaluate.

I cannot reproduce this on my FP5.

That said, it's weird that you start having these problems after switching from Daily channel to RC channel. Images in the RC channel are actually images from Daily channel being copied to RC channel. So I have no idea why that happens...

@adorsaz said in Call for testing: Ubuntu Touch 24.04-1.1:

On a Fairphone 4, I've migrated from daily build (19th October) to this RC, I confirm I am still able to use VoLTE to make a call.

Although I cannot send SMS to recipient with phone number formated with my country prefix (+41).
I share log here with redacted recipient phone number:

sms_send.log

Edit: during the day I was able to receive VoLTE call and receive SMS.

There are some changes in how we send SMS over VoLTE recent. It's possible that this is the cause.

CC: @mariogrip -- the log seems to indicate that QCom-side IMS service wants a "fallback"?

@lazarus said in Call for testing: Ubuntu Touch 24.04-1.1:

@peat_psuwit Tried to install the 24.04-1.x channel release on my Sony Xperia X using the UBports installer. Installing was completed, but after reboot the device hangs at the white "Sony" screen for multiple minutes and won't boot any further.

Staying connected to the PC I can see the network connection established via USB, but I can't connect to 10.15.19.82 using ssh.

It's known that Sony Xperia X doesn't boot 24.04-1.x images. We're still investigating this issue. This is the reason we don't publish a stable image for Sony Xperia X yet.

I think I myself forgot to put it into the latest previous announcement... yeah, sorry about that. We'll fix the announcement.

@lduboeuf said in Call for testing: Ubuntu Touch 24.04-1.1:

@peat_psuwit
I think an update of Telegram is needed for the notifications list not cleared fix

The Teleports update should not be needed for this to be fixed, at least in the specific case of Teleports.

Update 18 November 2025 (2): Apologize for the mistake. We've published Ubuntu Touch 20.04 OTA-11 RC 2 to include a fix for sending SMS on some VoLTE-enabled devices.. The release date for Ubuntu Touch 20.04 OTA-11 is still 25 November 2025.

---

We've just released the RC image for the Ubuntu Touch 20.04 OTA-11. Please take some time to switch your spare/development phone to the 20.04 RC channel and test this OTA.

Ubuntu Touch 20.04 OTA-11 is a maintenance release of 20.04 series. This release contains mostly bug fixes and small improvements. The notable ones are:

• USB-C headset support is now also enabled on 20.04 series as well.
• Fix audio playback not automatically stopped when a Bluetooth headset is disconnected.

Please note that only critical and security fixes will be able to enter Ubuntu Touch 20.04 OTA-11 as this point. Normal bug fixes and new features will need to wait for our next release. Please do not discuss normal bug fixes and new features here.

Ubuntu Touch 20.04 OTA-11 is expected to be released on 13 November 2025. We appreciate all testing we will receive.

---

At the same time, we've also released the RC image for Ubuntu Touch 24.04-1.1. We have a dedicated forum post. Note: please refrain from discussing Ubuntu Touch 24.04-1.1 in this post.

Update 18 November 2025

• Ubuntu Touch 24.04-1.1 RC 2 is now available for testing. This release fixes:
  • Issues with voice calls on Volla Phone 22.
  • Crash in Messaging app when attempting to play an attached video or audio.
  • Sending SMS on some VoLTE-enabled devices.

The new release date for Ubuntu Touch 24.04-1.1 is 25 November 2025.

• Due to a migration in Volla Phone 22's hardware abstraction layer (HAL), after receiving Ubuntu Touch 24.04-1.1 RC 1 or later (including daily channel), you will be unable to switch back to Ubuntu Touch 24.04-1.0 using UI. Please follow this instruction to use UBports Installer to re-install Ubuntu Touch 24.04-1.0.

• It is known that Sony Xperia X doesn't boot Ubuntu Touch 24.04-1.x images. This has been known since before 24.04-1.0 release, but due to administrative mistake, the list of device on our release announcement was not updated. The release announcement blog has since been updated. Due to its age, we're unable to guarantee if we'll be able to restore support for Sony Xperia X within 24.04-1.x releases or not. We're sorry for your inconvenience.

---

We've just released the RC image for Ubuntu Touch 24.04-1.1. Please take some time to switch your spare/development phone to the 24.04-1.x RC channel and test this update.

Ubuntu Touch 24.04-1.1 is a maintenance release of 24.04-1.x series. This release contains mostly bug fixes and small improvements. The notable ones are:

• Improved startup time on first boot after upgrading from Ubuntu Touch 20.04 series.
• Fix media scanning daemon getting stuck at 100% CPU usage, draining battery.
• Fix notification badges not appearing in the launcher for Phone and Messaging app.
• Fix applications e.g. TELEports unable to clear notifications before placing a new one.
• Fix incorrect calendar being shown in the pull-down (indicator) menu.
• Fix certain applications using embedded web browser crashing after attempting to use the browser.
• Fix Wi-Fi hotspot being broken on certain devices.
• Prevents deleted Wi-Fi or VPN connection re-appearing after reboot.
• General bug fixes and security updates.

To receive Ubuntu Touch 24.04-1.1 on a device running Ubuntu Touch 24.04-1.0, heads to System Settings -> Updates -> Update Settings -> Release Channel, then select "24.04-1.x Release candidate". Go back to the previous page, and then install the available update.

If your phone is running Ubuntu Touch 20.04 OTA-10, you can receive Ubuntu Touch 24.04-1.1 by first following the instructions above (but select "20.04 Release candidate" instead), then go to System Settings > Update again to upgrade to 24.04-1.1 RC.

Please note that only critical and security fixes will be able to enter Ubuntu Touch 24.04-1.1 as this point. Normal bug fixes and new features will need to wait for our next release. Please do not discuss normal bug fixes and new features here.

Ubuntu Touch 24.04-1.1 is expected to be released on 13 November 2025. We appreciate all testing we will receive.

---

At the same time, we've also released the RC image for Ubuntu Touch 20.04 OTA-11. We have a dedicated forum post. Note: please refrain from discussing Ubuntu Touch 20.04 OTA-11 in this post.