Which flow(s) eat my battery?

Post your questions and help other users.

Moderator: Martin

User avatar
kintrupf
Posts: 257
Joined: 10 Sep 2013 08:59

Re: Which flow(s) eat my battery?

Post by kintrupf » 10 Dec 2013 20:41

Unfortunately BetterBatteryStats requires root for the partial Wake Lock statistics, at least on KitKat :(

User avatar
Martin
Posts: 4468
Joined: 09 Nov 2012 14:23

Re: Which flow(s) eat my battery?

Post by Martin » 11 Dec 2013 20:44

Ahh, yes, listing the partial wakelocks requires root. Google seems to remove more and more useful features from Android for non-root users :(
The new EAP build of v1.20 fixes some issues, please update to the latest version, reboot the device once and see if you still run into the battery problem.

Are you using any flows which use a sensor trigger (Compass, Device Orientation, Pressure, Shake or Speed)?
Does one of the flows run into a timeout or takes forever to execute and is constantly highlighted in red in the flow list?

Do you happen to have adb installed on your desktop PC?
If yes, you could print the battery infos on the command line:
adb shell dumpsys batteryinfo > batteryinfo.txt

User avatar
kintrupf
Posts: 257
Joined: 10 Sep 2013 08:59

Re: Which flow(s) eat my battery?

Post by kintrupf » 12 Dec 2013 09:44

I'm really considering rooting my phone. With Android 4.3 it wasn't really necessary, but with KitKat it seems mandantory! I may even go back or use a custom ROM like Cyanogenmod.
By now I curse the day KitKat was offered to my phone and I was stupid enough to install it :x

I've updated to the newest EAP build and will monitor the battery usage once the battery is full again and the statistics are reset.
None of my flowss uses sensor triggers, but I use the plugin "Movement detection" as trigger.

Unfortunately, even with adp I can't get any battery stats. The result is "Can't find service: batteryinfo" :(

User avatar
kintrupf
Posts: 257
Joined: 10 Sep 2013 08:59

Re: Which flow(s) eat my battery?

Post by kintrupf » 12 Dec 2013 16:41

Preliminary results after a full charge and 37 minutes on battery with newest EAP 1.20 build from yesterday:

Screen: 40%
Automagic: 24%
Android OS: 13%
Phone idle: 9%

Automagic use details:
CPU total: 1m 30s
Keep awake: 14m 9s

Automagic statistics:
Time spent in flows: ~35 seconds (30s of that deep sleep)
Flows execute: ~30

User avatar
Martin
Posts: 4468
Joined: 09 Nov 2012 14:23

Re: Which flow(s) eat my battery?

Post by Martin » 12 Dec 2013 19:15

Sorry, my mistake, the service is probably called batterystats on your ROM :oops:
Following command should work:
adb shell dumpsys batterystats > batterystats.txt

Could you please also send the flows to info@automagic4android.com so I can try to reproduce the problem on my device.

User avatar
kintrupf
Posts: 257
Joined: 10 Sep 2013 08:59

Re: Which flow(s) eat my battery?

Post by kintrupf » 13 Dec 2013 08:04

Now the stats are working :P
I've send them to your e-mail along with my flows.

Yesterday evening I got the OTA update to KitKat 4.4.2. I will check during the next days if this will affect Automagics battery usage.

Addendum:
After temporarily disabling all flows the battery drain from Automagic dropped to zero.
I will now enable some flows or group of flows at a time to determine which flows spike the battery usage...

Post Reply