Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
correct usage of "adb shell input"
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  3 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
dreamerBoy  
View profile  
 More options Nov 20 2008, 11:14 pm
From: dreamerBoy <Paul.Hube...@gmail.com>
Date: Thu, 20 Nov 2008 20:14:05 -0800 (PST)
Local: Thurs, Nov 20 2008 11:14 pm
Subject: correct usage of "adb shell input"
Hi -

I am wondering what the correct invocation of "adb shell input" is -

It could be potentially very useful for me if I could inject key
events into a running app.

I've tried:

> adb shell input keyevent KEYCODE_0

or

> adb shell input keyevent KEYCODE_CALL

etc. with an emulator running.  I was inside the Dialer app and I was
hoping that my numbers would show up.  They do not.  Neither the CALL
or the ENDCALL buttons are clicked.

I'm a little confused about the "adb shell input keyevent" syntax
because it doesn't specify whether the action is UP or DOWN (or does
it imply both a DOWN then an UP?).

More often than not, I get something like:

[1]   Killed                  input keyevent CALL

when I attempt to run "adb shell input keyevent .."

In frustration, I tried  "adb shell input keyevent 4" but this seemed
to bounce me out of the dialer back to the menu.

Can anyone shed some light as to whether I'm using this command
correctly or if not, how and in what context it is intended to be
used?

Thanks so much.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Madhusudhan K  
View profile  
 More options Dec 2 2008, 8:25 am
From: Madhusudhan K <madhu.andr...@gmail.com>
Date: Tue, 02 Dec 2008 18:55:33 +0530
Local: Tues, Dec 2 2008 8:25 am
Subject: Re: [android-developers] correct usage of "adb shell input"
Hi
       You can use key codes directly like
    adb shell input keyevent 7    # for key '0'
    adb shell input keyevent 8    # for key '1'
    adb shell input keyevent 29    # for key 'A'
    adb shell input keyevent 54    # for key 'B'
we can also send string as a text, like
    adb shell input text "ANDROID"

The below text is the whole list of all keyevent names with their
respective codes numbers...

0 -->  "KEYCODE_UNKNOWN"
1 -->  "KEYCODE_MENU"
2 -->  "KEYCODE_SOFT_RIGHT"
3 -->  "KEYCODE_HOME"
4 -->  "KEYCODE_BACK"
5 -->  "KEYCODE_CALL"
6 -->  "KEYCODE_ENDCALL"
7 -->  "KEYCODE_0"
8 -->  "KEYCODE_1"
9 -->  "KEYCODE_2"
10 -->  "KEYCODE_3"
11 -->  "KEYCODE_4"
12 -->  "KEYCODE_5"
13 -->  "KEYCODE_6"
14 -->  "KEYCODE_7"
15 -->  "KEYCODE_8"
16 -->  "KEYCODE_9"
17 -->  "KEYCODE_STAR"
18 -->  "KEYCODE_POUND"
19 -->  "KEYCODE_DPAD_UP"
20 -->  "KEYCODE_DPAD_DOWN"
21 -->  "KEYCODE_DPAD_LEFT"
22 -->  "KEYCODE_DPAD_RIGHT"
23 -->  "KEYCODE_DPAD_CENTER"
24 -->  "KEYCODE_VOLUME_UP"
25 -->  "KEYCODE_VOLUME_DOWN"
26 -->  "KEYCODE_POWER"
27 -->  "KEYCODE_CAMERA"
28 -->  "KEYCODE_CLEAR"
29 -->  "KEYCODE_A"
30 -->  "KEYCODE_B"
31 -->  "KEYCODE_C"
32 -->  "KEYCODE_D"
33 -->  "KEYCODE_E"
34 -->  "KEYCODE_F"
35 -->  "KEYCODE_G"
36 -->  "KEYCODE_H"
37 -->  "KEYCODE_I"
38 -->  "KEYCODE_J"
39 -->  "KEYCODE_K"
40 -->  "KEYCODE_L"
41 -->  "KEYCODE_M"
42 -->  "KEYCODE_N"
43 -->  "KEYCODE_O"
44 -->  "KEYCODE_P"
45 -->  "KEYCODE_Q"
46 -->  "KEYCODE_R"
47 -->  "KEYCODE_S"
48 -->  "KEYCODE_T"
49 -->  "KEYCODE_U"
50 -->  "KEYCODE_V"
51 -->  "KEYCODE_W"
52 -->  "KEYCODE_X"
53 -->  "KEYCODE_Y"
54 -->  "KEYCODE_Z"
55 -->  "KEYCODE_COMMA"
56 -->  "KEYCODE_PERIOD"
57 -->  "KEYCODE_ALT_LEFT"
58 -->  "KEYCODE_ALT_RIGHT"
59 -->  "KEYCODE_SHIFT_LEFT"
60 -->  "KEYCODE_SHIFT_RIGHT"
61 -->  "KEYCODE_TAB"
62 -->  "KEYCODE_SPACE"
63 -->  "KEYCODE_SYM"
64 -->  "KEYCODE_EXPLORER"
65 -->  "KEYCODE_ENVELOPE"
66 -->  "KEYCODE_ENTER"
67 -->  "KEYCODE_DEL"
68 -->  "KEYCODE_GRAVE"
69 -->  "KEYCODE_MINUS"
70 -->  "KEYCODE_EQUALS"
71 -->  "KEYCODE_LEFT_BRACKET"
72 -->  "KEYCODE_RIGHT_BRACKET"
73 -->  "KEYCODE_BACKSLASH"
74 -->  "KEYCODE_SEMICOLON"
75 -->  "KEYCODE_APOSTROPHE"
76 -->  "KEYCODE_SLASH"
77 -->  "KEYCODE_AT"
78 -->  "KEYCODE_NUM"
79 -->  "KEYCODE_HEADSETHOOK"
80 -->  "KEYCODE_FOCUS"
81 -->  "KEYCODE_PLUS"
82 -->  "KEYCODE_MENU"
83 -->  "KEYCODE_NOTIFICATION"
84 -->  "KEYCODE_SEARCH"
85 -->  "TAG_LAST_KEYCODE"

-- Madhu


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Abhijeet Kamble  
View profile  
 More options Oct 26 2012, 7:01 am
From: Abhijeet Kamble <elite.dragonkni...@gmail.com>
Date: Fri, 26 Oct 2012 04:01:19 -0700 (PDT)
Local: Fri, Oct 26 2012 7:01 am
Subject: Re: [android-developers] correct usage of "adb shell input"

hi friends,
i am trying to reach CALIBRATION through ADB command line:

adb shell
$ am start -a android.settings.SOUND_SETTINGS

it reaches to the: Settings->sound & display ->

Now i want to know how can i reach to

Settings->sound & display -> calibration

please replay on this friends, my phone is dead from a month due to bad
calibration.

thank you :)


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »