I've seen a lot of complaints that the Note 8.0 is more a big Note II than a small Note 10.1
(mainly the fact that it has the capacitive buttons setup)
This works on the Note II, so hopefully someone can try this out on their Note 8.0
I'm waiting for mine to get shipped to me, but I'll update after I test it (unless someone gets to it first.)
To disable the capacitive buttons:
Root your Note. Get a file explorer that can use the root to edit system files. Go to system/usr/keylayout and open generic.kl with a text editor, find keys 158 and 139 and put a "#" sign in front of both. Save the file and reboot phone. Then go to settings and disable the light.
Then you can add software keys by editing your build.prop file.
Add the following line to the end with root explorer and reboot.
qemu.hw.mainkeys=0
or change the dpi, as discussed here:
http://forum.xda-developers.com/forumdisplay.php?f=2245
kisaten said:
I've seen a lot of complaints that the Note 8.0 is more a big Note II than a small Note 10.1
(mainly the fact that it has the capacitive buttons setup)
This works on the Note II, so hopefully someone can try this out on their Note 8.0
I'm waiting for mine to get shipped to me, but I'll update after I test it (unless someone gets to it first.)
To disable the capacitive buttons:
Root your Note. Get a file explorer that can use the root to edit system files. Go to system/usr/keylayout and open generic.kl with a text editor, find keys 158 and 139 and put a "#" sign in front of both. Save the file and reboot phone. Then go to settings and disable the light.
Then you can add software keys by editing your build.prop file.
Add the following line to the end with root explorer and reboot.
qemu.hw.mainkeys=0
or change the dpi, as discussed here:
http://forum.xda-developers.com/forumdisplay.php?f=2245
Click to expand...
Click to collapse
well the first step only makes the haptic feedback stop. The keys still work. But the build.prop edit works for the onscreen keys
how about change the following line in build.prop?
ro.build.characteristics=tablet
mingkee said:
how about change the following line in build.prop?
ro.build.characteristics=tablet
Click to expand...
Click to collapse
That line is already in there in the build.prop.
It's weird... this seems to work at first, as the menu capacitive key doesn't work on the home screen, but then works in apps - same scenario on the capacitive back key. And even more odd, on the newly "added" on-screen keys, the back key does nothing in any situation.
I honestly don't understand the desire for onscreen buttons as opposed to the capacitive/hardware buttons under the screen. I hated those software buttons on my Nexus 10 and removed the bar entirely to give myself the extra screen space (And gestures to make up for the lack of buttons). Just a waste of screen space in my opinion. I wish Android tablets had what the iPad uses (Four finger gestures for switching apps and returning home) rather than taking up the screen. (GMD Gesture works quite well, but not as iPad seamless yet).
To each their own though, just my opinion. The capacitive buttons are already there, why disable them and put the buttons on the screen.
NickTheMajin said:
I honestly don't understand the desire for onscreen buttons as opposed to the capacitive/hardware buttons under the screen. I hated those software buttons on my Nexus 10 and removed the bar entirely to give myself the extra screen space (And gestures to make up for the lack of buttons). Just a waste of screen space in my opinion. I wish Android tablets had what the iPad uses (Four finger gestures for switching apps and returning home) rather than taking up the screen. (GMD Gesture works quite well, but not as iPad seamless yet).
To each their own though, just my opinion. The capacitive buttons are already there, why disable them and put the buttons on the screen.
Click to expand...
Click to collapse
I agree with you, but I think some people are having problems brushing up against the capacitive buttons while holding it in landscape, like while watching a movie for example.
jntdroid said:
I agree with you, but I think some people are having problems brushing up against the capacitive buttons while holding it in landscape, like while watching a movie for example.
Click to expand...
Click to collapse
To each their own. It is certainly personal preference but I think anyone with that problem should look into GMD Gesture control rather than adding the navigation bar. You're just lowering the amount of screen realestate you have to work with. GMD Gesture Control works surprisingly well.
I changed (added a # in front of the entries) the melfas-touchkey.kl and sec_touchkey.kl files in system/usr/keylayout
(then turned off the lights and vibrate in settings)
But this was on my Note (N7000) and it seems to disable the buttons after a restart.
Anyone want to take a shot at that?
(Still waiting for my N5110 to get shipped here (a friend is sending one to me since I'm living in Japan atm)
I use Button Savior (so the bar auto hides) for now, but I'm looking for a solution that's similar to what I had on my TF101 Transformer:
I was running Revolver firmware on the TF101 and it let me hide the softkeys for home/back/menu. Then you'd longpress the power button to access the functions/bring them back.
GMD gesture control looks like it'd work really well if we can get the capacitive buttons to disable
GMD spen control might be good too for people (like me) who use the pen a lot.
It's still a great tablet either way!
I've not purchased my Note 8.0 yet, but this is a concern for me. Not sure what my ideal solition would be though. By reverting back to the onscreen buttons, your eating in to the screen real estate. I though about the option of making the buttons s pen enabled only, but that would be frustrating having to take the s pen out just to use them. The option to use the power button or on screen gesture to enable/ disable the buttons sounds like it might be the best possibility. How viable that is as an option, I'm not sure...
Y'know this wouldn't be a huge issue for me if Adobe allowed Photoshop Touch to be rotated 180 degrees. But here we are.
I was planning on using LMT pie controls to use the device but still want to disable the capacitive buttons. Also, while we're on the subject, does anyone else's home button get stuck?
Sent from my GT-N5110 using Tapatalk HD
Div033 said:
Also, while we're on the subject, does anyone else's home button get stuck?
Sent from my GT-N5110 using Tapatalk HD
Click to expand...
Click to collapse
No - if yours is, you should definitely return it or swap it out.
I'm not so much worried about turning off the capacitive keys until the nav bar is fully functioning.
Ok, aside from the "nav bar good/bad" debate, here's where we are with this...
The qemu.hw.mainkeys=0 edit in the buildprop does enable the nav bar like on the Note 2, but the buttons are a little funky. This is what you get:
Recents
short and long press you will get recents.
Home
short- Home
long- pulls up nav ring and recents almost simultaneously.
Back
short- back
long- multiwindow
There's also an ^ key on the right that does nothing. I'm gonna try to see what I can do to get these buttons working somewhat properly. Mainly replace recents with menu.
I've got some experience with it from my brief Note 2 days, which is probably a good forum to look through for mods like this. I'm thinking a lot of it applies being so similar.
Yes please! I just want some consistency with my note 8.0 and my nexus 4. When I go back to the nexus 4 I am looking for hardware buttons or pressing them harder. Heh.
Disabled capactive keys achieved
kisaten said:
I've seen a lot of complaints that the Note 8.0 is more a big Note II than a small Note 10.1
(mainly the fact that it has the capacitive buttons setup)
This works on the Note II, so hopefully someone can try this out on their Note 8.0
I'm waiting for mine to get shipped to me, but I'll update after I test it (unless someone gets to it first.)
To disable the capacitive buttons:
Root your Note. Get a file explorer that can use the root to edit system files. Go to system/usr/keylayout and open generic.kl with a text editor, find keys 158 and 139 and put a "#" sign in front of both. Save the file and reboot phone. Then go to settings and disable the light.
Then you can add software keys by editing your build.prop file.
Add the following line to the end with root explorer and reboot.
qemu.hw.mainkeys=0
or change the dpi, as discussed here:
http://forum.xda-developers.com/forumdisplay.php?f=2245
Click to expand...
Click to collapse
I have achieved the ability to disable the capacitive keys with finger touch but keep the s-pen capable of using the capacitive keys. Here is how(Do this at your own peril, I take no responsibility):
Using root explorer or a root file editor navigate to /system/usr/keylayout
You will see many files but the two we are interested in is Generic.kl and sec_touchscreen.kl
First open Generic.kl and comment out lines 139 and 158. Do this by placing a # sign in front of the specified lines.
Save and Exit the file then open sec_touchscreen.kl
Comment out lines 139 and 158 by placing the # in front of the specified lines, Save and Exit.
Reboot tablet.
Capacitives are now disabled with finger touch, but still usable with the s-pen. You can also disable the capacitive light under your settings>display if you so choose.
I put a guide in the Note 8 Developer forum here:
http://forum.xda-developers.com/showthread.php?t=2250941
Did this:
kisaten said:
Then you can add software keys by editing your build.prop file.
Add the following line to the end with root explorer and reboot.
qemu.hw.mainkeys=0
http://forum.xda-developers.com/forumdisplay.php?f=2245
Click to expand...
Click to collapse
And this:
ual4720 said:
I have achieved the ability to disable the capacitive keys with finger touch but keep the s-pen capable of using the capacitive keys. Here is how(Do this at your own peril, I take no responsibility):
Using root explorer or a root file editor navigate to /system/usr/keylayout
You will see many files but the two we are interested in is Generic.kl and sec_touchscreen.kl
First open Generic.kl and comment out lines 139 and 158. Do this by placing a # sign in front of the specified lines.
Save and Exit the file then open sec_touchscreen.kl
Comment out lines 139 and 158 by placing the # in front of the specified lines, Save and Exit.
Reboot tablet.
Capacitives are now disabled with finger touch, but still usable with the s-pen. You can also disable the capacitive light under your settings>display if you so choose.
I put a guide in the Note 8 Developer forum here:
http://forum.xda-developers.com/showthread.php?t=2250941
Click to expand...
Click to collapse
Golden. :victory: Thanks both.
Edit: Back doesn't seem to work all the time, anyone else? Hit or miss... doesn't work, most of the time
slopokdave said:
Did this:
And this:
Golden. :victory: Thanks both.
Edit: Back doesn't seem to work all the time, anyone else?
Click to expand...
Click to collapse
I haven't had any issues so far. hitting the back with the s-pen works every time; however,I have noticed that sometimes the s-pen won't recognize my stroke because the tip of the pen doesn't depress all the way! Mostly when I have to much of an angle on the pen.
Sent from my GT-N5110 using Tapatalk HD
ual4720 said:
I haven't had any issues so far. hitting the back with the s-pen works every time; however,I have noticed that sometimes the s-pen won't recognize my stroke because the tip of the pen doesn't depress all the way! Mostly when I have to much of an angle on the pen.
Sent from my GT-N5110 using Tapatalk HD
Click to expand...
Click to collapse
Yes, it works with my s-pen all the time too; both software and capactive keys. It's with my finger, on the on-screen software keys, that it doesn't work most of the time. Try it.
slopokdave said:
Yes, it works with my s-pen all the time too; both software and capactive keys. It's with my finger, on the on-screen software keys, that it doesn't work most of the time. Try it.
Click to expand...
Click to collapse
I see what you mean! I'm trying to find the reason!
Sent from my GT-N5110 using Tapatalk HD
ual4720 said:
I see what you mean! I'm trying to find the reason!
Sent from my GT-N5110 using Tapatalk HD
Click to expand...
Click to collapse
Bingo. Strange eh. I'll keep looking too.
Sent from my GT-N5110 using Tapatalk HD
So I found it really annoying when watching Netflix and accidentally hitting back or recent apps softkeys. Which pauses or exits out of movie everytime I do. Because of placement of soft keys (Navigation buttons) on Galaxy Tab Pro 8.4. (Which is where I hold the tab in landscape)
So I found a way to disable back/ recent apps and Home buttons. Temporarily
Settings /Device /Accessibility
Scroll to very bottom
Enable interaction control
Use volume down and home at same time to enable
Uncheck all checkboxes
Now soft keys (Navigation buttons) and home are disabled.
Usefully when watching a movie and holding with your hand on softkeys.
(Have to disable multi window to enable this feature)
If helped, thanks would be appreciated.
trevor7428 said:
So I found it really annoying when watching Netflix and accidentally hitting back or recent apps softkeys. Which pauses or exits out of movie everytime I do. Because of placement of soft keys (Navigation buttons) on Galaxy Tab Pro 8.4. (Which is where I hold the tab in landscape)
So I found a way to disable back/ recent apps and Home buttons. Temporarily
Settings /Device /Accessibility
Scroll to very bottom
Enable interaction control
Use volume down and home at same time to enable
Uncheck all checkboxes
Now soft keys (Navigation buttons) and home are disabled.
Usefully when watching a movie and holding with your hand on softkeys.
(Have to disable multi window to enable this feature)
If helped, thanks would be appreciated.
Click to expand...
Click to collapse
I tried to do this on the demo units in Best Buy but I couldn't get it to work. Could it be the demo software they had on it?
dimcorner said:
I tried to do this on the demo units in Best Buy but I couldn't get it to work. Could it be the demo software they had on it?
Click to expand...
Click to collapse
Possibly idk? Works on mine. Sometimes tablets/ TV have a retail firmware on them which isn't the same as what you take home. So could be possible
This worked for me.
http://brandtkrueger.wordpress.com/...ation-buttons-on-the-galaxy-s3-requires-root/
Home key had to be disabled in both of the below locations. This completely disables the hardware keys so make sure to enable the on screen keys first.
Note: The onscreen keys don't show up in landscape mode for some reason so I use LMT launcher for the few times I need navigation keys in landscape.
Generic.kl
gpio-keys.kl
Sent from my SM-T320 using xda app-developers app
kirbo20 said:
This worked for me.
http://brandtkrueger.wordpress.com/...ation-buttons-on-the-galaxy-s3-requires-root/
Home key had to be disabled in both of the below locations. This completely disables the hardware keys so make sure to enable the on screen keys first.
Note: The onscreen keys don't show up in landscape mode for some reason so I use LMT launcher for the few times I need navigation keys in landscape.
Generic.kl
gpio-keys.kl
Sent from my SM-T320 using xda app-developers app
Click to expand...
Click to collapse
Does anyone know how to disable the back light on the capacitive keys? I've been able to disable the buttons from functioning and I've got LMT launcher installed but I'd really like to stop them from lighting up if possible.
The only thing that stops me from buying the tab pro 8.4 at the moment are the hardware keys. I am used to on screen buttons and as I can see in some review-videos and as some of you already mentioned, if you hold the tablet in landscape you could accidentally come in touch with the capacitive keys or the home button. Therefore I am very interested in how you can handle the tab pro 8.4 with hardware-keys disabled and on screen keys enabled. Can anyone share some screenshots how it looks like?
kirbo20 said:
Note: The onscreen keys don't show up in landscape mode for some reason so I use LMT launcher for the few times I need navigation keys in landscape.
Click to expand...
Click to collapse
So at the moment there is no way to have googles on screen buttons in landscape mode?
I use xposed additions to remap buttons from single click to long press on my son's 8.4 since he kept accidentally hitting buttons and getting frustrated. Not exactly what you are looking for but it has helped us here. Take a look at button Savior on the play store as well. You could use xposed additions to disable buttons and then use button Savior buttons.
Sent from my Galaxy Note Pro 12 using Tapatalk
Hallo, the new Recent Apps button is annoying me. So i tried to rebind the button to menu. This worked. I changed the /system/usr/keylayout/Generic.kl. (Swapped key 254 (APP_SWITCH) and key 127 (MENU). But I don't know how to rebind the APP-SWITCH key to the hold home key, wich brings me to Google Now. Google Now would be nice on hold MENU, but if I hold the changed button S Finder appears.. I don't need it. So could you tell me, how to bind APP-SWITCH to hold HOME, and Google Now to hold MENU please?
The change I made was inspired by this thread: http://forum.xda-developers.com/showthread.php?t=2337229
Thanks, Colin P
You can use the xposed framwork additions module to remap hardware keys. Or any number of other Play store apps will also endeavor to do so for you.
Or you could directly edit the the /system/usr/keylayout files. As you aren't already doing this though, I can only presume that you aren't familiar with the syntax. In which case, xposed will be your best option.
.
I have a question that involves keylayout, since this is a similar thread, I thought I should ask here. I've added on-screen navigation buttons, and want to disable the soft touch keys (I accidentally press them a lot...). I found out through a Note 2 forum that I need to put a # sign in front of keys 158 and 139, but I think it might be different for Galaxy S5. Can someone help me disable the two soft touch keys (back and recent apps keys). Thanks a lot
You should start your own thread, rather than hijack an existing one.
In short, you can either use an app like Xposed to reassign the keys or edit the keylayout files directly. Simply leave the keys in question unassigned. If you find that the keys still light up, that can be disabled in the Settings menu with the touch key duration setting = always off.
.
Is there a ROM that uses soft Home & navigation keys instead of capacitative keys?
I have a Verizon S4 that I have been using on Tmobile (No LTE, just 3/4G).
I recently dropped in water and the hard home button and both capacitative buttons don't work anymore. Everything else works fine (for now).
Is there a ROM I can flash which has soft home and navigation keys on the screen instead of using the hard home buttons and capacitative navigation keys?
It would be a bonus if this ROM will let me use LTE on Tmobile.
I am on stock 5.01 but it is rooted (not sure if it's unlocked but I think I can do that).
Those can be enabled on any ROM. Soft keys are a part of Android, so they are available on any phone running Android. They are simply disabled on devices with hardware buttons.
You have edit the build.prop and add a certain line if I'm not mistaken.
Code:
qemu.hw.mainkeys=0
Save, reboot. You should, in theory, have soft keys after the reboot.
Pwnycorn said:
Those can be enabled on any ROM. Soft keys are a part of Android, so they are available on any phone running Android. They are simply disabled on devices with hardware buttons.
You have edit the build.prop and add a certain line if I'm not mistaken.
Code:
qemu.hw.mainkeys=0
Save, reboot. You should, in theory, have soft keys after the reboot.
Click to expand...
Click to collapse
Can you remind me where to find the build.prop?
superflysocal said:
Can you remind me where to find the build.prop?
Click to expand...
Click to collapse
It's in system.
This is an answer you could've gotten by googling it and you wouldn't have had to wait for my response. So you effectively just wasted time.