Need help with rapid touch pressing

[Rimon Thomas]

Hi,

I am new in this forum and to the app Tasker.

I am looking for help to make my tasker do a pressing/tap loop.

E.g pressing the volume up button starts the task and starts pressing on the middle of the screen. By pressing volume down button the task should stop.

Can anyone help me?

Thank you

[easiuser]

I think the only way to detect a volume up/down button press in native Tasker is to detect a change in the volume level.  This doesn't work if you are already at min/max volume.

You will need a rooted phone and you can run the shell command "input tap xpos ypos" to simulate a press on the screen.

The Autoinput plugin can intercept volume button presses and start/stop a task  Autoinput can also simulate screen taps without root but I have had limited success with non-rooted devices.

[John Doe]

TouchTask plugin can perform what you need

[Rimon Thomas]

Thank you for your replies.

I downloaded Touchtask and I did not make more progress than with Tasker.

I manage to start a task that goes home and opens an app, but it does not want do the next task which is tp tap on a specific x,y position. When enabling each task manually with >> button, I get an error message for the tap task:

06.52.24/E FIRE PLUGIN: Actions / com.twofortyfouram.locale.intent.action.FIRE_SETTING: 7 bundle keys
06.52.24/E Actions: plugin comp: com.balda.touchtask/com.balda.touchtask.receivers.FireReceiver
06.52.24/E add wait type Plugin11 time 1
06.52.24/E add wait type Plugin11 done

What does that mean??
My phone is not rooted.

I am going crazy, I feel like what I want to do is easy, rapid touch press on a specific x,y position, but I don't know how to do it.

I appreciate your help!!

[John Doe]

It's the strange way of Tasker to say that the action is not completed, an error or timeout occurred. You can use "continue after error" and print %errmsg. It could be worth to have a screenshot of your "tap" action and maybe the export of your task. On Android version older than Nougat, it's possible that an accessibility service can't tap on a specific x y point, it's a platform limitation. Did you select the point using x y manually or you used the helper button?