- KeyEvent
- Class Overview
- Key Event Class
- Definition
- Remarks
- Constructors
- Fields
- Properties
- Methods
- Explicit Interface Implementations
- Extension Methods
- PocketMagic
- Where Technology meets magic
- Blog options
- Programmatically Injecting Events on Android – Part 1
- Method 1: Using internal APIs
- Method 2: Using an instrumentation object
- Method 3: Direct event injection to /dev/input/eventX
- Sample Code
- Other great resources:
- This article has 101 Comments
KeyEvent
Class Overview
Object used to report key and button events.
Each key press is described by a sequence of key events. A key press starts with a key event with ACTION_DOWN . If the key is held sufficiently long that it repeats, then the initial down is followed additional key events with ACTION_DOWN and a non-zero value for getRepeatCount() . The last key event is a ACTION_UP for the key up. If the key press is canceled, the key up event will have the FLAG_CANCELED flag set.
Key events are generally accompanied by a key code ( getKeyCode() ), scan code ( getScanCode() ) and meta state ( getMetaState() ). Key code constants are defined in this class. Scan code constants are raw device-specific codes obtained from the OS and so are not generally meaningful to applications unless interpreted using the KeyCharacterMap . Meta states describe the pressed state of key modifiers such as META_SHIFT_ON or META_ALT_ON .
When interacting with an IME, the framework may deliver key events with the special action ACTION_MULTIPLE that either specifies that single repeated key code or a sequence of characters to insert.
In general, the framework cannot guarantee that the key events it delivers to a view always constitute complete key sequences since some events may be dropped or modified by containing views before they are delivered. The view implementation should be prepared to handle FLAG_CANCELED and should tolerate anomalous situations such as receiving a new ACTION_DOWN without first having received an ACTION_UP for the prior key press.
Refer to InputDevice for more information about how different kinds of input devices and sources represent keys and buttons.
Источник
Key Event Class
Definition
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Object used to report key and button events.
Remarks
Portions of this page are modifications based on work created andВ shared by the Android Open Source Project and used according to terms described in the Creative Commons 2.5 Attribution License.
Constructors
Create a new key event.
Create a new key event.
Create a new key event.
Create a new key event.
Create a new key event.
Create a new key event.
A constructor used when creating managed representations of JNI objects; called by the runtime.
Create a new key event.
Create a new key event.
Create a new key event.
Fields
Properties
Retrieve the action of this key event.
For the special case of a #ACTION_MULTIPLE event with key code of #KEYCODE_UNKNOWN , this is a raw string of characters associated with the event.
Returns the runtime class of this Object .
(Inherited from Object)
Gets the device that this event came from.
(Inherited from InputEvent)
Gets the primary character for this key.
Retrieve the time of the most recent key down event, in the android.os.SystemClock#uptimeMillis time base.
Retrieve the time this event occurred, in the android.os.SystemClock#uptimeMillis time base.
Returns the flags for this key event.
The handle to the underlying Android instance.
(Inherited from Object)
Returns true if no modifier keys are pressed.
Returns the pressed state of the ALT meta key.
For #ACTION_UP events, indicates that the event has been canceled as per #FLAG_CANCELED .
Returns the locked state of the CAPS LOCK meta key.
Returns the pressed state of the CTRL meta key.
Returns the pressed state of the FUNCTION meta key.
For #ACTION_DOWN events, indicates that the event has been canceled as per #FLAG_LONG_PRESS .
Returns the pressed state of the META meta key.
Returns the locked state of the NUM LOCK meta key.
Returns true if this key produces a glyph.
Returns the locked state of the SCROLL LOCK meta key.
Returns the pressed state of the SHIFT meta key.
Returns the pressed state of the SYM meta key.
Is this a system key? System keys can not be used for menu shortcuts.
For #ACTION_UP events, indicates that the event is still being tracked from its initial down event as per #FLAG_TRACKING .
Gets the KeyCharacterMap associated with the keyboard device.
Retrieve the key code of the key event.
Returns the maximum keycode.
Returns the state of the meta keys.
Gets a mask that includes all valid modifier key meta state bits.
Returns the state of the modifier keys.
Gets the number or symbol associated with the key.
Retrieve the repeat count of the event.
Retrieve the hardware key id of this key event.
This API supports the Mono for Android infrastructure and is not intended to be used directly from your code.
This API supports the Mono for Android infrastructure and is not intended to be used directly from your code.
Gets the Unicode character generated by the specified key and meta key state combination.
Methods
Create a new key event that is the same as the given one, but whose action is replaced with the given value.
Create a new key event that is the same as the given one, but whose flags are replaced with the given value.
Create a new key event that is the same as the given one, but whose event time and repeat count are replaced with the given value.
Create a new key event that is the same as the given one, but whose event time and repeat count are replaced with the given value.
Creates and returns a copy of this object.
(Inherited from Object)
Describe the kinds of special objects contained in this Parcelable’s marshalled representation.
(Inherited from InputEvent)
Deliver this key event to a KeyEvent Callback interface.
Indicates whether some other object is «equal to» this one.
(Inherited from Object)
Get the character that is produced by putting accent on the character c.
Returns a hash code value for the object.
(Inherited from Object)
Get the character conversion data for a given key code.
Gets the first character in the character array that can be generated by the specified key code.
Gets the first character in the character array that can be generated by the specified key code.
Gets the Unicode character generated by the specified key and meta key state combination.
Returns true if only the specified modifiers keys are pressed.
Determines whether the event is from the given source.
(Inherited from InputEvent)
Returns true if the specified keycode is a gamepad button.
Returns whether this key will be sent to the android.media.session.MediaSession.Callback if not handled.
Returns true if this key code is a modifier key.
Called by the garbage collector on an object when garbage collection determines that there are no more references to the object.
(Inherited from Object)
Gets a keycode by its symbolic name such as «KEYCODE_A» or an equivalent numeric constant such as «29».
Returns a string that represents the symbolic name of the specified keycode such as «KEYCODE_A», «KEYCODE_DPAD_UP», or an equivalent numeric constant such as «1001» if unknown.
Returns true if only the specified modifier keys are pressed according to the specified meta state.
Returns true if no modifiers keys are pressed according to the specified meta state.
Normalizes the specified meta state.
Wakes up a single thread that is waiting on this object’s monitor.
(Inherited from Object)
Wakes up all threads that are waiting on this object’s monitor.
(Inherited from Object)
Sets the Handle property.
(Inherited from Object)
Call this during Callback#onKeyDown to have the system track the key through its final up (possibly including a long press).
Returns a string representation of the object.
(Inherited from Object)
Causes the current thread to wait until another thread invokes the java.lang.Object#notify() method or the java.lang.Object#notifyAll() method for this object.
(Inherited from Object)
Causes the current thread to wait until another thread invokes the java.lang.Object#notify() method or the java.lang.Object#notifyAll() method for this object.
(Inherited from Object)
Causes the current thread to wait until another thread invokes the java.lang.Object#notify() method or the java.lang.Object#notifyAll() method for this object.
(Inherited from Object)
Flatten this object in to a Parcel.
Explicit Interface Implementations
| IJavaPeerable.Disposed() | (Inherited from Object) |
| IJavaPeerable.DisposeUnlessReferenced() | (Inherited from Object) |
| IJavaPeerable.Finalized() | (Inherited from Object) |
| IJavaPeerable.JniManagedPeerState | (Inherited from Object) |
| IJavaPeerable.SetJniIdentityHashCode(Int32) | (Inherited from Object) |
| IJavaPeerable.SetJniManagedPeerState(JniManagedPeerStates) | (Inherited from Object) |
| IJavaPeerable.SetPeerReference(JniObjectReference) | (Inherited from Object) |
Extension Methods
Performs an Android runtime-checked type conversion.
Источник
PocketMagic
Where Technology meets magic
- Home
- /
- Android
- /
- Software
- /
- Programmatically Injecting Events on Android – Part 1
Simple Android Show Password login form
Teltonika RUT955 NMEA HTTP Post + Parser
NMEA GPS Library for Microcontrollers -2-
Covid Coronavirus Face Mask
TTP229 Capacitive Touch Keypad
Blog options
Programmatically Injecting Events on Android – Part 1
Posted By Radu Motisan on April 29, 2012
Note: Part two on programmatically injecting events on Android has been published and is available here.
The successful Android platform has been around for a few years now. End users get lots of bells and whistles in fancy applications, but for developers, this “open-intended” platform seems even more tangled up than ever.
There are various APIs that still do not work, others that get deprecated-and-out in a single release, or some that are locked up for the supreme security purpose, invoked so very often by platform developers, that probably feel they’ve given the right answer.
All in one, Android also comes with a lot of frustration, because tools that are needed to accomplish various tasks or even more advanced applications, are put behind bars on purpose.
Another example of many is injecting a key press programmatically or the similar counter-part, injecting a touch event (mouse).
Because a malicious programmer might develop a software that would open your Market app and download payed apps without you knowing about it, developers world wide are prohibited from sending a key press programmatically to other applications except their own.
This is just ridiculous narrow thinking.
Of course there will always be a balance between security and functionality, but with paranoia it quickly turns to total failure. In other words why limit something so useful that can create so little damage? Users are warned about risks with normal permissions and it should stay that way for other features as well.
I’ll just leave them with their issues and get back to the topic: I am aware of three methods for injecting events programmatically. This refers both to keyboard events (keys) and mouse events (touch events).
Method 1: Using internal APIs
This approach has its risks, like it is always with internal, unpublished APIs.
The idea is to get an instance of WindowManager in order to access the injectKeyEvent / injectPointerEvent methods.
The ServiceManager and WindowsManager are defined as Stubs. We can then bind to these services and call the methods we need. The interfaces are included in the sample code attached at the end of this article.
To send a key do the following:
To send touch/mouse events use:
This works fine, but only inside your application 
The moment you’re trying to inject keys/touch events to any other window, you’ll get a force close because of the following exception: 
Not much joy, as INJECT_EVENTS is a system permission. A possible solution is discussed here and here.
Method 2: Using an instrumentation object
This is a clean solution based on public API, but unfortunately it still requires that INJECT_EVENTS permission.
For touch events you can use:
All good inside the test application, and will crash instantly when trying to inject keys to outside apps, not because the approach doesn’t work, but because Android Developers have chosen so. Thanks guys, you rock! Not.
By looking at sendPointerSync’s code, you will quickly see it uses the same approach as presented in method 1). So this is the same thing, but packed nicely in a easy to use API:
Method 3: Direct event injection to /dev/input/eventX
Linux exposes a uniform input event interface for each device as /dev/input/eventX where X is an integer. We can use it directly and skip the above Android Platform permission issues.
For this to work, we will need root access, so this approach only works on a rooted device.
I felt it was easier to deal with linux using native C code, but a pure java implementation is also possible. Therefore I have added a small JNI component to handle the interface with /dev/input/eventX.
The sample code I wrote doesn’t detect the X number automatically, so make sure you set that before running the code. By default I set it to event3. You can change that in NativeInput.java, see code below. 
As I said, this last method requires root. By default the eventX files have the permission set for 660 (read and write for Owner and Group only). To inject keys from our application, we need to make it writable. So do this first: 
You will need root to run the chmod command.
Sample Code
Other great resources:
Note: Part two has been published and is available here.
This article has 101 Comments
Thx for the nice little demo.
I cant get method 3 to work on my sgs2 with android 4.03. I installed your demo application and chanced it to method 3. When it was installe I did adb shell su chmod 666 /dev/input/event3 but nothing happens when i pres start.
Logcat says:
5-30 10:21:38.642: D/dalvikvm(19464): Late-enabling CheckJNI
05-30 10:21:38.657: I/dalvikvm(19464): Turning on JNI app bug workarounds for target SDK version 5…
05-30 10:21:38.662: D/dalvikvm(19464): Debugger has detached; object registry had 1 entries
05-30 10:21:38.737: D/dalvikvm(19464): Trying to load lib /data/data/net.pocketmagic.keyinjector/lib/libinput.so 0x41507800
05-30 10:21:38.742: D/dalvikvm(19464): Added shared lib /data/data/net.pocketmagic.keyinjector/lib/libinput.so 0x41507800
05-30 10:21:38.747: D/JNI(19464): Debug enabled.
05-30 10:21:38.747: D/JNI(19464): intCreate call (/dev/input/event3)
05-30 10:21:38.747: D/JNI(19464): intCreate success: 44
05-30 10:21:38.902: D/CLIPBOARD(19464): Hide Clipboard dialog at Starting input: finished by someone else… !
05-30 10:21:56.802: D/AKI(19464): Inject method:3
05-30 10:21:56.802: D/JNI(19464): intSendEvent call (44,1,46,1)
05-30 10:21:56.802: D/JNI(19464): intSendEvent done:16
05-30 10:21:56.802: D/JNI(19464): intSendEvent call (44,1,46,0)
05-30 10:21:56.802: D/JNI(19464): intSendEvent done:16
05-30 10:21:57.802: D/AKI(19464): Inject method:3
05-30 10:21:57.802: D/JNI(19464): intSendEvent call (44,1,46,1)
05-30 10:21:57.802: D/JNI(19464): intSendEvent done:16
05-30 10:21:57.802: D/JNI(19464): intSendEvent call (44,1,46,0)
05-30 10:21:57.802: D/JNI(19464): intSendEvent done:16
05-30 10:22:36.947: D/dalvikvm(19464): Debugger has detached; object registry had 1 entries
Can you se what im doing wrong here?
what is the su? Should I enter my computers password?
Hi,
step1 My device(Motorola Xoom 3.2) is rooted.and following below steps to perform keyInject at any Pixel on device
step–1(a) Set event3 chmod to 777
(b) Running below Code in a background thread.
m_ni.SendKey(46 , true);
m_ni.SendKey(46, false);
step–2 To check key Event create another application with no title-bar and having A single button with OnClickListener. when the button is clicked it will display a Toast.
step -3 Launch 1st step App and then 2nd step App
but nothing is happening neither it display any Exception nor it display the toast.
please help.
Источник
