Time context starting only when phone is awake

[Mike]

Hey All.
I've been using Tasker for many years and i know that most of the time when something doesn't work, it's probably our fault.
But here... i need some help.

I've set a TIME context that starts at 4AM and repeats every 30 mins until midnight.
I've set some tasks ( whichever) to be launched with it.

The problem : the context is launched only when my phone is awake or has been awake not too long ago.
If i'm not using my phone for some hours, the context won't be launched!

I have the LOG running and i can see when is the context launched.
Any suggestions why this happens ??
Thanks

[Marta Hintz]

Your either on 5.xx lollipop, or have a Samsung phone. ..

[fiSh]

If that is a serious answer is it documented somewhere as I have the problem 5.1.1 on a Samsung S6 :(

[Dale Smith]

Marta tends to be turse. If you don't touch your phone. How many triggers do you get?

[John Fisher]

Hi Dale,
I have only just realised that it's happening. After an android update I have been noticing that some of my tasks didn’t seem to be working. Now I suspect they aren't auto run as often as usual.
Also a simple meditation timer Task has developed a mind of its own. A wait at the start to allow me to settle, for example, followed by a bell can take much longer than usual, but when I reduced it I was surprised when it worked for the entered time. You may be pleased to know it generally has me meditating longer...
Just before I leave for work, every five minutes, I am told the time. I have grown to tune it out, but this morning I noticed it wasn't speaking until I went into Tasker to check, and the next one worked.
If there is a developer I could set up an event that should log every five minutes and report how it goes.
(I hate typing on a phone)

Sent from phone

On 25 Sep 2015 17:57, "Dale Smith" <dales...@gmail.com> wrote:

Marta tends to be turse. If you don't touch your phone.  How many triggers do you get?

--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/5etY6GHxCO4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.
Visit this group at http://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

[Rich Belthoff]

I believe if you search this forum for timed event and lollipop you might able to fund some info in how others solved this problem. I recall reading about someone's testing but can't locate the thread just now or I'd include the link.

[fiSh]

Thanks Rich,

eventually I found other reports, but didn't find a fix that worked for me. Still it makes me feel less lonely! It's as though android is trying to use less battery by not poking the apps or something. Hoping that android reverses the problem.

[Mike]

I am indeed on Samsung S6 and Android 5.1.1

Seems that this bug is related to Android 5.1.1, see this topic : https://groups.google.com/forum/#!topic/tasker/k1k2IewKzN8
So guess the only solution is to wait for Pent to update the app when he recovers

ps: I also noticed today that my other task, based on calendar entry, is launched a few minutes late instead of right on time as it used to be :-(

[Dale Smith]

I'm using a Samsung S5 and also hate typing on a phone. Check out Samsung's SideSync app. It displays your phone on your PC and you can use the mouse and keyboard. Really nice app to use.

[Adam Greatrix]

On Saturday, 26 September 2015 21:57:00 UTC+1, Mike wrote:

I am indeed on Samsung S6 and Android 5.1.1

Yep - same here Samsung Galaxy S6 with 5.1.1. I have a Time entry to run every 6 hours and it just doesn't run.

I'm sure it did run on my Nexus 5, also running stock 5.1.1. though.

[Sebastian Zappe]

Hi,

I got exactly the same problem on my Honor 7,running 5.0. The irritating point is, at last I used an Honor 6 with 5.1.1 and I got no problems and also my old HTC Sensation running 5.1.1 was perfectly starting my time based tasks. This irritating behavior first time came up with my new Honor 7.

Cheers,
Sebastian

[Pent]

I have an idea what this might be on 5.1.1, will try to fix it for next update.

Pent

[Mike]

Thank you Pent !
 Might it be the same reason why my calendar entry events are starting about 2 mins later than scheduled ?

Hope you feel better !

[Pent]

 Might it be the same reason why my calendar entry events are starting about 2 mins later than scheduled ?

Yes.

Hope you feel better !

No, and I have a load of marshmallow work ahead of me, but thanks for hoping :-)

Pent

[Andrea Bruzzesi]

Thanks for keeping up with this issue, and best wishes for all real life stuff!

[YY-YY]

Thanks for your reply on the thread I started (https://groups.google.com/forum/#!topic/tasker/X0mL5m06gt8), bringing me here.  As mentionned, mine is a samsung galaxy s4 running android 5.0.1.  Scheduling and reminders is the main purpose of me using the s4.   Shoud/could I root it?   Thanks and get better...

[Pent]

>   Shoud/could I root it?  

Won't help.

Pent

[Pent]

I posted a beta at the top of the forum, would be great if people could test that with
time contexts.

Pent

[Mike]

thanks Pent, but I'm afraid problems are still there..
my 'every 30 mins' context doesn't run (I checked 'run log' too ), and my calendar entry event start 3 mins later.. tried with version 4.8b1m on Galaxy S6 edge 5.1.1 Official Rom COH2.

[Pent]

my 'every 30 mins'  context doesn't run (I checked  'run log' too ),  and my calendar entry event start 3 mins later.. tried with version 4.8b1m on Galaxy S6 edge 5.1.1 Official Rom COH2.

What does your task do ? Could you try a simple Write File action with %TIME as the contents.

I've tested this time context on an Android 6.0 Nexus 5 and it works fine, am trying a 5.1.1 now.

Also: have you specified midnight (23.59?) in the time context, or completely deselected the To time ?

Pent

[John Doe]

IMHO, it's not a Tasker problem or a bug related with timer. It seems that in the latest Samsung fw 5.1.1, there is a really aggressive policy against apps, where they are killed when the screen off after a while. If it's the case you should try to check the Tasker foreground notification time. If the time change (and no profile activation happens) means that Tasker is killed and restarted. On this fw even system bind services like notification services are killed, I don't know what Samsung really thinks when it implements this crap.

[Pent]

Thanks for the hint and tip JD.

I tried a Nexus 6 with 5.1.1 seems just fine so far, I'm testing on a 5.0.2 Samsung tablet now, don't have a more recent
Samsung.

Maybe the later Samsungs have some sort of exclusion list in Settings ?

Pent

[John Doe]

I don't have a Samsung but I received report for the same problems. It seems they have implemented something similar to doze/app standby.

[John Doe]

Correction: this new "feature" is related with Samsung Galaxy S6/Edge starting from fw G920FXXU3COI9

[Mike]

so I did a context 'every 30mins' with task write on file, and another one every 30 mins from 4.05 to 00.05.

now it's 22:25 here, this is the result
the first context wrote
14.00
14.30
17.30
18.02

the second context wrote
12.05
16.06
17.05
17.35
22.05

it MIGHT be Samsung related as it was working fine before my last firmware upgrade, yet I hope there is a solution for this, especially for the calendar entry event context that keeps starting 2 or 3 mins later (my phone is not muted on time anymore !).

Will the future marshmallow upgrade (that should arrive in December for the s6 edge)
-keep that bug or
-will it be fixed in any marshmallow (even a Samsung one) ?
- or we can't know yet?

thanks

[Pent]

so I did a context 'every 30mins'  with task write on file,  and another one every 30 mins from 4.05 to 00.05.

Sorry to be difficult, but could you also try it with a single profile with a time context please ?

Also please enable Menu / More / Run Log and check for Status = Start and Details = Monitor lines.

Don't go into the Tasker UI during the experimentation (it can cause the monitor to restart if you
make changes), then we can see if the monitor is being killed in the gaps.

Pent

[Pent]

p.s. I have not been able to reprodice this with N5 (6.0), N6 (5.1.1) or Samsung tablet (5.0.2), it's
looking like JD is correct in it being a Samsung problem with later ROMs. If you're running the monitor
in foreground (the Tasker icon shows in the status bar) and there is no whitelist of apps offered by
Samsung, I'm not sure what else I can do.

You're not on a custom ROM or rooted, right ?

Pent

[Mike]

How could you be "difficult" trying to help me !?? :-)

