Hello,
I need to remove the soft keys from my tablet, I tried a lot but I was unable to make it work as it should.
I do not want to use immersive mode cause it hides but the user can get it back on with a swipe...
The only way that I've managed to make something near is to put "qemu.hw.mainkeys=1" on build.prop file, this hides, but once again if I swipe the keys get back visible...
How can I hide it so it does never get back visible no matter what I do?
Thanks
zejulios said:
Hello,
I need to remove the soft keys from my tablet, I tried a lot but I was unable to make it work as it should.
I do not want to use immersive mode cause it hides but the user can get it back on with a swipe...
The only way that I've managed to make something near is to put "qemu.hw.mainkeys=1" on build.prop file, this hides, but once again if I swipe the keys get back visible...
How can I hide it so it does never get back visible no matter what I do?
Thanks
Click to expand...
Click to collapse
If you remove this entire line from build.prop:
Code:
qemu.hw.mainkeys=[number]
...the soft keys shouldn't come back.
Hello,
The qemu.hw.mainkeys wore not there when I got the tablet. I have added.
I have tried =0 and =1, =0 show on start, =1 hide's on start, but if you slide it shows back again...
juliosilva said:
Hello,
The qemu.hw.mainkeys wore not there when I got the tablet. I have added.
I have tried =0 and =1, =0 show on start, =1 hide's on start, but if you slide it shows back again...
Click to expand...
Click to collapse
I have found this, this and that for you to look at. I can't help too much more, but hopefully those links will be of assistance.
Related
I really don't like the hardware buttons...the home key is too slim and I always press the menu key when playing with the device in landscape, while I really appreciated the on screen navigation bar of the galaxy nexus. It's simply always there, it's a lot faster to access the app switcher and it's really better in everything (in my opinion of course).
If it isn't yet possible I'll stick with my nexus till this feature will be available because I really can't stand with those poor designed hardware keys.
Thank you very much
Marco
Wait for cm9/aokp
Sent from my GT-I9300 using xda premium
I second that... on screen keys are the way forward... saves accidental presses too.
Sent from my Galaxy Nexus using Tapatalk 2
Waiting for someone to bring out the on screen buttons on Samsung rom as well.the problem with aokp rom is that some Samsung functions are lost. I tried to enable it in Samsung rom by it freezes the phone. I can see that the Samsung onsxreen button has slightly different icon that standard ics. Hopefully someone can figure put how to do it on stock rom soon
en0203 said:
Waiting for someone to bring out the on screen buttons on Samsung rom as well.the problem with aokp rom is that some Samsung functions are lost. I tried to enable it in Samsung rom by it freezes the phone. I can see that the Samsung onsxreen button has slightly different icon that standard ics. Hopefully someone can figure put how to do it on stock rom soon
Click to expand...
Click to collapse
You and me both... The on screen keys is the reason I'm still using my gnex as opposed to my gs3.
Sent from my Galaxy Nexus using Tapatalk 2
why dont you try the app Button Saviour bro? Had my friend try it on his S3 and it works perfectly.
raymondswong said:
why dont you try the app Button Saviour bro? Had my friend try it on his S3 and it works perfectly.
Click to expand...
Click to collapse
It's not quite the same and looks no where near as nice.... Plus I would also want to disable the capacitive buttons.
I too want to disable the home button and cap buttons and use on screen nav when I get my phone. Is it possible on a samsung based rom? I know you can enable on screen nav pretty easily and on the GS2 there was a way to disable the buttons and lights but on the Gs2 I thought it cost too much screen real estate. with a 4.8 inch screen I wouldnt mind giving up a little bit of it for on screen nav
graffixnyc said:
I too want to disable the home button and cap buttons and use on screen nav when I get my phone. Is it possible on a samsung based rom? I know you can enable on screen nav pretty easily and on the GS2 there was a way to disable the buttons and lights but on the Gs2 I thought it cost too much screen real estate. with a 4.8 inch screen I wouldnt mind giving up a little bit of it for on screen nav
Click to expand...
Click to collapse
I don't mind the home button still working as I don't think I would make any accidental presses, the capacitive buttons on the other hand need to be disabled.
Lets get a dev to make it happen... I don't mind donating to the cause either.
ronak47 said:
I don't mind the home button still working as I don't think I would make any accidental presses, the capacitive buttons on the other hand need to be disabled.
Lets get a dev to make it happen... I don't mind donating to the cause either.
Click to expand...
Click to collapse
Well when I get the device in a few weeks I will attempt it if its not done by then
Sent from my SGH-I777 using Tapatalk
here is a post by GalaxyUser that shows you how to enable the lockscreen rotation on ics. following the instructions you can also enable the ics navigation bar as well as a number of other mods. the options are in the bools.xml file within framework-res.apk\res\values\bools.xml.
http://forum.xda-developers.com/showthread.php?t=1525045
select the line that says
<bool name="config_showNavigationBar">false</bool>
and change false to true
then follow the rest of his instructions.
also, instructions to disable or enable the capacitive menu and back keys:
(i did not come up with these instructions but found them on a search a long time ago...cant remember the thread or else I would link to it)
1) Use a program like root explorer
2) go to /system/usr/keylayout
3) create a new file named "melfas-touchkey.kl" with the following text:
#key 158 BACK VIRTUAL
#key 139 MENU VIRTUAL
4) also create a second file named "sec_touchkey.kl" with the same text
5) change the permissions of both files to "rw-r--r--" (just like the other files in the directory)
6) reboot...done!
to re-enable just remove the files you just created and reboot
good luck
thanks
hocgwai said:
here is a post by GalaxyUser that shows you how to enable the lockscreen rotation on ics. following the instructions you can also enable the ics navigation bar as well as a number of other mods. the options are in the bools.xml file within framework-res.apk\res\values\bools.xml.
http://forum.xda-developers.com/showthread.php?t=1525045
select the line that says
<bool name="config_showNavigationBar">false</bool>
and change false to true
then follow the rest of his instructions.
also, instructions to disable or enable the capacitive menu and back keys:
(i did not come up with these instructions but found them on a search a long time ago...cant remember the thread or else I would link to it)
1) Use a program like root explorer
2) go to /system/usr/keylayout
3) create a new file named "melfas-touchkey.kl" with the following text:
#key 158 BACK VIRTUAL
#key 139 MENU VIRTUAL
4) also create a second file named "sec_touchkey.kl" with the same text
5) change the permissions of both files to "rw-r--r--" (just like the other files in the directory)
6) reboot...done!
to re-enable just remove the files you just created and reboot
good luck
Click to expand...
Click to collapse
Wow, that's the right link. I was able to disable softkeys and I already tried messing with bools.xml but my new framework-res crashed everything. I gave a look to the link you posted and it seems to be great! Tomorrow if I find some spare time I'll try.
Thank you very much!
hocgwai said:
here is a post by GalaxyUser that shows you how to enable the lockscreen rotation on ics. following the instructions you can also enable the ics navigation bar as well as a number of other mods. the options are in the bools.xml file within framework-res.apk\res\values\bools.xml.
http://forum.xda-developers.com/showthread.php?t=1525045
select the line that says
<bool name="config_showNavigationBar">false</bool>
and change false to true
then follow the rest of his instructions.
also, instructions to disable or enable the capacitive menu and back keys:
(i did not come up with these instructions but found them on a search a long time ago...cant remember the thread or else I would link to it)
1) Use a program like root explorer
2) go to /system/usr/keylayout
3) create a new file named "melfas-touchkey.kl" with the following text:
#key 158 BACK VIRTUAL
#key 139 MENU VIRTUAL
4) also create a second file named "sec_touchkey.kl" with the same text
5) change the permissions of both files to "rw-r--r--" (just like the other files in the directory)
6) reboot...done!
to re-enable just remove the files you just created and reboot
good luck
Click to expand...
Click to collapse
Thank you so much. Those hardware buttons were driving me insane. Happy to have them disabled now. Thanks, gratefully given!
may i get a little help?
Somehow i cant change the permission of melfas_touchkey.kl
if i try Anttek explorer says the partition is read only... (i have root privileges) however i created the file with.. strange..
What i did wrong?
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
Ok i know you can switch them round, and I have tried to change the file so key 158 etc is MENU, but it still opens the recent apps
Is there any way to get the menu back, like the oneplus one had
thanks in advace
biojo said:
Ok i know you can switch them round, and I have tried to change the file so key 158 etc is MENU, but it still opens the recent apps
Is there any way to get the menu back, like the oneplus one had
thanks in advace
Click to expand...
Click to collapse
Add menu button via GravityBox (Root Needed)
cheers, but tried this and it doesnt work, my phone is rooted and status bar mods works, but when it comes to buttons even after restart its like the system sticks to its settings
tried it on oneplue one on cm12.1 and it works
I really would like the menu Button on my left hardware Button. Is there any Option to get this going, because I am really used to this from the One.
doesnt look like it for now, i`ve tried various xposed modules, but they all seem to bring up the same thing despite saying menu.
I even tried editing the keyboard map and this says menu.
Hopefully they`ll be a CM rom soon then i can go onto it, still using the ONO for now
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.
Hello all, I'm having a difficult time rebuilding my phone setup as I like it, this is removing the on-screen navigation buttons modifiying build.prop by adding qemu.hw.mainkyes=1 to make android believe the phone has physical buttons and then using LMT launcher pie. My problem is that modifiyng my build.prop leads to a non-working system. I just get a blank screen and then the UI crash and restart the process indefinietly. I've been doing this exact modification to all my phones and never had an issue, even with this same phone on stock nougat or LOS Oreo, but stock oreo is a no-go for me. Does LG introduced some kind of obligatory on-screen buttons on oreo or is something wrong on my end?
Looks like you need a reflash. Modding build.prop is dangerous, if you forget to set the right permission things will go wrong.
Meybe you can try adb shell settings put global policy_control immersive.navigation=* It'll just hide you nav bar unless you pull it out, works on most Android and doesn't need root.
valest said:
Looks like you need a reflash. Modding build.prop is dangerous, if you forget to set the right permission things will go wrong.
Meybe you can try adb shell settings put global policy_control immersive.navigation=* It'll just hide you nav bar unless you pull it out, works on most Android and doesn't need root.
Click to expand...
Click to collapse
Ok that will work to hide on-screen buttons but the thing is, going that way makes really hard to use pie lmt launcher buttons. I agree that modifiyng build.prop is dangerous but I've been doing it since my Nexus 4 days since on-screen buttons really bother me. I only add this line qemu.hw.mainkyes=1 and then use pie but now it makes my phone unusable. I discover that stock build.prop already have that line but ending in =0 of course as it does have on-screen navigation buttons, but even changing this single value to 1 produces a crash on the system