Related
This is really a low-level type of hack, as it just requires editing a few files.
------------------------------------------------------------------------------------------
Sick of the Hero not having a designated "camera" button?
Well then, remap the damn thing.
How to:
MAKE A BACKUP OF THE FILE BEFORE PROCEEDING
Firstly, we'll need to pull the file that controls the heroc keypad which is entitled "heroc-keypad.kl" in "system/usr/keylayout".
To pull the file:
Code:
adb remount
adb pull system/usr/keylayout/heroc-keypad.kl heroc-keypad.kl
Now the file will appear in your Android SDK tools folder so you can edit it.
I recommend using Notepad++ but any kind of text editing tool will work.
Now open the file and it should look a little something like this(minus the "unuse" keys):
Code:
key 102 HOME
key 139 MENU WAKE_DROPPED
key 158 BACK
key 127 SEARCH
key 231 CALL
key 107 ENDCALL WAKE_DROPPED
key 191 DPAD_CENTER
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
As you can see, there are different attributes assigned to each key.
Specific application/action launchers:
Code:
HOME #Launches "Home"
MENU #Launches "Menu"
BACK #Takes you back to the last activity
SEARCH #Launches "Universal Search"
CALL #Launches the "Phone" activity and corresponding .apk or initiates a call
ENDCALL #Ends a call
CAMERA #Launches "Camera" activity and corresponding .apk
FOCUS #Initiates Auto-Focus while using the Camera
VOLUME_UP #Self explanatory
VOLUME_DOWN #^
And attributes saying if it should wake the phone at button push to complete the action, or if it should just complete the action without waking the screen.
Code:
WAKE #Completes the action without waking the screen
WAKE_DROPPED #Wakes the phone to complete the action
NOTE: "CAMERA" can't utilize the "WAKE_DROPPED" attribute since it's an attempt to launch an activity without initializing anything else.
Anyways you can assign any of these attributes to any of the keys.
Personally, I remap the Phone button to launch the Camera, and the Search button to activate Auto-Focus:
Code:
key 231 CAMERA
key 127 FOCUS
Then when I'm using the Camera, I just hold down the "SEARCH" button to focus and push the "TALK" button to take a snapshot.
After you're done with your edits, you'll need to save the file properly(NO .txt files!), and then you'll have to push it back to the phone.
Code:
adb remount
adb push heroc-keypad.kl /system/usr/keylayout
Reboot your phone, and then long press the selected button to see if your edits worked!
Enjoy!
UPDATE!!!!
Code:
--------------------------------------------------------------------
key 200 MEDIA_PLAY_PAUSE #Pauses Music
key 201 MEDIA_PLAY_PAUSE #^
key 166 MEDIA_STOP #Stops the media
key 163 MEDIA_NEXT #Plays next media
key 165 MEDIA_PREVIOUS #Plays previous media
key 168 MEDIA_REWIND #Rewinds the media
key 208 MEDIA_FAST_FORWARD #Fast Forwards the media
The second half is from the AVRCP.kl which controls media actions on our device. But as you can see the keys aren't correctly mapped as we don't have that many(or those key numbers) at our disposal.
What you can actually do is take these attributes and map them in heroc-keypad.kl
Code:
key 102 HOME
key 139 MENU WAKE_DROPPED
key 158 BACK
key 127 MEDIA_PLAY_PAUSE WAKE
key 231 CALL
key 107 ENDCALL WAKE_DROPPED
key 191 DPAD_CENTER
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
This maps the attribute "MEDIA_PLAY_PAUSE" at the "SEARCH" key. By pushing it, you can pause media with the first push and play it with a successive push. The added attribute "WAKE" allows it to complete the action without waking the phone.
__________________________________________________________________________________________________
I want to thank Geniusdog254 for the heads up regarding not having to edit AVRCP.kl
CHECK OUT HIS FREE APP: Search2Play(Hero/Evo support!)
and
CHECK OUT HIS REMAPPING MOD FOR THE G1
Big thanks!
NOTE: You can also use Root Explorer or any other Root File Manager that has Text Editing
Custom app launching
Ok, so with some inspiration from BuglessPete's How to make script run by using hardware keys. I've devised an 'idea' as to how to custom launch an activity with keypad push.
Currently, you can launch any activity from shell by just using am.
Here's an example of launching the browser using am in the shell:
Code:
am start -a android.intent.action.MAIN -n com.android.browser/.BrowserActivity
Which results in:
Code:
Starting: Intent { act=android.intent.action.MAIN cmp=com.android.browser/.BrowserActivity }
And the program launches!
But if you put this into a script, even a basic linux shell script, you can call it quickly just by running the script! So in theory if you map this script to a keycode, you can call the script by a button push.
How?
Well first, before you compile the ramdisk, you need to create a service that contains the script necessary for the intent activity you are trying to accomplish.
Second, you have to add the proper keycodes in an init script of your choice:
Code:
#example
service <activity> /path/to/yourservice
oneshot
disabled
keycodes 107 127
Which maps the activity to the search button after launching the service with the endcall button
This is currently just a theory as I haven't tested it out myself(busy with other things).
But if you would like to attempt it, I'd love feedback.
Quick Service Creation Tutorial: http://developerlife.com/tutorials/?p=356
Little error.. heroc_keypad.kl is in /system/usr/keylayout/heroc_keypad.kl.
EDIT: And it's heroc-keypad and not heroc_keypad.
HeroMeng said:
Little error.. heroc_keypad.kl is in /system/usr/keylayout/heroc_keypad.kl.
Click to expand...
Click to collapse
Nice catch, lol.
Always forget something simple.
EDIT: I really need to start posting stuff while using my laptop.
nice
thanks man this is awesome.
im just "learning" linux. how would i set up the search button for an intent(sp) like opening the browser.apk
feefeeboomboom said:
thanks man this is awesome.
im just "learning" linux. how would i set up the search button for an intent(sp) like opening the browser.apk
Click to expand...
Click to collapse
Well "SEARCH" essentially launches the browser by linking it automatically to google search.
But, in regards to assigning it to launch a different(unlisted) activity, I'm not sure. That's something I'm actually looking into myself, and I think I'm making a little bit of head way .
Haha great work [HOPE]maybe the hero development won't die[/HOPE]
I'm putting this in my sig if you don't mind?
thatguythatdid said:
Haha great work [HOPE]maybe the hero development won't die[/HOPE]
Click to expand...
Click to collapse
As long as there are people there willing to learn, development for the Hero will never die.
[RANT]
I'll make a post in the General Section with all the bookmarked dev'ing related resources that I've found over the year. Then people can just jump in and start reading/tinkering.
What I don't like about the HeroCDMA forum is that most of the community here doesn't share much of HOW they did/do things. Hopefully that will change.
=D
[/RANT] (Please don't respond to this part, haha)
almost forgot what program are you using to open the kl file? Mine always comes out in a horizontal line instead of a vertical like yours?
Edit: Nevermind wordpad does it great
notepad++ is the sh!-|-
feefeeboomboom said:
notepad++ is the sh!-|-
Click to expand...
Click to collapse
I'm a dumbass. I didn't read the entire post before I asked my question and thought that nevermind. Yes notepad is the s
Good work, thanks for putting together a very easy to read how-to.
Thanks for this, the trackball is so annoying for pictures. I made the changes just as it states to but the zoom won't work on the search button, I hold it down and it does nothing, any idea why that may be? And the search button no longer responds on the homescreen, which makes sense but why not in the camera app?
chrish03 said:
Thanks for this, the trackball is so annoying for pictures. I made the changes just as it states to but the zoom won't work on the search button, I hold it down and it does nothing, any idea why that may be? And the search button no longer responds on the homescreen, which makes sense but why not in the camera app?
Click to expand...
Click to collapse
Zoom? Do you mean auto-focus?
I want to do this but I cant get my phone to remount. I have never had a problem before.
cd c:\android-sdk-windows\tools
adb remount
doesn't remount says "no devices found"
CarbonKang said:
I want to do this but I cant get my phone to remount. I have never had a problem before.
cd c:\android-sdk-windows\tools
adb remount
doesn't remount says "no devices found"
Click to expand...
Click to collapse
Heh, is your phone plugged in? USB cable damaged? USB port damaged? Hole plugged? Bears?
If it's none of those, do this:
Code:
adb kill-server
adb start-server
then
Code:
adb remount
If that doesn't work, start from the top again.
Decad3nce said:
Zoom? Do you mean auto-focus?
Click to expand...
Click to collapse
LOL, reading comprehension FTW! I got FOCUS and ZOOM confused. Don't play with your phone late at night!
Decad3nce said:
Heh, is your phone plugged in? USB cable damaged? USB port damaged? Hole plugged? Bears?
If it's none of those, do this:
Code:
adb kill-server
adb start-server
then
Code:
adb remount
If that doesn't work, start from the top again.
Click to expand...
Click to collapse
none of that worked. And there is nothing wrong with the ports at all. I think its Darchdroid.. It has something defective every time I use it lol.
CarbonKang said:
none of that worked. And there is nothing wrong with the ports at all. I think its Darchdroid.. It has something defective every time I use it lol.
Click to expand...
Click to collapse
Do you have USB debugging enabled?
(I haven't had any problems with darchs build)
Decad3nce said:
Do you have USB debugging enabled?
(I haven't had any problems with darchs build)
Click to expand...
Click to collapse
ya, trust me I know what I'm doing.
It just doesn't work
I would love to show you a logcat... but i cant adb remount LOL
Can someone make a flashable zip so i can have a designated camera button as search? I want to be able to click it to take a snap shot of my phone with dro cap.
Thanks
Alright, the Galaxy series, although awesome, suffers from some issues. None are as frustrating as when the damn capacitive (bottom) buttons stop working!
Normally it seems that all four bottom buttons don't fail at the same time, just one or two. This doesn't seem to be as much of a physical problem as a software one, probably an application running in the forefront that is blocking them. Now it is hard to do much of anything if the settings button (left side) fails, as you cannot access most settings for your apps. Both my outside buttons rarely work, the aforementioned settings button (left) and the search button (right). Search button doesn't matter to me, I can call up search on screen easily enough. The other two are home and back buttons. Back is more necessary than home. So to work around this Samsung-induced-pain-in-the-ass, I swapped the search button function for the home.
Here's how:
Make sure you are roted and have a rooted file manager. Root Explorer tends to work best.
1. Open Root Explorer, and make sure it is mounted r/w.
2. Navigate to /system, /usr, /keylayout.
3. Tap/hold Broadcom_Bluetooth_HID.kl, and select 'Open in Text Editor'. If you get a Warning message, that means you are mounted r/o so you just need to click the Mount R/W button above.
4. Change key 139 to read HOME instead of MENU.
Change key 102 to read MENU instead of HOME.
Hit the back capacitive button and choose to save. It will create a Broadcom_Bluetooth_HID.kl.bak file also so if you want to undo this then just erase the new Broadcom_Bluetooth_HID.kl file and then erase the .bak off the other file.
5. Now open the melfas_touchkey.kl file the same way by holding it until it allows you to select 'Open in Text Editor'.
Change key 139 to read HOME instead of MENU.
Change key 102 to read MENU instead of HOME.
Hit the back capacitive button and choose to save. It will also create a .bak file.
6. Open the qwerty.kl file by holding it until it allows you to select 'Open in Text Editor'.
Change key 102 to read MENU instead of HOME.
Change key 139 to read HOME instead of MENU.
Hit the back capacitive button and choose to save. It will again create a .bak file.
7. Back out of Root Explorer and restart your phone.
Now, when you push your home button it will bring up your settings menu in whatever application is open, and your settings button will do the home function (or nothing, as my outside buttons do as they don't usually work). I now use my back button to get me to home, it just takes a few more pushes as it goes one step at a time. Not as much of a pain as not being able to set program functions, that's for sure!
Note: Depending on your setup, the file names might be slightly different on other Android devices, but they will always be very similar. They'll all have a bluetooth.kl, touchkey.kl and qwerty.kl (or whatever your keyboard layout might be). You can also fool around with other key settings if you wish to experiment, depending on what is and is not working at the current time. Just save your original .bak files so you can put it back to normal easily. If you alter the .kl file more than once, it will overwrite the .bak file again (which is not used by the phone) so make sure you copy the .bak's to another directory (such as /sdcard/backups or your regular computer).
Hope this makes your lives easier and don't forget to thank me if I helped you.
Modified Home key acting up
So after using this mod for a little while, it has been working well except for some slight stalling of response from the capacitive buttons (which was happening before the mod) and an awfully annoying habit of backing out of programs by itself due to the modified left button which was originally Settings but I changed to Home with the above mod. When this happens, I can see the left button go dark as if it's been physically pressed, so obviously there is some electrical or software malfeasance happening there.
The fix to this problem is to navigate to your /system/usr/keylayout folder again and:
Delete: "key 139 HOME"
In each of these three folders we altered earlier:
Broadcom_Bluetooth_HID.kl
melfas_touchkey.kl
qwerty.kl
The result is that no action is associated with the leftmost capacitive button, which is fine because it wasn't working properly in the first place. This was becoming problematic as I typed in Terminal or while using my Ubuntu build on the phone.
Now, if there was also a problem with the search popping up by itself then you would just have to delete "key 217 SEARCH". Remember why I initially did this was because the outside capacitive buttons were not functioning properly and I needed the settings button more than home while in programs.
Fully Functioning Capacitive Button Workaround
I actually found a specific need for the home key.
When in Terminal Emulator, if I want to back out to the main screen and access another application, I have to use my back button. Trouble is, the back button also closes out the terminal session, which is a pain in the *ss if I want to just look up something in my browser and then go back to it. I have to then restart my session and retype on the small as hell keyboard. So I was thinking, how am I going to implement a home key function in my drop-down start menu which is always accessible and low-and-behold, here it is:
SoftKeys for Root Users
https://market.android.com/details?...EsIm5ldC5ob29wYWpvby5hbmRyb2lkLlNvZnRLZXlzIl0.
This is a great app. Solves the problem. Starts immediately on boot.
There's also this for just a home key in the start menu drop-down, no start on boot though:
BK Softhome
https://market.android.com/search?q=bk+softhome&c=apps
Problems solved! I now have disabled all 4 capacitive buttons while using Softkeys for Root Users for all functions. (Delete: key 102, key 139, key 158, and key 217 in all three folders listed in original post)
One of the annoying things about the S4 is the lack of software navigation buttons. I was used to using them on my Nexus 4 so I really missed having them on my S4.
First of all, root is required to edit these files.
Basically, all you have to do is add 'qemu.hw.mainkeys=0' to the build.prop in /system and reboot to enable the software buttons. If you're happy with that you can stop there, but you can also disable the hardware buttons if you want.
Go to /system/usr/keylayout and open 'Generic.kl' in a text editor and find the lines that say 'key 139 MENU WAKE_DROPPED', 'key 158 BACK WAKE_DROPPED', and 'key 172 HOME' and place a # at the start of each line. Take care here because if you add a # to the wrong line, you won't have a way to wake the phone. Reboot and those hardware buttons will be disabled.
I've tested it with various apps and the phone resizes them appropriately. Software menu buttons appear where appropriate and video players cause the buttons to fade away. The only odd thing I've found is that the app drawer is shifted to a 4x4 layout instead of the regular 5x4. Also, home and back do not vibrate properly and I'm not sure which lines to edit to fix that.
futurejohn said:
One of the annoying things about the S4 is the lack of software navigation buttons. I was used to using them on my Nexus 4 so I really missed having them on my S4.
First of all, root is required to edit these files.
Basically, all you have to do is add 'qemu.hw.mainkeys=0' to the build.prop in /system and reboot to enable the software buttons. If you're happy with that you can stop there, but you can also disable the hardware buttons if you want.
Go to /system/usr/keylayout and open 'Generic.kl' in a text editor and find the lines that say 'key 139 MENU WAKE_DROPPED', 'key 158 BACK WAKE_DROPPED', and 'key 172 HOME' and place a # at the start of each line. Take care here because if you add a # to the wrong line, you won't have a way to wake the phone. Reboot and those hardware buttons will be disabled.
I've tested it with various apps and the phone resizes them appropriately. Software menu buttons appear where appropriate and video players cause the buttons to fade away. The only odd thing I've found is that the app drawer is shifted to a 4x4 layout instead of the regular 5x4. Also, home and back do not vibrate properly and I'm not sure which lines to edit to fix that.
Click to expand...
Click to collapse
Do you know how to re-size screen buttons ?
p.s. everything works fine, but it to big ((
x111 said:
Do you know how to re-size screen buttons ?
p.s. everything works fine, but it to big ((
Click to expand...
Click to collapse
The easiest way to do that is to change the lcd density. The default is 480 which makes everything MASSIVE. I find about 440 to be about perfect, but you can tweak it to find whatever is most comfortable for your eyes.
To change the lcd density, the simplest way is to go to build.prop and find the line that says 'ro.sf.lcd_density=480'. Change the 480 to whatever you want. Smaller numbers mean that things will be smaller and more spaced out and larger numbers will cause things to be larger and closer together. Reboot after you change the number and save the file for it to take affect.
You can also use tools like ROM Toolbox to make the edits if you find using an app easier to use than a text editor.
I recommend keeping a backup of your original build.prop for easy restoration.
futurejohn said:
The easiest way to do that is to change the lcd density. The default is 480 which makes everything MASSIVE. I find about 440 to be about perfect, but you can tweak it to find whatever is most comfortable for your eyes.
To change the lcd density, the simplest way is to go to build.prop and find the line that says 'ro.sf.lcd_density=480'. Change the 480 to whatever you want. Smaller numbers mean that things will be smaller and more spaced out and larger numbers will cause things to be larger and closer together. Reboot after you change the number and save the file for it to take affect.
You can also use tools like ROM Toolbox to make the edits if you find using an app easier to use than a text editor.
I recommend keeping a backup of your original build.prop for easy restoration.
Click to expand...
Click to collapse
It works, but again buttons is too big and change ro.sf.lcd_density low than 440 will be too small, and also I need change just screen buttons, other staff looks nice for me with ro.sf.lcd_density 480.
Please, tell step by step how to change it.
Also, do you know how to disable light of sensor buttons? (very annoying)
x111 said:
It works, but again buttons is too big and change ro.sf.lcd_density low than 440 will be too small, and also I need change just screen buttons, other staff looks nice for me with ro.sf.lcd_density 480.
Please, tell step by step how to change it.
Also, do you know how to disable light of sensor buttons? (very annoying)
Click to expand...
Click to collapse
The only way I can tell to just shrink the navigation bar is to edit the framework-res.apk. From my research, you have to decompile the apk, edit the navigation bar field in dimens.xml, and recompile the apk. I tried that but ended up having to restore my phone after I got a bunch of force closes. :laugh:
It's obviously a bit more complex than what I just mentioned so I'll just have to mess around with it more before I know how to do it.
If anyone else has experience editing framework-res any help you could offer would be awesome.
futurejohn said:
One of the annoying things about the S4 is the lack of software navigation buttons. I was used to using them on my Nexus 4 so I really missed having them on my S4.
First of all, root is required to edit these files.
Basically, all you have to do is add 'qemu.hw.mainkeys=0' to the build.prop in /system and reboot to enable the software buttons. If you're happy with that you can stop there, but you can also disable the hardware buttons if you want.
Go to /system/usr/keylayout and open 'Generic.kl' in a text editor and find the lines that say 'key 139 MENU WAKE_DROPPED', 'key 158 BACK WAKE_DROPPED', and 'key 172 HOME' and place a # at the start of each line. Take care here because if you add a # to the wrong line, you won't have a way to wake the phone. Reboot and those hardware buttons will be disabled.
I've tested it with various apps and the phone resizes them appropriately. Software menu buttons appear where appropriate and video players cause the buttons to fade away. The only odd thing I've found is that the app drawer is shifted to a 4x4 layout instead of the regular 5x4. Also, home and back do not vibrate properly and I'm not sure which lines to edit to fix that.
Click to expand...
Click to collapse
Thanks!
Is there a way to disable the S4 menu and back buttons from lighting up?
jedinegotiator said:
Is there a way to disable the S4 menu and back buttons from lighting up?
Click to expand...
Click to collapse
CM10.2 has this toggle built-in.
Chahk said:
CM10.2 has this toggle built-in.
Click to expand...
Click to collapse
No way to do it without Cyanogen?
Anyone? Also there is no vibration pressing the back and home keys on the navbar. Reading the SIII and Note forums, I believe this is due to the lack of vibration support in kernel. Can anyone confirm?
futurejohn said:
One of the annoying things about the S4 is the lack of software navigation buttons. I was used to using them on my Nexus 4 so I really missed having them on my S4.
First of all, root is required to edit these files.
Basically, all you have to do is add 'qemu.hw.mainkeys=0' to the build.prop in /system and reboot to enable the software buttons. If you're happy with that you can stop there, but you can also disable the hardware buttons if you want.
Go to /system/usr/keylayout and open 'Generic.kl' in a text editor and find the lines that say 'key 139 MENU WAKE_DROPPED', 'key 158 BACK WAKE_DROPPED', and 'key 172 HOME' and place a # at the start of each line. Take care here because if you add a # to the wrong line, you won't have a way to wake the phone. Reboot and those hardware buttons will be disabled.
I've tested it with various apps and the phone resizes them appropriately. Software menu buttons appear where appropriate and video players cause the buttons to fade away. The only odd thing I've found is that the app drawer is shifted to a 4x4 layout instead of the regular 5x4. Also, home and back do not vibrate properly and I'm not sure which lines to edit to fix that.
Click to expand...
Click to collapse
I have tried adding that qemu.hw.mainkeys=0 on build.prop but the soft keys dont come and on every press the systemUI stopping sign comes. Anything else I can do to avoid this. tried it with apex, nova and next launcher. Using omega ROM 14.1
x111 said:
It works, but again buttons is too big and change ro.sf.lcd_density low than 440 will be too small, and also I need change just screen buttons, other staff looks nice for me with ro.sf.lcd_density 480.
Please, tell step by step how to change it.
Also, do you know how to disable light of sensor buttons? (very annoying)
Click to expand...
Click to collapse
"ro.sf.lcd_density" isn't present over here....
But I added that line at the end of all lines in my build.prop ... Setting it at 400-480 gave me very big icons .. 300 gives me the original size of icons.. So I set it at 260.. Now it's giving me a Tablet like look...
And that all above is fine..
But after changing the values.. How is it possible that it changed all my default icons of System Apps...?? Even though those icons were not present in those APKs...?? :what::what:
And yes.. Talking abt NavBar .. Its smaller and much SPACED... Thnkx fo that...
And if u want to ENABLE or DISABLE Light of Hardware buttons here's the link to that APK..
https://www.dropbox.com/s/5qhpbuh5syvl39z/Capacitive.apk
Just download it.. And there are options...
Sent from my Micromax A116 using XDA Premium 4 mobile app
does anyone know if this can be implemented with tasker?
Sorry, this is a little off topic but:
I keep accidentally pressing the hardware navigation keys when typing, particularly when i am in a rush. Is there any way that this method can be used with tasker or any similar app to disable the buttons when the keyboard is in use?
Thank you .. finally I found the solution for my problem ( menu key stop working ).
You will need a root explorer and All in One Gestures app.
Look in device/system/usr/keylayout for generic.kl
Make a backup of this file before editing.
Open it in a text editor and look for lines "Key 158 BACK" and "Key 172 HOME"
Swap BACK and HOME then save and reboot.
Then open All in One Gestures and under hardware keys tab, swap funtion of home and back again.
Somewhere along the line the wake funtion is dropped. Everything else works as normal.
I needed this feature disabled b/c wallet case would keep screen on constantly and eat battery.
I found a slightly better alternative. Your method effectively disables the key light of the BACK button.
My method is:
Edit Generic.kl. Find key with SEARCH, and comment it with a #. Then find HOME, and replace HOME with SEARCH. Go into All In One Gestures, and click on the FAB with "+". Add " Search" key, and assign it the action for Home. That's it. Same effect, but key light for BACK still works!
Both working with Note 4 too.
With first method you are loosing backlight and haptic feedback, while with second you are gaining haptic feedback on home button too.
And you need to set long press for 'google now', otherwise it won't work.
Thoth33 said:
You will need a root explorer and All in One Gestures app.
Look in device/system/usr/keylayout for generic.kl
Make a backup of this file before editing.
Open it in a text editor and look for lines "Key 158 BACK" and "Key 172 HOME"
Swap BACK and HOME then save and reboot.
Click to expand...
Click to collapse
I did a variation of this. I swapped 254 MENU with 172 HOME. That's all. No need to install Xposed or any other apps.
This works simply by editing system files without having to install other apps like Exposed.
Now, the menu button is HOME. But it won't wake the phone, because menu does nothing unless phone is already awake. HOME button is MENU, but it doesn't wake the phone.
Perfect!
I managed to disable the back button by going to /system/usr/keylayout/Generic.kl and adding # in front of key 139 menu and key 158 back but the recents button still works after rebooting. This was the old method when the left button was a menu not recent apps button. Which button number is for recents?
3bs11 said:
I managed to disable the back button by going to /system/usr/keylayout/Generic.kl and adding # in front of key 139 menu and key 158 back but the recents button still works after rebooting. This was the old method when the left button was a menu not recent apps button. Which button number is for recents?
Click to expand...
Click to collapse
You can do that with an app from Play Store. The app is called All in one Gesture. It allows you to change actions on all keys on your phone. It worked for me.
Ninolina said:
You can do that with an app from Play Store. The app is called All in one Gesture. It allows you to change actions on all keys on your phone. It worked for me.
Click to expand...
Click to collapse
Thanks a lot!
3bs11 said:
I can't customise what the short press does
Click to expand...
Click to collapse
That screen look a bit different on my S6. Did you activated it when it asked for it? When you first started it did it asked you for something?
3bs11 said:
I managed to disable the back button by going to /system/usr/keylayout/Generic.kl and adding # in front of key 139 menu and key 158 back but the recents button still works after rebooting. This was the old method when the left button was a menu not recent apps button. Which button number is for recents?
Click to expand...
Click to collapse
I just did this myself. I made the same mistake as you did, such that the recent key/button was still operational. I then realized that it's not a menu button, but it's an app switcher function, hence "recent". Under "# samsung", there should be "key 254 APP_SWITCH". That's the one to disable the app switcher key or "recents" button.
Hope this helps out anyone out there looking for this.
How do I get to this coding
hoang51 said:
I just did this myself. I made the same mistake as you did, such that the recent key/button was still operational. I then realized that it's not a menu button, but it's an app switcher function, hence "recent". Under "# samsung", there should be "key 254 APP_SWITCH". That's the one to disable the app switcher key or "recents" button.
Hope this helps out anyone out there looking for this.
Click to expand...
Click to collapse
hi, sorry for bother you but can you tell me how to do that? my recent apps key is always pressing and i go in holidays so i don t have time to take the phone to warranty.. can i perform that without root? thank you
macgaitas said:
hi, sorry for bother you but can you tell me how to do that? my recent apps key is always pressing and i go in holidays so i don t have time to take the phone to warranty.. can i perform that without root? thank you
Click to expand...
Click to collapse
To disable the capacitive button , you need root.
Rakcoon said:
To disable the capacitive button , you need root.
Click to expand...
Click to collapse
Thank you for your answer. the phone is three months old and already got a problem ..Basically is unusable the recent tab is always pop up..
macgaitas said:
Thank you for your answer. the phone is three months old and already got a problem ..Basically is unusable the recent tab is always pop up..
Click to expand...
Click to collapse
Dont root the phone. Take it to samsung for warranty claim when you get a chance.
They should be held accountable for the defect. Good luck.
macgaitas said:
Thank you for your answer. the phone is three months old and already got a problem ..Basically is unusable the recent tab is always pop up..
Click to expand...
Click to collapse
Rakcoon said:
Dont root the phone. Take it to samsung for warranty claim when you get a chance.
They should be held accountable for the defect. Good luck.
Click to expand...
Click to collapse
Just to verify, do you have any type of case on the phone, and if so, does the button do the same thing if you remove the case.
Otherwise, Rakcoon is correct. They should fix it under warranty.
THe best way to do is, add: qemu.hw.mainkeys=0 in build.prop, reboot and done.
There is another way to do is: Disable the hardware/back keys through: /system/usr/keylayout/Generic.kl and add # in front of key 139 menu and key 158. Also add the same to key 254 APP_SWITCH
Hope this helps..
vdbhb59 said:
THe best way to do is, add: qemu.hw.mainkeys=0 in build.prop, reboot and done.
There is another way to do is: Disable the hardware/back keys through: /system/usr/keylayout/Generic.kl and add # in front of key 139 menu and key 158. Also add the same to key 254 APP_SWITCH
Hope this helps..
Click to expand...
Click to collapse
Thanks to the above listing, I was in the middle of factory resetting my Samsung S6 back to stock (but still rooted) and my physical keys (app switcher and back buttons) wasn't working. I had to go in build.prop and generic.kl and reset them back to default values (e.g., put 1 for the mainkeys value and remove # in front of 158 and 254). Now the physical keys are working.
I font know
hoang51 said:
Thanks to the above listing, I was in the middle of factory resetting my Samsung S6 back to stock (but still rooted) and my physical keys (app switcher and back buttons) wasn't working. I had to go in build.prop and generic.kl and reset them back to default values (e.g., put 1 for the mainkeys value and remove # in front of 158 and 254). Now the physical keys are working.
Click to expand...
Click to collapse
You are always welcome mate.
If you want to disable the recent button all you have to do is download all in on gesture. There you can disable any button.
i cant find any of these places where the text is used to block these buttons.. build.prop? system-usr??? what do these even mean