So if i understand you correctly, you want me to have only 1 profile with a context "every 30 mins" and a tast "writing file %TIME" , then leave tasker for the day and return at night to check the log for "monitor" lines ?
doing it right now...

ps : until a fix is found, as an alternative, i'm using 2 profiles based on variable context that contains a 'wait 30 mins' task then change a variable to activate the second profile than contains the same wait 30 mins then rechange the variable to activate again the first context.... causing a loop and simulating a "every 30 mins" alternative that works well for now. 

However i could not create any alternative solution for the "calendar entry event" context that always starts 2-3 minutes after time.... any alternative on that or any hope for fix ???

[Mike]

I am on official Rom G925FXXU2COH2 Android  5.1.1   but i AM rooted (kernel version : 3.10.61-S6_Unikernel_v8-0002_rbgl@BlueDingo )

[Mike]

Ok so here is the result with a single time context 'every 30 mins' (time is now 2200) :

12.00
12.30
15.00
17.00
17.30
18.00
18.30

as for the log run, for some reason I can't see the log bfor everything before 18h41, but everything after that doesn't show any 'monitor' that started. (I used the filter to search).

[Andrea Bruzzesi]

Unfortunately the latest beta does not seem to solve the issue in my test.

I went as far as deleting all the profiles, uninstalling normal application and reinstalling the beta, and finally configuring only one time-triggered profile that occurs once per hour and tells the time.

