Offline
@Moem said in Call for testing: Ubuntu Touch 24.04-1.2:
@Vlad-Nirky Okay, those were instructions I could follow... thank you.
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, volteit 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 RCFix 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:
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:
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:
There are a few notable things in this result:
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.
A few years ago, I've added a code into upstream GStreamer's androidmedia to utilize NDK APIs for MediaCodec, in hope that one day we'll be able to utilize that in Ubuntu Touch.
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/4115
This holiday, due to a brief exchange with @thekit during the last devsync, my mind wandered again and I've decided to implement additional codepath which utilize NDK APIs to render decoded buffers with OpenGL instead of Java-based SurfaceTexture.
https://gitlab.freedesktop.org/peat-psuwit/gstreamer/-/tree/aimagereader?ref_type=heads
The code "works" but is still littered with TODOs in error handlings and handling of pause state (also see TODOs in the commit message itself). Essentially this is a demo-level code.
With that branch, the only thing that still require Java/JNI is the codec listing. While NDK recently added the APIs for that, it lacks some function which GStreamer expects (e.g. the ability to query supported color format), so it'll stay as Java/JNI for now (or use libhybris-specific APIs if we bring that to Ubuntu Touch).
Also this won't quite work with current cross-process media decoding pipeline in Ubuntu Touch's media-hub. Some additional work is needed to transport buffers cross-process (and add necessary synchronization). But that will have to wait lots, lots longer...
But if you happen to have an Android phone and want to toy with this code, the steps are:
./cerbero-uninstalled -c config/cross-android-arm64.cbc -c ../localconfig.cbc -v norust package gstreamer-1.0
gst-android (or any folder)
- arm64
- lib
- share
- [...]
diff --git a/subprojects/gst-examples/playback/player/android/app/build.gradle b/subprojects/gst-examples/playback/player/android/app/build.gradle
index d8e000598e7..a66163a9a87 100644
--- a/subprojects/gst-examples/playback/player/android/app/build.gradle
+++ b/subprojects/gst-examples/playback/player/android/app/build.gradle
@@ -27,7 +27,7 @@ android {
targets "gstplayer"
// All archs except MIPS and MIPS64 are supported
- abiFilters 'armeabi-v7a', 'arm64-v8a', 'x86', 'x86_64'
+ abiFilters 'arm64-v8a'
}
}
}
@@ -47,6 +47,10 @@ android {
ndkVersion '25.2.9519653'
namespace 'org.freedesktop.gstreamer.play'
+
+ packagingOptions{
+ doNotStrip "**/libgstreamer_android.so"
+ }
}
afterEvaluate {
diff --git a/subprojects/gst-examples/playback/player/android/app/src/main/jni/CMakeLists.txt b/subprojects/gst-examples/playback/player/android/app/src/main/jni/CMakeLists.txt
index 79bdf8b80fd..fa027e35c58 100644
--- a/subprojects/gst-examples/playback/player/android/app/src/main/jni/CMakeLists.txt
+++ b/subprojects/gst-examples/playback/player/android/app/src/main/jni/CMakeLists.txt
@@ -26,10 +26,12 @@ set(GSTREAMER_NDK_BUILD_PATH "${GSTREAMER_ROOT}/share/gst-android/ndk-build/")
include("${GSTREAMER_NDK_BUILD_PATH}/plugins.cmake")
set(GSTREAMER_PLUGINS ${GSTREAMER_PLUGINS_CORE} ${GSTREAMER_PLUGINS_PLAYBACK} ${GSTREAMER_PLUGINS_CODECS} ${GSTREAMER_PLUGINS_NET} ${GSTREAMER_PLUGINS_SYS} ${GSTREAMER_PLUGINS_CODECS_RESTRICTED} ${GSTREAMER_CODECS_GPL} ${GSTREAMER_PLUGINS_ENCODING} ${GSTREAMER_PLUGINS_VIS} ${GSTREAMER_PLUGINS_EFFECTS} ${GSTREAMER_PLUGINS_NET_RESTRICTED})
set(GStreamer_EXTRA_DEPS gstreamer-play-1.0 gstreamer-player-1.0 gstreamer-video-1.0 glib-2.0)
+set(G_IO_MODULES openssl)
+
find_library(ANDROID_LIB android REQUIRED)
find_library(LOG_LIB log REQUIRED)
-find_package(GStreamerMobile COMPONENTS ${GSTREAMER_PLUGINS} fonts REQUIRED)
+find_package(GStreamerMobile COMPONENTS ${GSTREAMER_PLUGINS} fonts ca_certificates REQUIRED)
add_library(gstplayer SHARED player.c dummy.cpp)
target_link_libraries(gstplayer
Edit subprojects/gst-examples/playback/player/android/gradle.properties to point gstAndroidRoot to the directory you make in step 3.).
Open subprojects/gst-examples/playback/player/android in Android Studio and build the project.
Launch the example with:
adb shell am start -a android.intent.action.VIEW -d "https://test-videos.co.uk/vids/bigbuckbunny/webm/vp8/1080/Big_Buck_Bunny_1080_10s_5MB.webm" org.freedesktop.gstreamer.play
Feel free to replace the URL with another video, depending on what video codec is supported by your device. Note that currently H.26[45] doesn't work because of another GStreamer bug, so you'll likely want a VP[89] or AV1 videos.
Enjoy, I guess?
Ubuntu Touch 20.04 OTA-11 is released. Thank you everyone for testing.
https://ubports.com/blog/ubports-news-1/ubuntu-touch-24-04-1-1-and-20-04-ota-11-release-3984
Ubuntu Touch 24.04-1.1 is released. Thank you everyone for testing.
https://ubports.com/blog/ubports-news-1/ubuntu-touch-24-04-1-1-and-20-04-ota-11-release-3984
During the periodic scanning of the local media, gst-hybris gets loaded by Gstreamer, a media framework, to perform HW-accelerated video decoding. gst-hybris expected the rendering element ("sink") to be HW-accelerated as well, but media scanning does not use HW-accelerated rendering. This results in memory corruption, which could potentially be exploited by a specifically-crafted media.
The pipeline constructing process of Gstreamer is dynamic; it can automatically pick the demuxer, decoder(s), and sink(s) based on the file type, file content, and component's capability. In this case, Gstreamer picks gst-hybris' HW-accelerated decoder as the decoder, but "fakesink" as the sink (as the scanner only wants to know certain metadata).
Now, to perform HW-accelerated video rendering, gst-hybris has a dedicated sink which co-operate with the decoder in order to pass decoded video frame without copying the memory. When Gstreamer connects the decoder with the sink, the decoder can access the sink to perform necessary co-ordination. However, the decoder forgot to check if the sink it accesses is the one it can co-operate, which results in the code writing into the memory it's not supposed to access.
In order for this to be exploited, the video has to be on the device, which subsequently leads to it being scanned. Video playback in other cases is not affected, as they always use HW-accelerated video rendering.
CWE-843: Access of Resource Using Incompatible Type ('Type Confusion')
Severity: Medium
Starting in Ubuntu Touch 20.04 OTA-11 and 24.04-1.1, gst-hybris checks the type of the sink before casting to the expected type.
The issue was discovered on 30 September 2025, during a debugging of another issue.
The issue was discovered before the release of Ubuntu Touch 24.04-1.0, but we did not manage to work it through and fix it in time for that release.
Ubuntu Touch 20.04 OTA-11 and 24.04-1.1 was released on 1 December 2025, coordinated with the publication of this advisory.
@gandalf said in Call for testing: Ubuntu Touch 20.04 OTA-11:
After some more testing it seems that VoLTE is not working properly on my FP4. It shows up in the settings and status indicator but as soon as I make a call it drops back to 3G.
Is VoLTE officially part of this ota?
VoLTE on Fairphone 4 has been enabled at port level and should be available starting from Ubuntu Touch 24.04-1.1 and 20.04 OTA-11. That said, we're aware that our VoLTE code is not fully stable. This is something we'll work on in the future.
Update 26 November 2025: The release of Ubuntu Touch 24.04-1.1 and 20.04 OTA-11 has been delayed due to my personal situation (there has been flooding in my area). Now that the situation has improved, I'll now work on finalizing the release of both versions and get the update to the stable channels as soon as possible.
Update 26 November 2025: The release of Ubuntu Touch 24.04-1.1 and 20.04 OTA-11 has been delayed due to my personal situation (there has been flooding in my area). Now that the situation has improved, I'll now work on finalizing the release of both versions and get the update to the stable channels as soon as possible.
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
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?