Update 4 May 2026: We've published Ubuntu Touch 24.04-1.3 RC 3 which fixes the regression regarding sensor support. We hope that this is the final RC; Ubuntu Touch 24.04-1.3 is still scheduled to be released on 7 May 2026.

@gpatel-fr said:

BTW 2: I have done already 3 back and forth between 1.2 and 1.3 RC2 and I have trouble reproducing the problem, that is, I have seen the problem in my last reinstall of 1.2 . Color me baffled

I have tested on my side and I can indeed reproduce the problem on both 24.04-1.2 and 24.04-1.3 RC 2. So this is likely a problem on the Gallery app and not on the Ubuntu Touch per-se. As such, we'll fix this issue on the Gallery app and will publish the update on OpenStore in the future. A GitLab issue is opened at: https://gitlab.com/ubports/development/apps/lomiri-gallery-app/-/work_items/130

Thank you you and @linus67 for bringing this issue up.

@gpatel-fr said:

BTW this does not look normal: the version is not incremented while there is about 500 LOC added in the RC version.

How did you determine that? I see the exact number of LoC [^1] on both 24.04-1.2, 24.04-1.3 RC 2 and 24.04-2.x daily images.

[^1]: determined with find /usr/share/click/preinstalled/gallery.ubports/3.1.1 -type f -print0 | wc --files0-from=- | tail -1

@gpatel-fr said:

After looking at the MRs, there is one (1) change since 2 years. I don't see anything else but it's not a small change, rather a collection of logically unrelated changes.

@peat_psuwit
should not a 'stable' branch (something like 24-04-1.x that IIRC exist in some other repos) be in the repo and changes be backported only after having seen some testing in the 'unstable' branch ?

Unlike system components and some system apps, Gallery app is a Click application where updates are shipped from OpenStore. And said change has not been released to OpenStore yet, so I'm pretty sure it has not made it to 24.04-1.3.

I'll look into this problem in more detail. Since this is a regression, I'll try to fix this problem before the release of 24.04-1.3.

@adorsaz said:

I noticed one regression: in the top bar, the cellular network indicator (the triangle on the right of Bluetooth icon) is always empty. It does not report the signal strength. Fortunately calls/SMS work like I reported above.

@Equareo said:

same signal issue on fp4, the bar is empty in areas with "bad" connection and half bar where it usually is full. i also get full bar in some areas, but the threshold has changed. Devel from 06.04.26 did not have that issue.

I've asked one of the developers in the relevant area to look into this. Although, given that this is a cosmetic issue, it might not be fixed before 24.04-1.3 is released.

Update 25 April 2026: We've published Ubuntu Touch 24.04-1.3 RC 2 which includes necessary updates for the upcoming Volla Phone Plinius.

We've just released the RC image for Ubuntu Touch 24.04-1.3. 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.3 is a maintenance release of 24.04-1.x series. This release contains mostly bug fixes and small improvements. The notable ones are:

• Improved handling of desktop apps, including:
  • Allow launching X11 apps outside of Lomiri (e.g. from OpenStore/Snapz0r).
  • Fixed dangling placeholder windows and launcher entry when launching X11 apps.
  • Fixed launching applications written using GTK4.
• Improved handling of docks with input devices such as NexDock.
• Fixed playing back AMR voice message sent via MMS.
• Fixed scaling factor being slightly off in certain applications (in particular apps which use Qt auto scaling or embeded webview).
• Fixed shutdown hanging on some devices.
• General bug fixes and security updates.

To receive Ubuntu Touch 24.04-1.3 on a device running Ubuntu Touch 24.04-1.0 and later, 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-11, you can receive Ubuntu Touch 24.04-1.3 RC by first upgrading to Ubuntu Touch 24.04-1.2 first, then follow the above instructions.

Please note that only critical and security fixes will be able to enter Ubuntu Touch 24.04-1.3 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.3 is expected to be released on 7 May 2026. We appreciate all testing we will receive.

---

Note: there's no Ubuntu Touch 20.04 OTA available for testing at this time.

@OtaDr said in Call for testing: Ubuntu Touch 24.04-1.2:

