Android, low level shell click on screen
Use: input tap x y
(also input text, swipe, keyevent are available)
adb shell input tap x y
adb shell input swipe x1 y1 x2 y2
adb shell input text Hello!
adb shell input keyevent ID
By this way you do not need to care about hardware implementation. Using events you will have to imeplemnt them for each device. All these commands could be executed on device or on PC via ADB.
Happy testing! (:
To send touch event you need to do:
1 Set coordinates:
1 | <span style="color: #660000;">adb shell sendevent </span><span style="color: #660000;">/</span><span style="color: #660000;">dev</span><span style="color: #660000;">/</span><span style="color: #660000;">input</span><span style="color: #660000;">/</span><span style="color: #660000;">event2 </span><span style="color: #660000;">3</span><span style="color: #660000;"> </span><span style="color: #660000;">0</span><span style="color: #660000;"> x<br />adb shell sendevent </span><span style="color: #660000;">/</span><span style="color: #660000;">dev</span><span style="color: #660000;">/</span><span style="color: #660000;">input</span><span style="color: #660000;">/</span><span style="color: #660000;">event2 </span><span style="color: #660000;">3</span><span style="color: #660000;"> </span><span style="color: #660000;">1</span><span><span style="color: #660000;"> y</span></span> |
2 Send touch event (must have 0 0 0 pair):
1 | <span style="color: #660000;">adb shell sendevent </span><span style="color: #660000;">/</span><span style="color: #660000;">dev</span><span style="color: #660000;">/</span><span style="color: #660000;">input</span><span style="color: #660000;">/</span><span style="color: #660000;">event2 </span><span style="color: #660000;">1</span><span style="color: #660000;"> </span><span style="color: #660000;">330</span><span style="color: #660000;"> </span><span style="color: #660000;">1</span><span style="color: #660000;"><br />adb shell sendevent </span><span style="color: #660000;">/</span><span style="color: #660000;">dev</span><span style="color: #660000;">/</span><span style="color: #660000;">input</span><span style="color: #660000;">/</span><span style="color: #660000;">event2 </span><span style="color: #660000;">0</span><span style="color: #660000;"> </span><span style="color: #660000;">0</span><span style="color: #660000;"> </span><span style="color: #660000;">0</span><span><br /></span> |
3 Send release finger event (must have 0 0 0 pair):
1 | <span style="color: #660000;">adb shell sendevent </span><span style="color: #660000;">/</span><span style="color: #660000;">dev</span><span style="color: #660000;">/</span><span style="color: #660000;">input</span><span style="color: #660000;">/</span><span style="color: #660000;">event2 </span><span style="color: #660000;">1</span><span style="color: #660000;"> </span><span style="color: #660000;">330</span><span style="color: #660000;"> </span><span style="color: #660000;">0</span><span style="color: #660000;"><br />adb shell sendevent </span><span style="color: #660000;">/</span><span style="color: #660000;">dev</span><span style="color: #660000;">/</span><span style="color: #660000;">input</span><span style="color: #660000;">/</span><span style="color: #660000;">event2 </span><span style="color: #660000;">0</span><span style="color: #660000;"> </span><span style="color: #660000;">0</span><span style="color: #660000;"> </span><span style="color: #660000;">0</span><span><br /></span> |
Please note:
1 You can record events:
1 | <span><span style="color: #660000;">adb shell getevent</span></span> |
2 if you use getevent all event values are in hex.
CONFIRMED, THIS WAY IS NOT WORKING ANYMORE, at least for Android 2.2.
I have rechecked, Android low level events signature was changed starting from Android 2.2 Froyo.
I just dumped single click:
/dev/input/event2: 0003 0030 00000068
/dev/input/event2: 0003 0032 0000000a
/dev/input/event2: 0003 0035 0000022e
/dev/input/event2: 0003 0036 00000039
/dev/input/event2: 0000 0002 00000000
/dev/input/event2: 0003 0012 0000002f
/dev/input/event2: 0003 0014 00000001
/dev/input/event2: 0000 0000 00000000
/dev/input/event2: 0003 0030 00000000
/dev/input/event2: 0003 0032 0000000a
/dev/input/event2: 0003 0035 0000022e
/dev/input/event2: 0003 0036 00000039
/dev/input/event2: 0000 0002 00000000
/dev/input/event2: 0003 0012 00000020
/dev/input/event2: 0003 0014 00000000
/dev/input/event2: 0000 0000 00000000
It has obviously another structure.. I’m investigating right now this situation,
solution will be here tomorrow 😉
After a quick investigation I have reproduced the click for Froyo Android:
Perl script (click on screen at 558, 57 point):
system(“adb shell sendevent /dev/input/event2 0003 48 104“);
system(“adb shell sendevent /dev/input/event2 0003 50 10“);
system(“adb shell sendevent /dev/input/event2 0003 53 558“);
system(“adb shell sendevent /dev/input/event2 0003 54 57“);
system(“adb shell sendevent /dev/input/event2 0000 2 00000000“);
system(“adb shell sendevent /dev/input/event2 0003 18 47“);
system(“adb shell sendevent /dev/input/event2 0003 20 00000001“);
system(“adb shell sendevent /dev/input/event2 0000 0000 00000000“);
system(“adb shell sendevent /dev/input/event2 0003 48 00000000“);
system(“adb shell sendevent /dev/input/event2 0003 50 10“);
system(“adb shell sendevent /dev/input/event2 0003 53 558“);
system(“adb shell sendevent /dev/input/event2 0003 54 57“);
system(“adb shell sendevent /dev/input/event2 0000 0002 00000000“);
system(“adb shell sendevent /dev/input/event2 0003 18 32“);
system(“adb shell sendevent /dev/input/event2 0003 20 00000000“);
system(“adb shell sendevent /dev/input/event2 0000 0000 00000000“);
How I did it:
1. Start dump motion event you need to reproduce:
grep is very useful to filter output.
2. Do motion event you want to reproduce;
3. Than just convert all values from hex in dump to decimal values! 🙂
To find what eventX is working for you do following:
1. Start terminal and type
Please check my tutorial for low level interaction with device
Happy motion events reproducing! (:
Best regards,
Yahor
Lets decide, do you want to reproduce single tap?
If true - you can find a minimal set of events for this task in this article for point 558,57.
I just have started investigation and it is very cool that you are interested in my article :)
Answer, why you are getting different number of events:
a) you will never get less set of events, I have
http://softteco.blogspot.com/2011/03/android-writing-events-low-level-touch.html
It describes basics how to use getevents and sendevent.
I will highly appreciate any comment :) If you feel that you need some more info - just specify what you are interested in, and I will added it during launch
To record your own script based on your actions, rather than programming:
# convert getevent string to sendevent string
function convert_input()
{
awk '{
if (($1 != "") && (substr($0,1,1)=="/"))
{ sub(":","",$
Hello, PB,
The way is cool!
But, do you know how to add custom coords into this function?
Best regards,
Yahor
is this what you mean ? if you take your original code, you can do this:
# send a touch event at X Y
function atouchxy()
{
adb shell sendevent /dev/input/event3 0003 48 104
Yep, such scripts are more interesting :) But most interesting is to reproduce by this way drag motion event. Do you succeed to reproduce dragging? I have reproduced only short drag via shell script (Like you are preparing 2 fingers, touch screen by left finger, release, immideatelly touch screen by right finger.) Using this approach I'm unlocking the device.
On my Samsung Galaxy Tab (2.2) the sequence from getevent was shorter (12 lines instead od 16):
// touch screen:
/dev/input/event2: 0003 0035 0000039f // 53
/dev/input/event2: 0003 0036 0000022f // 54
/dev/input/event2: 0003 0030 00000028 //48
/dev/input/event2: 0003 0032 00000001 //50
/dev/input/event2: 0000 0002 00000000 //2
/dev/
thank you very much
KJ
You are very welcome, both line are optional and looks like used only for swipe motions.
Convert_input usage was perfectly described by PB:
adb shell getevent | convert_input > draw_a_circle.sh
Best regards,
Yahor
Thanks for such a useful blog.
I wanted to know if we can add delay while sending the commands?
i am capturing events using 'adb shell getevent' and sending the same sequence using 'adb shell sendevent'.
The application time to respond and meanwhile the sequence is lost. Any inputs shall be of great help.
You can use: sleep N
where N is timeout in seconds (but you able to specify milliseconds like: N=0.1).
Best regards,
Yahor
I am trying this but it's not working.
this is my output from getevent:
/dev/input/event4: 0003 002b 002c0003
/dev/input/event4: 0003 002a 820301ad
/dev/input/event4: 0003 002b 00120002
/dev/input/event4: 0003 002a 820301ad
/dev/input/event4: 0003 002b 00000000
/dev/input/event4: 0003 002a 80000000
/dev/input/event4: 0003 002b 00250004
What device do you use? Htc?
You have to analyse this output and find how to decode them :)
3 42 0 is 0 0 0 :)
Could you please try to do the following:
1. do a very quick click into 0,0 on your device and save the output;
2. do a very quick click into 0, 100 coord on your device and save the output;
3. do a very quick click
you can post only hex output, because decimal output has no sense :)
Best regards,
Yahor
/dev/input/event4: 0003 002b 00000000
/dev/input/event4: 0003 002a 80000000
/dev/input/event4: 0003 002b 00000000
/dev/input/event4: 0003 002a 80000000
I don't have time now to setup robotium, I will tonight
I have been working on decoding getevent.
after i take my finger off the screen the last command is always:
0003 002b 00000000
0003 002a 80000000
I can reproduce a click with only 4 lines, so only two lines actually make the click
the first is usually
00**000*
(0's stay the same but
Is there anything else I could try to get more accurate clicks?
Dan
Could you please try to do the following:
1) adb shell getevent
2) copy all interfaces list event0-N and post them with theirs names, like:
add device 1: /dev/input/event3
name: "kxtf9_accel"
add device 2: /dev/input/event0
name: "gpio-keys"
add device 3: /dev/input/event2
name: &
name: "compass"
add device 2: /dev/input/event8
name: "curcial-oj"
add device 3: /dev/input/event7
name: "dummy_keypad"
add device 4: /dev/input/event6
name: "lightsensor-level"
add device 5: /dev/input/event5
name: "incrediblec-keypad"
0003 002b 00**000*
0003 002a ********
0003 002b 00000000
0003 002a 80000000
the first part (00**000*) is the pressure of the click, the second part (*******) is the actual coords. (xxxxyyyy)
the last two lines only show up after I lift my finger off the screen.
I'm not sure how to decode it to make my own clicks yet
On my HTC Desire 2.2:
yahor@xeondtp:~$ adb shell getevent | grep event3
add device 7: /dev/input/event3
1) /dev/input/event3: 0003 002b 00260002
2) /dev/input/event3: 0003 002a 88f00e53
3) /dev/input/event3: 0003 002b 00270002
4) /dev/input/event3: 0003 002a 88ea0e6e
5) /dev/input/event3: 0003 002b 00000008
6) /dev/input/event3:
I haven't tested pressure yet but here is what I have
pressure on screen(have not tested different numbers yet)
0003 002b 00xx000x
at
So 8009000b would click at (1, 1) and 800a000c would click at (2, 2)
As I said before the left side of the screen is:
8009****
right:
83f1****
My screen width resolution is 600, but the hex codes allow for 1000 different coords.
I'm trying to emulate key press on samsung galaxy s2 with gingerbread 2.3.5, this is the getevent output: 14 lines
/dev/input/event2: 0003 0035 00000062
/dev/input/event2: 0003 0036 00000179
/dev/input/event2: 0003 0030 0000004c
/dev/input/event2: 0003 0032 00000004
/dev/input/event2: 0003 0039 00000000
/dev/input/
sendevent /dev/input/event2 3 53 98
sendevent /dev/input/event2 3 54 377
sendevent /dev/input/event2 3 48 76
sendevent /dev/input/event2 3 50 4
sendevent /dev/input/event2 3 57 0
sendevent /dev/input/event2 0 2 0
sendevent /dev/input/event2
Localeexecute plugin has root permissions. It just doesn't try to click, it will do anything else I set it to do. Just not clicks.
Dan
What is tasker? :)
Best regards,
Yahor
I think if you want to execute click, it would be better to create a *.sh file which takes coord params and run it from the tasker..
Also, make sure that your interface is accessible for your tasker, or do chmod 777 /dev/input/event4 :)
Best regards,
Yahor
It asks for root permissions for every command, but it tries to force close for every command. If I click wait instead of force close then it will continue to the next command and try to force close again.
I will try the *.sh script later tonight, thanks for the tip :)
Dan
And do you think it would be possible to automatically figure out what is the correct eventX for the current device touchscreen?
You are always welcome :)
Please share your results if possible :)
Best regards,
Yahor
The easiest way to find the correct eventX (in my opinion):
after you have adb setup connect your phone to your computer, open a command prompt and type
"adb getevent -p". That should list all events, showing the number. here is the result for my touchscreen:
add device 6: /dev/input/event4
name: "atmel-touchscreen"
"adb getevent -p" - really great tip!
Thanks a lot!
Happy testing! (:
Best regards,
Yahor
1. save all text lines in a txt file, for example:
sendevent /dev/input/event2 3 53 98
sendevent /dev/input/event2 3 54 377
sendevent /dev/input/event2 3 48 76
sendevent /dev/input/event2 3 50 4
sendevent /dev/input/
Thanks for the sharing knowledges and for the tip! :)
I can add, that if you replace 98 and 377 with $1 and $2 accordignaly, you would be able to run script with X, Y params: sh /sdcard/mytxtfile.txt 100 200
Happy clicking! (:
Best regards,
Yahor
I got the locale execute plugin to perform clicks for me, only problem is sometimes it tries to force close, just hitting 'wait' seems to fix it.
I checked the logcat and I am getting an 'app not responding' error. So its a problem with the responsiveness of the plugin.
I also tried executing the .sh script with a terminal emulator. instead of using !sendevent
when i run adb shell getevent | grep event2
in C:android-sdktools i get this:
'grep' is not recognized as an internal or external command,
operable program or batch file
what am i doing wrong? Thanks
The reason that "Grep" it is Unix command, try to use "Find" command for windows:
adb shell getevent | Find "event2"
or adb shell getevent | Find /i "event2"
where /i - for case insensitive lookup (perhaps -i)
Happy testing! (:
Best regards,
Yahor
I'm new here, and just starting to use adb to reproduce click on devices.
I have HTC Inspire ( Android vesion 2.2.1) and trying to record click.
I extracted events related to "touch":
adb shell sendevent /dev/input/event3 3 48 48
adb shell sendevent /dev/input/event3 3 50 5
adb shell sendevent /dev/input/event3 3 53 511
adb shell sendevent
Yep, your click is too long. Looks like you have something like double or triple click..
Best regards,
Yahor
Which lines are about it?
If you try to discover this blog, you would find the answer :)
Your click is very alike to slide/swipe.
If you cut first half, you should get a single click, just try to use:
adb shell sendevent /dev/input/event3 3 48 38
adb shell sendevent /dev/input/event3 3 50 3
adb shell sendevent /dev/input/event3 3 53 511
adb shell sendevent /dev/
thank you for your reply.
I've tried to use the code that you posted in your reply, and, got the same.
Some details what kind of click I'm trying to do:
I'm on youtube mobile video and clicking "play" button to start video. It switches to player where video starts to play, and this might affect the click. I've tried to perform simple click
I've removed few more lines:
adb shell sendevent /dev/input/event3 3 48 22
adb shell sendevent /dev/input/event3 3 50 1
adb shell sendevent /dev/input/event3 3 53 511
adb shell sendevent /dev/input/event3 3 54 414
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 48
You are always welcome :)
Happy testing! (:
Best regards,
Yahor
It works on my LG optimus(2.3.4 gingerbread)
You are always very welcome :)
Best regards,
Yahor
I try this on android 4.0.3 (SGS2)
This code works, but after it my phone is ignoring screen taps. Only reset helps.
Some remote control programms result the same. Some works good.
add device 1: /dev/input/event0
name: "Atmel maXTouch Touchscreen controller"
add device 2: /dev/input/event2
name: "7k_handset"
Just try to do:
chmod 777 /dev/event*
to make event0-event3 accessible for you.
Please let me know if you have another issue.
Best regards,
Yahor
/dev/eventX are accessible for me. The problem looks more like they changed something in the behavior. I dumped one touch and tried to reproduce it. It actually works if i run it as a script on the phone, else sending the commands would take to much time and android thinks i pressed the touchscreen for about a second. Here is what i'm sending to the phone (and actually
I think it should looks like:
sendevent /dev/input/event2 1 330 1
sendevent /dev/input/event2 3 48 14
sendevent /dev/input/event2 3 53 $1
sendevent /dev/input/event2 3 54 $2
sendevent /dev/input/event2 0 2 0
sendevent /dev/input/event2 0 0 0
sendevent /dev/input/event2 1 330 0
sendevent /dev/input/event2 3 48 0
sendevent /
Best regards,
Stefan
I tried to send touch event for x:113 y:165,
adb shell sendevent /dev/input/event2 1 330 1
adb shell sendevent /dev/input/event2 3 48 14
adb shell sendevent /dev/input/event2 3 53 113
adb shell sendevent /dev/input/event2 3 54 165
adb shell sendevent /
How can I do this?
Do I need to control pressure to do that?
I was able to emulate swipe and key press but not this button click on a screen where icons can be dragged.
sendevent /dev/
adb shell getevent | grep event2
method works. Thanks.
So I used the method and got result for ICS. Only 8 lines of code is need.
Yep, Google has changed signature.
Also, I can confirm that Samsung and HTC have own signatures on various platform levels.
Best regards,
Yahor
Is it possible user given (x,y) co-ordinates can be invoke as a local touch event for non-rooted device.
Rooted is possible to access /dev/input/event3 and we can convert our own coordinates and create a touch event. But Non-Rooted Android device How should I my approach? Kindly share your views.
yes, it is possible for 4.1 android device. Please check my newest post in this blog.
Best regards,
Yahor