Well, the only two times it woke up are when the device was already awake or just turned off.

A couple of hours ago I enabled logging and literally see no activity there.

[fiSh]

Hi, 

On my S6 5.1.1. I've just noticed that the smart manager app in the battery section has app optimisation which claims to optimise apps for "save battery power by optimising the power usage of apps". I've disabled tasker to see if that makes any difference. Is this something everone knows about except me or is it something new .... no time to see if it makes any difference at the moment ...

[Andrea Bruzzesi]

I'm with a Xiaomi Mi4c running stock MIUI firmware, and experience the same issue I had on Samsung S6 until I sold it.

I definitely tried all, and I mean all options I found on both devices, but the issue is the same: if the device is sleeping it is not woken up to perform Tasker's time-based profiles.

[Mike]

so you are talking about the 'battery' settings. In there I have a section called " abnormal battery usage" but it says that all apps have normal battery consumption. not sure what you disabled exactly? do you have a picture?

[Mike]

[John Fisher]

Screen captures attached

Sent from phone

On 26 Oct 2015 13:38, "Mike" <mikael...@gmail.com> wrote:

so you are talking about the 'battery'  settings. In there I have a section called " abnormal battery usage"  but it says that all apps have normal battery consumption.  not sure what you disabled exactly? do you have a picture?

--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/5etY6GHxCO4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.
Visit this group at http://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

[John Fisher]

I think I managed to send a couple of screen captures; on the battery usage one clicking on the Detail option gives me the app optimisation list. I scrolled down to tasker and disabled it. I'm at work so testing is problematic but I set a profile to tell me the time every five minutes. Until I booted it was no difference I got better results afterwards but not yet conclusive either way.

[fiSh]

On my Samsung S6 5.1.1 phone it came with a Samsung app smart manager, which I have been ignoring, not as part of the settings. I haven't noticed this optimization list before so it may have come with the update.

[Andrea Bruzzesi]

In my tests I find time-triggered profiles mange to run if the device is sleeping from no more than 10 minutes or so...

By the way trying to troubleshoot this issue I also tested out two apps: MacroDroid and eRobot, and both didn't have the issue, BUT the actions were triggered a couple of minutes after the requested time. Meh!

[fiSh]

Looking good so far after disabling the optimization. The time profile with five minute repeat fired and said the time every five minutes for the last hour or so without me touching the phone. Unfortunately I now need to use the phone which might confuse the test still, maybe ...  I'm running the version from the play store not the tasker beta version (great pent is back).

[Andrea Bruzzesi]

In my humble opinion 5 minutes is a time span too short to let the device go into deep sleep; I tried with 30 minutes and recurring actions don't get performed.

[fiSh]

It used not to work so now it working can only be a good sign, if inconclusive. 

[fiSh]

It appears that this same screen can be accessed from the settings.

[Mike]

I see, i don't have this Samsung feature of "App optimisation", this was include only in the latest firmware G925FXXU3COI9 (i have the COH2) which was released less than a month ago.
I'll update to that firmware tonight and deactivate Tasker from the "app optimisation"... we'll see what happen then.

[fiSh]

Unfortunately it isn't working this morning; even after a reboot and using the phone. Back to the drawing board (why the inconsistency?)

[Adam Greatrix]

Pent - I wonder if Samsung's "App Optimisation" is to blame? This appeared with Android 5.1.1 on the Samsung Galaxy S6 ROM, and is configurable in the latest update (that started rolling out around a week ago).

What this claims to do is automatically put a given app into "Power Saving" mode. This is a bit vague... but what it actually seems to do is it keeps tabs on when a given app was last actually opened by the user. If it has been more than 3 days (this is now configurable) the app is prevented from running in the background without the screen on (or unlocked?).

You can configure the days to wait for this automatic "App Optimisation", or you can set a given app to "Always Power Saving" or "Disabled for", or the default Automatic.

