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.
Related
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
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
The updated Gravity Box has the Android L Navigation Keys feature and it sticks. For those using Xposed and GRavity Box just select Enable Navigation Bar, then Enable Android L Nav Keys, reboot and you should be good to go.
Been using auto hide softkeys the whole time I've had this phone and it has always had the Android Lollipop softkeys and it, well, auto hides, giving you more screen to enjoy.
Sent from my MT2L03
Coffee Freak said:
Been using auto hide softkeys the whole time I've had this phone and it has always had the Android Lollipop softkeys and it, well, auto hides, giving you more screen to enjoy.
Sent from my MT2L03
Click to expand...
Click to collapse
How did you setup up autohide? I have tried expanded desktop in gravity box but it doesn't work.
ecvision said:
How did you setup up autohide? I have tried expanded desktop in gravity box but it doesn't work.
Click to expand...
Click to collapse
You have to download the app from the play store.
https://play.google.com/store/apps/details?id=com.gmd.hidesoftkeys
Sent from my MT2L03
Nice ! Thanks
ecvision said:
Nice ! Thanks
Click to expand...
Click to collapse
Make sure you pay the two bucks to go pro. It's worth it for the added features. You don't have to keep the active notification in the status bar. It's working flawless. Click on the thanks if it helps. Enjoy.
Sent from my MT2L03
If you have MT2-L05 or another China version auto hide soft keys is already in stock settings. I advise any non US mate 2 users NOT to use gravity box to mess with soft keys if you are on kitkat as it will mess up at some point and completely mess your phone up. ( It can actually make your soft keys completely disappear and never reappear, which is something of a problem, lol ).
You can however download android L navigation bar module for xposed which will give you android L navigation buttons or Android L shape navigation buttons. Just a heads up, as I have been there and messed my phone up trying with kitkat version of gravitybox, lol.
Hiding auto hide feature
For all that don't know. the phone comes with a hide feature built in. You have to edit the build.prop a little.
You need to add the line.
ro.config.hw_shownavisettings=true
And You need to make sure all these are true ---
ro.config.hw_navi_launcher=true
ro.config.hw_navigationbar=true
ro.config.shownavibarsetting=true
ro.config.shownavigationbar=true
After that reboot. And go in to settings and at the bottom you will see navigation bar.
Turn it on.
Then there will be a down arrow on the left side of the navigation bar, swipe down on it and it hides, swipe from the bottom to restore.
Use gravitybox and that and you are good to go.
4L0M said:
If you have MT2-L05 or another China version auto hide soft keys is already in stock settings. I advise any non US mate 2 users NOT to use gravity box to mess with soft keys if you are on kitkat as it will mess up at some point and completely mess your phone up. ( It can actually make your soft keys completely disappear and never reappear, which is something of a problem, lol ).
You can however download android L navigation bar module for xposed which will give you android L navigation buttons or Android L shape navigation buttons. Just a heads up, as I have been there and messed my phone up trying with kitkat version of gravitybox, lol.
Click to expand...
Click to collapse
Xposed module did not work when I tried it on my US version which is why I used Gravity Box to enable it.
mtyler7807 said:
For all that don't know. the phone comes with a hide feature built in. You have to edit the build.prop a little.
You need to add the line.
ro.config.hw_shownavisettings=true
And You need to make sure all these are true ---
ro.config.hw_navi_launcher=true
ro.config.hw_navigationbar=true
ro.config.shownavibarsetting=true
ro.config.shownavigationbar=true
After that reboot. And go in to settings and at the bottom you will see navigation bar.
Turn it on.
Then there will be a down arrow on the left side of the navigation bar, swipe down on it and it hides, swipe from the bottom to restore.
Use gravitybox and that and you are good to go.
Click to expand...
Click to collapse
Auto hide softkeys app is better. Much more customizable and it autohides. I tried the built in manual method when I first got the Mate 2 and there's a lot of lag with it.
Sent from my MT2L03
4L0M said:
If you have MT2-L05 or another China version auto hide soft keys is already in stock settings. I advise any non US mate 2 users NOT to use gravity box to mess with soft keys if you are on kitkat as it will mess up at some point and completely mess your phone up. ( It can actually make your soft keys completely disappear and never reappear, which is something of a problem, lol ).
You can however download android L navigation bar module for xposed which will give you android L navigation buttons or Android L shape navigation buttons. Just a heads up, as I have been there and messed my phone up trying with kitkat version of gravitybox, lol.
Click to expand...
Click to collapse
I really hope you're wrong. I love the 5.0 icons with the black background. I hope this never screws up..
Mozgus said:
I really hope you're wrong. I love the 5.0 icons with the black background. I hope this never screws up..
Click to expand...
Click to collapse
Wouldn't an alternative be to replace the button images in SystemUI.apk or wherever they're located? Maybe framework-res.apk?
In the past on kitkat I used a build.prop edit to enable the nav keys on my note 3. It worked fine and I used rom toolbox's build.prop editor to do so. Now however I'm on lollipop and I'm rooted but I'm not sure if that will work.
The reason I'm asking here instead of just tying it out is because I don't have a backup to revert to and I've seen some conflicting answers while googling this. So an anyone confirm that adding "qemu.hw.mainkeys=0" will still work?
-thank you
Make a back up of your build.prop.
Like this
Copy the build.prop and paste it in the same system folder and replace the name.
/system/build.proporiginal
Add what you need to and reboot... if it dont work you can use twrp file manager to delete the build.prop and rename the original.
Thank you. I'll uh try later. I found an alternative in the meanwhile that works great. But first I need to get a custom recovery.
I have Lightning Launcher settings programed to
Menu key long press-open Phone
Back key long press-open Camera
ttkyles said:
I have Lightning Launcher settings programed to
Menu key long press-open Phone
Back key long press-open Camera
Click to expand...
Click to collapse
Would that work in any app?
yup sure does ...
on home screen
menu and back long press goes to specific app. ..
lightning launcher doesn't get much press..But if you take the time to learn its configuration endless possibilities. ...you'll find its the most customizable launcher out.
I show my iPhone phanboy co workers...That i can launch 24 different apps...with a single swipe gesture from my single home screen set up LL.
screenshot
ttkyles said:
yup sure does ...
at anytime or any app
menu and back long press goes to specific app. ..
lightning launcher doesn't get much press..But if you take the time to learn its configuration endless possibilities. ...you'll find its the most customizable launcher out.
Click to expand...
Click to collapse
Well i checked it out. i didnt see a app switcher setting for the menu key.
Also what custom recovery are some of you guys using?
im using twrp 2.8.6.1
Build.prop edit worked for me
evilvoice said:
Build.prop edit worked for me
Click to expand...
Click to collapse
Cool. Great to know. Do you have an screenshots?
With that string added to build.prop, it breaks screenshot (even palm motion). If they are important, I would find another way to take screenshots or wait for xposed.
I can tell you what the buttons look like and what they do, but that's it.
The first button is a backwards "Play" button and it is the same as "Back" but long pressing it does nothing.
The second looks like an "o" centered vertically and horizontally and is the "home" button. Long pressing brought up options for me of Google search, Tasker, or Pressy.
The third button looks like "Stop" from a music player and is the app switcher (recent apps). No long press.
The icons are white and the bar is black
I searched for a way to edit their function but couldn't find anything that didn't require xposed or Softkeyz app.
evilvoice said:
With that string added to build.prop, it breaks screenshot (even palm motion). If they are important, I would find another way to take screenshots or wait for xposed.
I can tell you what the buttons look like and what they do, but that's it.
The first button is a backwards "Play" button and it is the same as "Back" but long pressing it does nothing.
The second looks like an "o" centered vertically and horizontally and is the "home" button. Long pressing brought up options for me of Google search, Tasker, or Pressy.
The third button looks like "Stop" from a music player and is the app switcher (recent apps). No long press.
The icons are white and the bar is black
I searched for a way to edit their function but couldn't find anything that didn't require xposed or Softkeyz app.
Click to expand...
Click to collapse
Yeah i tried it just know and its a bit more messed up than it was in kitkat. Stock apps look strange etc. Well thank you for being the first to test for me.
Sorry all if queastion was before (can't find answer and I'm really pissed off)...is it possible to remove this arrow under the keyboard on pixel 6 (pic in attach)?! I had pixel 6 pro few days ago (returned because fingerprint sensor didn't work) and I'm shure that I didn't had arrow there (gestures used too, all same as here). Tried to find option to turn off everywhere but no success...hope that this is not feature from todays jan update?!
You can't remove that arrow, it's used to hide and un-hide the keyboard.
Proday said:
Sorry all if queastion was before (can't find answer and I'm really pissed off)...is it possible to remove this arrow under the keyboard on pixel 6 (pic in attach)?! I had pixel 6 pro few days ago (returned because fingerprint sensor didn't work) and I'm shure that I didn't had arrow there (gestures used too, all same as here). Tried to find option to turn off everywhere but no success...hope that this is not feature from todays jan update?!
Click to expand...
Click to collapse
That's not a new feature. Has always been there. If rooted you can remove with a mod that removes navbar, gesture pill, etc..
It is different if using two button or three button navigation.
I use the three button navigation and the back arrow key in the navigation changes to a down arrow key.
Pixel's implementation of down arrow on the navbar (or at least the padding below) is actually better than not having anything (like Xiaomi did on MIUI). The OS cannot recognize smartly if you meant a swiping up gesture or just simply pressing the space button, hence this placement.
Lughnasadh said:
That's not a new feature. Has always been there. If rooted you can remove with a mod that removes navbar, gesture pill, etc..
Click to expand...
Click to collapse
Tnx for info mate. I'll search for it.
vandyman said:
It is different if using two button or three button navigation.
I use the three button navigation and the back arrow key in the navigation changes to a down arrow key.
View attachment 5508985
Click to expand...
Click to collapse
I know mate, but I'm using swipe last 3 years, can't go back on old commands...and this way I have more screen space to look at.
peter_betos said:
Pixel's implementation of down arrow on the navbar (or at least the padding below) is actually better than not having anything (like Xiaomi did on MIUI). The OS cannot recognize smartly if you meant a swiping up gesture or just simply pressing the space button, hence this placement.
Click to expand...
Click to collapse
Whell thats individual thing. This way I'm loosing about 1cm of screen size, on samsung (one plus) phones it works for me without any problem.
Anyway, now im certain that it is not to remove id witouth root...thanks all one more time.
Try this method (pictures attached) worked for my OnePlus 10 pro oxygenos13 beta.
1. Go to the settings
2. Open additional setting or direct search 3rd option
3. Keyboard & input method
4. keyboard location
5. Select hide
Romi007 said:
Try this method (pictures attached) worked for my OnePlus 10 pro oxygenos13 beta.
1. Go to the settings
2. Open additional setting or direct search 3rd option
3. Keyboard & input method
4. keyboard location
5. Select hide
View attachment 5688671 View attachment 5688673
Click to expand...
Click to collapse
you're awesome
it worked
i like getting my inquiry resolved fast
that was fast
Lughnasadh said:
That's not a new feature. Has always been there. If rooted you can remove with a mod that removes navbar, gesture pill, etc..
Click to expand...
Click to collapse
I am using gensture navigation in lineageOS 19, and I also meet this problem that my phone have a very wide bottom bar when I input something. My phone have a small screen so that I have a bad experience when I input, but I couldn't find related setting in my phone setting. However I have rooted so could you give me this module? Thank you very much!
A marinated egg said:
I am using gensture navigation in lineageOS 19, and I also meet this problem that my phone have a very wide bottom bar when I input something. My phone have a small screen so that I have a bad experience when I input, but I couldn't find related setting in my phone setting. However I have rooted so could you give me this module? Thank you very much!
Click to expand...
Click to collapse
HideNavBar/README.md at master · Magisk-Modules-Repo/HideNavBar
Contribute to Magisk-Modules-Repo/HideNavBar development by creating an account on GitHub.
github.com
Lughnasadh said:
HideNavBar/README.md at master · Magisk-Modules-Repo/HideNavBar
Contribute to Magisk-Modules-Repo/HideNavBar development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Thanks very much!