Excessive power consumption through permanent wakelock?

[kintrupf]

Recently, I started to observe a very unfortunate phenomena. Automagic seems to keep the phone constantly awake.
This, of course, results in a very excessive power consumption

Unfortunately, the wakelock(s) which seems to cause this behavior, are displayed as *overflow* and thus cannot be connected to any particular flow.
What can I do to prevent this? If this power drain is not noticed early it empties the battery completely in just a few hours!
And the only way to end this power drain is to reboot the phone...

Nexus 5, Android 4.4.4 KitKat, root

Screenshot_2016-01-08-11-49-49.jpg (40.82 KiB) Viewed 18453 times

Screenshot_2016-01-08-11-49-30.jpg (48.47 KiB) Viewed 18453 times

Screenshot_2016-01-08-11-49-02.jpg (64.04 KiB) Viewed 18453 times

[MURTUMA]

For me, Wakelock Detector on play store has been a good app to track down problematic wake locks. Also, I use an Xposed module Amplify to tame those. So far, I haven't seen any problematic behaviour by AM, so I can't give you any tips on that. But see if Wakelock Detector helps you.

[kintrupf]

For me, Wakelock Detector on play store has been a good app to track down problematic wake locks. Also, I use an Xposed module Amplify to tame those. So far, I haven't seen any problematic behaviour by AM, so I can't give you any tips on that. But see if Wakelock Detector helps you.

I have both apps installed. But I did not think of Wakelock Detector
My results with Amplify are mixed. I did not really see an improvement in battery usage, but the location services got worse.

[MURTUMA]

Yes, the overall effect of Amplify to actually help battery life is questionable, as I think the dev has thrown the numbers from absolutely worst case. However, it has fixed me a flawed app that kept my screen on for unknown reasons to me.

Just so I don't get lost in translation, I ask what do you mean by not thinking Wakelock Detector?

[Martin]

*overflow* is used by the internal battery statistics of Android when an app used more than 30 different names for the wake locks. After the 30th wake lock name it starts to group everything in *overflow".
Please restart the device to clear the battery statistics and disable the flows you don't need until you can reproduce the problem.
The statistics within Automagic look OK to me since there's no flow that is executed for 30 minutes.

[kintrupf]

Just so I don't get lost in translation, I ask what do you mean by not thinking Wakelock Detector?

I meant that I forgot at that time that I had Wakelock Detector installed, so I didn't use it to diagnose the problem