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.

Update 30 September 2025: after debugging, we've decided that it's likely that the report where some devices fail to boot after installing Ubuntu Touch 24.04-1.0 RC 2 is likely a false positive. As such, it's been decided to go ahead with the release of 24.04-1.0.

Which means that Ubuntu Touch 24.04-1.0 is now released.

https://ubports.com/blog/ubports-news-1/ubuntu-touch-24-04-1-0-release-3973

Thank you for everyone involved in testing.

Update 25 September 2025: we've had a report where some devices fail to boot after installing Ubuntu Touch 24.04-1.0 RC 2, which requires us to delay the release of Ubuntu Touch 24.04-1.0. We're looking into it and will provide update as soon as possible.

Ubuntu Touch 20.04 OTA-10 is released! Thank you everyone involved in testing.

https://ubports.com/blog/ubports-news-1/ubuntu-touch-20-04-ota-10-release-3972

@Vlad-Nirky said in Call for testing: Ubuntu Touch 24.04-1.0:

@peat_psuwit
Hello.
I took some photos with my Xiaomi Redmi Note 9 Pro running UT 24.04-1.0 RC 1 during a few days of holiday.
The indoor photos are fine, but those taken outside are overexposed.
I restarted the phone, but that didn't change anything.

The image quality of the device largely depends on the hardware-specific code from device manufacturer; we don't have much control over it. As such, I would suggest you to ask your port's maintainers to take a closer look into this.

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

First impressions:
<...>
Telegram Notifications are nor overriden ( list is always growing)
<...>

You're saying that anewer notification from the same contact should replace the old one, but doesn't? That's probably lomiri-push-service as we have a big refactor there to migrate to a different DBus library. If you can turn this into a GitLab issue I would appreciate it. Otherwise I can do it too.

Update 19 September 2025: Ubuntu Touch 24.04-1.0 RC 2 has been released. This release fixes an issue with embedded webview in some applications and fixes changelog.

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

With Ubuntu Touch 24.04-1.0 nearing release, many app developers will probably want to make sure their applications are available after the users upgrade their phone. This post will answer a number of questions you might have in mind.

Before we continue: version terminology

Throughout this post, I may use 24.04-1.x and 24.04-1.0 interchangeably. Technically, 24.04-1.x is a series which represent 24.04-1.0, 24.04-1.1, 24.04-1.2 etc, while 24.04-1.0 is a specific version from the series. However, we intends to maintain application compatibility across all minor versions throughout 24.04-1.x series. So, from app developers perspective, what is true for 24.04-1.0 should be true for the entire 24.04-1.x series as well.

I will indicate if I say something that is applicable for 24.04-1.0 but not for the rest of the series.

Do I have to re-build my application against Ubuntu Touch 24.04-1.x?

Surprisingly, the answer is complicated. At the most basic level, applications built against Ubuntu Touch 20.04 will still be downloadable on OpenStore for 24.04-1.x users, and applications that has already been installed will still be available on users' devices. However, depends on how the application is built, it might run fine on Ubuntu Touch 24.04-1.x, or it might outright crash from the beginning.

The best way to answer this is to install Ubuntu Touch 24.04-1.0 RC 1 on one of your phone and then try to run your app on it. But the following are rules-of-thumb:

• If your application is completely QML-only: most likely, your application will just run fine on Ubuntu Touch 24.04-1.x. However, you may still have to slightly modify the code to stop using unsupported types. For example, if you use Lomiri.OnlineAccounts 0.1, you'll have to change that to SSO.OnlineAccounts 0.1 since the former is not supposed to be used, even on 20.04.
• If your application contains C or C++ code: now it depends on what library you're using:
  • If your app uses only Qt libraries (such as libQt5Core, libQt5Gui, libQt5Quick etc.), then your application should run fine, unless you use private symbols for them. [^1]
  • If your app uses other libraries, then we can't really say for sure if your application will work as-is; you'll have to test your application to be sure. In general, if your library's API/ABI is stable and used outside of Ubuntu Touch ecosystem (e.g. GLib), then chances are it'll work. But if you use some lesser-known one, then it's more likely that it won't.
  • The following non-exhaustive list of libraries lists libraries known to have API/ABI changed between 20.04 and 24.04-1.x and requires rebuild:
    • libssl1 (from OpenSSL)
    • Boost (if you use non-header-only parts; see here)
    • ICU (libicu*.so)
    • libtiff, libwebp
