As someone who's grown accustom to Samsung's style of Button layout, I think this useful.
Included are some files to manually move yourself to their respective directories.
max_brightness (which will make your keys not light up so it doesn't get confusing) goes in /sys/class/leds/button-backlight/
himax-touchscreen-cap.kl (this swaps the buttons) goes in /system/usr/keylayout/
Thanks! I'll try to make a zip to flash too!
Related
My HD2 "Frankenphone" (it's built from no less than 3 other HD2's) has no working hardware keys on the front of the phone. The volume keys, however, do still work. I therefore want to cook a rom based on an existing one that has Volume up/down mapped to HOME/Back.
Furthermore, I was wondering if I could somehow get the MENU button implemented as well. I understand that this is not possible through the SDK, but perhaps it can be done by writing native C code. E.g. a longpress Volume-up could be menu, a long-press Volume-down could be search.
I'm not asking for someone to do this for me, I'd like to do this myself. What I'm looking for are a few quick pointers to how to start this endeavor. I have previous experience cooking custom roms using toolchains under linux, and also experience writing C (non-gui) code under linux. So useful pointers would be :
* Where can I find the key mappings? I suppose this is part of the kernel/user space?
* How would I go about implementing the long-press feature? Or can you hint towards another possible solution that does not involve the front hardware keys (touchscreen snooping for gestures? accellerometer? Any other sensor?)
Take a look here:
http://source.android.com/porting/keymaps_keyboard_input.html
Hope that helps.
One thing I do in most builds is change my call key to a search key.
Hi!
Take a look at the following thread! http://forum.xda-developers.com/showthread.php?t=740629
paalkr said:
Hi!
Take a look at the following thread! http://forum.xda-developers.com/showthread.php?t=740629
Click to expand...
Click to collapse
Awesome, thanks! That worked like a charm. Mounted the system.ext2 loopback, patched the keys, and tadaah, working home + back. That at least makes the phone usable again.
Can anyone recommend a solution to get a working MENU action? It looks like long-press back is handled by apps individually (e.g. in the browser it will show a history), while long-press home displays a task switcher. I could live with long-press back being handled by android itself to implement the menu function.
(edit) looks like this is possible, e.g. here it mentions "including some special features to support the virtual hard keys that are appearing on recent devices such as Droid." Now how did they do that?
I don't know about everyone else, but I've found that I instinctively want to push the home button on my phone when I want to end a call. It's burned me SOOOOO many times. I think it's funny how many Android devices seem to have their buttons mapped wrong! For example, I just bought a Coby Kyros 7015A tablet and it has a "rocker" style button on the top that just logically seems like it should be a volume up/down rocker, but for some odd reason they decided to assign "home" and "Menu" to the two sides of the rocker. In addition, the big silver button in the middle seems like it should logically be the Home button, but it is the back button instead.
After a little fiddling around with my Kyros tablet I discovered where the keymapping files are located:
Code:
/system/usr/keylayout/
there are two plain text files in this directory which need to be modified in order to make changes to keymapping, "qwerty.kl" and the other one is going to be named something to do with your particular device. You will need to edit them with a Unix compatible editor like Notepad++ on Window$, but Gedit or Kate will do just fine on Linux.
After successfully remapping the "back" button as "home" and the home/menu as volume up/down on my Kyros, I decided to tackle setting a button to hang up on my Optimus. Of course the first thing I did was make a backup in the recovery.
NOTE! This may not be a great idea for every ROM. Make sure that before you proceed, your ROM has "Spare Parts" and you can change the default behavior of the "end" button. The default behavior of the End button is to shut the screen off and it can not be changed on some ROMs.
This goes without saying, but you are editing files in /system/ so you will need to be rooted.
On the Optimus running CM7, the two files you need to edit are "qwerty.kl" and the other file is called "thunder_keypad.kl"
Code:
adb pull /system/usr/keylayout/
* make sure you put that last / at the end! it tells it to pull all of the files in the directory.
Editing these files is a pretty straightforward process. Basically, after you pull the files from your phone, you open the files and replace the instances of "HOME" with "ENDCALL". Save the files and push them back to the device, and then reboot. That's it!
Code:
adb push qwerty.kl /system/usr/keylayout/qwerty.kl
adb push thunder_keypad.kl /system/usr/keylayout/thunder_keypad.kl
adb reboot
Now you can hit the home button to hang up during a phone call instead of having to hit one of the hardware buttons to wake up the phone, which usually puts you at your homescreen or somewhere else just to have to get back into the phone call and hit the soft button hopefully before the screen goes black because of the proximity sensor (it's designed to do that!)
Like I had mentioned earlier, you're going to want to go into spare parts and change the default "End" button behavior to "Go to Home". Basically you remapped the end call button to where your home button is and then you're telling the Android OS that the end call button will emulate the normal behavior of the home button. Make sense? Didn't think so...
Works great on Mik's CM7. The only "bug" i've found so far is that when you're in the app drawer, hitting home doesn't take you back to your homescreen.
Here are my edited .kl files
Just in case you're really REALLY lazy and don't want to take the time to edit the files yourself (or if you don't have a Unix compatible editor)
Just remount and push them to /system/usr/keylayout/
Anyway to add the menu button to the navbar when using tablet mode?
Looks like this is something that can be done by modifying systemui.apk
I was able to modify the home and back button as they had preexisting keycodes but what I really want todo is replace the recent apps button as this is something i never use. But adding keycode to that did not work and it retained its original function. Does anyone have any ideas or experience in this area?
was able to get it working heres a modified systemui.apk if anyone is interested.
So I've done a search on Google and Xda about this topic and so far there doesn't seem to be much information on this except to find a thread about the inability of the android system in remapping of keys (or maybe the thread just went out of topic)
Thread; http://forum.xda-developers.com/showthread.php?t=1244702
So I'm wondering whether the remapping of the right click button to give a command 'Open Context Menu' is possible to immitate the function of a real computer (All these taking into consideration that it is also possible to remap buttons of the dock)
If you were to have it mimic the behavior of a real computer it wouldn't work. Android uses a right mouse button as if you were touching and holding on an object.
The only thing i would be interested in is remapping the second button the same as the primary button. Effectively having left click and left click.
Now it shouldn't be *that* hard to make a simple program to accomplish this, simply an extension to remap the buttons to whatever android specific task you want, this is already semi possible with the remapping of soft keys in CM 10.1/AOKP builds, so something like that should be possible.
Unfortunately i have no coding experience. I would love to see this done though
Nexus 4. Paranoid edition.
No, today I search & found a solution - http://forum.xda-developers.com/showpost.php?p=55848773&postcount=7
what i'm looking for is a mod (flashable or DIY instructions, i don't care) that'll
-remap the buttons to multitask, home, back
-remap longpress home to google now
-activate onscreen menu overflow buttons in apps (as seen on phones without dedicated menu keys)
-put a Sense 4 style menu bar on the bottom of the screen on apps that need it - but slim! not massive like the onscreen keys that i get if i turn em on via buildprop editing
i've tried doing this myself and i can get as far as remapping the individual keys (and i managed once - i forget how - to remap the longpress home) but i can't get the menu overflow buttons in apps to appear for anything, and i don't even know how to start getting the Sense-style menu bar. In fact, when i remapped the menu button to multitasking, i couldn't access the menu in any app at all.
oh, and i want to do this on a touchwiz based rom, because of the s-pen and camera goodies.
if this isn't possible, is there at least some way to make menu the multitasking button, and longpress it for menu, while activating the onscreen menu buttons?
(hell, if that can't be done, can i just leave it as is and get the menu overflow buttons? because they'd make using the phone via external monitor or s-pen - both of which i do a lot - much, much easier)
thanks in advance!
Have you tried apex launcher. I use most of the things you are wanting via Apex
Sent from my SCH-I605 using xda app-developers app