So I'm looking at remaping the soft keys (specifically the search) on the front of the phone. There appears to only be one "SEARCH" in the /system/usr/keylayout/vision-keypad.kl - key 217 (see code below) - that if changed has the following 2 effects:
1. Alters the functions of both the soft key on the front of the phone and the search key on the hardware keyboard. When I remap one, they both change to match your modification.
2. When changed, long press functionality of the soft key is lost. It will only accept a short press.
"SEARCH" can be successfully changed to "MENU", "BACK", and "CALL" (possibly others I have not tried) then pushed to the phone in recovery and function perfectly. However, when I map it to be the "POWER", the soft key does nothing on press, while the hardware search key on the slide-out works fine.
Has anyone found a way around this?
We remap the track pad to wake because we dont like using the top mounted power button, but it only does a half-ass job because when you want to shut the screen back off, you still have to reach for the power button. I think the track pad wake mod needs its own 'bacon bits'
Code:
# column 0
key 185 USER3 WAKE_DROPPED
key 100 ALT_RIGHT WAKE_DROPPED
key 217 SEARCH WAKE_DROPPED
key 28 ENTER WAKE_DROPPED
key 38 L WAKE_DROPPED
key 14 DEL WAKE_DROPPED
key 54 SHIFT_RIGHT WAKE_DROPPED
I think you're out of luck with regard to an easy fix. I just did a quick experiment with evtest and it looks like the softkeys on the screen are just areas of the touchscreen that the window manager treats specially and generates synthetic key events in response to touches on, instead of being actual mappable keys.
teferi said:
I think you're out of luck with regard to an easy fix. I just did a quick experiment with evtest and it looks like the softkeys on the screen are just areas of the touchscreen that the window manager treats specially and generates synthetic key events in response to touches on, instead of being actual mappable keys.
Click to expand...
Click to collapse
Well the are mappable. I managed to make it be the menu button and the back button just fine. It just doesnt want to be the power button..
The same key can be used as a single quick press or a long press. It is considered two different keys though. So you would have to figure out what the long press equivalent of the search button would be and change that one.
The way this thread can stay in developmental, is show steps on how you are remapping the keys.
For others to gain knowledge or this thread is moving to Q&A
Mikey1022 said:
The way this thread can stay in developmental, is show steps on how you are remapping the keys.
For others to gain knowledge or this thread is moving to Q&A
Click to expand...
Click to collapse
Maybe I'm off here, but if I was making this post to show the steps, would that not fall under a "How To" or "Guide"? My goal here is development. Development –noun 1. the act or process of developing; growth; progress. Or in my case, I'm in the act/process of developing a remapped key file to make the search soft key into a power key, and to then share with the rest of the forum. My progress so far is that I've managed to map it to a menu key and a back key with no problems, and am reaching out to others for help as to why it is that when I change it to the power key, it doesn't accept my changes.
Its kinda a gray zone, in that if I were to successfully remap it to the power button and post the file here, it would, technically speaking, be less of a development thread than it is now - because it would be finished developing and instead, merely contain a file with instructions.
However, as requested, and for those who are interested:
The file you are looking for, is as mentioned in the OP, "vision-keypad.kl" and is located in /system/usr/keylayout. You can edit it with a text editor like Notepad++. The line that I am looking at, also refer to OP, is key 217.
I'm thinking now, after messing with it some more, that maybe because it is a soft key it cant be mapped to power, being that as soon as the screen shuts off it no longer functions... But then again there exists widgets that, upon press, turn off the screen and they function fine, so I see no reason this shouldn't. I'll keep you posted on what I find, and would appreciate any help in the mean time.
i'd love to be able to map a longpress menu and a longpress back action. Cyanogen 6.1 allows longpress back to be turned into force kill foreground process. So there is a way to capture longpress on those 4 keys, the question is, what does the system read that keypress as and how can it be mapped.
sundar2012 said:
i'd love to be able to map a longpress menu and a longpress back action. Cyanogen 6.1 allows longpress back to be turned into force kill foreground process. So there is a way to capture longpress on those 4 keys, the question is, what does the system read that keypress as and how can it be mapped.
Click to expand...
Click to collapse
So it is doable! There are some .bin files in the /system/usr/keychar folder that correspond to the .kl files in the ../keylayout folder, but i havent been able to read them. Maybe thats it.. Gonna figure that out when I land tomorrow and get my computer set up
I changed the Search function key to Camera and it only works on a long press and I get no result on a short press. So maybe the function you are trying to rename the Search key to has to be specific to either way i.e. short or long press but not both.
So it will either work as a long press key for some functions or a short press key for others.
Read the window manager source (from AOSP or CM), determine what scancodes it synthesizes in response to touches or long-touches on the softkeys, edit keylayout accordingly.
Doesn't ButtonRemapper from Android App Dev section work on G2? :S
hey guys, i dont know if you all figured this out or not, I just got the g2, and to remap the key to power button you have to change it to "ENDCALL" not "POWER", after, reboot and voila! your search button now acts like a power button!!!!! Hope this helps!!!!!
Need to Map Back button to one of the soft key
Rceently I bought HTC Desire Z (no warranty), and I am facing the problem with 4 bottom buttons of the touch screen (menu, back, home and search). So I am planning to do hardware map for one of the softkeys to BACK button.
Could you please provide me step-by-step installation of all the softwares and the procedure I need to do for updating "vision-keypad.kl" file. Appreciate your help.
My one more doubt is that what is the difference between "WAKE_DROPPED" & "WAKE". I have seen these keywords in ".kl" file in GITHUB.
Please give me reply ASAP. I am frustrated with the way the mobile is working. Just imagine how it will be if back button stop working and you are in the middle of some application. I restarted my mobile some dozens of times.
Right now i'm looking into remapping the buttons on my One V. When I look into atmel-touchscreen.kl and himax-touchscreen.kl under /system/usr/keylayout/, I see that the search button is mapped to "key 217". I curious to what action key 217 is actually mapped to, as I've tried long pressing and combination pressing every thing on the phone.
Could someone enlighten us on the mysterious key 217?
Burlingtonrox said:
Right now i'm looking into remapping the buttons on my One V. When I look into atmel-touchscreen.kl and himax-touchscreen.kl under /system/usr/keylayout/, I see that the search button is mapped to "key 217". I curious to what action key 217 is actually mapped to, as I've tried long pressing and combination pressing every thing on the phone.
Could someone enlighten us on the mysterious key 217?
Click to expand...
Click to collapse
i'd like to know as well!
-sent from space.
Do any of the other One series phones have a search key? Maybe they forgot to remove that line? Just an idea.
Key 217 doesn't apply on our phone as it doesn't have a search button.
Just some redundant code probably.
In phones with a search button, you can remap key 217 i.e. the search button, to the recent apps or the power button or whatever...
First come smiles. Then come lies. Last is gunfire.
does any one know how to change the key layout of the android sofy keys, i mean in a normal android or a nexus product, the soft keys goes in the order as ( First is the back button, then middle is home and last in the right is recent tasks button).
but in samsung s3 and note 2, when soft keys are enabled. The soft key layout is reversed. I mean the back button soft key which is supposed to be in the left is in the right , and the recent tasks button which is supposed to be in the right is in the left. Any one knows how to change the soft key layout?
anything to do with tht build.prop or the sys/usr/keylayout file?
slavehunter105 said:
does any one know how to change the key layout of the android sofy keys, i mean in a normal android or a nexus product, the soft keys goes in the order as ( First is the back button, then middle is home and last in the right is recent tasks button).
but in samsung s3 and note 2, when soft keys are enabled. The soft key layout is reversed. I mean the back button soft key which is supposed to be in the left is in the right , and the recent tasks button which is supposed to be in the right is in the left. Any one knows how to change the soft key layout?
anything to do with tht build.prop or the sys/usr/keylayout file?
Click to expand...
Click to collapse
I feel you mate.
Yes you are right go to sytem/usr/keylayout/generic.kl and swap 139 with 158 and reboot.
You need to use something like solid explorer that gives you root acces.
Have fun, W
wmfreak said:
I feel you mate.
Yes you are right go to sytem/usr/keylayout/generic.kl and swap 139 with 158 and reboot.
You need to use something like solid explorer that gives you root acces.
Have fun, W
Click to expand...
Click to collapse
I believe the 139 is for the menu button right? and 158 for back button ? but thr is no menu button on the soft keys right? its just a home button, back and recent tasks button. whats the number for the recent tasks button.
ill give it a try....thanks a ton man..
How do you enable them? I am on cm nightlies latest
Sent from my GT-N7100 using xda premium
Hey, I'm trying to change the functionality of the hardware keys. I have seen different solutions, I tried with some apps and I have tried editing Genaric.kl.
I changed:
key 139 MENU
to
key 139 MENU VIRTUAL
But it didn't solve my problem. Right now the buttons are "Back - menu - recent apps" I come from Oxygen OS version 1 on my 1+1 and on that version I was able to change short hold function on the button in the settings but I can't seem to do that on the latest version of Oxygen OS. So I have swapped places with "Back" and "Recent apps" so my current order is "Recent apps - menu - back" I want the recent apps to become a menu button instead like it was on 1+1. I've also read the "MENU" actually is APP_SWITCH which is not stated in Genaric.kl.
Does anyone have a detailed solution for this?
Thanks!
The menu button doesn't really exist any more. It's been phased out for ages.
blackalice said:
The menu button doesn't really exist any more. It's been phased out for ages.
Click to expand...
Click to collapse
Still doesn't answer my question Sir.
I believe it's possible but I can't find the solution.
To edit the tap, long touch and slide right and left one has to locate the file
fpc1020p.kl
That can be found at (with root enabled):
/system/usr/keylayout/
In that file the following items can be found:
key 158 (touch) VIRTUAL
key 249 (slide right)
key 254 (slide left)
key 183 (long touch) VIRTUAL
and for example to edit long touch as a shortcut to HOME you set:
key 183 HOME VIRTUAL
But how and where do you edit the double tap and press and double press actions?
Cheers!
This functionality was present on my seller stock ROM. After upgrading to Lineage 14.1 I'm left with partly extended/partly limited functionality of the button, while it looks like the solution is at a hands reach.
I have not ventured into custom ROM territory only to prevent losing the U button functionality.
How to edit double tap home ??