For those who struggle with this problem on android 10. The black bar on keyboard, you can type this on adb:
--> Start with:
ADB THING:
Windows ADB Setup https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Enable USB debugging in Developer mode and authorization will pop-up when is connect with the PC.
Open and type in CMD --> adb shell
Then wm overscan 0,0,0,-55 it's better because(-75) may interfere with gestures...
wm overscan 0,0,0,-25 is also good
bar will be gone! . For rooted users you can just type wm overscan 0,0,0,-50 on terminal.
It is ok to set for -50 if there is some problems with the gestures
Default value is 0,0,0,0
thx to @elmarian756
surdustef said:
For those who struggle with this problem on android 10.0.1. The black bar on keyboard, you can type this on adb:
HTML:
adb shell wm overscan 0,0,0,-75
and bar will be gone! . For rooted users you can just type wm overscan 0,0,0,-75 on terminal.
Default value is 0,0,0,0
thx to @elmarian756
Click to expand...
Click to collapse
I get this message: "wm command not found"
pcplayer said:
I get this message: "wm command not found"
Click to expand...
Click to collapse
Try to use the commands separately
You can also try this on the terminal emulator in your phone.
Just use su wm overscan 0,0,0-75
fathomer said:
You can also try this on the terminal emulator in your phone.
Just use su wm overscan 0,0,0-75
Click to expand...
Click to collapse
Thank you!! Su at the beginning was the solution!
Set to -122 for me ?
EDIT : nope, it also moves the goats notifications so -75 is better
Helped a lot
Thank you very much for your sharing!
Thx for the tip
Would have gave you 2 thumbs up if it would have let me. It's the little things that make so much difference.
tried this for 2 days and it seems to be interfere with the A10 gestures. In some apps it's real hard to swipe up to go to home
aleck0112 said:
tried this for 2 days and it seems to be interfere with the A10 gestures. In some apps it's real hard to swipe up to go to home
Click to expand...
Click to collapse
You can bigger values than -75
I have discovered that the fullscreen gestures (Q) module for magisk fixes this issue in both landscape and portrait mode.
Ghibif said:
I have discovered that the fullscreen gestures (Q) module for magisk fixes this issue in both landscape and portrait mode.
Click to expand...
Click to collapse
Works great, Thank you!
Ghibif said:
I have discovered that the fullscreen gestures (Q) module for magisk fixes this issue in both landscape and portrait mode.
Click to expand...
Click to collapse
amazing, thank you so much!
Installed this and set wm overscan to 0,0,0,5 and it's perfect for me. Without setting this the Swiftkey keyboard sits kinda too low for me and looks a bit weird, 5 is perfect on 7T
Ghibif said:
I have discovered that the fullscreen gestures (Q) module for magisk fixes this issue in both landscape and portrait mode.
Click to expand...
Click to collapse
I second this. Much easier than the command and works great.
GlitchMob said:
I second this. Much easier than the command and works great.
Click to expand...
Click to collapse
most important is, it does not mess with full screen gesture, while the command does
Nice to know... Tried it and works perfectly! Thx a lot
Hey, I just wanted to say thanks to all of you. It was bothering me so much!
Related
Does anyone experience extreme lag when using immersive mode on Oreo? I find that my phone lags when trying to turn the screen back on. It is especially evident when the screen has been off for more than 10 minutes. It is so bad that I cannot answer phone calls if the screen has been off for a few minutes as I hear the ringtone but the screen stays black. Does anyone know of a solution ? Immersive mode is a must have for me and I will have to revert to nougat for the time being if no solution is available.
I had the same problem and battery drain. Try using the following command to enter immersive mode. It fixed the lag and battery drain for me.
adb shell settings put global policy_control immersive.navigation=apps,-com.google.android.googlequicksearchbox
bokononfoma said:
I had the same problem and battery drain. Try using the following command to enter immersive mode. It fixed the lag and battery drain for me.
adb shell settings put global policy_control immersive.navigation=apps,-com.google.android.googlequicksearchbox
Click to expand...
Click to collapse
This did the trick! I just changed .navigation to .full so I could get the status bar to hide too.
Thank you
bokononfoma said:
I had the same problem and battery drain. Try using the following command to enter immersive mode. It fixed the lag and battery drain for me.
adb shell settings put global policy_control immersive.navigation=apps,-com.google.android.googlequicksearchbox
Click to expand...
Click to collapse
Do you enter this command into terminal emulator? Just the same way you wrote starting with "adb shell."
coolhandz said:
Do you enter this command into terminal emulator? Just the same way you wrote starting with "adb shell."
Click to expand...
Click to collapse
In terminal without "adb shell"
bokononfoma said:
I had the same problem and battery drain. Try using the following command to enter immersive mode. It fixed the lag and battery drain for me.
adb shell settings put global policy_control immersive.navigation=apps,-com.google.android.googlequicksearchbox
Click to expand...
Click to collapse
What kind of battery drain? I had lag on Oreo before I went back to Nougat, and also weird battery issues like apps reporting hours of use when they were only on screen for minutes.
If nav bar hiding was the cause of both issues I might try Oreo again.
Ezrem said:
What kind of battery drain? I had lag on Oreo before I went back to Nougat, and also weird battery issues like apps reporting hours of use when they were only on screen for minutes.
If nav bar hiding was the cause of both issues I might try Oreo again.
Click to expand...
Click to collapse
Yes. I had similar experience. I did a factory reset but still had the problem. Hiding the nav bar was the cause, and using this command fixed the problem.
0hfrankieboy said:
This did the trick! I just changed .navigation to .full so I could get the status bar to hide too.
Thank you
Click to expand...
Click to collapse
Wow, and all this time I thought Oreo was a pos, buggy, battery sucking release....
Phone feels normal again. This fixed all my issues!! Who would've thought...
I want to say that I too,...had the same lagging issue. And has worked for me too. Thank you both!!!
Sorry for sticking my nose in here, but how are you guys enabling immersive mode? It's not native to Oreo is it?
JimSmith94 said:
Sorry for sticking my nose in here, but how are you guys enabling immersive mode? It's not native to Oreo is it?
Click to expand...
Click to collapse
Jim unfortunately it is not a native option in oreo. As far as I know one must have root and run the commands posted above in terminal or through adb.
0hfrankieboy said:
Jim unfortunately it is not a native option in oreo. As far as I know one must have root and run the commands posted above in terminal or through adb.
Click to expand...
Click to collapse
Thanks Frank. I've been using Custom Navigation Bar: https://play.google.com/store/apps/details?id=xyz.paphonb.systemuituner&hl=en but it toggles off or on for all apps/screens. I miss the Xposed Force Immersive Mode that let you pick and choose which apps you wanted to "immerse".
Is there a way to couple this command with Tasker so we can pick and choose which apps are immersive? That's how I've been doing it with Custom Navigation Bar, i.e. creating immersive profiles and enabling/disabling them for specific apps. Now thanks to this thread, I'm finding out it's probably what's causing my wake problems.
Thank you sir, this has been bothering me so long since Oreo update.
I have done factory reset, done clean update, cleaned the internal storage etc...
your comments really works for me.
bokononfoma said:
I had the same problem and battery drain. Try using the following command to enter immersive mode. It fixed the lag and battery drain for me.
adb shell settings put global policy_control immersive.navigation=apps,-com.google.android.googlequicksearchbox
Click to expand...
Click to collapse
Guys i use "tiles" and among the various options there is the tile for "immersive mode".
Works with all apps.
Just Whatsapp has some problem: if you enter emoji, the insertion bar disappears and you have to click the "back" button to see everything.
boojay said:
Is there a way to couple this command with Tasker so we can pick and choose which apps are immersive? That's how I've been doing it with Custom Navigation Bar, i.e. creating immersive profiles and enabling/disabling them for specific apps. Now thanks to this thread, I'm finding out it's probably what's causing my wake problems.
Click to expand...
Click to collapse
You can run the command as a shell, you also have to check use root.
Sent from my Pixel XL using XDA Labs
Atomregen said:
You can run the command as a shell, you also have to check use root.
Click to expand...
Click to collapse
I was afraid of that. My preference would be to have a non-root method, but it sounds like the only workaround is to root.
Thanks though.
boojay said:
I was afraid of that. My preference would be to have a non-root method, but it sounds like the only workaround is to root.
Thanks though.
Click to expand...
Click to collapse
Here is an article, where it is described without root.
Atomregen said:
Here is an article, where it is described without root.
Click to expand...
Click to collapse
Sweet, will have a look! Thx
So I've been testing another workaround for the past 24 hours and it seems to be working. It's actually a really simple solution that makes use of my first post about using Tasker to enable/disable immersive profiles for specific apps. All I did was add a task that disabled immersive mode whenever I turn off my screen, and voila, no more delays when waking the phone.
Hey, trying to swap my recent and back buttons. I've tried Custom Navigation Bar app, as well as the adb shell command (adb shell settings put secure sysui_nav_bar "space,recent;home;back,space").
While both methods (the same, from what I understand) swap the buttons, the buttons are spaced closer together than they used to be. I suppose I can just get used to it, but it looks funny to me. Anyone have a different solution?
Recent, space; Home; Space, back
The 'spaces' have to be swapped in their respective space. At least this is how I remember when in the same sit
dontbeweakvato said:
Recent, space; Home; Space, back
The 'spaces' have to be swapped in their respective space. At least this is how I remember when in the same sit
Click to expand...
Click to collapse
That command makes the buttons too far apart. It's weird that these commands can't get the default spacing correct
I think there's space for 5 icons but some require a 'space' within their icon field. What were you using custom navbar app?
dontbeweakvato said:
I think there's space for 5 icons but some require a 'space' within their icon field. What were you using custom navbar app?
Click to expand...
Click to collapse
Yeah, I tried both custom navbar as well as through adb, but the spacing is off for both. but I believe they basically do it the same way. Interestingly enough, without inverting the recent and back buttons, the spacing gets messed up by custom navbar. It's not a huge deal, just something I noticed
Hopefully Google bakes it into 8.1 system tuner
beezar said:
Yeah, I tried both custom navbar as well as through adb, but the spacing is off for both. but I believe they basically do it the same way. Interestingly enough, without inverting the recent and back buttons, the spacing gets messed up by custom navbar. It's not a huge deal, just something I noticed
Hopefully Google bakes it into 8.1 system tuner
Click to expand...
Click to collapse
This method still works worked for me on Android P beta. The gestures work as they should after the swapping the buttons. I left in "recent" in the script. No issues when doing this.
Thanks Fatphatboy88
https://forum.xda-developers.com/showpost.php?p=74133909&postcount=4
You have to install the ADB and fastboot
plug you phone into your computer
turn on debugging mode
open up a command prompt window in the adb folder on your computer
these are the following commands I used. I did notice if you have small hands you could type ";home;recent,back" and it will put the home icon in the middle and the other two buttons on the right. What ever button you put the semi colons around will be in the center of the screen.
Type
adb shell
settings put secure sysui_nav_bar "space,recent;home;back,space"
localfinesse said:
This method still works worked for me on Android P beta. The gestures work as they should after the swapping the buttons. I left in "recent" in the script. No issues when doing this.
Thanks Fatphatboy88
https://forum.xda-developers.com/showpost.php?p=74133909&postcount=4
You have to install the ADB and fastboot
plug you phone into your computer
turn on debugging mode
open up a command prompt window in the adb folder on your computer
these are the following commands I used. I did notice if you have small hands you could type ";home;recent,back" and it will put the home icon in the middle and the other two buttons on the right. What ever button you put the semi colons around will be in the center of the screen.
Type
adb shell
settings put secure sysui_nav_bar "space,recent;home;back,space"
Click to expand...
Click to collapse
Sorry to revive an old thread, but I didn't want to start a new one for the same problem... Can anyone tell me if this method works on Pie stock? Do I need to root/unlock bootloader? My phone is almost completely factory, and I love it aside from the back/recent buttons being different than I'm used to.
Smoghog said:
Sorry to revive an old thread, but I didn't want to start a new one for the same problem... Can anyone tell me if this method works on Pie stock? Do I need to root/unlock bootloader? My phone is almost completely factory, and I love it aside from the back/recent buttons being different than I'm used to.
Click to expand...
Click to collapse
I believe you need to be rooted.
Smoghog said:
Sorry to revive an old thread, but I didn't want to start a new one for the same problem... Can anyone tell me if this method works on Pie stock? Do I need to root/unlock bootloader? My phone is almost completely factory, and I love it aside from the back/recent buttons being different than I'm used to.
Click to expand...
Click to collapse
check out https://play.google.com/store/apps/details?id=xyz.paphonb.systemuituner no root required
uicnren said:
check out https://play.google.com/store/apps/details?id=xyz.paphonb.systemuituner no root required
Click to expand...
Click to collapse
I looked at that, but the string of bad reviews turned me off of using it. I would much prefer the clean and simple fix that localfinesse highlighted above, if possible.. I may give it a shot even though I'm not rooted, just to see if it works.
I've been using it since I got the phone last year;works great. I am rooted. The only tiny glitch I had was when I switched to using the gesture navigation. After I switched back to the three buttons, the recent menu was gone. However, I went into the app and it appeared again. It works just as it had before.
localfinesse said:
This method still works worked for me on Android P beta. The gestures work as they should after the swapping the buttons. I left in "recent" in the script. No issues when doing this.
Thanks Fatphatboy88
https://forum.xda-developers.com/showpost.php?p=74133909&postcount=4
You have to install the ADB and fastboot
plug you phone into your computer
turn on debugging mode
open up a command prompt window in the adb folder on your computer
these are the following commands I used. I did notice if you have small hands you could type ";home;recent,back" and it will put the home icon in the middle and the other two buttons on the right. What ever button you put the semi colons around will be in the center of the screen.
Type
adb shell
settings put secure sysui_nav_bar "space,recent;home;back,space"
Click to expand...
Click to collapse
Just a follow-up for anyone who comes along to this thread later - You CAN do the above method suggested by localfinesse even if you are not rooted. It was easy to just go ahead and do it that way since I would have had to have to use adb commands from the pc to authorize the custom navigation bar app, anyhow. Feels much better now
Edit: I'm on Android Pie final, no root or unlock. All you need is Developer Options opened and USB Debugging enabled.
Follow-up questions: Does anyone know what else can be added in the two extra spaces? Is there a list somewhere? And Is it possible to launch camera from one?
Smoghog said:
Just a follow-up for anyone who comes along to this thread later - You CAN do the above method suggested by localfinesse even if you are not rooted. It was easy to just go ahead and do it that way since I would have had to have to use adb commands from the pc to authorize the custom navigation bar app, anyhow. Feels much better now
Edit: I'm on Android Pie final, no root or unlock. All you need is Developer Options opened and USB Debugging enabled.
Follow-up questions: Does anyone know what else can be added in the two extra spaces? Is there a list somewhere? And Is it possible to launch camera from one?
Click to expand...
Click to collapse
Idk if you can do that with the adb shell command. But you *can* use Custom Navigation Bar without root. It also offers extra left/right buttons, and you can assign functions to those buttons (including launching apps).
The adb shell commands work perfect. Used it on my work pixel 2.
Hi,
USB-C alt mode is working fine with the 5G, but I can't find the Desktop mode in the dev settings,
Is it possible to activate it with adb or any way ?
Thx
Was about to ask ?
I checked with adb shell, there is no force_desktop_mode_on_external_displays settings
Force Desktop mode is present on V4.09 !
adrienfr said:
I checked with adb shell, there is no force_desktop_mode_on_external_displays settings
Click to expand...
Click to collapse
With ROM Common v4.09, force_allow_on_external and force_desktop_mode_on_external_displays are presents in settings with adb shell !
So do you have to use adb to make it work?
I just tried that, and it does sort of work, but there is no actual desktop mode installed, so it's very buggy and doesn't work well or look good. The only way to control the "desktop" screen is with peripherals, like a mouse and keyboard, as there is no touchpad-like interface on the phone. If you do have all that, and you have enabled "Enable freeform windows" and "Force activities to be resizable", all apps should work.
usergentoo said:
So do you have to use adb to make it work?
Click to expand...
Click to collapse
Yes, with ADB
adb shell
settings put global force_desktop_mode_on_external_displays 1
settings put global force_allow_on_external 1
Reboot the phone and it's ok
You can install Sentio to have a full desktop environment, but with sentio, you have to disable force_desktop_mode_on_external_display (force_desktop_mode_on_external_display 0) to get it work properly
Insyder28 said:
I just tried that, and it does sort of work, but there is no actual desktop mode installed, so it's very buggy and doesn't work well or look good. The only way to control the "desktop" screen is with peripherals, like a mouse and keyboard, as there is no touchpad-like interface on the phone. If you do have all that, and you have enabled "Enable freeform windows" and "Force activities to be resizable", all apps should work.
Click to expand...
Click to collapse
Sentio app, or the XDA apk Lawnchair are desktop like apps that work good
I have also tried with UserLand and it works like a charm
You can also install SecondScreen app to manage the out display size : https://play.google.com/store/apps/details?id=com.farmerbb.secondscreen.free
adrienfr said:
Sentio app, or the XDA apk Lawnchair are desktop like apps that work good
I have also tried with UserLand and it works like a charm
Click to expand...
Click to collapse
Yes, true, but you have to set it as your default launcher to work properly, and the 5G doesn't allow you to do that yet. I haven't gotten Lawnchair or Sentio to display properly on the second screen.
Insyder28 said:
Yes, true, but you have to set it as your default launcher to work properly, and the 5G doesn't allow you to do that yet. I haven't gotten Lawnchair or Sentio to display properly on the second screen.
Click to expand...
Click to collapse
You don't need to set Sentio as default launcher, for me it's really working great, i can work like i used to work with a PC
Sentio launches when you connect a new screen and set the display in landscape mode and with second screen the display is resized
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!
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.