@giampy Same issue with my xperia x, the battery drains faster now, after ota16.
@hsabun I wonder how you use your phones. I have my xperia X connected to wifi all day and I don't notice difference in battery. I usually charge once day and get around 18-24 hours per full charge.
@kugiigi If you used the phone with the sim card you would notice the pain. My Xperia X is for daily use on stable channel.
@giampy Yes, I have a sim card. It's my daily driver too. I don't use mobile data though, just wifi since I'm always at home these days I'm not a heavy user but I use from time to time for browsing, email, and telegram.
@kugiigi Apparently we have found the problem, the data connection with the sim card.
AppLee last edited by
Mobile data is known to drain the battery faster than WIFI (especially 4G) but that doesn't explain how OTA16 may have changed something.
The power consumption for the modem should not have changed...
Keneda last edited by Keneda
This is the same on my phone, that's why i run most of time on 3G and only switch to 4G when i need more bandwich (more bandwich = more energy).
Wifi consume less because you are near source (most of time at home), so power needed is lower for same bandwich.
This probably also has to do with frequencies used in each case.
AppLee last edited by
@kugiigi my Xperia x i don't use it as a daily driver, but it does get a sim and always on wifi. Prior to otp 16, I easily lasted for more than 48 hours, but now it's like 30-34 hours.
I also estimate the higher loss at about 30%.
It's not a big deal for me either, but in the blog <the release of Ubuntu Touch OTA-16> an improvement in battery life on the Xperia X was announced.
Translated with www.DeepL.com/Translator (free version)
Maybe it's related to the latest kernel changes (Jan and Feb):
@c4pp4 This sounds like a clue, because I changed directly in the <stable channel> from OTA-15 to OTA-16. So without fluent update in the <developer channel>.
@mario-ch Look how many changes was made in a couple of days so I think fluent update wouldn't help.
@c4pp4 I meant that I noticed the difference, between 2 Dec 20 to 15 Mar 2021 better than if I had done the small updates week by week.
@mario-ch I know what you mean but e.g.:
Jan 21 - 7 commits
Jan 24 - 7 commits
Jan 27 - 13 commits
Jan 29 - 13 commits
Jan 31 - 17 commits
No chance to recognize when the change was made.
After discussing here, my Xperia X just went down to 20% in just 13 hours
Do you have apps that is always running on your phone? Mine is usually TELEports and Pesbuk.
c4pp4 last edited by c4pp4
Recent changes of CPU governors related to suzu:
This governor will scale the number of CPUs online depending on both CPU load and the number of runnable threads with careful but simple and precise calculations.
This governor makes decisions based on the utilization data provided by the scheduler. It sets the CPU frequency to be proportional to the utilization/capacity ratio coming from the scheduler. If the utilization is frequency-invariant, the new frequency is also proportional to the maximum available frequency. If that is not the case, it is proportional to the current frequency of the CPU. The frequency tipping point is at utilization/capacity equal to 80% in both cases.
Maybe @fredldotme could bring back availability of previous default governor, I'm not sure if it was "interactive" or what. Then we can try to test it via command:
echo "interactive" | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
fredldotme last edited by
I got mixed responses from the recent Xperia X work. Some say battery life has improved, now some claim it got worse. Generally those who got worse battery life had suspension prevention enabled in some apps.
@c4pp4 I'm not sure that schedutil is at fault here. Also we need it as it sets CPU frequencies in a kthread context, which is required for some mutexes to work correctly and not drag down the system into a panic.
You could try reverting this commit locally and see for yourself if it's due to the way the CPU is actually idling: https://github.com/fredldotme/device-kernel-loire/commit/84d9466cc10cc869b3a19086208cf4c6c59ef9b0
IMPORTANT: You will lose the ability to get notifications on time.
I'd rather suggest not using suspension prevention in UTTT as that's not a supported configuration for exactly this reason.