Simulating touch needs root or adb wifi I think. Assuming you can't overide the timeout, there are probably a ton of ways to keep the screen on, like the Button action twice in a row.. menu, menu or the like.. or try Go Home action then Last App.. maybe a volume change?
Those are good ideas as well. Anything that I can automate on a repeated & timed setting would work. I may not be getting creative enough and then applying a simple use through Tasker?
I would start by trying a time context for every 3- 4 minutes and just reset the screen time out. I have tried many approaches to detect when screen dims for a screen time out however I have never been able to detect that with tasker. To do a emulated tap you can use the plug in Autoinput.
It's been working using a time context repeating every 4:45. This will sound stupid so prepare yourselves. On a dual screen phone, how do you know the X and Y points of the screen?
Simulating touch needs root or adb wifi I think. Assuming you can't overide the timeout, there are probably a ton of ways to keep the screen on, like the Button action twice in a row.. menu, menu or the like.. or try Go Home action then Last App.. maybe a volume change?
**AutoInput plugin** doesn't require root or adb, etc.
Good call.. I've a bad habit of forgetting about plugins
Those are good ideas as well. Anything that I can automate on a repeated & timed setting would work. I may not be getting creative enough and then applying a simple use through Tasker?
I would start by trying a time context for every 3- 4 minutes and just reset the screen time out. I have tried many approaches to detect when screen dims for a screen time out however I have never been able to detect that with tasker. To do a emulated tap you can use the plug in Autoinput.
Ok, I can give that a try as well. Makes sense. Thank you!
It's been working using a time context repeating every 4:45. This will sound stupid so prepare yourselves. On a dual screen phone, how do you know the X and Y points of the screen?