On previous phones including the S5 you could just change the build.prop or use gravity box to add them but every time I try on reboot I get system UI crashing non stop until I undo my changes.
Has anyone gotten them somehow?
What about the side key panel?
Sent from my SM-N910C using XDA Free mobile app
That's in the way and inconvenient. They should have just added pie
Use Xposed and install GravityBox and use Navigation Bar Tweak feature
pcboyy said:
Use Xposed and install GravityBox and use Navigation Bar Tweak feature
Click to expand...
Click to collapse
It doesn't work. My post says that It doesn't.
zgroten said:
It doesn't work. My post says that It doesn't.
Click to expand...
Click to collapse
Had same issue. Use dynamic navbar on playstore or lmt pie. I went for dynamic navbar it's amazing and can be customised to your absolute liking.
I've installed dynamic Navbar but can't seem to figure out how to make it work like a regular Navbar and not sit on top of items on the screen.
I am using lmt pie...loving it
Sent from my SM-N910C using Tapatalk
Nobody can get regular softkeys without system UI crashing?
nope, seems like there's some piece of code missing, so that every time you activate those softkeys it just bootloops. have tried a number of methods, haven't found one that works. missing that soft home button (
eydryan said:
nope, seems like there's some piece of code missing, so that every time you activate those softkeys it just bootloops. have tried a number of methods, haven't found one that works. missing that soft home button (
Click to expand...
Click to collapse
This is a shame. I figured this would be one of the first mods due to the popularity and convenience of on-screen buttons. The bezel on the Note 4 is so small at the bottom that it wouldn't even look like a waste of space to have a navigation bar. The capacitive buttons are so easily pressed due to the small bezel. I don't mind this, but I wish the option for on-screen was included by samsung. I also hate the "back" button on the right side because I'm left-handed and can't reach it with my dominant hand. That should be reversible as well. Is that possible?
I also recommend lmt. The back button is instant.
whittikins said:
but I wish the option for on-screen was included by samsung. I also hate the "back" button on the right side because I'm left-handed and can't reach it with my dominant hand. That should be reversible as well. Is that possible?
Click to expand...
Click to collapse
If device is rooted then you can remap back and menu key by editing generic.kl
Sent from my SM-N910G using xda premium
dr.ketan said:
If device is rooted then you can remap back and menu key by editing generic.kl
Sent from my SM-N910G using xda premium
Click to expand...
Click to collapse
Did exactly that as soon as I got it. Although I actually prefer back key on right, just find note too wide to reach across, being left handed. Turned off the key light, not to cause confusion, and I guess it took a day to train muscle memory.
Sent from my SM-N910W8
dr.ketan said:
If device is rooted then you can remap back and menu key by editing generic.kl
Sent from my SM-N910G using xda premium
Click to expand...
Click to collapse
Ah, thanks! What would I change to simply disable the Recent and Back keys completely? I have on screen keys now. I still want to keep the home button because I don't accidentally press it.
Actually, I just put a # in front of the line for app_switcher, which worked. What do I change or remove to disable the capacitive Back hardware key? Thanks!
EDIT: figured it out!
To disable the Recent and Back hardware keys (capacitive buttons), edit /system/usr/keylayout/Generic.kl and put a # in front of these 2 lines:
key 158 BACK
key 254 APP_SWITCH
Save and reboot!
whittikins said:
Ah, thanks! What would I change to simply disable the Recent and Back keys completely? I have on screen keys now. I still want to keep the home button because I don't accidentally press it.
Actually, I just put a # in front of the line for app_switcher, which worked. What do I change or remove to disable the capacitive Back hardware key? Thanks!
EDIT: figured it out!
To disable the Recent and Back hardware keys (capacitive buttons), edit /system/usr/keylayout/Generic.kl and put a # in front of these 2 lines:
key 158 BACK
key 254 APP_SWITCH
Save and reboot!
Click to expand...
Click to collapse
That's very useful!:good:
marvi0 said:
Had same issue. Use dynamic navbar on playstore or lmt pie. I went for dynamic navbar it's amazing and can be customised to your absolute liking.
Click to expand...
Click to collapse
What is this lmt pie?
kopkiwi said:
What is this lmt pie?
Click to expand...
Click to collapse
It's an amazing app here in xda developed by a recognized member that adds pie control to your phone
drmodify said:
It's an amazing app here in xda developed by a recognized member that adds pie control to your phone
Click to expand...
Click to collapse
The only thing about let and pie control in general is that it auto dissappear. When multiple back key is required, it is a pain.
Which is why I have resorted to using side key panel when I don't want to use capacitive. I edited settings database to add transparency to side panel menu as well as having a hint bar dissappear. I moved it to the comfortable zone for my thumb, and trigger it without fail. It says on till I press outside of the side menu.
It is working great for me. Although I would rather have standard nav bar for purely visual reasons as well as more modding options.
Sent from my SM-N910W8
I too am a lover of a static nav bar on my Galaxy Devices.
I now have a SM-N910P now and am frustrated as heck at not being able to get it functional here, on a rooted stock NK2. I used to run SlimKat 4.4.2 on my SPH-L710 and loved the navbar that they baked into the ROM. SlimLoli is maturing for the Note 4, but it doesn't yet have any S-Pen support baked in. This fact, when coupled with how well Samsung and Sprint have done with TouchWiz on the Note 4 have caused me to hold off on putting a custom ROM on the device.
So, what to do.?. Editing buildprop does indeed cause the looping system UI FC. UDN is an excellent solution barring one issue, and that it is doesn't have a means to dedicate a portion of the display to the nav bar. It just overlays on top of the launcher's/app's UIs. I'd be willing to pay for a solution that fixes this.
Pie controls have never really clicked with me. Not yet being willing to move away from NK2, I find that I am wondering if there is a way to force a portion of the bottom of the screen to be entirely dedicated to a specific app, all of the time. As depicted in this screeny, UDN overlays and it is frustrating as hell.
Anyone have any ideas yet?
-t
Related
I have got rid of the 3 dot menu bar which is easy(zip file posted). But trying to remap recent apps was a fail. When I try to remap recent to menu it would affect home button not working so in the zip is the file the original file to remap buttons if you want to take a look and see if anyone here can remap recent to menu. AND eventually me or someone else will figure out long press remaping.
As well I figured out using the GMD Gestures app from playstore, you can create your own gesture and set it to recent apps if you want.
FYI for the 3 dot menu bar removal it requires you to delete the build.prop via recovery file manager than flash. For some reason it wont replace the file. So delete than flash and same with the button remap file in the zip.
THE BUTTON REMAP IS JUST FOR PEOPLE WHO WANT TO LOOK AT THE FILE TO SEE IF THEY CAN FIX.
THE NO MENU FILE IS A FLASHABLE TO GET RID OF MENU BAR.
well to fix the files not being overwritten via the flashable i changed your updater-script to /dev/block/mmcblk0p32 vs /dev/block/mmcblk0p2 but also didn't have any luck on the mod working either..the first time it made my recents button basically do nothing my home button seem to just select things and then backed as usual.. and then i edited the .kl file thinking maybe since you had things things right next to eachother and not on each line it caused a error i just had the menu (3 dots) issue disappear but the recents key worked as usual.. maybe just user error.
lasphyxial said:
well to fix the files not being overwritten via the flashable i changed your updater-script to /dev/block/mmcblk0p32 vs /dev/block/mmcblk0p2 but also didn't have any luck on the mod working either..the first time it made my recents button basically do nothing my home button seem to just select things and then backed as usual.. and then i edited the .kl file thinking maybe since you had things things right next to eachother and not on each line it caused a error i just had the menu (3 dots) issue disappear but the recents key worked as usual.. maybe just user error.
Click to expand...
Click to collapse
So re-mapping DOES work if you edit the .kl file and fix the typo?
Argumentation said:
So re-mapping DOES work if you edit the .kl file and fix the typo?
Click to expand...
Click to collapse
no the remapping didn't work once i fixed the typo.. but it did remove the menu from the apps that show it on the bottom of the screen so it half worked..
lasphyxial said:
no the remapping didn't work once i fixed the typo.. but it did remove the menu from the apps that show it on the bottom of the screen so it half worked..
Click to expand...
Click to collapse
Ah, ok. :good: Also, did it break multitasking?
You might want to check with runandhide about long press remapping:
http://forum.xda-developers.com/showthread.php?t=1681034
He got this working on the evo lte by changing this code:
http://forum.xda-developers.com/showpost.php?p=26734996&postcount=3
I agree with you that the recent apps button should be menu on tap and recent apps on long press.
str8upx said:
You might want to check with runandhide about long press remapping: http://forum.xda-developers.com/showthread.php?t=1681034
He got this working on the evo lte.
Click to expand...
Click to collapse
I will pm him and see if he can help with long press.
He fixed long press on home but that is already google now which I like. I'm asking him about long press on recent key.
Actually the modified build.prop is what gets rid of 3 dot menu bar.
What's the reasoning behind making the recent apps button do menu upon tap and actually show recent apps upon long press? That seems logically backwards to me.
Maybe its just because I use the recent apps button more than any other, but it seems like it should be like it is stock and then upon long press show the menu. Isn't that how HTC did it officially on their update to the One?
Obviously its a matter of personal preference - glad to see someone working on this (thank you!) because that bar is driving me nuts haha.
thenickisme said:
What's the reasoning behind making the recent apps button do menu upon tap and actually show recent apps upon long press? That seems logically backwards to me.
Maybe its just because I use the recent apps button more than any other, but it seems like it should be like it is stock and then upon long press show the menu. Isn't that how HTC did it officially on their update to the One?
Obviously its a matter of personal preference - glad to see someone working on this (thank you!) because that bar is driving me nuts haha.
Click to expand...
Click to collapse
Yeah I like it more that way too
Sent from my HTC6435LVW using xda app-developers app
+1, I like it that way too.
Sent from my HTC6435LVW using xda premium
So if I flash this MOD ... will this just remove the annoying 3 dot menu on the bottom of my phone that comes up on all the screens/apps that I use.
Or am I going to lose the functionality of pressing recent apps, home, back?
whats this MOD do, as is..?
Thank you! I can't thank you enough!
Sent from my HTC Droid DNA
-4ndr01d- said:
So if I flash this MOD ... will this just remove the annoying 3 dot menu on the bottom of my phone that comes up on all the screens/apps that I use.
Or am I going to lose the functionality of pressing recent apps, home, back?
whats this MOD do, as is..?
Click to expand...
Click to collapse
Well since my zip file does not replace files then all you do is delete build.prop via recovery file manager and flash. It won't mess with capacitive buttons unless you deleted that file too but don't so only 3 dots will go away.
thenickisme said:
What's the reasoning behind making the recent apps button do menu upon tap and actually show recent apps upon long press? That seems logically backwards to me.
Maybe its just because I use the recent apps button more than any other, but it seems like it should be like it is stock and then upon long press show the menu. Isn't that how HTC did it officially on their update to the One?
Obviously its a matter of personal preference - glad to see someone working on this (thank you!) because that bar is driving me nuts haha.
Click to expand...
Click to collapse
Probably because you have had to long press for recent apps since android cupcake. Its natural.
So if I am following this thread correctly, this WILL completely remove the 3 dotted menu, HOWEVER, we have NO access to getting in to an app menu until the recent button can be remapped. Correct?
BFirebird101 said:
So if I am following this thread correctly, this WILL completely remove the 3 dotted menu, HOWEVER, we have NO access to getting in to an app menu until the recent button can be remapped. Correct?
Click to expand...
Click to collapse
yes or you can download GMD Gestures app from play store and set a gesture to menu. Thats what I do.
So like mentioned above, the 3 dot menu will be gone and capacitive buttons will work as normal?
and use the GMD gesture app to get into menus of applications?
can we revert this process if something happens. like replace the files it removes.
obviously in a ZIP bc we cant push them with root explorer yet
str8upx said:
Probably because you have had to long press for recent apps since android cupcake. Its natural.
Click to expand...
Click to collapse
But that was a long press of the home button correct? A lone button dedicated to recent apps functionality wasn't introduced until ICS. Considering the vast majority of general users(not us XDA types), I would argue that most people had never heard of the recent apps feature until el Goog stuffed it down everyone's throat when they shifted into the new 3 button system. I feel like that has become key to the operation of Android and considering the changes from 4.1 to 4.2 Google intends to keep it that way and build around it.
I know this is a mod that really isn't for the general public, but I feel like Google is a smart company. Just browse through their dev guidelines and you can see that they take every single detail into account and invest HEAVILY into finding the best way to operate Android. -I don't feel like this design change was a shot in the dark for them.
Of course, this would all be moot if HTC had decided they weren't 'too cool' for on-screens.
Sorry, ill get off my UX soapbox haha
So there is no 3 dot removal yet? Where does it place it to?
Not an iPhone.....
luke1333 said:
So there is no 3 dot removal yet? Where does it place it to?
Not an iPhone.....
Click to expand...
Click to collapse
There is. The mod I posted removes 3 dot but you need to delete build.prop via recovery file manager before flashing because it will flash a modified build.prop.
Also using GMD Gesture app for menu.
At Your Own Risk!!! I Am Not Responsible For Anything You Do To Your Device
So if you are like me you're tired of looking at the gaudy version of a nav bar and soft keys that amazon has come up with. So I started looking around for a way to modify the soft keys to look more like stock android. I may at some point dive into the framework and rewrite portions to do this, but in my search I came across an old method for removing the nav bar altogether. It is a very simple build.prop edit and at the same time adds some screen real-estate. I've confirmed this does work on this device, check out the screenshots below.
How to(rooted device):
1- You will first need a soft key/nav buttons app(once this is done the stock keys will be gone, and kinda hard to navigate without some). I like using Button Savior, it allows you to place the soft keys anywhere around the perimeter of the screen, and has multiple themes you can use. Also if you have the paid version you can change the number and position of buttons
2- Using a file manager navigate to /system/build.prop file
3- Open build.prop with a text editor, scroll to the end and on a new line enter:
Code:
qemu.hw.mainkeys=1
4- Save and reboot.
Now there are ways to do this with launchers but it will not be permanently removed and will still show up in apps.
To get stock keys back just delete the line you entered in the build.prop and reboot
Remove soft keys
onemeila said:
At Your Own Risk!!! I Am Not Responsible For Anything You Do To Your Device
So if you are like me you're tired of looking at the gaudy version of a nav bar and soft keys that amazon has come up with. So I started looking around for a way to modify the soft keys to look more like stock android. I may at some point dive into the framework and rewrite portions to do this, but in my search I came across an old method for removing the nav bar altogether. It is a very simple build.prop edit and at the same time adds some screen real-estate. I've confirmed this does work on this device, check out the screenshots below.
How to(rooted device):
1- You will first need a soft key/nav buttons app(once this is done the stock keys will be gone, and kinda hard to navigate without some). I like using Button Savior, it allows you to place the soft keys anywhere around the perimeter of the screen, and has multiple themes you can use. Also if you have the paid version you can change the number and position of buttons
2- Using a file manager navigate to /system/build.prop file
3- Open build.prop with a text editor, scroll to the end and on a new line enter:
Code:
qemu.hw.mainkeys=1
4- Save and reboot.
Now there are ways to do this with launchers but it will not be permanently removed and will still show up in apps.
To get stock keys back just delete the line you entered in the build.prop and reboot
Click to expand...
Click to collapse
Hello
Just wanted to say thanks for the above info. It all works great and the extra room on the screen is appreciated. By the way, I am using CM 10 rom on my RAZR M, and it works great there as well. Doesn't work perfectly on the stock RAZR M, although both soft keys and header info (3G/4G-signal strength, etc).are removed as well, but there is a System.UI closing warning. However, it does work on the stock if the added directions are removed from build.prop in text editor, but NO reboot. Otherwise the stock keys return.
Works on 7" KFHD, too. Just set up, very cool. Big thanks
Sent from my rooted Kindle Fire HD
onemeila said:
At Your Own Risk!!! I Am Not Responsible For Anything You Do To Your Device
So if you are like me you're tired of looking at the gaudy version of a nav bar and soft keys that amazon has come up with. So I started looking around for a way to modify the soft keys to look more like stock android. I may at some point dive into the framework and rewrite portions to do this, but in my search I came across an old method for removing the nav bar altogether. It is a very simple build.prop edit and at the same time adds some screen real-estate. I've confirmed this does work on this device, check out the screenshots below.
How to(rooted device):
1- You will first need a soft key/nav buttons app(once this is done the stock keys will be gone, and kinda hard to navigate without some). I like using Button Savior, it allows you to place the soft keys anywhere around the perimeter of the screen, and has multiple themes you can use. Also if you have the paid version you can change the number and position of buttons
2- Using a file manager navigate to /system/build.prop file
3- Open build.prop with a text editor, scroll to the end and on a new line enter:
Code:
qemu.hw.mainkeys=1
4- Save and reboot.
Now there are ways to do this with launchers but it will not be permanently removed and will still show up in apps.
To get stock keys back just delete the line you entered in the build.prop and reboot
Click to expand...
Click to collapse
Works fine on my recently re-rooted 7.2.2 - went ahead & sprung for the pro so I could remap the phone key to something useful ("calling home", going to the original home so I can read books. I sometimes forget that's what I originally bought it for).
Thanks.
Sadly, i must say that i detected an issue. Some apps that are coming with an own menu-button lost this button, e.g. Aldiko (app to read books) or google chrome. In chrome, the menu can be accessed with the menu-button that comes with button saviour, but the menu of Aldiko can't be accessed at all.
Sent from my rooted Kindle Fire HD
This will work for me until cm 10 comes out. Confirmed working on Kindle Fire HD 7". This also fixes the issue of the keyboard in landscape mode.
Wow, this is the greatest thing I have done to my kindle yet, make sure to install button savior first or else you are gonna be having a hard time fixing it. Couldnt access my root to change the build prop back to install button savior, luckily i was able to download the apk file on my computer and transfer it over and install it. Set it to appear when i swipe from the right corner...and goes away after 5 seconds..different themes... and alot of options when it comes to using custom triggers. Found a pro version on google, works flawless.
Thanks for the tip, but can I suggest the better looking ltm launcher.
Sent from my KFTT using Tapatalk 2
Nice tip, I used button saviour previously on my HTC Desire and found it to be a great piece of kit, but I've noticed that while using it on my Kindle, particularly in portrait mode, when the button saviour bar is closed there is a flicker lower down the screen which is very annoying. Its as though it repositions itself at the bottom of the screen before closing. I'm using the pro version as well, so it's not got anything to do with that.
For now I've gone back to the default nav bar - it is annoying that there is no autohide for that really as otherwise it does the job. There must be a way to autohide it as some apps do that.
I also had the no menu button problem. I had to go back to stock nav bar till that is figured out..oh well
Sent from my KFOT using Tapatalk HD
rockystar000 said:
I also had the no menu button problem. I had to go back to stock nav bar till that is figured out..oh well
Sent from my KFOT using Tapatalk HD
Click to expand...
Click to collapse
You can customize it in button savior to make a menu button there are a ton of extras in the settings
Sent from my KFTT using XDA Premium HD app
Yeah i know but with out stock nav bar the menu button doesn't do anything. For instance if i set it up with a menu button on button savior but no nav bar when an app should have a menu button it wouldn't be there any more. The button savior menu button also does nothing when u click it. If the stock nav bar is their however then the button savior menu button works again and it appears in the app again
Sent from my KFOT using Tapatalk HD
rockystar000 said:
Yeah i know but with out stock nav bar the menu button doesn't do anything. For instance if i set it up with a menu button on button savior but no nav bar when an app should have a menu button it wouldn't be there any more. The button savior menu button also does nothing when u click it. If the stock nav bar is their however then the button savior menu button works again and it appears in the app again
Sent from my KFOT using Tapatalk HD
Click to expand...
Click to collapse
I had noticed this, but not the part about the menu working with the bar there. perhaps we could mod the framework-res.apk to set the height to 0 or something then we would not need to do the qemu.hw.mainkeys=1..
About the file edit?
When I open the file and type the new line in.. It will not let me save it. Is it write protected or something? How do I get past this?
Thanks!
thanks alot for sharing.ill give it a try in my kindle fire hd 7" keep it up and GODBless!
cmullins135 said:
When I open the file and type the new line in.. It will not let me save it. Is it write protected or something? How do I get past this?
Click to expand...
Click to collapse
What file explorer are you using? Some of the text editors dont work on this device. I believe I ended up using root browser.
You're a life saver, man! Couldn't stand the huge bar Amazon thought looked good
Edit: Is there any way to make it so Button Savior automatically acquire super user privileges upon boot, without having to interact with it first?
An unimportant request, but would be pretty awesome
Sent from my KF-HD7
searched, but couldn't find it - but can anyone point me to a method for removing the amazon adds when in lockscreen mode? I can't stand it...! Lol... Thanks in advance!
cmullins135 said:
When I open the file and type the new line in.. It will not let me save it. Is it write protected or something? How do I get past this?
Click to expand...
Click to collapse
If you use root explorer, it works perfect - just mount as R/W,and it'll let you save.
cmullins135 said:
When I open the file and type the new line in.. It will not let me save it. Is it write protected or something? How do I get past this?
Click to expand...
Click to collapse
Make sure you mount the s system folder, and make sure whatever text editor you use has super user permissions or it won't save
Sent from my KF-HD7
I take no responsibility for you breaking or causing issues on your tablet. Do this at your own risk!
Disable your Galaxy Note 8.0 Capacitive Keys
What you will need:
Root
Root explorer or similar program
and Be Careful
First:
Open your root explorer or similar app
navigate to system>usr>keylayout
Second:
Make backup of sec_touchscreen.kl
Third
This step has been, found to be not needed. Skip to step 4!
Fourth:
Open sec_touchscreen.kl
find line:
key 158 BACK WAKE_DROPPED
and place a # in front of it like:
# key 158 BACK WAKE_DROPPED
then find line:
key 139 BACK WAKE_DROPPED
and place a # in front of it like:
# key 139 BACK WAKE_DROPPED
Save your changes and close the file
reboot your tablet, and you are finished.
Your capacitive buttons will not respond to your fingers, but retain functionality with the s-pen.
ENJOY!
step 3 was not needed for this guide to work!
Hey ual4720, thanks for the great guide,this is the sort of stuff we need to get some development started for our tablet.
That's more of a how-to, a mod means flashing something
will there be custom roms coming?
Thai Damen said:
will there be custom roms coming?
Click to expand...
Click to collapse
I woud say yes, considering it's the same specs powering the Galaxy Note 10.1 (at least, i'm betting on this )
I'm actually sort of surprised someone hasn't tried flashing one of the Galaxy Note 10.1 roms on the Note 8 (I'm not recommending this, i'm not a developer. Just surprised no one (big kahuna's) tried this).
I can't wait until someone figures out how to make this a quick option on the drop down menu so we can toggle the keys on and off based on what we're doing
Sent from my SAMSUNG-SGH-I317 using xda premium
Just to be clear - this is only suppose to disable the capacitive function of the hardware buttons, not enable the virtual on-screen buttons or anything (the latter was what I was hoping for)? Don't mean to diminish the value of the first mod to appear on this forum - I just don't quite understand the use case for this. Thanks!
peng1can said:
Just to be clear - this is only suppose to disable the capacitive function of the hardware buttons, not enable the virtual on-screen buttons or anything (the latter was what I was hoping for)? Don't mean to diminish the value of the first mod to appear on this forum - I just don't quite understand the use case for this. Thanks!
Click to expand...
Click to collapse
I use my tablet in landscape a lot! I found it was hard to hold the tablet with both hands because I kept hitting the Capacitive keys. this is my way of solving that! I thought I would Share it.
Sent from my GT-N5110 using Tapatalk HD
I hope it didn't sound like I was criticizing the patch. I was genuinely interested in how people were using this - we all have our own ways of doing things. For example, the hardware buttons have turned out to be more convenient than I expected for me because I use the tablet in bed a lot, and I find it's easier to touch the buttons if I hold the tablet upside down, so the buttons are at the top. With virtual buttons, they'd just move themselves back to the bottom!
Thanks, working good with LMT launcher.
colhavoc said:
I woud say yes, considering it's the same specs powering the Galaxy Note 10.1 (at least, i'm betting on this )
I'm actually sort of surprised someone hasn't tried flashing one of the Galaxy Note 10.1 roms on the Note 8 (I'm not recommending this, i'm not a developer. Just surprised no one (big kahuna's) tried this).
Click to expand...
Click to collapse
Similar specs, but different. If you tried flashing a ROM you'd softbrick your device. There are a number of devs working on ports and I'm sure we will be seeing customs appearing soon in the future.
Sent from my GT-N5110 using XDA Premium HD app
Thanks a lot for sharing detail information about the Galaxy Note. This will be helpful for me to developing stuff.
Hello all,
after disabling capacitive keys, install GMD gesture control to get the same through customized swipes.
Now SNote will work without being annoyed by keys at the end of the page
Hi all,
I kinda like the HW buttons and I wished they were real buttons rather than capacitive.
Is there a way to disable them ONLY in certain apps? I would like them to be disabled when I use S notes only.
Also,
the mod mentions "Your capacitive buttons will not respond to your fingers, but retain functionality with the s-pen."
So I can actually still use the buttons using the Spen?
Thanks!
For those who tried this, I wonder what app do you use to simulate the "back" and "menu" button WITHOUT using the Stylus?
I'd love to disable the capacitive keys, but there are times when I need to bring up the menu or go back WITHOUT taking out the Stylus and drawing the gesture.
lanwarrior said:
For those who tried this, I wonder what app do you use to simulate the "back" and "menu" button WITHOUT using the Stylus?
I'd love to disable the capacitive keys, but there are times when I need to bring up the menu or go back WITHOUT taking out the Stylus and drawing the gesture.
Click to expand...
Click to collapse
i use apps gesture control. can get it from playstore. the free version is sufficient for daily use unless you want to make custom gesture. go for pro.
andrianarison said:
Hello all,
after disabling capacitive keys, install GMD gesture control to get the same through customized swipes.
Now SNote will work without being annoyed by keys at the end of the page
Click to expand...
Click to collapse
Good day. Could you explain "get the same through customized swipes?"
Do you mean it's possible to toggle the editing or renaming of the "sec_touchscreen.kl" file?
Even if you do this, will you need to restart every time?
theraker007 said:
I can't wait until someone figures out how to make this a quick option on the drop down menu so we can toggle the keys on and off based on what we're doing
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
I 2nd this.:good:
I'm using the unofficial CM 10.2 for the note and have deactivated both buttons, but they are still glowing. Is there a way to deactivate this too?
kingofcomedy said:
I'm using the unofficial CM 10.2 for the note and have deactivated both buttons, but they are still glowing. Is there a way to deactivate this too?
Click to expand...
Click to collapse
Try in the Setting, where you can disable it.
So ive been search around for a while now on how to fix this. And to anyone that chimes in and says why do you need the menu button obviously you don't use older apps, the new touch button on the screen is a huge annoyance especially since i've used my phones this way since my first S1. Regardless this is how i want it and so do many other people.
Currently this is only for a rooted phone
I have figured out how to remap the left soft key from the App Switcher/Multi window over to the old style menu key. Instructions for that can be found here
But now i don't have any way of switching to my currently open apps, after remapping the left key, the longpress now takes you to search. and long pressing on the home button also takes you to another variation of the search (both i dont use nor want). I want to be able to remap my left softkey on longpress to open up currently open apps (APP_SWITCH) and it would be nice if long pressing on Home could open the Task Manager as it did on my S3.
As far as i can tell editing of the longpress function is done via a Policy edit. Read about that HERE
Keep in mind that post is from 2014 so i have no idea if the internal code is still being handled the same way, i couldn't even find that file on my S6, but i did find a file called SEPOLICY in my root folder using ROOT EXPLORER. Do any of you know more about this and how I can go about changing this? im sure its a code level adjustment. Thanks
Long-press home button can be controlled without root easily.
Check out this app:
https://play.google.com/store/apps/details?id=com.spada.nowgesturetweaksfree
I use the long-press home to get to my last used app.
I wonder if I can remap my buttons to launch any other apps.. Will have to tinker around a bit.
Ewww.
@rbiter said:
Ewww.
Click to expand...
Click to collapse
if you have nothing useful to bring to this discussion then please get out
j1635 said:
if you have nothing useful to bring to this discussion then please get out
Click to expand...
Click to collapse
very useful. menu for navigation is long long outdate. software nave or 3 dots is the customary way to go. adding a secondary menu button is redudant and unnecessary. my little ewww comment brought a lot to the table. you tryingt to call me out on it is less useful.
@rbiter said:
very useful. menu for navigation is long long outdate. software nave or 3 dots is the customary way to go. adding a secondary menu button is redudant and unnecessary. my little ewww comment brought a lot to the table. you tryingt to call me out on it is less useful.
Click to expand...
Click to collapse
lol f off
If you guys use Dropbox, how do you get to the menu with SORT, etc.. without a menu key. This is making me crazy. I'm using nova launcher and there is no floating menu key. ????
The problem is if not every developer uses it, it's inconsistent.
It often helps if the options etc. In apps are on the top, so you don't have to fidget with your phone to reach the top or use two hands.
The menu button on every app is positioned somewhere else, so I find the op wanting it justified.
All in one gestures let's you remap every key, for some odd reason on my s4 I can remap the menu key, but on the S6 for some odd reason the option of the menu key has vanished in the same app:what:
Sent from my SM-G925F using XDA Free mobile app
Hi pal. Hope it helps. Make 254 button remap, then install nova launcher, in tab gestures select long press menu and then recent app. Profit! Now once tapped you have menu button, long pressed - recent apps.
So, i made it, i use it. It works.
j1635 said:
So ive been search around for a while now on how to fix this. And to anyone that chimes in and says why do you need the menu button obviously you don't use older apps, the new touch button on the screen is a huge annoyance especially since i've used my phones this way since my first S1. Regardless this is how i want it and so do many other people.
Currently this is only for a rooted phone
I have figured out how to remap the left soft key from the App Switcher/Multi window over to the old style menu key. Instructions for that can be found here
But now i don't have any way of switching to my currently open apps, after remapping the left key, the longpress now takes you to search. and long pressing on the home button also takes you to another variation of the search (both i dont use nor want). I want to be able to remap my left softkey on longpress to open up currently open apps (APP_SWITCH) and it would be nice if long pressing on Home could open the Task Manager as it did on my S3.
As far as i can tell editing of the longpress function is done via a Policy edit. Read about that HERE
Keep in mind that post is from 2014 so i have no idea if the internal code is still being handled the same way, i couldn't even find that file on my S6, but i did find a file called SEPOLICY in my root folder using ROOT EXPLORER. Do any of you know more about this and how I can go about changing this? im sure its a code level adjustment. Thanks
Click to expand...
Click to collapse
but if i want to change the long press from split screen to menu? how do i find that? will it work the same?
Delphinus3 said:
but if i want to change the long press from split screen to menu? how do i find that? will it work the same?
Click to expand...
Click to collapse
look at my Rom.. it needs changes in framework to get that working..and it is working
Alex-V said:
look at my Rom.. it needs changes in framework to get that working..and it is working
Click to expand...
Click to collapse
i saw your page.. there are 2 roms i seem to like, yours and EMPORIA but idk who is best. lol i haven't even bought the phone yet but yea the menu button will be missed for me. what i want in a rom? if its based on stock i like it as close to stock as possible (no bloatware), call recording, if there's an option for increasing camera performance thats awesome, better battery life than stock original. that's it basically. and if i only want to root, how can i change menu longpress? i hered theres like a toolbox root app for galaxy devices...
Delphinus3 said:
i saw your page.. there are 2 roms i seem to like, yours and EMPORIA but idk who is best. lol i haven't even bought the phone yet but yea the menu button will be missed for me. what i want in a rom? if its based on stock i like it as close to stock as possible (no bloatware), call recording, if there's an option for increasing camera performance thats awesome, better battery life than stock original. that's it basically. and if i only want to root, how can i change menu longpress? i hered theres like a toolbox root app for galaxy devices...
Click to expand...
Click to collapse
it's only my personal rom..means it's not made for making any profit or let's say thousands of users..
i think you must try it yourself for one or two days and compare..my is very clean
I've enabled the navkey, but the capacitive buttons are still working, i have tried editing the key layout settings but its still there.. Also tried gravity box but no luck.. Any help? Thanks
Use gravity box to disable backlight (under display section). Then use a file manager and editor with root access (I used ES File Explorer) and open the file synaptics_dsx.kl (it is located under system>user>keylayout) and then edit it by adding a # in front of the key entries. Save, reboot and your hardware keys should be off
kanagawaben said:
Use gravity box to disable backlight (under display section). Then use a file manager and editor with root access (I used ES File Explorer) and open the file synaptics_dsx.kl (it is located under system>user>keylayout) and then edit it by adding a # in front of the key entries. Save, reboot and your hardware keys should be off
Click to expand...
Click to collapse
Thanks mate, i have disabled the light though editing synaptics didnt work, but i figured it out by editing atmel_mxt_T100_touchscreen.kl,
Now, my problem is switching the back button and recent..
Why do you want to do that?
---------- Post added at 09:23 AM ---------- Previous post was at 09:19 AM ----------
I have enabled the soft keys via buildprop, disabled the hardware keys in the synaptic file, disabled the backlight and added double tap home key to sleep and long press home key for menu using gravity box. Looking good with the Pixel launcher, although unfortunately don't get the transparent white dock background.
Screenshot:
jlou0918 said:
I've enabled the navkey, but the capacitive buttons are still working, i have tried editing the key layout settings but its still there.. Also tried gravity box but no luck.. Any help? Thanks
Click to expand...
Click to collapse
hii can you tell me how u activated navigation bar i have tried several ways including cm13 and gravity box
how did you do it
thanks
[email protected] said:
hii can you tell me how u activated navigation bar i have tried several ways including cm13 and gravity box
how did you do it
thanks
Click to expand...
Click to collapse
You can do it manually if you have root, just need to change a value from 1 to 0 in the buildprop file (it's easy to find the relevant line as it has a description). However, I just use a free root app called Softkey Enabler from the Play Store. This makes it very quick to enable or disable the nav bar.
I leave the hardware keys on (because their long press functions are useful) but in accessibility settings I switch their layout around to match the nav bar. I use another root app called Keyboard Backlight Controller to disable their backlight.
kanagawaben said:
You can do it manually if you have root, just need to change a value from 1 to 0 in the buildprop file (it's easy to find the relevant line as it has a description). However, I just use a free root app called Softkey Enabler from the Play Store. This makes it very quick to enable or disable the nav bar.
I leave the hardware keys on (because their long press functions are useful) but in accessibility settings I switch their layout around to match the nav bar. I use another root app called Keyboard Backlight Controller to disable their backlight.
Click to expand...
Click to collapse
Which rom are u on?
I tried soft key enabler on official 16s and 19s it didn't work
I am on cm13 umbrella and it's really good
Far better fingerprint recognition
Better battery life I lost 3% over night
and finally i tried ur buildprop thing for soft keys it worked thanks for that BTW
Did u get to make the Navbar transparent by any chance
I have used the settings in cm13 to turnoff the backlit of capacitive buttons but there still functional can explain how u disable them or use them as u do for long press
Cheers for the help
[email protected] said:
Which rom are u on?
I tried soft key enabler on official 16s and 19s it didn't work
I am on cm13 umbrella and it's really good
Far better fingerprint recognition
Better battery life I lost 3% over night
and finally i tried ur buildprop thing for soft keys it worked thanks for that BTW
Did u get to make the Navbar transparent by any chance
I have used the settings in cm13 to turnoff the backlit of capacitive buttons but there still functional can explain how u disable them or use them as u do for long press
Cheers for the help
Click to expand...
Click to collapse
I am currently using 17S based Cuoco92. Fingerprint recognition has been just fine for me on Cuoco92, and on stock 16S, 17S and 19S - fast and accurate. The nav bar I have is transparent, just like in stock android. To disable the hard keys, go into system-usr-keylayout and edit the synaptics file (just add a # in front of the lines relating to the keys).
kanagawaben said:
I am currently using 17S based Cuoco92. Fingerprint recognition has been just fine for me on Cuoco92, and on stock 16S, 17S and 19S - fast and accurate. The nav bar I have is transparent, just like in stock android. To disable the hard keys, go into system-usr-keylayout and edit the synaptics file (just add a # in front of the lines relating to the keys).
Click to expand...
Click to collapse
Thanks for the info really appreciate it
I have found a small thing do u have any fix for it?
The notification panel doesn't fully open due to the nav keys
Some other elements get blocked as well
Any solution?
[email protected] said:
Thanks for the info really appreciate it
I have found a small thing do u have any fix for it?
The notification panel doesn't fully open due to the nav keys
Some other elements get blocked as well
Any solution?
Click to expand...
Click to collapse
No, don't think there's anything you can do about that I'm afraid. I have actually gone back to just using the hard keys as they come. The soft nav keys are nice, but bit of a waste of screen space when you have perfectly good hard keys there to use.
kanagawaben said:
No, don't think there's anything you can do about that I'm afraid. I have actually gone back to just using the hard keys as they come. The soft nav keys are nice, but bit of a waste of screen space when you have perfectly good hard keys there to use.
Click to expand...
Click to collapse
Yea your right about that but the screen is big so having on screen buttons help in using the phone with one hand
I am surprised how the hardware buttons completely disappears when not back lit better then even OnePlus one
I have put a request in the feedback app for a feature like OnePlus one for choice between on screen and off screen
[email protected] said:
Yea your right about that but the screen is big so having on screen buttons help in using the phone with one hand
I am surprised how the hardware buttons completely disappears when not back lit better then even OnePlus one
I have put a request in the feedback app for a feature like OnePlus one for choice between on screen and off screen
Click to expand...
Click to collapse
I would love them to add that feature. It was one of the best things about CM13 on my Zenfone 2.
Currently I am using the stock eui launcher (it's so smooth and light, and I don't really need an app drawer because I don't download so many apps) and the soft keys don't go so well with that launcher, but I also have the Pixel launcher installed, and I really like using the soft keys with that.