I'm wondering if the problem regarding the reported loss of handsfree via Bluetooth has been resolved? Thanks for the info.

I'm not aware of a Bluetooth-related issue being fixed in this release. Could you please provide me with a reference to the report?

@kristatos said in Call for testing: Ubuntu Touch 24.04-1.2:

@OtaDr Reported where? I never had a functional handsfree with UT. And I am on UT since 2015 with several devices and several software-versions and several cars with different infotainment-systems

Handsfree voice call has been broken and fixed several times in the life of Ubuntu Touch, a number of times by me . So I'm sorry to hear that handsfree has never been working for you. The challenge of Bluetooth handsfree support is the sheer number of handset vendors who could have their own quirks & behaviors, so it's really hard to get all of them tested.

May I know which device do you have?

Ubuntu Touch 20.04 OTA-12 is released. Thank you everyone for testing.

https://ubports.com/blog/ubports-news-1/ubuntu-touch-24-04-1-2-and-20-04-ota-12-release-3987

Ubuntu Touch 24.04-1.2 is released. Thank you everyone for testing.

https://ubports.com/blog/ubports-news-1/ubuntu-touch-24-04-1-2-and-20-04-ota-12-release-3987

@Moem said in Call for testing: Ubuntu Touch 24.04-1.2:

This is odd, but in a good way. I just switched back to 1.x RC to test, and I can report that my Pebbles now work! The oddness is: when it didn't work, RC 1.2 was already out, but apparently I was on RC 1.1 somehow.

I don't care very much, I'm just happy to report that it works

Thank you for additional testing. At least we know it's not a regression.

@DJac said in Call for testing: Ubuntu Touch 24.04-1.2:

@Vlad-Nirky the same probleme was report :
https://forums.ubports.com/topic/11938/anyone-else-is-having-wrong-caller-id-when-receiving-a-cal/6
no solutions actualy, but a Git issue is open.
https://gitlab.com/ubports/development/core/packaging/ofono/-/issues/3

Thank you for bringing up reported issue. Preliminary investigation showed that the problem does not seem to be caused by changes introduced between 24.04-1.1 and 24.04-1.2. We're going to continue investigation in the issue mentioned in the quote.

@DJac said in Call for testing: Ubuntu Touch 24.04-1.2:

I notice no vibration on sony xperia X. (at start, with keyboard...). Is it a probleme on my device or with the 24.04-1.2 RC (1 & 2) ?

We've discussed about this issue in a meeting, and have decided to not hold Ubuntu Touch 24.04-1.2 for Xperia X based on this issue, as it's better for Xperia X to receive up-to-date software, even if it's not perfect.

We'll continue to look into this; I've filed a GitLab issue for this.

@Moem said in Call for testing: Ubuntu Touch 24.04-1.2:

@Vlad-Nirky Okay, those were instructions I could follow... thank you.

journalctl.log

Not sure this will help since I'm now back on Stable.

