The latest incident with high battery drainige was now when also mobile data started behaving badly (no 4G, no internet).
I got about 400-500mA constant drainige and I saw with CSD tool that instance /usr/sbin/ofonod was using 100,2%. It sounds a bit weird to my ears.
When I got mobile data working again with multitude of resets/flymodes, then ofonod wasn’t anymore at all on the list of power consumers. Drainige dropped to about 100mA.
The ofonod-cpu-guzzling-problem is wellknown and monitored. Hopefully a fix for that behaviour will be adressed for the next update(s).
As workaround you can restart the service:
devel-su systemctl restart ofono
Works for me every time it occurs.
In my case it will be triggered once a cold-boot/restart session.
WLAN<->Mobile Data/Bluetooth-Connection/Disconnection seem to trigger that.
I don’t have any info to share on this and it’s not usually pre-announced I’m afraid, but any announcements will be made here in the forum of course (and following @dcaliste’s repository roundup is also always a good idea too).
Is there a special link for the “repository roundup”, I’m not sure, what you mean?
GitHub - dcaliste/sailfishos-digest This is the page where @dcaliste summarizes the latest source code updates on a biweekly/monthly basis
Thanks for the link, I registered me for watching.
Did this pull request find its way in 4.4.0.72?
Most likely not, looking at the detailed changelog. But it will in 4.5.
Power consumption on my 10 III remains very bad. Holding the 10 III in one hand and the XA2 Ultra in the other, with only Battery Buddy or AIDA64 running (in order to see current draw), I always get TWICE the power consumption of the XA2U on the 10 III. In such conditions the XA2U current draw fluctuates between some 50-80 mA, whereas on the 10 III its lower limit is 110-115 mAh.
BTW, what is your /mnt/vendor/persist/battery/battery_cycle_count saying? Mine has already reached 42 full cycles, which is really worrying.
After using both XA2 (Ultra) and X10II and X10III for long time, I do agree that X10III has sub-optimal battery life. The idle current is a bit high indeed, but I don’t have good ideas how to diagnose the power users beyond basic command line stuff…and that resolution, or worse, permission level, may not be enough. Ve may have to dig ourselfs into the AOSP territory here…
Or if we’re lucky, just some device configuration may be incorrect. The CPU governor/frequency issue was hidden in plain sight for months at least, there may be other values to fix, too.
After many weeks of tests, I actually cannot see any perceptible difference when it comes to power consumption while using different governors (performance, schedutil, ondemand) or enabling 300 MHz as minumum frequency. Oddly, sometimes it actually turns to worse. And even if I see any improvement, it is actually so small that it’s not worth the hassle.
And it’s actually not a problem when the device is in sleep (when it goes as low as 35-40 mA if nothing wakes it up too often), the problem is when it is in use. Even light use, just holding it in hand with the display on is enough for it to eat 110-250 mA, with frequent spikes up to 500-600 or more. The XA2U with its huge and less power efficient display and 14 nm (i.e. probably also more power hungry) CPU draws 50-80 mA in such conditions.
My understanding is that the display consumption in 10iii depends with the background colour brightness . Have you tried using a dark theme?
Do you know by chance what is the best way to read out the cycle count on a XA2?
Sadly, excessive power consumption takes place even when the display is off, which can be checked using the terminal or via ssh, e.g.
The XA2 Ultra in same conditions still eats several times less energy (see the next post after the one quoted above for XA2U figures). So it’s not the screen.
On the XA2 Ultra it is in /sys/class/power_supply/battery/subsystem/bms/cycle_count (as well as a few copies/symlinks of it) in other locations
but it doesn’t work (as it always contains 0).
That while loop supposed to wake the phone every second to run a process, not sure how much it contributes to power consumption as practically the phone does not go to idle mode?
You can try to change it from one second to whatever else. Note, however, that if it goes to sleep then it probably won’t give you any output for that period of time.
Anyway, as I wrote earlier, the problem is not with idle, as in that state it goes as low as 30-40 mA. The actual problem is that WHEN IN USE it is an enormous energy hog, eating 2 or even 3 times more current than the XA2 Ultra in the same conditions.
My 10 III is actually a mirror of my XA2 Ultra - same data, same applications installed, even the same SIM card (a so called “Tandem” i.e. twin SIM with the same number). In identical conditions the 10 III draws double to tripple the current the XA2U draws. All reviews of the 10 III (with stock Android onboard) give it standby and talk times several times longer than those we get under SFOS. So the problem is definitely in software.
If I understood things correctly, cores don’t just have to run at lowest frequencies, but also get disabled through S-states. Not sure how granular it is, whole cluster or individual cores.
There raising the minimum frequency might help keep other cores off. But it is a pure guess. Do S-states work on SFOS the same as on Android?
As for governor, as long as it is not performance one, idle usage should remain the same. When the device is hot or you have load spikes, there you should see gains.
Hi wetab73, I managed to reduce battery consumption by disabling WiFi at times, when I wear the phone in my trousers or lay it “display down” on a table. This might not fit for everyone, but I i think it is worth mentioning. Details see: Situations: “display down”
Could you install and run powertop on both devices and compare the wakeups displayed by powertop?