I have a task that I'm trying to run 10 minutes after my screen goes off, but I'd like it to only trigger again when the screen goes back on instead of repeating a 10 minute loop. Is this possible?

57 views
Skip to first unread message

joy

unread,
Jan 23, 2017, 4:44:59 PM1/23/17
to Tasker
I thought that "Events" would only run the attached task once when the settings are met. But it seems that it keeps running - every 10 minutes as long as my display remains off.

I don't know how to get around this. Any ideas?

Logan Fury

unread,
Jan 23, 2017, 6:06:16 PM1/23/17
to Tasker
This isnt elegant, and very basic (as is my Tasker knowledge) but may work for you:

Add an action at the end of the repeating every 10 mins task to set your Tasker Profile thats firing it to OFF
Add an additional profile with a state of Display On with the action of setting that same Tasker Profile to ON

I believe this would be a brute force way to toggle the profile into inactivity with screen off, to stop the continued running, but have it immediately reactivate and be standing by for conditions as soon as screen is on again.

Hope this helps,

Logan

Rich D

unread,
Jan 23, 2017, 6:52:26 PM1/23/17
to Tasker Google Groups Post




I don't know how to get around this. Any ideas?





Could you post your profile  here...  

Long press on the profile or task name / ( 3 dot menu with 4.0+ ) export / export "DESCRIPTION" to clipboard (not XML)

Any linked tasks will be exported with the profile they are linked to..

To be able to export, The beginner mode needs to be off and the profile needs to be named by you (Not the Tasker listed name.  Tasker will list your profile with the context name if you have not given it one).



joy

unread,
Jan 23, 2017, 6:56:58 PM1/23/17
to Tasker
Thank you for the replies.

Here is my exported profile. I realize that Greenify has a lock and Greenify option and an auto option, but I find when I'm on my phone, if I forget to do something and try to turn my phone back on, the Greenify action makes my phone lag. Adding the "wait" more or less that I'm done using my phone for whatever activity I previously performed. If that makes sense....

Profile: Greenify (24)
Cooldown: 20
Event: Display Off
Enter: Greenify (56)
Abort Existing Task
A1: Wait [ MS:0 Seconds:0 Minutes:10 Hours:0 Days:0 ]
A2: Stop [ With Error:Off Task: ] If [ %SCREEN ~ on ]
A3: Hibernate Now [ Configuration:All greenified apps Timeout (Seconds):0 ]

joy

unread,
Jan 23, 2017, 6:58:04 PM1/23/17
to Tasker
Oops the cool down options shouldn't be there. I was just trying to see if that might help to limit to executes to my liking,which will ultimately be my alternative setup.

Rich D

unread,
Jan 23, 2017, 7:22:45 PM1/23/17
to Tasker Google Groups Post

Here is my exported profile. I realize that Greenify has a lock and Greenify option and an auto option, but I find when I'm on my phone, if I forget to do something and try to turn my phone back on, the Greenify action makes my phone lag. Adding the "wait" more or less that I'm done using my phone for whatever activity I previously performed. If that makes sense....


I do not know what greenify is or what it does, so I really do not understand that.


Profile: Greenify (24)
        Cooldown: 20
        Event: Display Off
Enter: Greenify (56)
        Abort Existing Task
        A1: Wait [ MS:0 Seconds:0 Minutes:10 Hours:0 Days:0 ]
        A2: Stop [ With Error:Off Task: ] If [ %SCREEN ~ on ]
        A3: Hibernate Now [ Configuration:All greenified apps Timeout (Seconds):0 ]

This profile should only Trigger once when the display goes off.  It should not be looping. I would start by checking the run log (menu / more / run log) to see if there are any clues there. You can post the relevant part of the log here as well.  I would suspect something is turning your display on and off and re-triggering the profile.

Joy Moleta

unread,
Jan 23, 2017, 7:44:12 PM1/23/17
to tas...@googlegroups.com
Thank you. I'll have it run for a while and get back to you.

--
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/crZIYHmDviU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tasker+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

joy

unread,
Jan 23, 2017, 9:11:38 PM1/23/17
to Tasker
I shortened the wait time to see the actions. It keeps looping. The screen was off the entire time and I didn't move it at all.


