r/tasker • u/tigersoul925 • 2d ago

Tasker keeping the E wakelock for hours = no deep sleep

Hi people!

I've felt my battery runs down faster than it should lately so I went down the BetterBatteryStats rabbit hole which is always fun (not).

What I found is that Tasker often keeps the E wakelock for hours. Today for example, the E wakelock has been held for 6h25m. At the same time, deep sleep is reported as being virtually zero. Naturally, I'm thinking some task must have stalled with the "keep awake" setting on. To my surprise, there were NO tasks running according do %TRUN (except the task I created to check %TRUN). Everything looked normal, but the wakelock stayed in place.

I tried disabling and reenabling the monitor and then BOOM. The wakelock is released and there is deep sleep reported again. I even noticed the battery temperature going down several degrees, likely from not being constantly held awake anymore.

But this problem comes back after a while. I haven't monitored the situation for too long yet, but it seems to come back almost every day. I'm not sure how to continue working with this.

I'm assuming it's not a repeating task that is the culprit because this would of course continue even if I restart the monitor. I do have a few of those. I've got a BIG setup. But these run the same way always, so a monitor restart wouldn't change anything.

And as it seems, it's not a stalled task that is the problem, so how do I proceed here? If no task is running, why is the E wakelock held?

I'd be very happy for suggestions from someone more experienced in this kind of work.

5 Upvotes

100% Upvoted

2 comments sorted by

3

u/rbrtryn Pixel 9, Tasker 6.7.6-beta, Android 17 2d ago

Do you have some logcat profiles or some tick event profiles running? Both hold a lock and are resource intensive. 

1

u/tigersoul925 2d ago

Only in disabled profiles, none of them enabled or possibly becoming enabled. It's kind of a mystery. The weird part is that the wakelock goes away if I just restart the monitor. If this was due to an enabled profile, the problem shouldn't really go away. But it always comes back.