Thank you for the log (also thanks @vlad-nirky for a better instructions ). To help me pin point relevant log lines, could you please give me the approximated date and time you switched to RC and from RC, in your (device's) timezone?

@Moem said in Call for testing: Ubuntu Touch 24.04-1.2:

I have a Bluetooth problem on this RC. It does not see most of my Pebbles and can't connect to them. I'm now back on Stable and my Pebble Time connects just fine.

This is weird, as there are no changes related to Bluetooth merged in this release. Could you please collect logs using the following command over ADB or SSH, then pull the file over USB?

sudo journalctl --boot --grep 'blue' >Downloads/journalctl.log

Update 12 February 2026: we've published Ubuntu Touch 24.04-1.2 RC 2 which contain a fix for audio issue on Sony Xperia X.

@messayisto said in Call for testing: Ubuntu Touch 24.04-1.2:

@peat_psuwit I managed to install on my sony xperia x - awesome!!! Any special thing to test?
There is no sound at all. In terminal the command alsamixer gives an error: cannot load mixer controls: no such device.

@DJac said in Call for testing: Ubuntu Touch 24.04-1.2:

on Sony xperia X :
whats newly works in 24.04 :
whats not work now : sound
whats already not works : fingerprint, usb connection sharing.
whats already works : accelerometre, compass, rotation, orientation, gps, ambiante light, light (thanks to sensor status app), bluetooth, wifi, call, mobile data, sms, front camera, external storage, video, file tranfert, connectivity with computer, wifi acces point, sceen rotation.
can't confirme : principal camera (broken on my phone) fm radio (no app existing), wireless monitor, nfc, volte

it happens that the device made two boots (blocking on sony windows during 1-2 mn and reboot automaticaly)

Thank both of you for reporting. I've asked the port maintainer (Alfred) to have a further look at this. As sound and voice call is a relatively important thing, if we're unable to solve this by this release we'll continue to withhold Ubuntu Touch 24.04-1.2 from Xperia X in the stable channel.

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

@peat_psuwit
Hello.
No issues with usage, but my impression is that the battery drains faster than with the previous version.
Generally, I can go four days without any issues, but currently, in two days, I've gone from 100% to 17%.
Xiaomi Redmi Note 9 Pro (as you know).
How can I objectively assess this?

You could try switching back to stable channel in System Settings and see if it improves the situation. That said, looking at the list of changes landing in the image, I don't see anything that could affect battery life, so it's possible this is port-specific too.

@x.Dub said in Call for testing: Ubuntu Touch 24.04-1.2:

Hi
I am using the Asus Zenfone Max Pro M1 in dual sim mode.
For 24.04-1.2 RC

Fix and works:

• Switching mobile data SIM

Not working and broken:

• Reconnect to mobile data after phone call longer than 3 minutes.
• VoLTE
• Receiving SMS when mobile data is turned on and the modem is in a mode other than 2G. (If mobile data is turned off and the SIM card is switched to 2G mode, SMS receiving works normally.)

Do they happen recently with this update?

We've just released the RC image for the Ubuntu Touch 20.04 OTA-12. 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-12 is a maintenance release of 20.04 series. This release contains mostly bug fixes and small improvements. The notable ones are:

• Improve mobile data stability when VoLTE is active on some carrier.
• Further fixes for importing .ics calendar event files.

Please note that only critical and security fixes will be able to enter Ubuntu Touch 20.04 OTA-12 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.

Note: As we're pivoting our resources towards Ubuntu Touch 24.04-1.x and 24.04-2.x series, we're reducing the frequency of updates to Ubuntu Touch 20.04 series. It's likely that future updates to 20.04 series will occur only as needed. We recommend you to upgrade to Ubuntu Touch 24.04-1.1 or newer if this is viable for you.

Ubuntu Touch 20.04 OTA-12 is expected to be released on 19 February 2026. We appreciate all testing we will receive.

---

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

Update 12 February 2026: we've published Ubuntu Touch 24.04-1.2 RC 2 which contain a fix for audio issue on Sony Xperia X.

---

We've just released the RC image for Ubuntu Touch 24.04-1.2. 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.2 is a maintenance release of 24.04-1.x series. This release contains mostly bug fixes and small improvements. The notable ones are:

• Fixes booting Ubuntu Touch on Sony Xperia X.
  • Due to my Sony Xperia X starting to give up, I was not able to fully test this. Users of Sony Xperia X could help by testing this out.
• Improves mobile data stability when VoLTE is active on some carrier.
• Fixes receiving "cell broadcast" messages on multiple devices.
• Fixes deleting online accounts leaving calendars behind in Calendar app.
• Fixes switching mobile data SIM on some dual-SIM devices.
• Further fixes for importing .ics calendar event files.
• General bug fixes and security updates.

To receive Ubuntu Touch 24.04-1.2 on a device running Ubuntu Touch 24.04-1.0 or newer, 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-11, you can receive Ubuntu Touch 24.04-1.2 RC 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.2 RC.

Please note that only critical and security fixes will be able to enter Ubuntu Touch 24.04-1.2 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.2 is expected to be released on 19 February 2026. We appreciate all testing we will receive.

---

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

@klh said in My Ubuntu Touch devices participated in Thailand nationwide cell broadcast test:

@peat_psuwit do you have a spec for the Thai EBS? Looks like they require a working SIM card?

I have no idea where to look for that. I tried searching on web for it, but nothing that look like it. The only thing I can go by is Android's config file.

I still maintain that we'll need a CB topic database from e.g. Android and should not not rely on hardcoded set of topics from a non-regional specification.

In theory we should only need the table from 9.4.1.2.2 of 3GPP TS 23.041.

Hmm interesting. That spec does indeed list all topics I've seen on my Android phone. I think I've seen a different spec cited earlier that doesn't include some of them.

(For reference, I've seen the following topics: 4370, 4371, 4372, 4384, 4396)

Still, it doesn't seem to provide a grouping of topics for settings (or maybe I miss something). And it would also be useful to have a database for notification heading (e.g. in US the title for 4370 should be "Presidential alert", but that obviously won't fly for Thailand).

Unfortunately, the test today is inconclusive on whether we need to explicitly subscribe to topic "4370" or not.

We don't already? According to the same table, 4370 is not supposed to be settable by the user and always subscribed (I'm kind of extending the 3GPP definition of MMI here) so this shouldn't be a question - since afaik it's not required to be implemented at modem level, we should check what ofono reports and subscribe to the missing ones.

