Develop Bugs

hide navigation bar

Hi
Want to hide my navigation bar?
Any suggestions on how to go about it?

I would like to know this as well. AMOLED screens scare me.
Sent from my Pixel XL using Tapatalk

I think "pie control" does not require root.
Sent from my Pixel XL using XDA-Developers mobile app

I'm using swipe navigation, that's the reason i want to hide it.
Save the extra screen space

https: // play.google.com/store/apps/details?id=com.gmd.immersive (remove spaces)
I use this and highly recommend it for apps not requiring the keyboard much. Reason for this is that the keyboard will not appear while in full screen mode unless you swipe up, bring back the navigation keys, and then tap in the fillable field again. Otherwise it's the perfect app for long bouts of scrolling in apps like most reddit clients, twitter, google+, etc.

Power Toggle also has a quicksetting tile option for immersive mode im using nova launcher and i dont know if it's intentional or not but they have the option to make the navigation bar transparent. Give "Navbar app" a shot i think they have an option for a transparent bar as .
Sent from my Google Pixel XL using XDA Labs

Where is the option in Nova launcher to make the nav transparent?
Sent from my Pixel XL using Tapatalk

If you go under "Look and Feel" there should be an option that says "Hide notification", transparent, and dark. I tbought this was only fir the notification bar on the top but it instead made the navigation bar on the horrml
Sent from my Google Pixel XL using XDA Labs

I pulled the build.prop file via adb but can't seem to push it back after editing cuz i can't adb from recovery.

Hey,
So, screen burn in is definitely a concern of mine as well. I am well versed in AMOLED burn in going all the way back to the Droid Incredible and Verizon Fascinate days. From what I remember, it largely has to do with the black areas of the screen (notification bar, nav bar) not having any pixels being exercised. So, in essence, the rest of the screens pixels age (or burn in) creating that effect. Static images also burn in (nav bar buttons... Also concerning). I noticed somebody posted an app to change the nav bar colors with each app that's opened. Would this not prevent burn in as well as those pixels are now getting equally exercised along with the rest of the screen (with the colors changing too... Their being no static image)?
Just curious.

I edited the build.prop but I get system UI force close when I restart. Any ideas on how to stop that from happening? I want to use lmt launcher. Can't stand the nav bar.

easiest way to hide navigation bar is with Tiles app, with the imersive mode toggle. Doesn't require root either. Just an adb command to provide a certain permission.
https://forum.xda-developers.com/android/apps-games/app-tiles-t3423850

I used terminal and "settings put global policy_control immersive.navigation=*" command and I now have a stable phone. I hope an option to permanently disable the navbar will come along like the qemu line in build.prop

pxan8 said:
I used terminal and "settings put global policy_control immersive.navigation=*" command and I now have a stable phone. I hope an option to permanently disable the navbar will come along like the qemu line in build.prop
Click to expand...
Click to collapse
You used this after doing that qemu line in build.prop right? So basically two steps, one to make the nav bar go away, with the build.prop method and then the second one in terminal to get rid of the Force Close pop ups after a reboot? Am I right?

ithehappy said:
You used this after doing that qemu line in build.prop right? So basically two steps, one to make the nav bar go away, with the build.prop method and then the second one in terminal to get rid of the Force Close pop ups after a reboot? Am I right?
Click to expand...
Click to collapse
No, just the terminal command. If I change the build.prop I get system Ui force close. Unfortunately haven't figured out how to stop the fc pop ups. I just put the navbar in permanent immersive mode.
Terminal
"Su"
"settings put global policy_control immersive.navigation=*"

Deleted

pxan8 said:
No, just the terminal command. If I change the build.prop I get system Ui force close. Unfortunately haven't figured out how to stop the fc pop ups. I just put the navbar in permanent immersive mode.
Terminal
"Su"
"settings put global policy_control immersive.navigation=*"
Click to expand...
Click to collapse
Well that's great then. I am gonna try this out. If this terminal command makes it go away permanently and doesn't cause that FC issue then its better than the build.prop edit right? :laugh:

ithehappy said:
Well that's great then. I am gonna try this out. If this terminal command makes it go away permanently and doesn't cause that FC issue then its better than the build.prop edit right? :laugh:
Click to expand...
Click to collapse
Definitely better than the build.prop. At least this way the phone is stable

