4529000 / 3532620 = 78% so there’s a discrepancy vs. 81%. Check again around 60%, probably it’ll be even bigger.
charge_counter: 2853270
Homescreen shows 67% left of battery.
45290000 / 2853270 = 63% so the discrepancy (4%) got slightly bigger. But I guess it’s typical as on my 10 III it is right now 76% vs 73%, i.e. 3%.
The most strange thing is that my XA2 Ultra’s charge_counter when fully charged is 5688458 (i.e. more than 5600 mAh) 
Maybe due heat losses during charging.
Funny thing, thanks to this charge_counter I’ve discovered that I most probably have some Chinese battery inside my XA2 Ultra, probably one of those “5600 mAh” one can find on Aliexpress, be it a true capacity or the battery electronics just reporting it so. I bought the XA2U second hand and the seller was mentioning that battery was replaced by the service but I had no idea that he meant a third party battery and a “service” that uses such strange batteries… The funniest part is that it works OK, gives me very good working time, and the charge_counter decreases in a correct pace as the battery discharges, so it might mean that this 5600 mAh capacity is actually (close to?) real…
I have created a topic specifically for the [standby current drain] only(Standby Battery high drain on Xperia 10 III).
Please do, and update the new topic. I have added it to the 30th March community meeting, so if you feel like doing it soon…
I have same problem with battery on Xperia 10 III.
First of all it was because of ofonod, but it makes better after OS update (to 4.5.xx).
The second I found new problem with connected CardDav account. The process “/usr/libexec/buteo-oopp-runner carddav” consumes a lot of battery: a current obtained with Battery Buddy shows 500-600 mA. If I disable CardDav accound and kill the process after this, the current makes 100-200 mA.
The consuming process was found via PowerTop.
Consumption of 100-200 mA is still a CRIME. The XA2 Ultra, with its older SoC and huge screen, in the same conditions consumes 50-60 mA.
You cant compare IPS LCD (xa2 ultra) Smartphone vs OLED (10iii) Smartphones in terms of Energy-Consumption and expect it must be consume less Power.
My experiences starting with Windows Phone and later on some Sony Smartphones show me the opposide: OLED Smartphones consume more Power than IPS LCD Smartphones.
It depends of course on the content and brightness what OLED consumes. In my cases i use the same Backgrounds, colors…etc and OLED loose in that consumption game.
The XA2 Ultra consumes much less power than the 10 III in all conditions, also when the screen is off. Regardless of whether the display is on or off, the XA2 Ultra still uses at least twice less power than the 10 III.
I do have an idea for the cause of the high drain. I’ve seen it on my Fairphone2 running SFOS and my Sony Xperia 10iii, I’m curious to see if others see the same.
My FP2 could run about 4 days on a full battery, it was connected to 4G. At about the time my provided switched off 3G it could only run for about a day on a full battery. Since this was a community port i did some extensive troubleshooting with the developer and we couldn’t find anything in SFOS. Changing the mobile network to 2G only gets me back to 4 days on a full battery.
With my X10iii the situation is similar (although i didn’t have it when 3G was still available): When connected to 4G (no active data connection, just idle/standby) it’s 2 or 3 days, when set to 2G only it’s 4 or 5 days.
So the if 4G is available and 3G isn’t that seems to trigger high battery use when connected to 4G. Does anyone else have the same situation?
My idea why this could be the case is because calls on 4G are special and one method to create a call is CSFB which falls back to 3G. So there might be some process in the baseband/modem constantly scanning for 3G while connected to 4G so it can change quickly when a call has to be made, since no network is found it keeps scanning and draining the battery.
The topic here is specifically the standby current drain - when the phone has it’s radios turned off. You want this thread high-battery-drainage-xperia-10-iii
However as an aside, I have not noticed that disabling 4G affects the online power drain.
I’m sorry, you are right.
The correct topic seems to be High battery drainage Xperia 10 III
Maybe a moderator can move my message there?
Next update maybe?
Here there is about 100 options about power governators:
But those available are here listed
[root@sfos ~]# cat /sys/devices/system/cpu/cpufreq/policy0/scaling_available_governors
conservative powersave interactive performance schedutil
[root@sfos ~]# cat /sys/devices/system/cpu/cpufreq/policy4/scaling_available_governors
conservative powersave interactive performance schedutil
It would be possible to keep 4 cpu in a conservative mode and 4 in schedutil or any combination. I am not aware if it is better to run at full throttle few CPUs or keep balanced. My gut feeling indicates the second but …
I am trying this one configuration:
for i in /sys/devices/system/cpu/cpu[0-3]/cpufreq/scaling_governor;
do echo "interactive" >$i; done
for i in /sys/devices/system/cpu/cpu[4-7]/cpufreq/scaling_governor;
do echo "conservative" >$i; done`
mcetool \
--set-power-saving-mode=enabled \
--set-low-power-mode=enabled \
--set-psm-threshold=100 \
--set-forced-psm=disabled \
--set-ps-on-demand=enabled
The 10 III doesn’t have the interactive governor, and its CPU’s big.LITTLE core architecture is 6:2 and not 4:4. Please stop messing up in yet another thread.
Different hardware have different configuration but most the commands are the same.
-
Xperia 10 III : Octa-core (2x2.0 GHz Kryo 560 Gold & 6x1.7 GHz Kryo 560 Silver)
-
Xperia 10 II : Octa-core (4x2.0 GHz Kryo 260 Gold & 4x1.8 GHz Kryo 260 Silver)
Therefore it makes sense to have two different governor policies in the two CPUs sets:
for i in /sys/devices/system/cpu/cpu[0-1]/cpufreq/scaling_governor;
do echo “ondemand” >$i; donefor i in /sys/devices/system/cpu/cpu[2-7]/cpufreq/scaling_governor;
do echo “conservative” >$i; done`
The differences for Xperia 10 III in the code has been highlighted, very little. Anyway, thanks for the suggestion and information. Because now, I can write a script that can works for both. 
But if you post in a thread strictly related to the 10 III then the information you post should apply to the 10 III, or else it can only confuse others. It is not a thread about governors or CPU cores in general, but a 10 III specific one, so the information should be valid for the 10 III.
I did not question that it is possible (or maybe even useful) to use two different governors for the big and little cores (in fact, that’s how the 10 III used to be configured by default in previous OS releases, with schedutil for the little cores and performance governor for the big ones), but only that your information was not applicable to the 10 III and thus potentially misleading to others.
Anyway, now that Jolla switched to using schedutil for 10 III’s all 8 cores, and that several people tested using lower minimum frequencies (e.g. 300 MHz) for all cores and also other governors (e.g. ondemand), none of which gave any noticeable power drain reduction, neither during use nor in standby, we already came to the conclusion that it is all in vain because the actual reason of 10 III’s high power drain lays elsewhere, most probably in the AOSP layer.
1 Like
Maybe, but there are area of improvements:
because as far as I see the power management policy is disrupted by deamons that should sleep in theory but instead they are alive for too long time in CPUs and there are significant amount of CPUs used by kworkers and rcu_preempt. I never had to do with a smartphone before now but it is a normal shape of activity in a Linux embedded system.
Deactivate and observe?
2 Likes