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
Related
A number of users have been wanting to swap their menu and back softkeys... I believe it's handy for left-handed people who have smaller hands and can't reach the opposite button. So here's how you do it
1) Root phone
2) Using a root file explorer, navigate to /system/usr/keylayout.
3) Open the file Generic.kl
4) Make the following change:
LOCATE line
Code:
# key 139 MENU WAKE_DROPPED"
REPLACE with
Code:
# key 158 MENU WAKE_DROPPED"
LOCATE line
Code:
# key 158 BACK WAKE_DROPPED"
REPLACE with
Code:
# key 139 BACK WAKE_DROPPED"
Save the file Generic.kl, and reboot the phone. Your buttons are now swapped.
I have not provided an "update.zip" to do this, because lately far too many people are relying on one-click methods, and don't know how to make changes themselves, and "devs" don't document these methods for future. So please don't go making a flashable zip and posting it...
Thank You!!!
WOW
Been looking for this for along time, especially coming from Gnex the back soft key was on the laft side. There is also the size of the Note2, make it easier to work with the left hand only.
Thanks, W
pulser_g2 said:
A number of users have been wanting to swap their menu and back softkeys... I believe it's handy for left-handed people who have smaller hands and can't reach the opposite button. So here's how you do it
1) Root phone
2) Using a root file explorer, navigate to /system/usr/keylayout.
3) Open the file Generic.kl
4) Make the following change:
LOCATE line
Code:
# key 139 MENU WAKE_DROPPED"
REPLACE with
Code:
# key 158 MENU WAKE_DROPPED"
LOCATE line
Code:
# key 158 BACK WAKE_DROPPED"
REPLACE with
Code:
# key 139 BACK WAKE_DROPPED"
Save the file Generic.kl, and reboot the phone. Your buttons are now swapped.
I have not provided an "update.zip" to do this, because lately far too many people are relying on one-click methods, and don't know how to make changes themselves, and "devs" don't document these methods for future. So please don't go making a flashable zip and posting it...
Click to expand...
Click to collapse
Thank you! I was wondering if there was also a way to swap it for the on screen nav menu?
Sent from my Note 2
BigE-evo said:
Thank you! I was wondering if there was also a way to swap it for the on screen nav menu?
Sent from my Note 2
Click to expand...
Click to collapse
You mean you want on-screen navigation buttons, nexus style?
pulser_g2 said:
You mean you want on-screen navigation buttons, nexus style?
Click to expand...
Click to collapse
I am looking for a way to make the menu button persistent and also add a search button... can anyone help with that?
Thanks
Sent from my Galaxy Note II on Rogers Wireless
is this right? 3 menus and one back? i don't need a second back anywhere?
Sent from my SPH-L900 using xda app-developers app
wlpywd said:
is this right? 3 menus and one back? i don't need a second back anywhere?
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Well spotted, I've fixed that. You are basically swapping the numbers of menu and back, but I had a typo in it. The version in the thread is now correct.
I honestly think it's the right handed people who mostly hold their phones in their left hand. Thank you so much for this fix. I've been using button savior but this will be even better.
@Scott, if you want a customized buttons with more buttons, use button savior. You can customize size, location, number of buttons etc, here a pic. I have it setup where if i hit the trigger, the buttons will pop out and go away in 1 second. very convenient. But since I only need back button, this thread is a better way for me it seems.
@OP, Now that i have this setup, is there another line i can change to turn off the lights behind these button permanantly?
edit: nvm there was an option under display to turn those off
boodies said:
I honestly think it's the right handed people who mostly hold their phones in their left hand. Thank you so much for this fix. I've been using button savior but this will be even better.
@Scott, if you want a customized buttons with more buttons, use button savior. You can customize size, location, number of buttons etc, here a pic. I have it setup where if i hit the trigger, the buttons will pop out and go away in 1 second. very convenient. But since I only need back button, this thread is a better way for me it seems.
@OP, Now that i have this setup, is there another line i can change to turn off the lights behind these button permanantly?
edit: nvm there was an option under display to turn those off
Click to expand...
Click to collapse
Hmm interesting, I am right handed, and hold my phone in my right hand. I do admittedly have no problem reaching the far side of the screen with my thumb for typing etc...
If I'm not typing then I still hold it in my right hand, but from the centre, giving me a full reach across the whole phone...
But whether you're left or right handed doesn't matter... Fix is the same For anyone else looking for it, the lights on the buttons can be disabled in display settings.
is there a generic.kl tutorial thread somewhere? to learn how to customize everything? I'd like to modify some long press and double press functionality. Play around a bit.
the only, only, only thing i miss from the evo-lte coming to this phone is the dedicated hardware camera/search button on the side. i feel this note is just one physical button short. oh well.
Sent from my SPH-L900 using xda app-developers app
wlpywd said:
is there a generic.kl tutorial thread somewhere? to learn how to customize everything? I'd like to modify some long press and double press functionality. Play around a bit.
the only, only, only thing i miss from the evo-lte coming to this phone is the dedicated hardware camera/search button on the side. i feel this note is just one physical button short. oh well.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Why not just use "Swipe Pad" app & its just one finger action to camera button from any screen.
I'll look at swipe pad, but,i mainly used the button for search and long press for voice search. i rarely,rarely use the camera at all. the buttons at the bottom, physical buttons, could really have been 4 again on a phone this size. personal preference like the extra side button, that's all.
Sent from my SPH-L900 using xda app-developers app
Its the first app i install on a device, i use only the free version as its actually better kept simple & i only activate the 4 corners.
wlpywd said:
is there a generic.kl tutorial thread somewhere? to learn how to customize everything? I'd like to modify some long press and double press functionality. Play around a bit.
the only, only, only thing i miss from the evo-lte coming to this phone is the dedicated hardware camera/search button on the side. i feel this note is just one physical button short. oh well.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Double press - I don't think you can do this from generic.kl - you'd need to modify the framework where the buttons are received.
Possibly same for long presses, I'm not sure...
wlpywd said:
is there a generic.kl tutorial thread somewhere? to learn how to customize everything? I'd like to modify some long press and double press functionality. Play around a bit.
the only, only, only thing i miss from the evo-lte coming to this phone is the dedicated hardware camera/search button on the side. i feel this note is just one physical button short. oh well.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
http://source.android.com/tech/input/key-layout-files.html
http://www.thriveforums.org/forum/t...layout-any-usb-bluetooth-keyboard-rooted.html
boodies said:
http://source.android.com/tech/input/key-layout-files.html
http://www.thriveforums.org/forum/t...layout-any-usb-bluetooth-keyboard-rooted.html
Click to expand...
Click to collapse
you rock!!
Sent from my SPH-L900 using xda app-developers app
pulser_g2 said:
You mean you want on-screen navigation buttons, nexus style?
Click to expand...
Click to collapse
I would love to! On-screen touch buttons for Back at the left, home in the middle and multi-tasking windows list button at the right.
If you don't mind can you please share or point me to a link where I can get this?
srikat said:
I would love to! On-screen touch buttons for Back at the left, home in the middle and multi-tasking windows list button at the right.
If you don't mind can you please share or point me to a link where I can get this?
Click to expand...
Click to collapse
Try adding this to build.prop in /system :
qemu.hw.mainkeys=0
wlpywd said:
is there a generic.kl tutorial thread somewhere? to learn how to customize everything? I'd like to modify some long press and double press functionality. Play around a bit.
the only, only, only thing i miss from the evo-lte coming to this phone is the dedicated hardware camera/search button on the side. i feel this note is just one physical button short. oh well.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Did you try long pressing the menu button?
Looked around and didn't see this being brought up. Is there away to out the multitasking app instead of the menu button and bring back the 3 dot menu button back in apps? Hate freaking menu buttons and having to long press the home.
I remember figuring out a way to add software nav buttons on an S4 manually by editing some lines in the system but since the soft nav bar is already present I don't think that would work. Any ideas? Thanks.
Sent from my LG-D800 using Tapatalk 4
Root, and there's a few nav bar replacements in the play store that autohide as well.
Sent from my LG-D800 using Tapatalk 4
saywhat4118 said:
Looked around and didn't see this being brought up. Is there away to out the multitasking app instead of the menu button and bring back the 3 dot menu button back in apps? Hate freaking menu buttons and having to long press the home.
I remember figuring out a way to add software nav buttons on an S4 manually by editing some lines in the system but since the soft nav bar is already present I don't think that would work. Any ideas? Thanks.
Sent from my LG-D800 using Tapatalk 4
Click to expand...
Click to collapse
I'm with you, I think its stupid to have a dedicated menu button when android already has this covered.
The apps the poster above is speaking of does not fix this issue as it also hides the buttons, which is just dumb. Just be patient, I'm sure we will have a fix soon!
Sent from my Nexus 7 using Tapatalk 2
This may be my only gripe about this phone, I have tried several of the options, but you have to hide it or tour home screen icons in the dock get lost.
Sent from my LG-D800 using Tapatalk 4
While using the Note 2 I was able to go to the (root) system file and mess with the nav bar. Im going to play with this in a few. I'll report back.
jmill75 said:
While using the Note 2 I was able to go to the (root) system file and mess with the nav bar. Im going to play with this in a few. I'll report back.
Click to expand...
Click to collapse
With the S4 I was able to manually add the On screen nav buttons with a line of code. Default android soft buttons are back home and multitask LG edited that to the menu button which is annoying. Let me know what you find. I'm going to try some stuff my self
Sent from my LG-D800 using Tapatalk 4
While I would like to have a dedicated multitasking button, I don't think the menu button is a waste or stupid. There are still numerous apps that don't adhere to Google's new rules for a software menu button and they result in a black bar on the screen. LG dodged this by adding a dedicated software menu button. If you want to see how annoying it is, just pick up an HTC One (or DNA, or One X) and it will make more sense. What they did is emulate the Optimus G Pro (and Samsung's Touchwiz) with software buttons to give the same feel (hold home for multitasking, back and menu). I see why they did it. But yeah, it would be nice if they'd add an option for a multitasking button as either a fourth option or in place of the menu. It would certainly make more sense than the notification shade toggle.
greyhulk said:
While I would like to have a dedicated multitasking button, I don't think the menu button is a waste or stupid. There are still numerous apps that don't adhere to Google's new rules for a software menu button and they result in a black bar on the screen. LG dodged this by adding a dedicated software menu button. If you want to see how annoying it is, just pick up an HTC One (or DNA, or One X) and it will make more sense. What they did is emulate the Optimus G Pro (and Samsung's Touchwiz) with software buttons to give the same feel (hold home for multitasking, back and menu). I see why they did it. But yeah, it would be nice if they'd add an option for a multitasking button as either a fourth option or in place of the menu. It would certainly make more sense than the notification shade toggle.
Click to expand...
Click to collapse
The main reason I did not get the One was because of the stupid buttons. First not on screen and second only 2 buttons.
I do think it will only be a matter of time until someone makes a zip to add the recent button back. Wish I knew how
saywhat4118 said:
Looked around and didn't see this being brought up. Is there away to out the multitasking app instead of the menu button and bring back the 3 dot menu button back in apps? Hate freaking menu buttons and having to long press the home.
I remember figuring out a way to add software nav buttons on an S4 manually by editing some lines in the system but since the soft nav bar is already present I don't think that would work. Any ideas? Thanks.
Sent from my LG-D800 using Tapatalk 4
Click to expand...
Click to collapse
So my solution to this after 2 days of fiddling with the phone and trying EVERYTHING actually turned out for the better. The setup I have is using GMD gesture control for my buttons and auto hide navbar to have the navbar gone. This app let's you slide certain regions of the screen and trigger different conditions. I have no buttons at all on my screen and have slide functions that work perfect exactly where the Normal buttons would go. Slide up on the left is menu, slide in middle is home, and slide in right is recent apps. My back button is set by my thumb and it works out much better than I could have hoped.
kurofox23? said:
So my solution to this after 2 days of fiddling with the phone and trying EVERYTHING actually turned out for the better. The setup I have is using GMD gesture control for my buttons and auto hide navbar to have the navbar gone. This app let's you slide certain regions of the screen and trigger different conditions. I have no buttons at all on my screen and have slide functions that work perfect exactly where the Normal buttons would go. Slide up on the left is menu, slide in middle is home, and slide in right is recent apps. My back button is set by my thumb and it works out much better than I could have hoped.
Click to expand...
Click to collapse
Thanks I'm going to try this.
Sent from my LG-D800 using Tapatalk 4
Apps that have their own 3-dot menu
Thanks for the research on this topic. Does anyone know if the GMD app allows an app to retain its 3-dot menu functionality? I've encountered several apps that won't work with the G2's menu softkey preventing you from accessing the app's options.
thanks in advance!
I have rooted my Note 3 and remapped the navigation buttons to match the galaxy nexus I came from. Now that I don't have the menu button is there a way (maybe in the build.prop) to enable the onscreen menu button? If not is there a way to enable all onscreen navigation buttons for the note 3? I tried the "qemu.hw.mainkeys=0" approach but it caused system ui to crash. Thanks.
Looking for this as well. Got the same UI crash when adding that kind.
Why would you want to when we have hardware buttons?
Sent from my SM-N900V using Tapatalk now Free
Gvaz said:
Why would you want to when we have hardware buttons?
Click to expand...
Click to collapse
I remapped my hardware buttons to match my galaxy nexus onscreen buttons (from left to right: Back, Home, Recent Apps). As you can see I don't have a menu button mapped. A lot of apps have the menu button in the UI but it doesn't show up if your device thinks it has a hardware menu button. So what I am looking for is a way to tell android that I do not have a hardware menu button. Thanks.
could you keep us updated if you find anything? could you make a quick tutorial how you were able to remap the buttons, or does it work exactly like on the s3:
http://forum.xda-developers.com/showthread.php?p=34848407
smoothjeff said:
could you keep us updated if you find anything? could you make a quick tutorial how you were able to remap the buttons, or does it work exactly like on the s3:
http://forum.xda-developers.com/showthread.php?p=34848407
Click to expand...
Click to collapse
Yes it looks like it is exactly the same. Wish I could have found that guide when I was searching lol.
Do the correct icons appear to the right and left of the home button with this mod?
chhaggerty said:
Do the correct icons appear to the right and left of the home button with this mod?
Click to expand...
Click to collapse
Unfortunately not. I just turned the touch key lights off in display settings.
Has anyone figured this out yet?
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
I'm running the CM 13 alpha, and I have the soft nav keys enabled, but I can't for the life of me find out how to turn off the capacitive buttons (I keep hitting them while trying to read and have the device in portrait).
I've tried modifying a few of the key layout files (/system/usr/keylayout) but no avail... I did manage to disable the home button lol.
Any ideas?
Edit: Ah of course... it was /system/usr/keylayout/sec_touchscreen.kl, who would've thought! For anyone looking to do this, just edit this file and add #'s in front of the values.