pxan8 said:
Definitely better than the build.prop. At least this way the phone is stable
Click to expand...
Click to collapse
Hey mate how to revert to old settings? I ran that command and it hides the navigation bar, but it still comes up when I swipe from bottom, which is annoying as I use GMD and I don't need it to come up at all. So I guess I'll go with the build.prop method, but just wanna know how to revert to old settings in Terminal.

ithehappy said:
Hey mate how to revert to old settings? I ran that command and it hides the navigation bar, but it still comes up when I swipe from bottom, which is annoying as I use GMD and I don't need it to come up at all. So I guess I'll go with the build.prop method, but just wanna know how to revert to old settings in Terminal.
Click to expand...
Click to collapse
Hi... It's easy, the answer is right here on XDA...
https://forum.xda-developers.com/pixel-xl/themes/how-to-enable-true-immersive-modes-t3554299
Cheers...

18:9 immersive mode/gesture controls/no root

DISCLAIMER: This guide was NOT made by me, I'm simply sharing this here because it's really useful IMO.
This is a guide made by reddit user turkcem421, on how to take advantage of this beautiful 18:9 aka 2:1 display.
Here's the link https://www.reddit.com/r/lgg6/comments/7bqy5r/guide_fullscreen_immersive_mode_with_gesture/
And some screenshots...

Very interesting, thank you. I was also looking for a way to do this after playing with a friend's iPhone X and realizing how outdated a navigation bar now feels.
I was on a different path. Instead of enabling immersive mode, my goal is to disable the soft keys entirely. This requires editing build.prop, which requires root, which I can't get on my H870DS. However it seems to be possible to edit it with adb as well, was going to try that next.
EDIT: file system is read-only, doesn't work with adb.
Also, there's an app called Pie Control that can provide gesture navigation controls and is very elegant IMHO. My goal is to use that as a replacement for soft keys.

Hi crabnebula,
Author of the reddit guide here. I actually tried the adb build.prop approach also! It was pretty tough to write it to the system successfully (as you noticed, there are a lot of weird things on the backend of the LG G6 compared to the Nexus phones that I am used to) but eventually I did manage to write it and chmod it by combining a lot of tricks I learned hereHowever it did not have any effect, i.e. the LG G6 ROM does not seem to care about what that line of build.prop says and just shows the buttons anyway. After that failure I ended up figuring out the solution that I put in the guide.
Pie controls looks nice too, I was considering it. There are two things I like about all-in-one gestures though that to my knowledge are not in the others (but I have not checked thoroughly)
1) all in one gestures includes both gesture controls and immersive mode in the same app, and the immersive mode also has a built-in fix to let the keyboard work (see my guide). I don't know another way to have immersive mode with a working keyboard, and it is also really handy that it's all one app, i.e. if for any reason the app crashes or is stopped then the nav bars also come back when the gesture controls stop working.
2) there is an 'alt-tab' functionality, comparable to double tapping on multitasking button. Very handy to do this with a single swipe. I didn't see any other apps that had this (but maybe I did not look hard enough)
 @yilun thanks for posting the guide here!

Thank you! The UI looks so much better without the nav-bar and status bar there to interfere. ^^

turkcem421 said:
Hi crabnebula,
Author of the reddit guide here. I actually tried the adb build.prop approach also! It was pretty tough to write it to the system successfully (as you noticed, there are a lot of weird things on the backend of the LG G6 compared to the Nexus phones that I am used to) but eventually I did manage to write it and chmod it by combining a lot of tricks I learned hereHowever it did not have any effect, i.e. the LG G6 ROM does not seem to care about what that line of build.prop says and just shows the buttons anyway. After that failure I ended up figuring out the solution that I put in the guide.
Pie controls looks nice too, I was considering it. There are two things I like about all-in-one gestures though that to my knowledge are not in the others (but I have not checked thoroughly)
1) all in one gestures includes both gesture controls and immersive mode in the same app, and the immersive mode also has a built-in fix to let the keyboard work (see my guide). I don't know another way to have immersive mode with a working keyboard, and it is also really handy that it's all one app, i.e. if for any reason the app crashes or is stopped then the nav bars also come back when the gesture controls stop working.
2) there is an 'alt-tab' functionality, comparable to double tapping on multitasking button. Very handy to do this with a single swipe. I didn't see any other apps that had this (but maybe I did not look hard enough)
@yilun thanks for posting the guide here!
Click to expand...
Click to collapse
Thank you for the reddit guide and the further information. I really appreciate that you took the time to share!
Guess I'll give up on the build.prop setting.
After playing with AIO Gestures a little more, I have to agree with you. The combination of features makes it more useful and I actually prefer the way it works when using both the bottom edge and corners to replace the 3 usual soft keys, instead of a pie menu.
The only issue I have is that the phone seems to drop out of immersive mode when returning to the launcher and certain apps, but it's a minor nuisance.
I'm hoping that in a next version of Android and/or in future OEM updates, they are going to introduce native gesture-based navigation, at least as an option. In the meantime, it's great to have an alternative that works without root. Thanks again!