20170123 15.51.58 M Restart ID0:0.0 Monitor
20170123 15.52.00 P Active ID15 Keep Screen
20170123 15.52.00 T Running ID16:2 Keep Screen
20170123 15.52.00 A OK ID56.1 Greenify.Wait
20170123 15.52.00 A OK ID16:2.1 Keep Screen.Display Timeout
20170123 15.52.00 T ExitOK ID16:2 Keep Screen
20170123 15.52.03 P Inactive ID15 Keep Screen
20170123 15.52.03 T Running ID-1029:3 System
20170123 15.52.03 A OK ID56.1 Greenify.Wait
20170123 15.52.03 A OK ID-1029:3.1 Anon.Display Timeout
20170123 15.52.03 T ExitOK ID-1029:3 System
20170123 15.52.06 P Instant ID24 Greenify
20170123 15.52.06 T ExitRep ID56 Greenify
20170123 15.52.06 T Running ID56:4 Greenify
20170123 15.52.06 A OK ID56.1 Greenify.Wait
20170123 15.56.02 A OK ID56:4.1 Greenify.Wait
20170123 15.56.02 A IfFail ID56:4.2 Greenify.Stop
20170123 15.56.02 A OK ID56:4.3 Greenify.com.oasisfeng.greenify\n***\n*!&$*;com.oasisfeng.greenify.GreenifyShortcut
20170123 15.56.02 T ExitOK ID56:4 Greenify
20170123 15.56.02 E Stop ID0:0.0 TaskService
20170123 15.56.09 P Instant ID24 Greenify
20170123 15.56.09 E Start ID0:0.0 TaskService
20170123 15.56.09 T Running ID56 Greenify
20170123 16.01.03 A OK ID56.1 Greenify.Wait
20170123 16.01.03 A IfFail ID56.2 Greenify.Stop
20170123 16.01.03 A OK ID56.3 Greenify.com.oasisfeng.greenify\n***\n*!&$*;com.oasisfeng.greenify.GreenifyShortcut
20170123 16.01.03 T ExitOK ID56 Greenify
20170123 16.01.03 E Stop ID0:0.0 TaskService
20170123 16.09.47 P Active ID15 Keep Screen
20170123 16.09.47 E Start ID0:0.0 TaskService
20170123 16.09.47 T Running ID16 Keep Screen
20170123 16.09.47 A OK ID16.1 Keep Screen.Display Timeout
20170123 16.09.47 T ExitOK ID16 Keep Screen
20170123 16.09.47 E Stop ID0:0.0 TaskService

Rich D

unread,
Jan 24, 2017, 1:42:15 PM1/24/17
to Tasker Google Groups Post

Could you also post the description of the "Keep Screen" profile?

The log shows the profile going active again in approx 4 min. So it appears a app or Tasker is turning on the display. Do you have the cell near work around ticked in the Tasker preferences?

Rich D

unread,
Jan 24, 2017, 4:19:18 PM1/24/17
to Tasker Google Groups Post


The log also shows the profile triggering 7 seconds after this action.

  A3: Hibernate Now [ Configuration:All greenified apps Timeout (Seconds):0 ]

You can try disabling this action and run the test again and check the run log to see if this action is  causing the issue. To disable a action just long press it and tap the power button icon.


Another thing to try is add a notify action as the first action in the task and have it give you %SCREEN.  This will tell you if your screen is truly on when the profile triggers. 

joy

unread,
Jan 24, 2017, 4:20:53 PM1/24/17
to Tasker
The keep screen profile just keeps the display on when specified apps are running. Tasker is one of the apps that I setup to run on this profile. That's why you see the profile on when we I clear the log and again when I return to tasker to copy the log.

After much research on this I think I've found something that will work that I can configure and understand. I've read the suggestion of running two profiles but within that is the use of variables and I'm not an advanced user.

I created the profile to run every 30 minutes and configured the task with if/else functions to trigger the task of Greenify.

BTW, Greenify is just an app that hibernates(force closes) apps that are not being used but are running in the background.

Thanks for your help Rich D.

joy

unread,
Jan 24, 2017, 4:25:34 PM1/24/17
to Tasker
Thank you. I did go ahead and use %SCREEN instead of the display off event. This seems to be a more stable setup so far.
Reply all
Reply to author
Forward
0 new messages