A bit high (I expected 1.0%/h) but I guess this is mostly caused by k9. This also seems to trigger your WLAN to start again (I’m just guessing). What do you think? Is it good or do you think it’s still more than before?
It’s also interesting to see that your SoC was pretty active for over > 1 h 24 m while the screen was only on for around 15 sec. So it was pretty busy “awake” in the background for more than one hour. 25 mins IMAP+ Mail, but the other 60 mins? No clue, maybe the waking up and falling back to sleep again takes time? Would be interesting to know more about this. Maybe Alarms + falling back to sleep again?
Screen On (): 15 s (15 s) Ratio: 0,0%
Wifi On (): 8 h 39 m 43 s (31183 s) Ratio: 100,0%
Wifi Running (): 8 h 39 m 43 s (31183 s) Ratio: 100,0%
Deep Sleep (): 7 h 15 m 24 s (26124 s) Ratio: 83,8%
Awake (): 1 h 24 m 18 s (5058 s) Ratio: 16,2%
CPU States
1,21 GHz (): 1 h 24 m 10 s 16,2%
988 MHz (): 0,0%
754 MHz (): 0,0%
497,25 MHz (): 8 s 0,0%
Deep Sleep (): 7 h 15 m 24 s 83,8%
Mine
Other Usage
===========
Deep Sleep (): 9 h 33 m 48 s 91.5%
Awake (Screen Off) (): 49 m 12 s 7.8%
Screen On (): 3 m 54 s 0.6%
Wifi On (): 10 h 26 m 55 s 100.0%
Wifi Running (): 10 h 26 m 55 s 100.0%
No Data Connection (): 10 h 26 m 55 s 100.0%
No or Unknown Signal (): 10 h 26 m 55 s 100.0%
Screen dark (): 7 s 0.0%
Screen medium (): 3 m 47 s 0.6%
================
Kernel Wakelocks !!! wakeup_sources !!!
================
EINT wakelock (): 40 m 38 s Cnt:(c/wc/ec)3806/121/3807 6.5%
event0-649 (): 10 m 49 s Cnt:(c/wc/ec)3655/7/0 1.7%
alarm (): 2 m 49 s Cnt:(c/wc/ec)1623/7/0 0.5%
WLAN Timer (): 2 m 4 s Cnt:(c/wc/ec)136/0/0 0.3%
PowerManagerService.WakeLocks (): 44 s Cnt:(c/wc/ec)1262/7/0 0.1%
CPU States
==========
1.21 GHz (): 50 m 5 s 8.0%
988 MHz (): 0.0%
754 MHz (): 1 s 0.0%
497.25 MHz (): 3 m 16 s 0.5%
Deep Sleep (): 9 h 33 m 48 s 91.5%
========