• If your application is written in Rust or Go and you use Qt or QML, then you'll almost certainly have to rebuild your application. This is because the integration between Rust/Go and Qt uses Qt's private symbols which have changed between Qt 5.12 (20.04) and 5.15 (24.04-1.x).

Note: if you intends to support armhf architecture (32-bit ARM), you'll have always have to recompile your application, as armhf binaries built against 20.04 will not run on 24.04-1.x. This is due to Ubuntu and Debian's 64-bit time_t transition. Note that there's currently no supported Ubuntu Touch devices with armhf architecture.

[^1]: Ideally, the sdk-libs and sdk-libs-dev seeds should defines what is stable for applications to consume. In practice, this list is poorly maintained and most people don't think about this when writing their applications. There are things that we should not promise, and there are things that we should have promised, but doesn't. So for now this list is advisory. Also so see Canonical-era wiki page about Click frameworks.

How do I build my applications against Ubuntu Touch 24.04-1.x?

The steps are:

1. Make sure you run Clickable version 8.4.0 or later, which include necessary fixes for uploading applications built against 24.04-1.x to OpenStore.
2. In clickable.yaml, specify ubuntu-touch-24.04-1.x as the framework:

framework: ubuntu-touch-24.04-1.x

Alternatively, specify framework using CLICKABLE_FRAMEWORK environment variable (useful for dual-building against both 20.04 and 24.04-1.x, see below).

export CLICKABLE_FRAMEWORK='ubuntu-touch-24.04-1.x'

3. In your manifest.json, make sure to specify framework as "@CLICK_FRAMEWORK@". Most applications is probably doing this already, but it's worth checking to be sure.

    "framework": "@CLICK_FRAMEWORK@",

4. In your AppArmor manifest file(s), specify policy_version as "@APPARMOR_POLICY@". This allows Clickable to fill in the correct AppArmor policy version corresponding to the Click framework. If you have multiple AppArmor manifiest files (e.g. for your main application and your push helper), make sure to update all of them.

    "policy_version": "@APPARMOR_POLICY@"

5. Run clickable build as usual. Now the application should be built against Ubuntu Touch 24.04-1.x.

Note that applications built against 24.04-1.x will not run on 20.04 devices. In fact, the device will outright refuse to install your Click. This is intended; your application might call APIs that has been added in between versions, so we prevent this to avoid surprises.

If I upload applications built against 24.04-1.x to OpenStore, will it be offered to devices running 20.04?

No. OpenStore will offer the latest version which is still compatible with a particular device. For example, if you uploaded version 1.2.2 built against 20.04, then subsequently upload version 1.3.0 built against 24.04-1.x, devices running 20.04 will receive version 1.2.2, while 24.04-1.x devices will receive version 1.3.0.

I want to provide updates for my app to 20.04 devices after I upload a new version for 24.04-1.x. Can I do that?

Yes. OpenStore has been updated to accept a new Click which is older than the current version, as long as the Click's framework is different. Using the previous example again, if you uploaded version 1.2.2 built against 20.04 then subsequently upload version 1.3.0 built against 24.04-1.x, you can then upload version 1.2.3 built against 20.04 and 20.04 devices will receive this update. At the same time, 1.3.0 will continue to be provided to 24.04-1.x users.

I want to provide the same versions but built against both 20.04 and 24.04-1.x. Can I do that?

Yes, with one caveat: your built Clicks must have unique versions.

Wait, that's a "no", isn't it?

Well, indeed. But here's the technique: with some configurations, you can build your application twice using the same code, and still get a different versions out of it. Here's the way I do it:

• Make manifest.json a "build-time configured file". Then, add a build-time flag to define a suffix to the version of the Click.
• In your build scripts/CI configuration, build your app twice, varying CLICKABLE_FRAMEWORK. This might be multiplied by architectures, so in practice you might build your apps 6 times.
• In clickable.yaml, set the Click's version suffix based on the ${SDK_FRAMEWORK} environment variable, which Clickable will set to the framework you defined earlier. Note that shell's command substitution/variable expansion is available for you, so you can modify this variable further.
• Make sure you leave "framework" in manifest.json as "@CLICK_FRAMEWORK@", and your "policy_version" in AppArmor manifest(s) as "@APPARMOR_POLICY@". This allows Clickable to fill in the appropriate values.

For a concrete example, see this lomiri-calendar-app MR.

