20 ratings (4.400 average)
What's new in this version (0.0.4):
v0.0.1 First public release.
v0.0.2 Improved stability, added Exit button.
v0.0.3 Code updates.
v0.0.4 Changed drawables, added sharing, added more info in export text.
Once, I was playing with a number of Chinese tablets and trying different ROMs on them as they are technically the same hardware (HSG X5A variants).
I've had some problems getting the hard buttons to work though, so I wrote this application to detect key events and print them out. It will print out the following:
KeyEvents: The KeyEvents as Android understands them (KeyUp, KeyDown, KeyLongPress, KeyMultiple)
LogCat: Any relevant messages in logcat. Its filtered based on keywords declared in arrays.xml
Kernel: Any relevant messages in the kernel log. Its filtered based on keywords declared in arrays.xml. Kernel log parsing needs root.
The three checkboxes at the top control what information will be displayed.
This is a personal debug tool, but I hope it will be of some use to someone else.
While the application is running, the only "hard" keys which should work is "Home" and power. All others will produce their keycodes.
The SU request is to read the kernel log, so I can check if any keyevents are thrown by the kernel.
The location of keylayout files in Android is /system/usr/keylayout.
Kernel log parsing needs root
Both logcat and kernel log monitoring will only display lines containing words from two arrays in arrays.xml (i.e. you need to recompile the app to change them at the moment)
Currently the filters are:
READ_LOGS: Used to access the Logcat log.
WRITE_EXTERNAL_STORAGE: Used to write the exported data to the SD card.
Last comments from Android Market
@Kathleen, The application exits when you press the home button on the device. If that doesn't happen to you email me and I'll try to fix it.
Please add an exit/disable key capture button. Your app should never capture key events without a way to interrupt.
Works exactly as described, thanks!
Not bad, but I agree with Kathleen. Needs an exit button--not just press HOME, leaving the app running in the background, as suggested to her.