You access these settings by going o the Smart Manager app, pressing the Battery quarter of the screen, then under "App optimisation" press "DETAIL", where you can turn the whole thing on or off, or adjust the settings for each app.

I'll grab the beta soon and test this for you. But in any event it's probably advisable to have Samsung owners turn this off, or at the very least set it to "Disabled for" for Tasker and its plugins like the various Auto apps.

[Adam Greatrix]

Whoops - what fiSh said (my bad - just catching up).

[anodyn...@gmail.com]

Adam, I have app optimization set to off for Tasker (and all auto apps plugins) and been running the latest beta for a couple of days on my S6 5.1.1. Unfortunately the behavior is just the same, profiles relying on the time context will not trigger successfully. Also I noticed the same issue before the app optimization appeared with one of the Samsung updates so I doubt it is related.

[Andrea Bruzzesi]

I took the chance to install a CyanogenMod port on my Xiaomi Mi4c, thus replacing stock MIUI firmware: all is working as expected and Tasker time-triggered profiles works as they should.

So I gather is not a "stock" Android issue on some battery saving feature but rather a custom implementation some brands perform on their firmwares.

In my recent experience Samsung Touchwiz and Xiaomi MIUI suffer of this issue, while OnePlus One and the same Xiaomi device with CM ROM both work well.

[Adam Greatrix]

Agreed. I set a profile to run every 30 minutes from 0000 to 2359 to write the time to a text file and I got this:

15.57
16.00
16.30
20.30
22.30
00.00
11.30
12.00
20.00
22.00

It's now 10.48, so it didn't run once in the last 10 hours.

I rebooted my phone at around 08.00.

I have the latest stock firmware on the S6 which was released around 2 weeks ago.

App optimisation is on in general, but off for Tasker and all plugins.

Running Google Launcher.

Pent - happy to test anything you suggest.

[Piotr.23]

Same here: the latest stock firmware on the S6 which was released around 2 weeks ago.

However, I found something interesting: when I disabled Chime Time

https://play.google.com/store/apps/details?id=hyperfine.chimes&hl=en

the Time context profile started to work (but the next day, it stopped again)

BTW, Chime Time rings exactly 3 minutes past hour... the author says it could be due to the restrictive energy saving

Piotr

[YY-YY]

Tests on my  SG S4 5.0.1. give similar schemes to the ones mentionned in other posts. Thus, as I understand, it is not specifically linked to the 5.1.x OR 6.x updates.  YY

[Brian Houghton]

My Note 4 running 5.0.1 hasn't had any problems waking for timed events.

On Thu, Oct 29, 2015 at 12:20 PM, YY-YY <yves.f...@gmail.com> wrote:

Tests on my  SG S4 5.0.1. give similar schemes to the ones mentionned in other posts. Thus, as I understand, it is not specifically linked to the 5.1.x OR 6.x updates.  YY

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.

Visit this group at http://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

--

-------------------------------
Regards,
Brian Houghton
bahou...@gmail.com

[Pent]

Pent - happy to test anything you suggest.

I don't think you mentioned anything from the Run Log ?

(please check my previous post but one)

Pent

[Adam Greatrix]

There are no monitor entries at all in my run log. The only Status=Start entries that I have are the expected TaskService.

[ISILDUR]

Same problem with me, SGS6. I have noticed that more apps have similar problem like alarm clock app called Timely. However there are other alarm clock apps that can handle with this problem on time (like Alarm Clock Extreme Free). So it seems that can be resolved. Other thing I have noticed is how android handle time updates when screen is off - when turning screen on you can see for a half of second old time (before phone was put into sleep mode). That time is updated in blink of an eye to the current time. So possible Tasker is using this not refreshed time when screen is off? Maybe other way of getting time from system should be implemented in Tasker? I dont remember this behavior on previous Galaxy devices like S5, S4, S3 - time was already updated when you turned on screen. Probably Sammy not updating system time when sleep for battery saving purposes.

[Adam Greatrix]

I just checked my text file that is updated with the time every 30 minutes, and noticed something interesting...

There is an obvious gap in the times from when I go to bed at night, until the time I up in the morning.

But some days it IS working correctly, right through the night. I wonder what is making it work some nights and not others.

One idea is that I have a notification reminder profile, which repeats a notification every 5 minutes to remind me to look at my phone if I miss something. I wonder if it's working on nights when someone messages me after I've put my phone on silent, and the repeat notification is waking the phone every 5 minutes?

