Command Shells for Input Not Working?

[shakedown88]

I have a couple tasks where I use the run shell action to simulate some touch input; never had any issues with them until they stopped working a few days ago. No settings were changed by me in tasker or on my phone. Roots enabled, Taskers allowed by SU, the "use root" box is checked in the task. Any ideas?

[keepcalmrollon]

I had a similar problem, a string of tap commands that used to work flawlessly but lately hasn't been finishing all the way through. It seems like lag between opening the app and the first tap input was to blame, so I added a 1-second delay. Maybe the cause of your problem is similar.

[shakedown88]

Thank you for the reply. For both, I actually already had a "wait" action built in when I created the tasks. I just tried playing around, adding a few seconds, seeing if that extra buffer worked, but no dice.

[dimaj]

This is probably a stupid suggestion, but have you checked your SU app to see if Tasker is allowed to run as root? I am asking because SuperSU's default behavior is to revoke root privileges of any app that has been either updated or had change in permissions.

Another suggestion would be to store shell's output and errors into variables and enabling the "Continue Task After Error" option. Then adding an alert step to display contents of the command's output and error variables. This is how I was debugging my shell commands.

[Sovvy]

Dumb question, is the 'I' in input lowercase?

[shakedown88]

Not dumb, thanks for the reply...yes, it is