Related
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.
Hello all,
I have attached the latest rootfs.img from Xdandroid with corrected key layout for the blackstone as you may have noticed that by default we have two power buttons and have lost the multitasking keymap. Please find below the latest rootfs <rootfs-20110123-5cafe3f> with modified keymapping to regain the multitasking keymap and also the home button.
Yes I am aware you can adjust the end button behaviour in spare parts but you still won't have the multitasking keymap.
Update: Fixed init.eclair.rc and init.eclairhero.rc for updated android binary in latest XDAndroid rootfs.img, eclair now boot's as it should.
Best Regards,
ST1Cl<^^aN
-- Reservered --
At the moment my focus was to return the multitasking functionality, I will be further modifying the keymapping to suite our needs and to be more blackstone specific.
Best Regards,
ST1Cl<^^aN
ok fixed init.eclair.rc and init.eclairhero.rc for updated android binary, uploading updated rootfs.img in a moment...
Best Regards,
ST1Cl<^^aN
Stickman89 said:
Hello all,
I have attached the latest rootfs.img from Xdandroid with corrected key layout for the blackstone as you may have noticed that by default we have two power buttons and have lost the multitasking keymap. Please find below the latest rootfs <rootfs-20110123-5cafe3f> with modified keymapping to regain the multitasking keymap and also the home button.
Yes I am aware you can adjust the end button behaviour in spare parts but you still won't have the multitasking keymap.
Update: Fixed init.eclair.rc and init.eclairhero.rc for updated android binary in latest XDAndroid rootfs.img, eclair now boot's as it should.
Best Regards,
ST1Cl<^^aN
Click to expand...
Click to collapse
Thank you!!!!!
Could You specify what function is assigned to each button? Does it work like in WM ?
Hello,
This key assignment is perfect I think ! Thank you stickman89
some precisions about it:
- Call button: call or voice command (hold)
- Home button: Options & show keyboard (hold)
- Previous button: previous screen
- End button: sleep & end call (if on call) & shutdown options (hold)
sleep is an option under Spare parts => End button behavior => Go to sleep
- Power button: home & recent apps (hold 1 second)
In launcherPro preferences I configured to open/close notifications, when already on home => it's convenient to show notifications by pressing twice on power button)
Thanks, but there is a way to reassign those buttons?
I prefer WM style, where power button means power and home suits home
teti77 said:
Thanks, but there is a way to reassign those buttons?
I prefer WM style, where power button means power and home suits home
Click to expand...
Click to collapse
I will later be modifying those key's to suit our needs, if I match the winmo key layout I will need to set-up long press functions as well, I will try my best to please everyone. Atm this is just to return the missing multitasking function...
Best Regards,
ST1Cl<^^aN
can you map long press end button to recent apps,and leave the power button for power control and shutdown options? ; since home is more frequently used than power on/off , and it's pretty much inconvenient to have it mapped to power button because it's not easily accessible
so,
end >home
long press end >recent apps
power > screen off
long press power > shutdown options
thanks
farukb said:
can you map long press end button to recent apps,and leave the power button for power control and shutdown options? ; since home is more frequently used than power on/off , and it's pretty much inconvenient to have it mapped to power button because it's not easily accessible
so,
end >home
long press end >recent apps
power > screen off
long press power > shutdown options
thanks
Click to expand...
Click to collapse
+1 *grin*
It's more intuitive... or we're more used to it
EDIT: Where's the blac100 keymap? I don't find it in /data/etc/keymaps...
The keymaps is located at /system/usr/keychars/qwerty.kl but it is a symlink to /etc/keymaps/raph_navi_pad.kl.BTW rootfs is already updated.Perhaps OP could submit his patch to stineb to be included for blac100 in the main tree
farukb said:
can you map long press end button to recent apps,and leave the power button for power control and shutdown options? ; since home is more frequently used than power on/off , and it's pretty much inconvenient to have it mapped to power button because it's not easily accessible
so,
end >home
long press end >recent apps
power > screen off
long press power > shutdown options
thanks
Click to expand...
Click to collapse
+1
This would make more sense to me too, especially as at the moment if you're stupid like me and fumble at 'previous/back' but get 'end' instead you end up in a mess with the device locked and having to press power to turn the screen on then swiping to unlock and end up back at the home screen.
+1
Looks better to work with it...
Stickman, does the last rootfs (20110210) bring this keymap for blackstone? Or the changes aren't commited yet?
Eodun said:
Stickman, does the last rootfs (20110210) bring this keymap for blackstone? Or the changes aren't commited yet?
Click to expand...
Click to collapse
i believe there's only one sure way to find out...
farukb said:
i believe there's only one sure way to find out...
Click to expand...
Click to collapse
I'm using it and keymap works great, and power & end buttons work as in WM
Sent from Blackstone using XDA App
Eodun said:
I'm using it and keymap works great, and power & end buttons work as in WM
Click to expand...
Click to collapse
does long press end show up list of recently ran apps
No, it lacks that. It would be perfect otherwise
Sent from Blackstone using XDA App
i'm sure when I tried this longpress did bring up recent apps
Hi guys. I have not found this topic on XDA. I am apologize, if still exists. It is only little trifle, but it is doing big work for me.
Change HKLM/HARDWARE/DEVICEMAP/TOUCH/BUTTONS/3/Area (it is working on opened system only)
from:
"341,810 480,910"
to:
"341,810 480,860".
Now you can hold WP7 phone normally and no mistake bing occures.
I am working on five buttons solution (adding buttons for copy/paste and for killapp), wait for results...
A few questions...
Does this increase the time that you have to press the search button to open the search form?
And what do you mean for "opened system"? Do you mean Interop-Unlock?
I can't see any BUTTONS folder in TOUCH folder, I have a Samsung Omnia 7 with Mango 7740.
Yeah, I think so. When you apply this edit, you'll have to press and hold the search button for a short time so you don't accidentally press it. Cool find, there - would be great if it really works. I have to try that one out for sure.
And I think that he means you have to have access to your registry...
Looking forward to this.
Looking at the registry key, I guess this is to reduce the area of the softkey button so that if you click near the magnifier, the search form won't be activated.
But I still can't find that registry key on my phone
what this does for me (HTC 7 Mozart, DFT v3) is disable the search button alltogether.
EDIT:I just realized that it doesn't really. The value changes the *vertical* area the button is registered. Setting a more reasonable value (880 or 885) makes the search button work again, but you have to press closer to the screen.
AshleyT said:
A few questions...
Does this increase the time that you have to press the search button to open the search form?
And what do you mean for "opened system"? Do you mean Interop-Unlock?
I can't see any BUTTONS folder in TOUCH folder, I have a Samsung Omnia 7 with Mango 7740.
Click to expand...
Click to collapse
I am not sure. I have it from DFT 7740 ROM installing. But, on unlocked NoDo (dev unlock, on Mango must be more) befor this ROM, I seen similar keys after its creating. And after "key creating" it has also subkeys and values.
May be it is HTC accorded, but I mean not.
Localhorst86 said:
what this does for me (HTC 7 Mozart, DFT v3) is disable the search button alltogether.
EDIT:I just realized that it doesn't really. The value changes the *vertical* area the button is registered. Setting a more reasonable value (880 or 885) makes the search button work again, but you have to press closer to the screen.
Click to expand...
Click to collapse
You must press only area between center of button and applications screen. When press all button, this is not working. With higher value is area bigger, but for me too much (I had very offen Bing instead working app).
FYI, the numbers you are messing with are screen coordinates. The soft buttons are extensions of the same touchscreen used for the display. The display is 800 pixels tall and 480 pixels wide. It appears that the Bing button is typically 101 pixels tall (810 to 910, with a 10-pixel gap beneath the screen before it registers) and 140 pixels wide (341 to 480). The numbers defined in that registry key are for tweaking the boundary box that defines the part of the touchscreen considered to be the Bing button.
BTW, there's no guarantee that the registry key exists on all phones (for example, it would have no meaning on a phone with physical buttons) and even where it does exist, the values quite likely vary between devices. Also, it may be a permissions-restricted key, which means a registry editor can almost certainly tweak it (they use high-privilege DLLs) but a registry browser (aside from WP7 Root Tools) won't be able to see it's there (since browsing is done with a low-privilege DLL).
Yes, it is only for unlocked native WP7 phones. Different values may be tried by phone type and by resizing area user wanting. I have wrote my factory values here - I have changed it to one half to be happier with my Search button. Everybody can make it how he want by his factory vaues.
The best value is probably 870.
Will this work on the HD7 ??
I have noticed this too that even when you press closer to the search button...it still recognizes it as a touch and the bing screen pops up !!
backlashsid said:
Will this work on the HD7 ??
I have noticed this too that even when you press closer to the search button...it still recognizes it as a touch and the bing screen pops up !!
Click to expand...
Click to collapse
Mine is working. Just reboot your phone and it works!
HTC HD7 (T-Mobile)
Thanks Martin7Pro!
linch said:
Mine is working. Just reboot your phone and it works!
HTC HD7 (T-Mobile)
Thanks Martin7Pro!
Click to expand...
Click to collapse
Thanks for confirming. Will do.
Cant find this value on omnia 7, any ideas? I have costom unlocked ROM
So I've just installed CM9 ICS on my Samsung Epic 4G. The problem is, I want to add WAKE to the Camera button, however it is not listed in the "cypress-touchkey.kl" keylayout file. I figured I would change it in the Generic.kl file, but that doesn't seem to work.
In 2.3, the camera button was in keylayout, but this is not the case for CM9. I tried added the Camera entry with 212 on the cypress.touchkey.kl but no luck. What should I do?
Thanks in advance for any and all help.
I believe I saw that option in the settings somewhere
phonehunter59 said:
I believe I saw that option in the settings somewhere
Click to expand...
Click to collapse
While I do appreciate the response, this in no way shape or form actually helps me. Let's say for instance that there is an option in Settings, saying "somewhere" doesn't really help. Second, I asked about the keylayout files. So even if there is a way to do this in the Settings page (which I don't think there is), I was still talking about keylayout files for a reason.
Sorry for sounding rude, but your response does not help me whatsoever. It's like saying that the answer is on the Internet... that's great and all and I'm sure it's on the Internet somewhere, but if I don't know where, then the answer is pretty pointless.
I apologize for my post and I was wrong anyway, there is no option. Sorry for taking your time
Sent from my SPH-D700 using Tapatalk
Solution
So after messing around with a few things, I finally found the solution which I will list below:
- To change Camera Button you need to edit s3c-keypad.kl
- To change Power Button, Vol+, Vol- you need to edit victory-keypad.kl
- To change soft keys (i.e. home button, menu, back, search) edit cypress-touchkey.kl
So to conclude, it is actually a combination of keylayout files. Please note that there are other listings for the buttons in various keylayout files such as Generic.kl, however do not edit these because they are not what the phone uses. I have tried almost all of the above keys and they have remapped successfully so long as you edit the key values in the .kl files listed above.
I hope this helps someone else who had the same problem.
steven.smith said:
So after messing around with a few things, I finally found the solution which I will list below:
- To change Camera Button you need to edit s3c-keypad.kl
- To change Power Button, Vol+, Vol- you need to edit victory-keypad.kl
- To change soft keys (i.e. home button, menu, back, search) edit cypress-touchkey.kl
So to conclude, it is actually a combination of keylayout files. Please note that there are other listings for the buttons in various keylayout files such as Generic.kl, however do not edit these because they are not what the phone uses. I have tried almost all of the above keys and they have remapped successfully so long as you edit the key values in the .kl files listed above.
I hope this helps someone else who had the same problem.
Click to expand...
Click to collapse
DO you or any one Know how to make the camera key launch a different camera app? i want it to start the MIUI camera but if i have both installed the cm9 camera starts with the camera hardware key.
Hi, I found you can activate softkeys on any stock rom by modify the build.prop value below
- Need root and use BuildProp Editor to edit
- Searh for words: qemu.hw.mainkeys=1 and change 1 to 0 it activates the softkeys.
- Save the changed and Reboot, your hardware key will still working as well
- The softkeys function is same to the hardware keys you can long press for screenshot, turn on camera etc
I don't know how to turn off the hardware key yet, if anyone know you can share it.
You can disable the hardware button in Settings/Accessibility/Virtual Button Control.
Just thought I'd add a little tidbit to this topic that I found after a dropped my LePro3 and lost home and back hardware key function. With the app Handy Soft Keys I now have (as the name suggests) really handy software keys. https://play.google.com/store/apps/details?id=ca.yesoft.handysoftkeys&hl=sv (There's an ad-free pro version available as well). No root required. I don't think it has the full functionality of the hardware buttons with long press, but I just needed the basic ones and if that's what someone else needs as well, well, it's there.
And by the way, if you don't want to go through settings etc hardware keys can be turned on/off easily by pressing power and volume up at at the same time.