I'm using something like this since 3 weeks. What I've did to get the immersive screen was all in adb code. What is causing the battery drain is Google apps that won't support 18:9 mode so you have to exclude them from immersive. You can still use youtube modded APK (18:9 support) and Chrome beta to get full screen.
The adb code is
adb shell settings put global policy_control immersive.navigation=apps,-com.android.chrome,-com.android.vending,-com.google.android.gm,-com.google.android.googlequicksearchbox
I use aiog too.

PinG91 said:
I'm using something like this since 3 weeks. What I've did to get the immersive screen was all in adb code. What is causing the battery drain is Google apps that won't support 18:9 mode so you have to exclude them from immersive. You can still use youtube modded APK (18:9 support) and Chrome beta to get full screen.
The adb code is
adb shell settings put global policy_control immersive.navigation=apps,-com.android.chrome,-com.android.vending,-com.google.android.gm,-com.google.android.googlequicksearchbox
I use aiog too.
Click to expand...
Click to collapse
Greenify doesn't help me with battery drain, anyway this tip solve my problems. Thanks a lot!

Happy to help

How can I disable it?

victor19 said:
How can I disable it?
Click to expand...
Click to collapse
You mean revert the whole process?
You can do it one by one manually, but I'd recommend just making a backup and factory resetting.
The other way is extremely time consuming and not very practical at all.

PinG91 said:
I'm using something like this since 3 weeks. What I've did to get the immersive screen was all in adb code. What is causing the battery drain is Google apps that won't support 18:9 mode so you have to exclude them from immersive. You can still use youtube modded APK (18:9 support) and Chrome beta to get full screen.
The adb code is
adb shell settings put global policy_control immersive.navigation=apps,-com.android.chrome,-com.android.vending,-com.google.android.gm,-com.google.android.googlequicksearchbox
I use aiog too.
Click to expand...
Click to collapse
I updated my immersive mode with the above command and did a reboot.
Solved my battery drain and heat problems immediately.
THANKS!!!

victor19 said:
How can I disable it?
Click to expand...
Click to collapse
adb shell settings put global policy_control null*
Just like that

I have set it up correctly but have a few questions. Is op possible to disable the navbar completely everytime i swipe up to go home from the buttom. The navbar shows up and is in the way. And is it possible to disable the white glow on the screen from the all in one gestures app?

To disable glow go to "personalization" > "edge preference" and set "opacity" to 0%.

PinG91 said:
I'm using something like this since 3 weeks. What I've did to get the immersive screen was all in adb code. What is causing the battery drain is Google apps that won't support 18:9 mode so you have to exclude them from immersive. You can still use youtube modded APK (18:9 support) and Chrome beta to get full screen.
The adb code is
adb shell settings put global policy_control immersive.navigation=apps,-com.android.chrome,-com.android.vending,-com.google.android.gm,-com.google.android.googlequicksearchbox
I use aiog too.
Click to expand...
Click to collapse
Does this solve all the apps that don't support 18:9? Is there a way to tell if there are other apps that cause it?
Sent from my LG-H870 using Tapatalk

tanguita said:
Does this solve all the apps that don't support 18:9? Is there a way to tell if there are other apps that cause it?
Sent from my LG-H870 using Tapatalk
Click to expand...
Click to collapse
This will solve the battery drain. If you need to take off another app from the inmersive just added to the line. ,-app

