You really want to use an abandoned app which is now nearly 15 years old? Really???
If yes, look at the first page of this thread. There is somewhere the original APK available...
[App] ButtonRemapper - Beta v0.2.4 (New Galaxy S version added)
- Thread starter appelflap
- Start date
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
144Important questions will be marked with the tag FAQ when they are answered in this thread. Search for FAQ with the "search this thread" button to fetch them.
-------- Update notes --------
Update (Jan 22): New, separate version for the Samsung Galaxy S (This version is not compatible with the Galaxy S variants like the Captivate and Vibrant. A version compatible with these devices will be posted soon)
A special version for the Galaxy Tab can be found here .
------ Initial Announcement --------
* Beta* for full rooted devices. (NAND unlocked. Full, permanent write access to the system dir is needed)
Tool to remap the hardware buttons. Or better: a generic tool to edit the key layout map file Android uses to map the keys. (For info about key layout files, see:
http://xdaforums.com/showthread.php?t=695936 and
http://source.android.com/porting/keymaps_keyboard_input.html)
Supported devices: All, except Samsung Galaxy S variants (only partial support. Update: new, separate version for SGS attached to this post), Droid 2 and Huawei U8110/Android 2.1. On the Vibrate and Captivate only a few buttons can be remapped.
(If you have issues with your device, please let me know)
Functions that can be assigned:
Code:"Power", "Home", "Menu", "Back", "Search", "Volume up", "Volume down", "Camera", "Focus", "Endcall", "Call", "Media Play Pause", "Media Stop", "Media Next", "Media Previous", "Media Rewind", "Media Fast Forward", "Dpad center", "Dpad up", "Dpad down", "Dpad left", "Dpad right"
As it with all root apps a Nandroid backup is adviced, because you never know.
Tips
In generall, these are the codes of the keys on a standard Android device (for people who can also edit the keyboard codes of a hardware keyboard):
Code:102, // home button 114, // Volume down 115, // Volume up 116, // Power 139, // Menu 158, // Back 217, // Search` 231, // CALL 232, // DPAD_CENTER 108, // DPAD_DOWN 103, // DPAD_UP 105, // DPAD_LEFT 106, // DPAD_RIGHT 211, // HEADSETHOOK 212, // CAMERA 242 // FOCUS
Attached is a little helper app (KeynrTracker.apk) to identify the keynumber you want to remap .
Faq
Q: can you do also other remappings with the buttons, like for example long pressing, double press, context sensitive remappings etc.
A: For now, this is pretty much it. Check out LaunchKey if you also want to remap the long-press search button.
Q: So this is it?
A: I do plan to add some more functionality and to update the interface, but when that will be I can't tell.
Reviews
Review by Android Police
Review by Gizmoninja
Changelog
v0.2.4: Fixed restore problem on some devices (Thanks ljjehl for noticing)
v0.2.3: Hasn't never been released
v0.2.2: * Added support for the Droid X (Thanks Doug for your feedback!) * added an option to hot reboot the device after applying a change, so one can almost change buttons on the fly.
v0.2 Fixed UI issues * Fix for Galaxy S Variants * added (camera) focus as an option to the "remap list"
--
If you like the app and/or wish to support this project consider buying the donation version from the market (Search term: ButtonRemapper). Don't feel obliged though!2
Interesting. Seems that the Acer-Liquid uses a similar approach as the Galaxy S variants. I think I can fix it with a general heuristic. Can't say when though.
I use a android function (getScanCode) for this and in the docs for this function/method it is said that:
So I wouldn't infer anything conclusive out of the output of the helper app.Code:public final int getScanCode () Since: API Level 1 Retrieve the hardware key id of this key event.[B] These values are not reliable and vary from device to device[/B]. Mostly this is here for debugging purposes.
Take a look at this doc:
http://developer.android.com/reference/android/view/KeyEvent.html
The constants here are different constants than used in the second column of the list in the buttonremapper app, but to some degree they correspond to eachother.
When you look at the dpad constants you see that it is stated that "May also be synthesized from trackball motions."
(The numeral values of the constants are complete different values than the scancodes displayed in the helper app: don't infer anything from it)1So on a nexus 1, this will only remap the power, volume rockers and possibly trackball? Will it work for the capacitive buttons?
