Can you try as below .
1. Create New Profile with Context -> Application
2. Here Select Your Application and create a Task with TASK -> Wait. Give few Seconds
3. Create another Task separately and Set Display Timeout to whatever you need. Give Name to task.
4. Long press the profile Task above and select Exit Task. Select task create for setting timeout.
So When your application open, tasker will not do anything, but as soon as you come out from that application, tasker should set the desire timeout.
Thanks & Regards
Sunil
--
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/IGP7oyOby8w/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/groups/opt_out.
I understand what you're saying, the application context won't work (although I applaud your attempt to work around it, very creative).
What you need, is a way to reset your ideal display timeout when using your media player! This is the process utilized by your device for live streams.
Now, it might be possible to use a %WIN context (maybe in conjunction with, or without the app context) to determine the media player is streaming content. For my device, the %WIN value becomes 'streaming media player'.
So, I suggest determining if this is true for your device during this process, and using that variable value as the activation context to start a task that sets your display timeout to the ideal setting.
> I have developed a semi-functional way to have the screen timeout with the video feed up. It entails an application trigger for the profile and a wait command, followed by a lock screen action
You have probably already tried this, but wouldn't just changing the screen timeout at this point 'after the wait' to work?
I could be wrong but here is how I think it would work..
1. App starts
2. Tasker detects app and starts wait action
3. App sets time out to always on and starts running.
4. After the short wait tasker now sets screen timeout.
I could be wrong about the way the application handles the screen always on...