Log follows...

15.57 (task test)

16.00
16.30
20.30
22.30
00.00
11.30
12.00
20.00
22.00

11.00
14.00
17.30
18.00
21.00
21.30
22.00
00.00
09.30
13.30
18.00
20.00
00.00
10.30
11.00
13.30
14.30
17.30
18.00
18.30
09.00
10.30
11.30
12.00
17.30
20.00
23.30
00.00
10.00
11.30
12.00
19.00
19.30
20.00
20.30
22.30
08.30
09.00
10.00
10.30
11.30
12.00
12.30
13.00
14.00
16.00
20.00
21.00
01.00
09.00
09.30
10.00
12.00
14.30
16.00
16.30
17.00
17.30
23.30
00.00
08.00
08.30
09.00
09.30
10.00
10.30
11.00
11.30
12.00
12.30
13.00
13.30
14.00
14.30
15.00
15.30
16.00
16.30
17.00
17.30
18.00
18.30
19.00
19.30
20.00
20.30
21.00
21.30
22.00
22.30
23.00
23.30
00.00
00.30
01.00
01.30
02.00
02.30
03.00
03.30
04.00
04.30
05.00
05.30
06.00
06.30
07.00
07.30
08.00
08.30
09.00
09.30
10.00
10.30
11.00
11.30
12.00
12.30
13.00
13.30
14.00
14.30
15.00
15.30
16.00
16.30
17.00
17.30
18.00
18.30
19.00
19.30
20.00
20.30
22.30
00.30
01.00
10.30
11.00
11.30
12.00
13.30
19.30
23.30
00.30
01.00
10.00
10.30
12.00
13.00
13.30
14.30
15.00
15.30
16.00
16.30
17.00
17.30
18.00
18.30
19.00
19.30
20.00
20.30
21.00
21.30
22.00
22.30
23.00
23.30
00.00
00.30
01.00
01.30
02.00
02.30
03.00
03.30
04.00
04.30
05.00
05.30
06.00
06.30
07.00
07.30
08.00
08.30
09.00
09.30
10.00
10.30
11.00
11.30
12.00
12.30
13.00
13.30
14.00
14.30
15.00
15.30
16.00
16.30
17.00
17.30
18.00
18.30
19.00
19.30
20.00
20.30
21.00
21.30
22.00
22.30
23.00
23.30
00.00
00.30
01.00
01.30
02.00
02.30
03.00
03.30
04.00
04.30
05.00
05.30
06.00
06.30
07.00
07.30
08.00
08.30
09.00
09.30
10.00
10.30
11.00
11.30
12.00
12.30
13.00
13.30
14.00
14.30
15.00
15.30
16.00
16.30
17.00
17.30
18.00
18.30
19.00
19.30
20.00
20.30
21.00
21.30
22.00
22.30
23.00
23.30
00.00
00.30
01.00
01.30
02.00
02.30
03.00
03.30
04.00
04.30
05.00
05.30
06.00
06.30
07.00
07.30
08.00
08.30
09.00
09.30
10.00
10.30
11.00
11.30
12.00
12.30
13.30
14.00
14.30
15.00
15.30
16.00
16.30
17.00
17.30
18.00
18.30
19.00
19.30
20.00
20.30
21.00
21.30
22.00
22.30
23.00
23.30
00.00
00.30
01.00
01.30
02.00
02.30
03.00
03.30
04.00
04.30
05.00
05.30
06.00
06.30
07.00
07.30
08.00
08.30
09.00
09.30
10.00
10.30
11.00
11.30
12.00
12.30
13.00
13.30
14.00
14.30
15.00
15.30
16.00
16.30
17.00
17.30
18.00
18.30
19.00
19.30
20.00
20.30
21.00
21.30
22.00
22.30
23.00
23.30
00.00
00.30
01.00
01.30
02.00
02.30
03.00
03.30
04.00
04.30
05.00
05.30
06.00
06.30
07.00
07.30
08.00
08.30
09.00
09.30
10.00
10.30
11.00
11.30
12.00
12.30
13.00
13.30
14.00
14.30
15.00
15.30
16.00
16.30
17.00
17.30
18.00
18.30
19.00
19.30
21.00
23.00
23.30
00.00
00.30
10.00
12.00
14.00
20.00
23.00
01.00
01.30
10.00
11.00
11.30
12.00
12.30
13.00
13.30
14.00
14.30
15.00
15.30
16.00
16.30
17.00
17.30
18.00
18.30
19.00
19.30
20.00
20.30
21.00
21.30
22.00
22.30
23.00
23.30
00.00
00.30

