AlarmManager partial wakelocks

Avi

unread,

Oct 9, 2012, 3:09:21 AM10/9/12

to tas...@googlegroups.com

I've been experiencing some heavy battery drain lately, and managed to narrow it down (with the help of BetterBatteryStats)
to the fact that I am getting a lot of wakelocks from the "AlarmManager".
By way of elimination and with the help of the "dumpsys alarm" commandin the shell,
I found out that the bulk of these "alarm" wakelocks are caused by Tasker.
The logic was that only profiles with recurring "Time" events will do that, but disabling those did not do the trick.
I need help figuring out which contexts can cause these alarms.

Thank you.

Pent

unread,

Oct 9, 2012, 3:44:06 AM10/9/12

to Tasker

If you can tell me the exact tag of the wakelock I might be able to
say more.

Pent

Avi

unread,

Oct 9, 2012, 3:48:44 AM10/9/12

to tas...@googlegroups.com

It does not appear as a "Tasker" wakelock, rather I see the "AlarmManager" wakelock increasing rapidly.
The question is what contexts use the "AlarmManager".
Obviously recurring time events do.
If I have a "time" context without recurrence, say "between 9:00 and 17:00", does this trigger an AlarmManager?

Thanks

Avi

unread,

Oct 9, 2012, 3:53:09 AM10/9/12

to tas...@googlegroups.com

I could give you the tasker labels from the "dumpsys alarm" output.
Will this help?

Pent

unread,

Oct 9, 2012, 4:03:27 AM10/9/12

to Tasker

> I could give you the tasker labels from the "dumpsys alarm" output.
> Will this help?

Possibly :-)

Pent

Pent

unread,

Oct 9, 2012, 4:04:32 AM10/9/12

to Tasker

> If I have a "time" context without recurrence, say "between 9:00 and
> 17:00", does this trigger an AlarmManager?

No idea. If it's 8am, it results in requesting the alarm manager to
send an alarm signal at 9am. What the alarm manager does in-between is
none of my business.

Pent

Avi

unread,

Oct 9, 2012, 4:08:30 AM10/9/12

to tas...@googlegroups.com

This is what I can come up with from the "alarms" report:

act=net.dinglisch.android.tasker.ANOFFCHECKORUM flg=0x14
act=net.dinglisch.android.tasker.WILLYUM flg=0x14
act=net.dinglisch.android.tasker.CALARUM flg=0x14
act=net.dinglisch.android.tasker.ALARUM flg=0x14

I appreciate the help.

Pent

unread,

Oct 9, 2012, 4:19:53 AM10/9/12

to Tasker

> act=net.dinglisch.android.tasker.ANOFFCHECKORUM flg=0x14

Alarm to do display off checks (every 10 mins)

> act=net.dinglisch.android.tasker.WILLYUM flg=0x14

Wait alarm. If you say Wait 10 Minutes, an alarm is set for when the
Wait expires.

> act=net.dinglisch.android.tasker.CALARUM flg=0x14

Alarm for the next calendar event

> act=net.dinglisch.android.tasker.ALARUM flg=0x14

Next Time context time

BTW, wake locks != battery used

Pent

Avi

unread,

Oct 9, 2012, 4:26:17 AM10/9/12

to tas...@googlegroups.com

Thank you.
This is very helpful

Dave Fisher

unread,

Oct 9, 2012, 4:31:34 AM10/9/12

to tas...@googlegroups.com

https://github.com/asksven/BetterBatteryStats/issues/222

I added the Tasker Wakelock info to BBS, but Sven hasn't updated the Wiki yet (I'd do it myself but I am not sure how the entries in the wiki link into the entries in BBS.

Pent

unread,

Oct 9, 2012, 5:44:08 AM10/9/12

to Tasker

I thought I remembered something about BBS and the tags :-)

Pent

Avi

unread,

Oct 9, 2012, 6:16:57 AM10/9/12

to tas...@googlegroups.com, mob...@the-darkside.co.uk

Thanks Dave.
I can see these wakelocks.
My issue is not with the direct wakelocks
rather with the ones that trigger the AlarmManager way too often.

Reply all

Reply to author

Forward