PinG91 said:
This will solve the battery drain. If you need to take off another app from the inmersive just added to the line. ,-app
Click to expand...
Click to collapse
Indeed it does... I screwed up mixing the command with the immersion from aiog (which activated immersion for everything). Thanks again!
Sent from my LG-H870 using Tapatalk

PinG91 said:
I'm using something like this since 3 weeks. What I've did to get the immersive screen was all in adb code. What is causing the battery drain is Google apps that won't support 18:9 mode so you have to exclude them from immersive. You can still use youtube modded APK (18:9 support) and Chrome beta to get full screen.
The adb code is
adb shell settings put global policy_control immersive.navigation=apps,-com.android.chrome,-com.android.vending,-com.google.android.gm,-com.google.android.googlequicksearchbox
I use aiog too.
Click to expand...
Click to collapse
So if you force immersive this way, you still need to use AIOG with the special settings applied through adb in order for the keyboard to function in immersive mode, or do you only use AIOG for the actual gestures?

crabnebula said:
So if you force immersive this way, you still need to use AIOG with the special settings applied through adb in order for the keyboard to function in immersive mode, or do you only use AIOG for the actual gestures?
Click to expand...
Click to collapse
Just for gestures. There is no need of touching any setting for immersive on AIOG.

Can't believe how simple that all was. Only thing I couldn't do was the SVC for ls993. Literally no one has it, spend 25 min looking and 5 minutes going through the tutorial.
Only issue I know is that some apps have a very small black sliver on the bottom, is this due to not forcing long display through the SVC? Does anyone know the SVC for ls993???
Either way, the rest works 1000x better than I expected and the battery drain solutions are terrific.
Home screen looks super good too

Android 10 swap navigation bar menu/back buttons

For a good while now, I've enjoyed switching the back and menu buttons so the back button is on the right side — seems more intuitive to me — when using the three button option.
Alternatively, if I use the swipe up feature instead, with the pill button...the back button stays on the right.
We've updated a Pixel 2 XL to Android 10 and Custom Navigation Bar app doesn't work.
I also tried running an ADB shell command:
Code:
settings put secure sysui_nav_bar "space,recent;home;back,space"
but that didn't help either on the 2 XL.
My 3 XL hasn't received the OTA update to Android 10 yet. I was hoping someone might have figured a way to swap the navigation buttons as I'm apprehensive about updating until I can achieve the swap.
Ideas/suggestions anyone...?
Thanks.

IconBoy said:
For a good while now, I've enjoyed switching the back and menu buttons so the back button is on the right side — seems more intuitive to me — when using the three button option.
Alternatively, if I use the swipe up feature instead, with the pill button...the back button stays on the right.
We've updated a Pixel 2 XL to Android 10 and Custom Navigation Bar app doesn't work.
I also tried running an ADB shell command:
Code:
settings put secure sysui_nav_bar "space,recent;home;back,space"
but that didn't help either on the 2 XL.
My 3 XL hasn't received the OTA update to Android 10 yet. I was hoping someone might have figured a way to swap the navigation buttons as I'm apprehensive about updating until I can achieve the swap.
Ideas/suggestions anyone...?
Thanks.
Click to expand...
Click to collapse
Depending upon what all else you might be interested in modding, you can flash this to swap your back and recents. You must choose three button mode because in two button mode, only the home button will show. This is a module so you can always delete it or disable it in magisk manager.
Edit: Very simple mod. No need to even decompile or recompile SystemUIGoogle.apk. Just in zip it, remove res/layout back.xml and recent_apps.xml. swap the names and replace.

how about for a VZW variant. I'd love to move the back button to the right so i can use the phone easier with one hand

