Call for testing: Ubuntu Touch 24.04-1.3
-
On the subject of battery consumption. It is very difficult to compare battery consumption when devices are being used simultaneously.
I only test and compare battery consumption under identical conditions without active use (for example, at night)
7 hours in aeroplane mode
7 hours with only calls and texts active
7 hours with selected background services also active. (Selected apps, such as Dekko, or those with connections to NextCloud)Using this test method, I have not observed any increased battery consumption with RC 1.3.
-
I have just updated FP4 to 24.04-1.3. I noticed that the cellular network strength indicator remains an empty triangle (as if I have no mobile network connection). Phone calls, SMS and cellular data however work and the carrier is also shown in cellular settings. Any one else experienced this?
-
@nogoogle see post 63 in this thread, An I read it somewhere else, too, forgot where. But I think its a known issue.
-
@nogoogle see post 63 in this thread, An I read it somewhere else, too, forgot where. But I think its a known issue.
Thank you, despite searching the thread for "indicator" post 63 did not pop up.
-
@nogoogle At the right bottom corner you can see a blueish field. Scroll up to the number 63.
-
I've been using it on three Pixel 3a devices running 24.04-1.3 for over a week.
Test conducted without using any apps and with all background processes disabled.On all devices, I'm seeing significantly higher battery consumption when Wi-Fi is turned on.
I don't know if this is a general issue with the Pixel 3a or if it has to do with the current RC 1.3.
-
Taking a look at what ofono is providing:
gdbus monitor --system --dest org.ofono --object-path /ril_0 Monitoring signals on object /ril_0 owned by org.ofono The name org.ofono is owned by :1.12 /ril_0: org.ofono.NetworkRegistration.PropertyChanged ('Strength', <byte 0x1e>) /ril_0: org.ofono.NetworkRegistration.PropertyChanged ('Strength', <byte 0x0f>) /ril_0: org.ofono.NetworkRegistration.PropertyChanged ('Strength', <byte 0x23>) /ril_0: org.ofono.NetworkRegistration.PropertyChanged ('Strength', <byte 0x11>) /ril_0: org.ofono.NetworkRegistration.PropertyChanged ('Strength', <byte 0x25>) /ril_0: org.ofono.NetworkRegistration.PropertyChanged ('Strength', <byte 0x16>) /ril_0: org.ofono.NetworkRegistration.PropertyChanged ('Strength', <byte 0x25>) /ril_0: org.ofono.NetworkRegistration.PropertyChanged ('Strength', <byte 0x07>) /ril_0: org.ofono.NetworkRegistration.PropertyChanged ('Strength', <byte 0x19>) /ril_0: org.ofono.NetworkRegistration.PropertyChanged ('Strength', <byte 0x25>) /ril_0: org.ofono.NetworkRegistration.PropertyChanged ('Strength', <byte 0x16>)it's clear that the triangle is optimistic, when ofono is reporting 0x25 (that is a signal quality of 38% the display is showing a good quality (a casual observing would say 75% although estimating surfaces on a triangle is misleading)
However when rhe reported quality change, the triangle changes also; it's not either empty or full.
In this my observations on my phone don't confirm what you see.Since I had not yet this trick to get at the ofono reported quality before, I can't say if the triangle was already optimistic before 24.04-1.3.
I got the idea of getting my phone near a window and it jumped to 0x2f (that is 47% where the triangle was full.
Optimistic indeed. That said, is this a bug or a feature ? Maybe 50% is as good as it gets. -
Overall 24.04-1.2 seemed to work perfect in my day to day usage.
Whereas 1.3 has some occasional quirks/regressions/differences? that are noticeable to me but not breaking enough to remember or make a note of each of them while out at work.
This signal strength was a noticeable one, I know the nearest mast is not far away and I know what is displayed now is very different to 1.2. Which is correct/accurate is another matter, if it's correct that's fine but ultimately people want to know at a glance if they can make a call and an empty triangle with even poor signal is not a helpful indicator if a call would be possible. Is there a different symbol for no signal as I haven't seen it? I believe you have to pull down and look at the carrier showing "Searching..." for this?
Another change I can remember is cellular data, before I could open the default browser anywhere and just browse straight away. Now intermittently with no WiFi available the browser will not have a data connection, the quick way I found to resolve this is shuffle cellular data off and on again. -
Overall 24.04-1.2 seemed to work perfect in my day to day usage.
Whereas 1.3 has some occasional quirks/regressions/differences? that are noticeable to me but not breaking enough to remember or make a note of each of them while out at work.
This signal strength was a noticeable one, I know the nearest mast is not far away and I know what is displayed now is very different to 1.2. Which is correct/accurate is another matter, if it's correct that's fine but ultimately people want to know at a glance if they can make a call and an empty triangle with even poor signal is not a helpful indicator if a call would be possible. Is there a different symbol for no signal as I haven't seen it? I believe you have to pull down and look at the carrier showing "Searching..." for this?
Another change I can remember is cellular data, before I could open the default browser anywhere and just browse straight away. Now intermittently with no WiFi available the browser will not have a data connection, the quick way I found to resolve this is shuffle cellular data off and on again.I have noticed some similar things as well. Also having to reboot the phone way more often than normal because something gets funky. It's not like it's ALL the time, but it is a noticeable increase. I've also had the phone outright freeze completely when something too big in the browser was happening.
-
@projectmoon I can confirm this exactly. I have to reboot more often, today i.e. I couldnt stop a call, so every day something weird is happening. volla quintus, 24.04-1.3 rc
-
@ralf
I tested on three Pixel 3a devices for one week. No active use. All background services turned off. Location services and Bluetooth also turned off.The same behavior occurred on every device. When I turn on Wi-Fi, power consumption increases dramatically.
Without Wi-Fi: 1 to 2% per hour
With Wi-Fi: 4 to 6% per hour -
I found the reason for my increased battery drain when using Wi-Fi.
On January 26, 2026, I installed an app called "UB Connect" from the OpenStore. ubconnect
I uninstalled it shortly after. The app wasn't uninstalled cleanly, and a ubconnect.daemon.service remained in the system.
Whenever Wi-Fi was turned on, this daemon would automatically start, but it failed because the app was missing. This prevented Ubuntu Touch from going into power-saving mode after the screen was turned off.After uninstalling and deleting all leftover files from the ubconnect app, Ubuntu Touch goes back into power-saving mode with Wi-Fi on, and the battery consumption is minimal like with mobile data.
-
I've found the cause of the increased battery drain on Wi-Fi.
Clear the list of saved Wi-Fi connections:
Go to Wi-Fi -> Wi-Fi Settings -> Saved Networks and tap “Forget” next to all the networks. Then reconnect to your home Wi-Fi network. After that, battery drain in standby mode will return to a minimum of < 2% per hour. -
I've found the cause of the increased battery drain on Wi-Fi.
Clear the list of saved Wi-Fi connections:
Go to Wi-Fi -> Wi-Fi Settings -> Saved Networks and tap “Forget” next to all the networks. Then reconnect to your home Wi-Fi network. After that, battery drain in standby mode will return to a minimum of < 2% per hour.Did that and it seems to work. Battery drain is in normal levels again. Weird quirk, though...
-
This problem has been fixed in current code, since it was merged 8 days ago today it was before the cut for this release. Not sure if it will be scheduled for next stable 24.04 release.
-
I have added a comment on my MR to point that the bug existed before 1.3. I have managed to revert my phone to 1.1 and I see the exact same thing.
If anyone having a 20.04 phone read this, it would be interesting to check if this problem (switching the bluetooth indicator in the battery page has no effect) occurred on this old version.
-
gpatel-fr said:
fix it.
this Bluetooth indicator problem - that was not a regression at all in fact - is now fixed in 26.04 and the next stable version (24.04-1.4) will have it.
-
@peat_psuwit
Hello Ratchanan.
Could you say me if bzip2 was present in earlier version of 24.04-1.x and has been removed in this one? (Some problems with OSM Scout Server users) -
phablet@ubuntu-phablet:~$ sudo system-image-cli -i current build number: 3 device name: FP5 channel: 24.04-1.x/arm64/android9plus/stable last update: 2026-06-12 13:19:07 version version: 3 version tag: 24.04-1.2 version rootfs: 2026-02-12T03:59:17Z_arm64_ubports/24.04-1.x_175_718b9c58bd8802cacb5507b06d6e30c53aaea337 version keyring: archive-master version device: 20260211-25990 version boot: 20260211-10310 phablet@ubuntu-phablet:~$ bzip2 -bash: bzip2: command not found
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