I have seen a bunch of posts regarding the capacitive buttons and on screen navigation buttons. Love them or hate them, this is how you can turn them off.
I will leave that up to you on how to get onscreen Navy buttons.
As for turning off the capacitive buttons this is how I did it.
1.To eneble onscreen buttons follow this thread http://forum.xda-developers.com/redm...mi-1s-t2950455
2. Download a root file explorer. Root Browser Lite --> http://goo.gl/b9ISW This is what I will use.
3.Load up Root Browser and navigate to system>usr>keylayout. We will be looking for a file called "atmel_mxt_ts.kl".
4. Select it and hit "Open as..." then "Text file" then "RB Text Editor"
5. Now we see this:
key 139 MENU
key 102 HOME
key 158 BACK
key 217 SEARCH
All you have to do is option out the keys you don't want to work with a #. So if you are like me and think the home button is fine, it will look like this.
#key 139 MENU
key 102 HOME
#key 158 BACK
key 217 SEARCH
6. When you have the ones you want optioned out just tap the little disk icon in the top right. It will ask for root rights, grant it, saved.
7. Now just reboot and DONE!
Tested on
1. One plus one a.k.a bacon(miui6, h2os, oxygen..you tell)
Sent from my bacon using Tapatalk
Hit thanks if this post helped you[emoji106]
Why on earth would anyone want to do that when there is a toggle to switch between On-Screen and Hardware Keys
PsyGik said:
Why on earth would anyone want to do that when there is a toggle to switch between On-Screen and Hardware Keys
Click to expand...
Click to collapse
OK give me a screen shot of that toggle in h2os,miui6
@Snapdragon815
Will this guide also turn off the HW key backlight?
Will it survive a reboot?
Mr.Ak said:
@Snapdragon815
Will this guide also turn off the HW key backlight?
Will it survive a reboot?
Click to expand...
Click to collapse
As you can see, i made this post 2 years ago, you can give it a try, do a backup on TWRP first, if everythinggoes as you expected, that good. If not you know how to restore.
Snapdragon815 said:
As you can see, i made this post 2 years ago, you can give it a try, do a backup on TWRP first, if everythinggoes as you expected, that good. If not you know how to restore.
Click to expand...
Click to collapse
Sorry for reviving the thread. ?
But I was hoping you atleast remember if this trick turn off HW key backlight or not.
Mr.Ak said:
Sorry for reviving the thread.
But I was hoping you atleast remember if this trick turn off HW key backlight or not.
Click to expand...
Click to collapse
Np mate,. Did it work? I don't rememberif it did or not
Related
Hi.
I really miss the search button from the Desire device. I have tried to remap the send (dial) button to search by altering the bravo-keypad.kl file in /system/usr/keylayout. But the change didn't work. My altered keypad file is posted below, maybe someone can tell me why it's not working?
SOLUTION: Edit the right file. In my build the default qwerty.kl file was used not the bravo-keypad.kl. Adding SEARCH to key 231 and 61 turns the send key into a search key Even voice search by long press works
key 102 HOME
key 139 MENU
key 158 BACK
key 217 SEARCH
key 107 ENDCALL WAKE_DROPPED
key 116 POWER WAKE_DROPPED
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
key 231 SEARCH
key 61 SEARCH
Sent from my HD2 running Android
just revert what you changed back to how it was.
then hold down the start button (Windows Logo) and the keyboard will pop up, once you start typing it will go into the search app.
mr_billionaire said:
just revert what you changed back to how it was.
then hold down the start button (Windows Logo) and the keyboard will pop up, once you start typing it will go into the search app.
Click to expand...
Click to collapse
Thanks for that tip, but unfortunately it does not work inside all applications.
Thought u ment the Hardware search buttom, missing that a lot, couse a lot of apps maps it (search buttom) to combine some function. If we take ån sms progie fex. The search buttom is maped to compose sms's, hope someone fine a way to map a Hardware key to the search buttom
Yeah I need to map Multi Task manager to a hard key, can you help with that?
-------------------------------------
Sent via the XDA Tapatalk App
Cobra2 said:
Thought u ment the Hardware search buttom, missing that a lot, couse a lot of apps maps it (search buttom) to combine some function. If we take ån sms progie fex. The search buttom is maped to compose sms's, hope someone fine a way to map a Hardware key to the search buttom
Click to expand...
Click to collapse
This is exactly what I have done, remapped the physical send button (left most button on the HD2) to behave like a search button. HTC Desire does not have a send button either, and I don't miss it. I find it more usefully to have a search button then a send (call) button.
Sent from my HTC Desire using XDA App
Where are you entering this data to change these settings?
-------------------------------------
Sent via the XDA Tapatalk App
Try remapping a button to DPAD_CENTER and see if it works for the trackball in camcorder.
paalkr said:
This is exactly what I have done, remapped the physical send button (left most button on the HD2) to behave like a search button. HTC Desire does not have a send button either, and I don't miss it. I find it more usefully to have a search button then a send (call) button.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Hi paalkr
Where is the file qwerty placed ? That would be great if it worked for me, I really miss the hardware search buttom.
Thanx
Cobra2 said:
Hi paalkr
Where is the file qwerty placed ? That would be great if it worked for me, I really miss the hardware search buttom.
Thanx
Click to expand...
Click to collapse
All files related to key mappings are located in /system/usr/keylayout . The qwerty.kl is the one that android is defaulting to if not specified otherwise. There may be some other kl files in the folder, but the vendor specific file is just "left overs" from the ROM rip (in some cases).
paalkr said:
All files related to key mappings are located in /system/usr/keylayout . The qwerty.kl is the one that android is defaulting to if not specified otherwise. There may be some other kl files in the folder, but the vendor specific file is just "left overs" from the ROM rip (in some cases).
Click to expand...
Click to collapse
Thanx big time mate for pointing me the right place, that is just what i needed for the handcent sms.
Sent from my HTC HD2 using XDA App
Mapping End Key
Has anyone mapped the end call button to work. On my Darkstone build I have to hit the end call on screen, hitting the red hard key just shuts the screen off (very annoying). I then have to wake up the phone and end the call.
I pulled both bravo_keypad and qwerty files but both seem to be set to the right end key.
Any ideas or help?
Jwatt0918 said:
Has anyone mapped the end call button to work. On my Darkstone build I have to hit the end call on screen, hitting the red hard key just shuts the screen off (very annoying). I then have to wake up the phone and end the call.
I pulled both bravo_keypad and qwerty files but both seem to be set to the right end key.
Any ideas or help?
Click to expand...
Click to collapse
theres an options in the settings menu to do this, i just cant find it. I used to have it set correctly, but changing roms every few days, you start to get confused. I would appreciate it if someone could point us in the right direction.
Thank you.
Thanks for this useful tip that works perfectly !
A way to only map quick press to Search and keep long press on DIAL Button associate to Phone ?
here is my qwerty.kl file. what did i do wrong?
songokussm said:
here is my qwerty.kl file. what did i do wrong?
Click to expand...
Click to collapse
Didn't succeed either, I mounted system as read write and modified qwerty.kl, rebooted but nothing changed. I would like a lot too having the search button on the call key :-(
I am on Shubcraft build
DocteurN said:
Thanks for this useful tip that works perfectly !
A way to only map quick press to Search and keep long press on DIAL Button associate to Phone ?
Click to expand...
Click to collapse
I would like that too, but I haven't sorted that out.
songokussm said:
here is my qwerty.kl file. what did i do wrong?
Click to expand...
Click to collapse
Could be that your build uses an other file then the qwerty.kl. Have you tried to edit the vendor specific file instead?
on my device using shubcraft v1.4 it was the htcleo-keypad.kl
Sent from my HD2
phrozendevil said:
on my device using shubcraft v1.4 it was the htcleo-keypad.kl
Sent from my HD2
Click to expand...
Click to collapse
phrozendevil is 100% correct it is the htcleo-keypad.kl file.
Now i just need help with chaning the volume buttons to the camera buttons.
I changed:
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
To:
key 115 CAMERA WAKE
key 114 CAMERA WAKE
Upon press it starts the camera app, but will not take a photo. However when i switch to the camcorder function, that works just fine.
Ideas?
ps: i just use a widget to control my volume, which is very rare for me.
Ok, I searched and can't find anything on this. Any thoughts?
FYI...Im using CM7
Thanks.
Sent from my NookColor using XDA Premium App
ramiss said:
Ok, I searched and can't find anything on this. Any thoughts?
FYI...Im using CM7
Thanks.
Sent from my NookColor using XDA Premium App
Click to expand...
Click to collapse
I don't know that you can stop one of the 4 inputs from waking up the hardware, but...
You can define the 'n' button to do something that doesn't offend you and set your screen to sleep after a very brief moment (15 seconds).
Why do you want to change the hardward button behavior?
byronczimmer said:
Why do you want to change the hardward button behavior?
Click to expand...
Click to collapse
Hi, thanks for answering. The reason for this request is because the screen keeps waking up as it moves around in my bag. Just lightly pushing on the case/cover I use will activate the button and leave the screen on until the timeout. I am surprised this isn't an issue for more people (or perhaps people aren't noticing their nook turning on.)
Lowering the timeout is not going to work since I do a lot of reading and having to tap the screen every 15 seconds would be a pain. Unless anyone has figured out how to get screebl to work??
You can completely disable the "N" button by editing the keyboard layout file. Using Root Explorer (paid app - but WELL worth it!) or equivalent, navigate to SYSTEM>USR>KEYLAYOUT then click the button at the top to "Mount R/W", now long-press the file "qwerty.kl" and choose "Open in Text Editor". Then find the following line:
Code:
key 102 HOME WAKE
and simply add a # to the beginning of that line so that it looks like this:
Code:
#key 102 HOME WAKE
Now press your MENU button and choose "Save & Exit". You'll need to reboot the Nook for the change to take effect.
Now your N button should be completely disabled. Just make sure you have the soft keys set up with a home button so you'll have a way to use that functionality when needed.
If you want to maintain the functionality of the "N" button but just prevent it from waking the Nook, simply remove the word WAKE from that line and don't insert the # character. I haven't tried this implementation, but it should work fine.
If you did what jason suggest, make sure you not hide the status bar.
You can change the "unhide" button to something else in Tablet Tweaks or you can use the long-press Power menu option which is also in Tablet Tweaks.
911jason - thanks for that.
Running CM7.0.3 from sdcard, used Root Explorer to find and edit the keyboard layout file.
Simply removed WAKE from the home button as suggested.
Works beautifully. Doesn't wake the device, yet does all the other stuff it's supposed to.
Score one victory for increased battery life for shared knowledge.
I have a soft case and it gets turned on in my pocket.
I went ahead and also removed WAKE from the volume up and down buttons.
Now the only way to wake the screen is the power button. The way my case is, that's the one button that won't get pressed in daily travel.
(don't know if reboot is necessary, but i'd assume so, and did after each change before testing)
Thanks!
TCAndroid said:
911jason - thanks for that.
Running CM7.0.3 from sdcard, used Root Explorer to find and edit the keyboard layout file.
[ ... ]
I went ahead and also removed WAKE from the volume up and down buttons.
Click to expand...
Click to collapse
I also took WAKE off the volume keys, because I tend to reach into my bag and adjust the volume while walking or waiting for the train. My buttons don't tend to get pressed, since my bag is for a netbook and my uncased NC doesn't rattle around. However, after adjusting the volume, the screen was live and the bag and its contents sometimes made random touches all over the screen...
The volume buttons now work exactly the way I want! Thanks for the very clueful answer to this question!
Of course, now I have another thing to do every time I update my ROM. I should learn how to make update scripts!
I am curious why HOME has WAKE and not WAKE_DROPPED, when it appears to behave like WAKE_DROPPED.
From what I understand, WAKE_DROPPED causes the device to wake from sleep but does not send the command normally associated with the button that was pressed. WAKE will wake from sleep and also send the command after doing so.
911jason said:
From what I understand, WAKE_DROPPED causes the device to wake from sleep but does not send the command normally associated with the button that was pressed. WAKE will wake from sleep and also send the command after doing so.
Click to expand...
Click to collapse
Exactly so. HOME acts like WAKE_DROPPED, doesn't it? But it's marked WAKE.
Actually, yes, you're right... just realized that. Not sure why it's behaving that way.
I was wondering if there is a way to change key functions on note 3, for example: by pressing menu key we can see recent apps instead of menu
I would be thankful if anyone can suggest a solution to do this:good::laugh:
arash2901 said:
I was wondering if there is a way to change key functions on note 3, for example: by pressing menu key we can see recent apps instead of menu
I would be thankful if anyone can suggest a solution to do this:good::laugh:
Click to expand...
Click to collapse
There are actually a couple different ways to do it...
You can used Xposed mod, with either Xposed Additions or MenuBeGone
(I've never used either of these methods...)
or, the way that I do it, manually edit the \system\usr\keylayout\Generic.kl file.
When I do it, I make the following two changes:
Change key 139 from MENU to BACK
Change key 158 from BACK to APP_SWITCH
Then I use button savior to add the menu for those things that need it...
(I'm coming from Nexus devices, so having the keys with back on the left, and app switch on the right is how I'm used to it...)
Ever wondered to use Google search ? Just saying.
Sent from my N9005
carnagecjb said:
There are actually a couple different ways to do it...
You can used Xposed mod, with either Xposed Additions or MenuBeGone
(I've never used either of these methods...)
or, the way that I do it, manually edit the \system\usr\keylayout\Generic.kl file.
When I do it, I make the following two changes:
Change key 139 from MENU to BACK
Change key 158 from BACK to APP_SWITCH
Then I use button savior to add the menu for those things that need it...
(I'm coming from Nexus devices, so having the keys with back on the left, and app switch on the right is how I'm used to it...)
Click to expand...
Click to collapse
thanks
that's helpful (kind of!)
I was able to change function of key like starting camera by pressing menu key, but still don't know how to put recent app instead of menu?
--------------------------------------------
[problem solved,found it]
thanks a million man
big help
arash2901 said:
thanks
that's helpful (kind of!)
I was able to change function of key like starting camera by pressing menu key, but still don't know how to put recent app instead of menu?
Click to expand...
Click to collapse
Quick and easy answer:
Change key 139 from MENU to APP_SWITCH
Hi,
i am previously a Moto G (2013) user.. got used to onscreen buttons like pie and gesture control.
Most of the guides available out there wont work with Le 1s.. so here it is
HTML:
do at your own risk. make sure you know about the consequences of things you are going to do.
i always recommend a back up while messing with system partition
Open this file
system>>usr>>keylayout>>ssynaptics_dsx_i2c.kl
look for below lines
Code:
key 158 BACK VIRTUAL
key 172 HOME VIRTUAL
key 580 APP_SWITCH VIRTUAL
change it to (put "#" before all lines)
Code:
#key 158 BACK VIRTUAL
#key 172 HOME VIRTUAL
#key 580 APP_SWITCH VIRTUAL
This disables the respective action of capacitive buttons.
To enable on screen navigation button(enabling this makes your screen looks awkward) though i would prefer to use Pie controls or LMT launcher etc..
go to build.prop
search for this line
Code:
#qemu.he.mainkeys=0
change it to
Code:
qemu.he.mainkeys=0
Reboot.
PS. i am also trying to disable backlight of disabled capacitive buttons, anyone knows can help me
reversegear said:
PS. i am also trying to disable backlight of disabled capacitive buttons, anyone knows can help me
Click to expand...
Click to collapse
You can download an app called keyboard backlight controller.
naparajito said:
You can download an app called keyboard backlight controller.
Click to expand...
Click to collapse
Yeah..
Thank you
I ve come across many apps which does that.. I'm exploring system level hack
For ex modifying this file(check screenshot) disables but it gets reverted back on reboot
That will have to fixed in kernel. Easy stuff though.
reversegear said:
Hi,
i am previously a Moto G (2013) user.. got used to onscreen buttons like pie and gesture control.
Most of the guides available out there wont work with Le 1s.. so here it is
HTML:
do at your own risk. make sure you know about the consequences of things you are going to do.
i always recommend a back up while messing with system partition
Open this file
system>>usr>>keylayout>>ssynaptics_dsx_i2c.kl
look for below lines
Code:
key 158 BACK VIRTUAL
key 172 HOME VIRTUAL
key 580 APP_SWITCH VIRTUAL
change it to (put "#" before all lines)
Code:
#key 158 BACK VIRTUAL
#key 172 HOME VIRTUAL
#key 580 APP_SWITCH VIRTUAL
This disables the respective action of capacitive buttons.
To enable on screen navigation button(enabling this makes your screen looks awkward) though i would prefer to use Pie controls or LMT launcher etc..
go to build.prop
search for this line
Code:
#qemu.he.mainkeys=0
change it to
Code:
qemu.he.mainkeys=0
Reboot.
PS. i am also trying to disable backlight of disabled capacitive buttons, anyone knows can help me
Click to expand...
Click to collapse
Thank you so much for this!!
I cracked my screen pretty badly. So I cannot use the capacitive buttons, and what is worse, they are activated randomly by themselves
I had previously found out how to activate the virtual buttons, which helped. But I did not know how to de-activate the capacitive buttons. This was a great help!!
However the app "Keyboard backlight controller" does not seem to work for me, it does not ask for root permission and it does not turn off the backlight.... but this is a very minor issue compared to my previous issues
While editing keys putting # , to disable capacitive buttons , it is showing a message "error occurred while saving the file, it will not be saved" what to do now I want to disable capacitive buttons
---------- Post added at 10:23 AM ---------- Previous post was at 10:14 AM ----------
Due to crack on display and improper function of capacitive buttons I want to disable that and I want to enable VIRTUAL navigation keys , while following mr.botze steps using codes while editing I mean after putting # and saving, it is showing a message " error while saving the file ,it will not be saved" what to do , anybody can help me out from this
Letvaffu said:
While editing keys putting # , to disable capacitive buttons , it is showing a message "error occurred while saving the file, it will not be saved" what to do now I want to disable capacitive buttons
---------- Post added at 10:23 AM ---------- Previous post was at 10:14 AM ----------
Due to crack on display and improper function of capacitive buttons I want to disable that and I want to enable VIRTUAL navigation keys , while following mr.botze steps using codes while editing I mean after putting # and saving, it is showing a message " error while saving the file ,it will not be saved" what to do , anybody can help me out from this
Click to expand...
Click to collapse
seems to be you dont have root previlages
reversegear said:
seems to be you dont have root previlages
Click to expand...
Click to collapse
...either that, or that you forgot to mount in R/W. What app are you using to view the files? In Root exporer, there is a button on the top that says "mount R/W" (read-write). If you don't press that you can only VIEW the files, not edit.
Is rooting needed?
botze said:
...either that, or that you forgot to mount in R/W. What app are you using to view the files? In Root exporer, there is a button on the top that says "mount R/W" (read-write). If you don't press that you can only VIEW the files, not edit.
Click to expand...
Click to collapse
I opened in edit mode but receive the error.. I have not rooted my mobile, is that the reason?
Hey guys,
So I used ZUI 2.3 for a bit and using DEVELOPER MODE you can enable the hardware keys to be used. But the left hardware key which was used as RECENT APPS key in the COS/CM/AOSP is used as MENU which is really not useful to me. Does anybody have an idea as to how to change the hardware key binding? I heard there is a file in which values can be changed once you have rooted the phone. I wish to know the details.
SarthakSL said:
Hey guys,
So I used ZUI 2.3 for a bit and using DEVELOPER MODE you can enable the hardware keys to be used. But the left hardware key which was used as RECENT APPS key in the COS/CM/AOSP is used as MENU which is really not useful to me. Does anybody have an idea as to how to change the hardware key binding? I heard there is a file in which values can be changed once you have rooted the phone. I wish to know the details.
Click to expand...
Click to collapse
Don't have ZUI installed, if you have "Settings->Buttons" you can change the HW keys from this option.
aaswar said:
Don't have ZUI installed, if you have "Settings->Buttons" you can change the HW keys from this option.
Click to expand...
Click to collapse
But all I could do was reassign to HOME button in the UTOUCH settings of ZUI. I want the solution for ZUI 2.3.
I am going to try this: (Button Remapper No Root)
https://play.google.com/store/apps/details?id=com.irishin.buttonsremapper&hl=en
EDIT:
Tried the app. RECENT working perfectly on the left hardware button. HOME soft touch to actually working like HOME isn't working flawlessly. But will do. So people who want the capacitive buttons like COS on the ZUI 2.3 should install that app and configure it like that. I am still looking for a better solution. Cheers!
aaswar said:
Don't have ZUI installed, if you have "Settings->Buttons" you can change the HW keys from this option.
Click to expand...
Click to collapse
There is no button option under setting... Menu and back key option is in developer settings.. I do enabled it.. But how to enable soft touch home by just a single tap...
ADDICTED777 said:
There is no button option under setting... Menu and back key option is in developer settings.. I do enabled it.. But how to enable soft touch home by just a single tap...
Click to expand...
Click to collapse
Two files specifically generic.kl and fpc1020tp.kl located in system /usr/keylayout are needed to be edited.
With the help of any root browser, simply open the generic.kl with a text editor and scroll to the 'key 158' and change the attribute from default 'BACK' TO 'HOME'. Similarly, open the fpc1020tp.kl and do the same modification.
Save both files and reboot to notice the change.
Bingo
QuazIqbal said:
Two files specifically generic.kl and fpc1020tp.kl located in system /usr/keylayout are needed to be edited.
With the help of any root browser, simply open the generic.kl with a text editor and scroll to the 'key 158' and change the attribute from default 'BACK' TO 'HOME'. Similarly, open the fpc1020tp.kl and do the same modification.
Save both files and reboot to notice the change.
Bingo
Click to expand...
Click to collapse
Then back key won't work... It'll always work as the home..
ADDICTED777 said:
Then back key won't work... It'll always work as the home..
Click to expand...
Click to collapse
Exactly
QuazIqbal said:
Exactly
Click to expand...
Click to collapse
Then what is the advantage of enabling the menu and back button... If the back button work no more... Cz after tweaking those two files back button will also work as the home button... So whats the point??
ADDICTED777 said:
Then what is the advantage of enabling the menu and back button... If the back button work no more... Cz after tweaking those two files back button will also work as the home button... So whats the point??
Click to expand...
Click to collapse
Dedicated Menu and Back key work as usual. Only the home button touch will not act as back key (as present in default zui)
QuazIqbal said:
Dedicated Menu and Back key work as usual. Only the home button touch will not act as back key (as present in default zui)
Click to expand...
Click to collapse
Thanks mate it worked.. By the way is there any way to screen search of google replace the menu button with recent app switch?? On ZUI
What about APP_SWITCH?
QuazIqbal said:
Two files specifically generic.kl and fpc1020tp.kl located in system /usr/keylayout are needed to be edited.
With the help of any root browser, simply open the generic.kl with a text editor and scroll to the 'key 158' and change the attribute from default 'BACK' TO 'HOME'. Similarly, open the fpc1020tp.kl and do the same modification.
Save both files and reboot to notice the change.
Bingo
Click to expand...
Click to collapse
Can i set the menu button to open Recent Apps/App Switch screen?
may I ask if the 2 capacitive buttons back and menu do light up or wont light even enable on ZUI 2.3?
also only blue notification light on all app notifications? mine only emit blue light even with other led apps, but charging red and full charge green,
thanks for any comments