Timed profile keeps setting next alarm

Jon Bray

unread,

Apr 28, 2016, 12:19:55 AM4/28/16

to Tasker

I've had a profile which runs every 10 minutes to do various things, and it has been working fine. After I upgraded to Marshmallow however I noticed that my 'next alarm' was nearly always within 9mins of the current time. Disabling the profile sorted the problem, and replacing the task normally called with a much simpler one didn't sort it- so it looks like it is the timer itself which is being read as next alarm. Has anyone else found this in marshmallow (Cyanogen version for Wileyfox swift)?

Pent

unread,

Apr 28, 2016, 5:16:27 AM4/28/16

to Tasker

I've had a profile which runs every 10 minutes to do various things, and it has been working fine. After I upgraded to Marshmallow however I noticed that my 'next alarm'

What's a 'next alarm' ?

Pent

Jon Bray

unread,

Apr 28, 2016, 5:52:53 AM4/28/16

to Tasker

The system keeps a note of the next alarm which is due - a number of apps use this including the autoalarm plugin for tasker. I display it as a widget using Zooper to reassure me that tasker is setting alarms properly (I work odd shifts).

Pent

unread,

Apr 28, 2016, 7:49:09 AM4/28/16

to Tasker

Is Menu / Prefs / Monitor / Use Reliable Alarms set to something which isn't Never ? If so, try setting
it to never.

Pent

Jon Bray

unread,

Apr 29, 2016, 4:12:03 AM4/29/16

to Tasker

Yep, that appears to have worked. Thanks :-)

Reply all

Reply to author

Forward