Looking for Testers: Ubuntu Touch 26.04-1.x (Early version)
-
@mariogrip
Here is an extract from yesterday’s journalctl.
I had several calls cut off, sometimes after just a few seconds of clear communication.
My wife’s number has been replaced with a random one.
journalctl_2026-06-16_ofono.txt -
FP 5 build 105
serious regression issue on mms ? have confirmed by switching back to 24.04-1.3 stable, can send and receive a mms to an Android phone, switch again to 26.04, failure to send and receive.
Astonishingly the Android phone report a failure to send (it has no issue sending to UT 24.04 or another Android phone). I say 'astonishingly' because I had always thought that MMS were asynchronous (the Android phone has RCS disabled)
On UT 26.04, trying to send a MMS leads to a spinning blue circle next to the text, spinning that never stops.
these tests were done in both cases with wifi OFF
(but it don't work better with wifi on)(I replaced the phone number of the UT phone by 26042604 and the one of the Android phone by 00000000)
-
Another problem: with Openstore 4.0, the store app fails to start.
After adding the following libraries back from a previous installation, it starts again:phablet@ubuntu-phablet:/opt/click.ubuntu.com/openstore.openstore-team/current/lib/aarch64-linux-gnu$ ls ~/Downloads/suppstore libicudata.so.74 libicudata.so.74.2 libicuuc.so.74 libicuuc.so.74.2 libxml2.so.2 libxml2.so.2.9.14 -
Please list the other devices that are capable to receive upgrade to 26.04-1.x .Previously Redmi note 9(merlin) worked with 26.04-1.x which has enough space.
-
yet another problem that I'm still investigating: push notifications. Still FP5 on build 111 now.
It has been exposed by me installing Deltatouch, the Ubuntu Touch client for DeltaChat.
It works well enough but needs a systemctl --user restart lomiri-push-helper to get any kind of notification (sending a text message to the UT phone is enough to show the problem).
Looking at the DeltaTouch repo, something like that has been reported, the maintainer has not been able to repro it reliably and asked for an issue to be created upstream that has been ignored.
With 26.04 the problem is very reproducible - rebooting several times, each time the notification don't work.
Needless to say, after switching back to 24.04-1.3, the notifications work fine (restart 2 times, each time the notification worked straight away without having to restart the service like in 26.04)
-
as noted elsewhere for 24.04-2, unstable now can provide the OSK to XWayland apps such as Chromium-UT, Min, UWolf.
-
as noted in latest Q&A, in 26.04 alternate browsers running in XWayland are now displayed as any other app in the launcher, no more 'X' icon.
-
gpatel-fr said:
libicudata.so.74
looking a bit more at this issue, this comes from the operating system upgrade: Ubuntu 24.04 comes with libicu74 while 26.04 uses libicu78.
Ubuntu 26.04 don't have libicu74, so don't seem to be able to use some binaries built for a previous Ubuntu version.
The use of snap in Ubuntu is something of a workaround for this problem I guess while click format was designed before the rise of snap/flatpak with their library packages.
-
FP5 build 137
Now it's the camera app that don't work anymore.
Like with the store, it's a missing library problem: libexiv2.so.27 called from libcamera-qml.so26.04 provides libexiv2-28, but contrary to libicu74 there is a compatibility layer in 26.04: libexiv2-27-compat, but it's not installed.
I don't see why this breakage appears only now. Was this libexiv2-27-compat library included previously in the rootfs and not anymore ? I am not keen on the idea of a regression test by installing a previous version of Ubuntu Touch 26.04 to check on that.
Anyway, getting the library from the compat package and doing an overlay to add it to the system solves this particular problem.
-
Device: Fairphone 5 (FP5)
OS Update Channel: 26.04-1.x/arm64/android9plus/daily
OS Build Number: 2026-07-01/2
Kernel: 5.4.302-qgki
Version: 144Installation Method:
Clean install using the UBports Installer (upgraded from a clean Android 13 installation).
Issues Encountered
Component Issue OpenStore Fails to start. No error messages displayed. Gallery Same as OpenStore, no response. Camera Stuck on loading spinner indefinitely. External Storage Card detected and formatted, but not mounted or visible in File Manager. WiFi Initial connection issues (randomly resolved after repeated attempts). Still unstable. Libertine Not functional. Snaps Unable to install GUI apps (e.g., Firefox, Chromium). qbittorrentinstalls but won’t launch.
Working Features
Component Status Calculator
Fully functional.Calendar
Works, including sync with self-hosted Radicale server.Clock
Fully functional.Contacts
Works, including sync with self-hosted Radicale server.Media Player
Starts successfully (video playback untested).Messaging
SMS sent/received successfully. (Note: Wife’s responses remain a work in progress.)Morph Browser
Fully functional.Music
Starts successfully (audio playback untested).Notes
Fully functional.Phone
Calls (incoming/outgoing) work.Terminal
Fully functional.Weather
Fully functional.Waydroid
Works well. (Note: Some apps cause overheating and ~20% battery drain/hour.)Cellular
Fully functional.Fingerprint Reader
Unlocking works.
A huge thank you to **@mariogrip ** and the entire UBports team for your incredible work on this project!
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login