[Ritchie Joe]

are you making any progress pent?

[ISILDUR]

well... any luck?

[Pent]

I don't know what will work on which device, but I have a new beta for testing soon, yes.

Pent

[Pent]

I posted a new beta (4.8b3), please try it out (make sure you
read the link in the post first...)

Pent

[Manuel Fernández Gómez]

Made the same test that didn't work with all the previous versions, but with 4.8b3, IT HAS WORKED!

The test consists in a profile that triggers with a specific calendar entry. The task just sets a global cleaned variable to 1. Then, add a calendar event that starts in more than 10 minutes (so the phone enters in deep sleep) and with a duration of just 1 minute. Finally, lock the phone and wait without waking it up in 12-14 minutes, to assure that the calendar event has taken place, and then check the variable value.

With all previous versions, the variable was still unset. -> So the profile didn't triggered.
With this 4.8b3 version, the variable is set to 1, as expected. -> Ok.

I've set the new "Use Reliable Alarms" setting to "When Off". Using S6 Edge with 5.1.1, and Tasker set to "Never" in app optimization.

[Cengiz]

Similar to the timing problem in Android M, Samsungs new Android L updates with "Smart Manager" app also restricts time rate and breaks time-context profiles of tasker. We are also discussing this issue and may be helpful for "doze" related problem, see the link below:

https://groups.google.com/forum/#!topic/tasker/49QaFLO5Sjo

Samsung Smart Manager app definitely prevents a profile (or profiles) to be activated repeatedly within less than 5 minutes!!! 

---------