Fun fact: Click package's version is not limited to just "major.minor.patch" format. Rather, it allows a full range of Debian package's version, including alphanumeric, ~, + and -. So you can include them in the version to help distinguish Git builds, Ubuntu Touch versions, and more.

My app currently doesn't build against 24.04-1.x. The version built against 20.04 doesn't start on 24.04-1.x due to missing libraries. I'm currently short on time. Is there a workaround?

There is one, indeed. Clickable has a feature to include libraries from the build environment into your Click (similar to Snapcraft's parts.<part-name>.stage). To do so, add the library names in the install-lib key of clickable.yml.

install_lib:
- libasound.so*

When your application is launched, system will make sure that your Click's library is added into LD_LIBRARY_PATH environment variable, which will make your app look into your Click first for any library it wants.

Note, however, that if you do this, you will want to make sure that the library you included is not actually depended on by one of the system library but under a different "soversion" [^2]. This is because 2 different soversions of the same library can have the same symbols; in that case, it's not guaranteed which version of the symbol will be used, and the behavior will be undefined [^3].

One way to check this is to install your Click on a 24.04-1.x device, then run:

LD_LIBRARY_PATH=/opt/click.ubuntu.com/<Click id>/current/lib/* \
  ldd /opt/click.ubuntu.com/<Click id>/current/<your app binary> | less

Then, inspect the output to make sure the same library with different "soversion" does not appear twice e.g. make sure libwebp.so.6 and libwebp.so.7 does not appear together.

(The exception to this rule is libicu*.so; ICU allows linking multiple versions of itself into one process by make sure all symbols have the version number appended. See ICU4C documentation.)

[^2]: "soversion" is the first version number after .so in the file name. For example, if a library has a file name libcurl.so.4, its "soversion" is 4.
[^3]: my understanding of the Click framework contract is that, if a library does not appear in sdk-libs or sdk-libs-dev, then you're supposed to bundle it in the Click package. However, due to this "soversion" clashing issue, I'm not sure this is the right approach to this problem...

---

I hope this post answers some of your questions and ease a migration of your apps to 24.04-1.x. If you have any question, feel free to leave a reply to this post and I'll try to answer them as best as I can.

Ubuntu Touch 24.04-1.0 RC 1 is available for testing.

Notable changes

• The dialog warning users to disable Wi-Fi before sending MMS has been removed due to false positives.
• You can now disconnect from wireless display from the virtual touchpad on the phone's screen.

(picture of the feature)

• Media playback control is fixed in the top-panel indicator, in applications, and over Bluetooth headset.
• Bug fixes and stability improvements across the system.

Known issues

• It's a long-standing issue that fingerprint sensor on Fairphone 5 does not always work. It's unclear when this might happen. This might manifest itself as keyboard for the login password prompt jumps up and down very rapidly; this is due to Lomiri repeatedly getting error from fingerprint sensor.
• You may still see a placeholder text as part of first boot's "What's new" page. We'll provide another update to fix the issue. (ubuntu-touch-meta#3)

If you're already running Ubuntu Touch 24.04-1.0 Beta 2, you'll be offered Ubuntu Touch 24.04-1.0 RC 1 automatically. Otherwise, follow the same instructions as outlined above.

Update 11 September 2025: Ubuntu Touch 20.04 OTA-10 RC 2 is published. This version includes fixes for various issues with Volla devices, along with a number of bug fixes.

The new target release date of Ubuntu Touch 20.04 OTA-10 is 25 September 2025 (the same date as Ubuntu Touch 24.04-1.0).

@Vlad-Nirky said in Call for testing: Ubuntu Touch 24.04-1.0:

In the latest build 24.04-2.x,

(Note that this thread is for 24.04-1.0 testing. 24.04-2.x is in early development and is not necessarily ready for testing.)

I noticed that when typing a sentence using the OSK, when you select a suggested word, it does not automatically add a space between the selected word and the rest of the text.

For the OSK issue, this seems to a side effect of us disabling Auto correction by default. If I enable "Auto correction" in 24.04-1.0, then selecting word suggestion adds a space. And if I disable "Auto correction" in 20.04, then the space isn't added either.

So for now you can enable "Auto correction" back on as a workaround. We'll probably fix this issue in a point release of 24.04-1.x series.

And the automatic brightness adjustment no longer works.
Xiaomi Redmi Note 9 Pro 24.04 r4

Sadly this one I cannot reproduce. I'm afraid you'll have to ask the port's maintainer for help on this one...