Tulsadiver said:
This is a module so you can always delete it or disable it in magisk manager.
Click to expand...
Click to collapse
Thank you for the suggestion.
I am not rooted so can't make use of Magisk.
(My signature shows that I am not rooted. I'll make sure I put that in the body text when I post again. )

IconBoy said:
Thank you for the suggestion.
I am not rooted so can't make use of Magisk.
(My signature shows that I am not rooted. I'll make sure I put that in the body text when I post again. )
Click to expand...
Click to collapse
Good idea as signatures do not show when viewing from Android.

Tulsadiver said:
Good idea as signatures do not show when viewing from Android.
Click to expand...
Click to collapse
I didn't realize that was the case. Thanks for the heads-up.

Tulsadiver said:
Depending upon what all else you might be interested in modding, you can flash this to swap your back and recents. You must choose three button mode because in two button mode, only the home button will show. This is a module so you can always delete it or disable it in magisk manager.
Edit: Very simple mod. No need to even decompile or recompile SystemUIGoogle.apk. Just in zip it, remove res/layout back.xml and recent_apps.xml. swap the names and replace.
Click to expand...
Click to collapse
I tried this on my Essential PH1 and it didn't move the back to the right. Do I just use Magisk with that zip or do I have to change it? Any other way? I'm using 2 button navigation.
Sent from my PH-1 using Tapatalk

csm10495 said:
I tried this on my Essential PH1 and it didn't move the back to the right. Do I just use Magisk with that zip or do I have to change it? Any other way? I'm using 2 button navigation.
Click to expand...
Click to collapse
Did you read his message? for that zip to work you must use the navbar with 3 buttons, it doesn't work on the 2 buttons style

FcukBloat said:
Did you read his message? for that zip to work you must use the navbar with 3 buttons, it doesn't work on the 2 buttons style
Click to expand...
Click to collapse
I tried 3 button as well and it had no effect. I guess I would prefer to use 2 button.
Sent from my PH-1 using Tapatalk

so maybe the problem is the different phone you own?

Op I'm in the same boat as you. I updated my 3 XL to android 10 and the first thing I tried to do was swap the back button to the right side. Sadly I couldn't make any method work as well. Hopefully someone will figure something out.

And here I am trying to figure out how I can use gestures with 3rd party launcher..
Even when I use fluid navigation or vivid navigation the recents no longer work

masri1987 said:
And here I am trying to figure out how I can use gestures with 3rd party launcher..
Even when I use fluid navigation or vivid navigation the recents no longer work
Click to expand...
Click to collapse
Fluid works great. That's what I use. You have to enable 3 button navigation.

Looks like we are a bunch of people with similar issue: we love to move the back key to the right, or give us full functional gesture navigation (which we could back from right edge of screen) with 3rd party launcher....
Hope someone come up something soon....
Tried make Nova launcher as a system app but this doesn't bring out recent gesture...

Tulsadiver said:
Fluid works great. That's what I use. You have to enable 3 button navigation.
Click to expand...
Click to collapse
Recents works with this?
edit: Enabling 3 button navigation and then enabling gestures with any 3rd party app \ disabling nav bar works with recents
The only thing missing is "clear all" which is nobiggie

I can swap for two way, or three way, just not together. Here's a module for two way.

Tulsadiver said:
I can swap for two way, or three way, just not together. Here's a module for two way.
Click to expand...
Click to collapse
OMG, this works wonderfully!! Thank you so much! Doing this on a regular Pixel 3 with Magisk 14 Beta.

plisk3n said:
OMG, this works wonderfully!! Thank you so much! Doing this on a regular Pixel 3 with Magisk 14 Beta.
Click to expand...
Click to collapse
I wouldn't have sworn it would work on the Pixel 3 but I'm glad it does.

help how to do this
Tulsadiver said:
Depending upon what all else you might be interested in modding, you can flash this to swap your back and recents. You must choose three button mode because in two button mode, only the home button will show. This is a module so you can always delete it or disable it in magisk manager.
Edit: Very simple mod. No need to even decompile or recompile SystemUIGoogle.apk. Just in zip it, remove res/layout back.xml and recent_apps.xml. swap the names and replace.
Click to expand...
Click to collapse
I have never used magisk, any advice on how to use this so i can swap my buttons? need instructions or something for a non user. I have used fastboot and it was switched around but now with android 10 im not happy haha. any advice or instructions would be wonderful THANKS

gesy17 said:
I have never used magisk, any advice on how to use this so i can swap my buttons? need instructions or something for a non user. I have used fastboot and it was switched around but now with android 10 im not happy haha. any advice or instructions would be wonderful THANKS
Click to expand...
Click to collapse
You must be rooted with Magisk. Once you are and if you are on stock 10, all you do is open Magisk manager, in the menu, click modules, click the "plus" button, find my mod that you should have put on your phones internal sdcard, flash it, and reboot.

How To Guide How-To Enable Two-Button Navigation on the OnePlus 9 Pro with Android 11!

Hey friends! I don't know about you guys, but I really dislike the latest implementation of Gesture Navigation and the old 3-Button Navigation bar makes me feel like I'm stuck back on Ice Cream Sandwich! It made me really sad when Google forced all the OEMs to ditch 2-Button Navigation. Fortunately, we can now get it back! Even on Android 11!!
You will need USB Debugging enabled on your phone and ADB installed on your computer. You will also need your phone to be rooted with the latest version of Magisk installed.
It's a super easy process and all it takes is installing one Magisk module and an ADB command. I've created two versions of the module, one with the standard height nav bar and another with a shorter one that takes up less space on the display. You can find both versions of the module here: https://www.rwilco12.com/downloads.php?dir=Files/Misc Files/Magisk Modules/Two-Button Navigation
After installing the module, all you have to do is go into ADB and run this command.
adb shell cmd overlay enable com.android.internal.systemui.navbar.twobutton
Here's a helpful video we recorded that should help you through the process.

Is there any way to bypass the adb command since you're using a Magisk module? Does it persist through reboots? Is there a way to run the command via the su command using a terminal emulator on the device rather than using a pc to issue the adb command?

TheKnux said:
Is there any way to bypass the adb command since you're using a Magisk module? Does it persist through reboots? Is there a way to run the command via the su command using a terminal emulator on the device rather than using a pc to issue the adb command?
Click to expand...
Click to collapse
I'm a noob at Magisk modules and couldn't figure out how to pass the ADB command during the flashing process. I'm hoping I can do a v2.0 and get that in there down the road though!
But yes, it persists through reboots. The only times it will get wiped is if you update your option in Settings, or if you flash a system update.
And I could see a terminal emulator working, I just haven't tried it myself yet.

rwilco12 said:
Hey friends! I don't know about you guys, but I really dislike the latest implementation of Gesture Navigation and the old 3-Button Navigation bar makes me feel like I'm stuck back on Ice Cream Sandwich! It made me really sad when Google forced all the OEMs to ditch 2-Button Navigation. Fortunately, we can now get it back! Even on Android 11!!
You will need USB Debugging enabled on your phone and ADB installed on your computer. You will also need your phone to be rooted with the latest version of Magisk installed.
It's a super easy process and all it takes is installing one Magisk module and an ADB command. I've created two versions of the module, one with the standard height nav bar and another with a shorter one that takes up less space on the display. You can find both versions of the module here: https://www.rwilco12.com/downloads.php?dir=Files/Misc+Files/Magisk+Modules/OnePlus+Oxygen+OS+11+-+Two-Button+Navigation
After installing the module, all you have to do is go into ADB and run this command.
adb shell cmd overlay enable com.android.internal.systemui.navbar.twobutton
Here's a helpful video we recorded that should help you through the process.
Click to expand...
Click to collapse
TY @rwilco12 but a thread was already initiated if I'm not wrong here : https://forum.xda-developers.com/t/how-to-enable-two-button-navigation.4260373/

Fre$h said:
TY @rwilco12 but a thread was already initiated if I'm not wrong here : https://forum.xda-developers.com/t/how-to-enable-two-button-navigation.4260373/
Click to expand...
Click to collapse
Lol I totally missed that post! I appreciate him sharing my video! The modules I posted here are different than the one he attached to his post. Same net effect, just more options.

rwilco12 said:
Hey friends! I don't know about you guys, but I really dislike the latest implementation of Gesture Navigation and the old 3-Button Navigation bar makes me feel like I'm stuck back on Ice Cream Sandwich! It made me really sad when Google forced all the OEMs to ditch 2-Button Navigation. Fortunately, we can now get it back! Even on Android 11!!
You will need USB Debugging enabled on your phone and ADB installed on your computer. You will also need your phone to be rooted with the latest version of Magisk installed.
It's a super easy process and all it takes is installing one Magisk module and an ADB command. I've created two versions of the module, one with the standard height nav bar and another with a shorter one that takes up less space on the display. You can find both versions of the module here: https://www.rwilco12.com/downloads.php?dir=Files/Misc+Files/Magisk+Modules/OnePlus+Oxygen+OS+11+-+Two-Button+Navigation
After installing the module, all you have to do is go into ADB and run this command.
adb shell cmd overlay enable com.android.internal.systemui.navbar.twobutton
Here's a helpful video we recorded that should help you through the process.
Click to expand...
Click to collapse
OP, in theory, do you think it would be possible to somehow disable onepluses built-in navigation gestures, but keeping the 'hide nav bar' feature that goes along with it? I ask this because, I'd love to use a third party app to do navigation gestures. The built-in gestures have this annoying animation when you swipe up from bottom or swipe from the sides. It's subtle and it's very brief but it's there. And my OCD wants to get rid of it. Fluid navigation gestures for example is very clean and you don't see an animation when you use any sort of gesture navigation. It looks so much sleeker and snappier.

Burt Squirtz said:
OP, in theory, do you think it would be possible to somehow disable onepluses built-in navigation gestures, but keeping the 'hide nav bar' feature that goes along with it? I ask this because, I'd love to use a third party app to do navigation gestures. The built-in gestures have this annoying animation when you swipe up from bottom or swipe from the sides. It's subtle and it's very brief but it's there. And my OCD wants to get rid of it. Fluid navigation gestures for example is very clean and you don't see an animation when you use any sort of gesture navigation. It looks so much sleeker and snappier.
Click to expand...
Click to collapse
In theory, yes, it is totally possible. I was able to do two different heights for the modules. Somebody could make one that has no height or even one that just never generates. That is beyond my skillset though. So in theory, yes, it is possible. Could I do it? Probably not.

What would be for me a better thing is just to be able to engage the gesture mode for the apps to be in full screen ( without the navbar) but with the navbar button's available too. A sort of weeding between a kingsize display with the usefull part of those buttons that I keep want to use for some reasons

Fre$h said:
What would be for me a better thing is just to be able to engage the gesture mode for the apps to be in full screen ( without the navbar) but with the navbar button's available too. A sort of weeding between a kingsize display with the usefull part of those buttons that I keep want to use for some reasons
Click to expand...
Click to collapse
Agreed!

Hello, did you remove the module? The directory is empty(

OnePlus Oxygen OS 11 - Two-Button Navigation (SHORT)
And
OnePlus Oxygen OS 11 - Two-Button Navigation (STANDARD)

bgkone said:
Hello, did you remove the module? The directory is empty(
Click to expand...
Click to collapse
Sorry about that, I must've posted the wrong link. I've updated it in the OP. Thanks!

How To Guide Remove NavBar Gesture Pill (and more) for Pixel 6 Pro

Update: This only works if you are rooted now, since the January 2022 patch.
Hi guys, I've seen several posts asking how to remove the Gesture Pill. It's easy if you're rooted, but it's also possible if you're not rooted.
Here is a step by step guide. There is also a huge amount of UI mods that can be made using the same method.
1. Download the Shizuku app from the Playstore
2. Start the Shizuku app by running the following adb command:
adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh
3. Download and install FabricateOverlay release from Github.
4. In FabricateOverlay click “Add Overlay”
5. Choose Android System
6. Click “Add”
7. Set “android:dimen/navigation_bar_height” to 1. Apply. Save. Tick.
8. Set “android:dimen/navigation_bar_frame_height” to 0. Apply. Save. Tick.
9. Enjoy!
Let me know in the thread if anything is unclear.
Thanks to @squee666 for an alternative solution that does not affect the keyboard! Try it out!
Credits:
Zachary Wander for the FabricateOverlay app and the instructions.
RikkaW for the Shizuku Api.
MishaalRahman, Quinny898 and various Redditors (especially LankeeM9 and audie-tron171) for the relevant settings.

Very nice, thank you for this!

Points 8 and 9 xan you be more specific.

Damn, it's too bad that the overlay system can't change fonts. I don't even want to install custom fonts, I just want to change the system default to the new Google font instead of Roboto. Without root.

Can we enable Fluid Navigation Gestures after applying a similar tweak?

tids2k said:
Points 8 and 9 xan you be more specific.
Click to expand...
Click to collapse
Basically you need to search "android:dimen/navigation_bar_height" by entering it in the search box. Then click on it. Then add the value in the value box and click "Apply". There are screenshots showing how it works here.

StrangerWeather said:
Basically you need to search "android:dimen/navigation_bar_height" by entering it in the search box. Then click on it. Then add the value in the value box and click "Apply". There are screenshots showing how it works here.
Click to expand...
Click to collapse
Thank you figured out eventually.

Guyinlaca said:
Can we enable Fluid Navigation Gestures after applying a similar tweak?
Click to expand...
Click to collapse
What do you mean?

Great! It works. Thanks!

But there seems to be one down-side ... when you enable the overlay the Google keyboard does not longer show the "down" marker to make the keyboard disappear. The android:dimen/navigation_bar_frame_height (0) is causing that. See attached 2 screenshots. First one is without overlay enabled, second one has overlay enabled. Notice how the little downward pointing arrow is gone on the second one.

foobar66 said:
But there seems to be one down-side ... when you enable the overlay the Google keyboard does not longer show the "down" marker to make the keyboard disappear. The android:dimen/navigation_bar_frame_height (0) is causing that. See attached 2 screenshots. First one is without overlay enabled, second one has overlay enabled. Notice how the little downward pointing arrow is gone on the second one.
Click to expand...
Click to collapse
Good point. However, you just need to swipe back for the keyboard to disappear.

StrangerWeather said:
Hi guys, I've seen several posts asking how to remove the Gesture Pill. It's easy if you're rooted, but it's also possible if you're not rooted.
Here is a step by step guide. There is also a huge amount of UI mods that can be made using the same method.
1. Download the Shizuku app from the Playstore
2. Start the Shizuku app by running the following adb command:
adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh
3. Download and install the latest FabricateOverlay release from Github
4. In FabricateOverlay click “Add Overlay”
5. Choose Android System
6. Click “Add”
7. Set “android:dimen/navigation_bar_height” to 0. Apply. Save. Tick.
8. Set “android:dimen/navigation_bar_frame_height” to 0. Apply. Save. Tick.
9. Enjoy!
Let me know in the thread if anything is unclear.
Credits:
Zachary Wander for the FabricateOverlay app and the instructions.
RikkaW for the Shizuku Api.
MishaalRahman, Quinny898 and various Redditors (especially LankeeM9 and audie-tron171) for the relevant settings.
Click to expand...
Click to collapse
What is the workaround for me that im rooted?

foobar66 said:
But there seems to be one down-side ... when you enable the overlay the Google keyboard does not longer show the "down" marker to make the keyboard disappear. The android:dimen/navigation_bar_frame_height (0) is causing that. See attached 2 screenshots. First one is without overlay enabled, second one has overlay enabled. Notice how the little downward pointing arrow is gone on the second one.
Click to expand...
Click to collapse
It might be possible to increase the bottom margin of the keyboard in system.ui. I'll check in a bit.
Edit: Actually, the handle is part of the navbar, which is the reason why it disappears when removing the navbar.

cultofluna said:
What is the workaround for me that im rooted?
Click to expand...
Click to collapse
Just open the Shizuku app and press "Start" in "Start (for rooted devices)".

So on Android 10, there was an overscan feature that allowed the 3 button navigation to be hidden and replaced with 3rd party navigation apps such as Fluid Navigation Gestures. This allowed swipe up from the bottom navigation much like OnePlus and Samsung offer. My curiosity is if this mod allows third party apps the hide and utilize the navbar.

Guyinlaca said:
So on Android 10, there was an overscan feature that allowed the 3 button navigation to be hidden and replaced with 3rd party navigation apps such as Fluid Navigation Gestures. This allowed swipe up from the bottom navigation much like OnePlus and Samsung offer. My curiosity is if this mod allows third party apps the hide and utilize the navbar.
Click to expand...
Click to collapse
Only if they integrate the Shizuku library into their app afaik.

I can confirm this working on my Pixel 3 XL on Android 12, no root, locked bootloader. Thank you so much for this!

StrangerWeather said:
Good point. However, you just need to swipe back for the keyboard to disappear.
Click to expand...
Click to collapse
Aha yes ... if you swipe above the keyboard it goes away ... did not know that! Thanks for that tip.

One question, how come that this sticks after reboot (even when disabling Shizuku/FabricateOverlay)?

foobar66 said:
One question, how come that this sticks after reboot (even when disabling Shizuku/FabricateOverlay)?
Click to expand...
Click to collapse
Basically you only need to give the app permission to change the settings (i.e. write to secure settings). Once the system setting is written it sticks. But if you want to change the value again you will need to go through the same process with both apps.