BUT as I wrote, new tasker update (https://groups.google.com/forum/#!topic/tasker/f83LWBsBx9A) has an improvement.

Now two or more profiles can be triggered at the same time (as long as they are simultaneous -same exact trigger time- and obey the minimum 5 minute restriction.

I don't know how Samsung can achieve this weird time limitation!!!

24 Ekim 2015 Cumartesi 23:24:29 UTC+3 tarihinde Mike yazdı:

so I did a context 'every 30mins'  with task write on file,  and another one every 30 mins from 4.05 to 00.05.

now it's 22:25 here,  this is the result
the first context wrote
14.00
14.30
17.30
18.02

the second context wrote
12.05
16.06
17.05
17.35
22.05

it MIGHT be Samsung related as it was working fine before my last firmware upgrade,  yet I hope there is a solution for this,  especially for the calendar entry event context that keeps starting 2 or 3 mins later (my phone is not muted on time anymore !).

Will the future marshmallow upgrade (that should arrive in December for the s6 edge)
-keep that bug or
-will it be fixed in any marshmallow (even a Samsung one) ?
- or we can't know yet?

thanks

[Niclas]

I tried to reproduce this on my s6 running 5.1.1 but am not seeing the issue you describe. I have 3 different profiles running simultaneously and triggering at different times, using 2,5 and 10 minute intervalls. All three are triggering correctly and writing the times to a log without missing a beat.

I have reliable alarms set to always and battery optimization disabled for tasker.

[Cengiz]

Good news. May be I should try it again with "always" option. I set reliable alarms to "when off" in order not ot see alarm icon at the notification area when screen is on. 

What is the exact effect of the "when off" and "always" options, does it make any difference on tasker's screen-off performance?

26 Kasım 2015 Perşembe 09:58:38 UTC+2 tarihinde Niclas yazdı:

[Pent]

What is the exact effect of the "when off" and "always" options, does it make any difference on tasker's screen-off performance?

Those options should have the same effect when screen is off.

Pent

[Adam Greatrix]

Alas, the beta doesn't fix the issue for me. I currently have a profile set to run every 10 minutes, and another every 30, both logging to a text file as above, and neither are running with the screen off.

If you need anything from me Pent, just ask.

[Adam Greatrix]

Trying with Use Reliable Alarms set now...

[Adam Greatrix]

All seems to be working fine with Use Reliable Alarms set on, and latest beta!

[Pent]

All seems to be working fine with Use Reliable Alarms set on, and latest beta!

How about with that set to When Off ?

Pent

[Adam Greatrix]

I'll test "When Off" now. Still working flawlessly with it set to Always.

[Adam Greatrix]

When Off has been selected for about 4 hours now, and everything has executed at exactly the right time with the screen off.

[YY-YY]

Today retests on the same

S G S4,   5.0.1, LRX22C;   battery:app optimisation = off.

Tasker 4.8b4m, use reliable alarms = always, 

Single profile (priority 50) every 6 min, write time (with secs) to file. I  tried half an hour ago,  it didn't trigger as soon as asleep.

YY

PS. Tasker scheduling was very important to me. I knew it was not the easiest to start with but accepted it because of its reliability.  Now, I lost confidence.  What alternative? Do other apps --like auto..te or aut...it or macr..id--  suffer from the same trouble? 

God damn those android updates...

[Pent]

6 minutes after display-off shouldn't be a problem even on MM, it takes a while to go into
Doze. It's more probably something to do with Samsung IMO. Perhaps something is killing
the service, especially likely if you have a rooted device or custom ROM.

Look in Menu / More / Run Log, see if you see lines describing a monitor restart,
they should be very rare in-between changes to data in the UI.

I presume you have also Run In Foreground checked in Monitor preferences.

Pent

[YY-YY]

No root, no custom

<Run In Foreground> is checked in Monitor preferences . SHould I remove this?

I could not tell what was in the log as run log was off

Now I just started the log... (Small question, what is the rule for tasker to chop the log file?  I think that, very often, I only have 3 minuts of log.)

Thanks Pent

YY.

[YY-YY]

NO MONITOR RESTART

www.alala.be/runlog.txt (interval 6 min for task  SysTest5Min.... but 13:42:00 14:00:25)

After starting run log, I don't see any restart of the monitor...

(No root, no custom,  <Run In Foreground> checked)

[Adam Greatrix]

Not running any kind of app killer or battery saving apps either Yves?

Pent - I'm going to call the issue described originally as fixed. Since installing the beta a few days ago and switching Use Reliable Alarms on in the preferences, all time based repeating profiles have started their takes exactly when expected.

For reference, this is on a Samsung Galaxy S6 running the latest 5.1.1 stock firmware for this device. App Optimisation is on in general, but explicitly turned off for Tasker and its plugins.

Thanks!

--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/5etY6GHxCO4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.

[YY-YY]

App Killer Running?  Not that I am aware of.  ( ZD Box is installed.  I didn't ask it to kill anything - except maybe a couple of times manually).

[Pent]

App Killer Running?  Not that I am aware of.  ( ZD Box is installed.  I didn't ask it to kill anything - except maybe a couple of times manually).

Sorry, I'm out of ideas, but it's probably something related to your particular setup, since
most (all other ?) seem to have seen the problem fixed with the latest beta.

Pent

[Andrea Bruzzesi]

Well, I for one still have the issue with stock Xiaomi MIUI firmware, even with any battery-saver feature disabled.

What I noticed is that the alarm clock icon didn't show-up on the statusbar whatever Tasker reliable alarm setting was set to.

Luckily I have the option to use an unofficial CyanogenMod ROM, but you might consider that Xiaomi is the fifth brand world wide (first in China) and have millions of active devices.

Not that I think this issue is Tasker's fault anyway, beware, I'm just adding something to think about.

[Pent]

Well, I for one still have the issue with stock Xiaomi MIUI firmware, even with any battery-saver feature disabled.

What I noticed is that the alarm clock icon didn't show-up on the statusbar whatever Tasker reliable alarm setting was set

Weird, you shouldn't be shown the option unless the functions are available in the ROM, so presumably
the call is being ignored or denied.

Pent

[Adam Greatrix]

An alarm clock icon shows in the status bar when Use Reliable Alarms is on?? Doesn't here...

--

[Pent]

An alarm clock icon shows in the status bar when Use Reliable Alarms is on?? Doesn't here...

Ah, sorry, I remember now that the API docs say that it *may* cause a visual indication
to the user that an alarm has been set, some ROMs have chosen not to it seems.

Pent

[YY-YY-YY1]

Hi,
What a pain. When running on my wife's S4, the problem is the same.
I am now using Automate from llamalab to write the time to a file. Then, in tasker, I use a profile triggered by a file change to schedule the periodic activity. The problem seems to be a Tasker problem, as Automate is very precise and very very low battery consuming!!!
Y

[YY-YY-YY1]

NB Automat write period is 5 minutes