It's not supposed to be settable, but this doesn't seem to be enforced by oFono. Currently our settings pane doesn't subscribe to this topic, but apparently Fairphone 5 subscribes to this topic anyway. Still, I reckon that we should be on the safe side and always add 4370 to the list of subscribed topics.

Also, currently there's no boot-time component which will subscribe to mandatory topics automatically (and on some region e.g. Thailand this doesn't seem to be limited to 4370 only; see the linked Android config). The settings pane is the only component which sets the topics. This is problematic because oFono don't have a set of initial topics (besides a small number of built-in ones from ETWS).

On 20 January 2026, Thailand government conducted a nationwide cell broadcast test. I've put my Ubuntu Touch devices to the test, and here are test results:

This requires some explanation:

• MR 34 refers to ofono-sailfish!34 which fixes how oFono dumps the raw CBS SMS from the network in case oFono fails to decode it.
• "Broad topic subscription" refers to me setting the subscribed topics beyond what is possible in Ubuntu Touch UI. Ubuntu Touch UI uses a hardcoded subset of CB topics, which does not include all topics I know exists for Thailand. More importantly, it does not include topic 4370 (National Alert) which supposedly should be always enabled.
• "Msg info" is pulled from my Android phone running Android 16, designated as the reference device which should always receive this CB.
• My Volla Phone 22 have a non-Thai SIM in it, and my Volla Phone X23 have a non-Thai and expired SIM in it. That's because that's all SIM I own...

There are a few notable things in this result:

• Interestingly, even though Fairphone 5 does not have "4370" topic subscribed in oFono, it still receives a broadcast with topic "4370". This may indicates that FP5's firmware does always subscribe to topic 4370.
• On the other hand, Volla Phone 22 which also does not have "4370" topic subscribed, does not receive the broadcast. Although, the SIM card I have in this device is actually a non-Thai one. So it's not clear if this device doesn't not receive a broadcast because the topic was not subscribed or because the device is in roaming mode.
  • In theory. roaming-ness should not affect the ability to receive broadcast. In practice, I don't know.
  • In hindsight, I should have swapped my Volla Phone Quintus to not have "broad topic subscription" and put it on my Volla Phone 22 instead, so it's clear what failure mode affects it.
• On both devices that does not receive broadcast, I do not see an indication in the log that it has received a broadcast but cannot decode it.

I still maintain that we'll need a CB topic database from e.g. Android and should not not rely on hardcoded set of topics from a non-regional specification. Unfortunately, the test today is inconclusive on whether we need to explicitly subscribe to topic "4370" or not.

That's it for today. I'll continue to watch the news and be prepared when the next round of testing happens.

@kugiigi NDK is basically a set of C APIs Android exposes to applications, allowing apps written in native code to get access to certain functionalities without calling Java APIs through JNI (Java Native Interface).

The good news is that these APIs should largely be usable on Halium-based UT devices as well. So the advantage is that we don't have to rely on bespoke APIs libhybris exposes, which allows us to share more code with upstream which already supports Android (in this case GStreamer).

This is not relevant to mainline devices.