Xperia X high battery consumption in Kvarken

REPRODUCIBILITY (% or how often): Always
BUILD ID = OS VERSION (Settings > About product):
HARDWARE (XA2, Xperia 10…): Xperia X
REGRESSION: (compared to previous public release: Yes, No, ?): Yes


I experience higher power consumption since updating from 4.0. There have been reports connecting this to WLAN use, but that is not the issue here, as far as I can tell.

I have tested as below to see if I can find a culprit app, to no avail. It looks more as an OS problem.

Please advice if there is anything more I should test.


In order to provide consistent data, I have

  • Charged to 80%
  • Switched off all radios (mobile, WLAN, BT) and GPS
  • Powered off the device
  • Powered on the device


  1. Setup as above
  2. Start zero or more apps
  3. Show home screen
  4. Leave device idle for 10+ hours


A drop in battery around 0.3%/h with four apps idle. Several days of light device use on a charge.


Apps running         Discharge
-----------------          -------------
None                       <0.2%/h        
Settings                    0.4%/h
Calendar                    0.4%/h
Four apps                  >1.4%/h

The four apps were Settings, Calendar, Situations and Pure Maps.


  • Under Koli 4.0.1 with these four apps “running” (i.e. idle), I could expect about the same discharge rate as Kvarken shows with no apps at all.
  • It seems more power is consumed when I actually use the apps, in comparison with Koli 4.0.1, but that is hard to measure. I get 0.5-2 days of use from a charge now.
  • It seems apps are slower to start and more sluggish to use, in comparison with Koli 4.0.1, which also hard to measure.


(But please note that my testing is with WLAN off.)

For me, this has been going for a few releases now. Using the original top tool (before the now more useless top got merged in), it was clear that systemd-logind was using the most CPU time, followed by voicecall-ui if I had been calling.

systemdatascope (or rather collectd) has recently gained per-process monitoring.

I suggest adding all of the suspected processes to this and leave it collecting for some time.

Then plot it with systemdatascope.

Note that it scaled graphs down to ‘millipercent’ so be sure to read them correctly.

Also note that you may want to use collectd’s ProcessMatch rather that Process directive for apps that apeear more than once in ps (like all the invoker-started apps).

1 Like