Hello all,
I just upgraded to the Moto g6, coming from the g5 with aokp ROM. My two most used and favorite features are the left and right arrows that appear in the navigation bar while typing, which allow the cursor to be accurately moved (annoyingly janky on the g6), and the ability to slide left or right over the notification bar to adjust the screen brightness without annoying extra swipes.
I was wondering if there is any way to get these two features on the Moto g6, as I have been missing them.
Thank your for your help!
raginhomosapien said:
Hello all,
I just upgraded to the Moto g6, coming from the g5 with aokp ROM. My two most used and favorite features are the left and right arrows that appear in the navigation bar while typing, which allow the cursor to be accurately moved (annoyingly janky on the g6), and the ability to slide left or right over the notification bar to adjust the screen brightness without annoying extra swipes.
I was wondering if there is any way to get these two features on the Moto g6, as I have been missing them.
Thank your for your help!
Click to expand...
Click to collapse
Those were features of the custom ROM you were using. Not the device itself.
That said, I enabled those features on mine with an Xposed module. Gravitybox. Works great. But, using Xposed, safetynet will fail. But if that's not an issue for you, Xposed is the way to go.
Magisk for root
Xposed for magisk (in magisk repo)
madbat99 said:
Those were features of the custom ROM you were using. Not the device itself.
That said, I enabled those features on mine with an Xposed module. Gravitybox. Works great. But, using Xposed, safetynet will fail. But if that's not an issue for you, Xposed is the way to go.
Magisk for root
Xposed for magisk (in magisk repo)
Click to expand...
Click to collapse
Thank you for the help!
I had asked about installing modules, but using the Xposed unity installer in magisk seemed to be what worked. somehow ended up with a very old clunky version of the app, which was not detecting that Xposed was installed. I'm all set to go, thanks again!
raginhomosapien said:
Thank you for the help!
I had asked about installing modules, but using the Xposed unity installer in magisk seemed to be what worked. somehow ended up with a very old clunky version of the app, which was not detecting that Xposed was installed. I'm all set to go, thanks again!
Click to expand...
Click to collapse
Great to hear. I use those features as well. Especially the arrows in nav bar for the cursor.
Related
My status and notification bars spread out and leave gaps.
How can I fix this?
I'm using apps which you can see in my screenshots.
Thank you in advance
I see that you're using Xposed and some modules. Did you install any module that uses/enhances/changes functionality of a Statusbar?
Maybe it's the StatusbarVolume?
I suggest disabling them in Xposed and then after reboot verify if the problem is still there. Most likely you will find the cause.
SquiffyGrain6 said:
I see that you're using Xposed and some modules. Did you install any module that uses/enhances/changes functionality of a Statusbar?
Maybe it's the StatusbarVolume?
I suggest disabling them in Xposed and then after reboot verify if the problem is still there. Most likely you will find the cause.
Click to expand...
Click to collapse
okay I turned off a few xposed modules and a few apps. that didn't work.
I actually installed all those apps during one day. Then I remember it happening quite early on during the day.. and one of the first programs I installed was elixir. After uninstalling elixir 2 I found out this app was the problem.
I installed it again and the problem reappeared after I tried to set a 'status bar'
Anyway, what Elixir 2 actually does is leave a completely transparent icon in the notification bar. I removed this with 'notifyclean'.
I'm definitely not a technoob, just a 1 week old root noob. Thanks for heading me in the right direction. Giving you a 'thanks'
Addition Info:
In fact, Elixir decided to stop working after using notifyclean. Elixir is okay but seems like I'm gonna just have to get rid of if since I really like notifyclean.
No problem, glad you sorted that all out
Disclaimer: I'm super noob with Xposed and GravityBox.
I'm running OxygenOS and I played with a bunch of tweaks in GravityBox, they all work just fine. But, with pie controls, I'm not quite sure about a thing here. I enabled it by tapping 'Always' in the option, that was supposed to enable the pie controls if I'm not wrong, but that didn't. Can someone tell me what am I doing wrong here?
javed24 said:
Disclaimer: I'm super noob with Xposed and GravityBox.
I'm running OxygenOS and I played with a bunch of tweaks in GravityBox, they all work just fine. But, with pie controls, I'm not quite sure about a thing here. I enabled it by tapping 'Always' in the option, that was supposed to enable the pie controls if I'm not wrong, but that didn't. Can someone tell me what am I doing wrong here?
Click to expand...
Click to collapse
You are in the wrong section. We have a support thread for GravityBox [LP] and it's here: http://forum.xda-developers.com/xposed/modules/app-gravitybox-v5-0-0alpha-tweak-box-t3037566
Anyway, check pie trigger position settings. Note, that if your device has navigation bar, pie won't work with bottom trigger set. Either use different screen edge or take advantage of expanded desktop to hide navigation bar and automatically enable pie when expanded desktop is turned on.
Are there any ADB commands (or apps) that allow you to hide the navigation bar on Android 11 Beta 1? The Navigation Gestures app (that I was using) crashed when Beta 1 began running.
The Hid Nav Bar app isn't doing the trick now either. It doesn't crash, it just doesn't hide the pill on the bottom.
"adb shell"
"wm overscan 0,0,0,-120"
"wm overscan 0,0,0,0"
this will hide your navigation bar.
Nabil Prodhan said:
"adb shell"
"wm overscan 0,0,0,-120"
"wm overscan 0,0,0,0"
this will hide your navigation bar.
Click to expand...
Click to collapse
Have you tried this already on the Pixel 4xl running the 1st Android 11 Beta? It works, then?
Eduardo1974 said:
Have you tried this already on the Pixel 4xl running the 1st Android 11 Beta? It works, then?
Click to expand...
Click to collapse
no, I haven't yet tried, but this is a suggestion to hide nav.
Eduardo1974 said:
Are there any ADB commands (or apps) that allow you to hide the navigation bar on Android 11 Beta 1? The Navigation Gestures app (that I was using) crashed when Beta 1 began running.
Click to expand...
Click to collapse
Use the Magisk module. It works perfectly on beta 1.
Awesome! I'm not rooted, though
EMJI79 said:
Use the Magisk module. It works perfectly on beta 1.
Click to expand...
Click to collapse
So, I tried this, and it worked great for a couple days. Today I woke up and my phone was on 3 button nav. Couldn't change it in settings. Rebooted, got a corrupt device alert, still not able to change in settings. Reboot again, no error, still no dice. Unchecked this and everything works again.
gettinwicked said:
So, I tried this, and it worked great for a couple days. Today I woke up and my phone was on 3 button nav. Couldn't change it in settings. Rebooted, got a corrupt device alert, still not able to change in settings. Reboot again, no error, still no dice. Unchecked this and everything works again.
Click to expand...
Click to collapse
Strange, I haven't had issues after weeks of use.
I use Magisk Canary if that makes a change.
Also the module has been updated recently (I only saw that today).
Might want to try again as the update states "hotfix for Android 11 beta":
Not working on beta 3 for me
I tried the Magisk module today, and it appears that when enabled, it does indeed disable the Android gesture navigation. Unfortunately, it looks like Android detects this and defaults to the 3-button navbar instead.
Going back to Android's navigation selection settings at that point shows only the 3-button and 2-button nav types available so long as the module is enabled.
Once the module is disabled, the gesture navigation option does up again as a choice.
Perhaps if the module disabled all three options Android offers, there would be nothing to default to, lol.
At any rate, it doesn't seem to work for me.
[FOR REFERENCE ONLY]
Problem solved!
The confounding variable was NOT Xposed Framework, but conena's Gesture Control app that was set up to use Immersive Mode to hide the navigation bar. And according to this post that I landed on purely by chance, if you don't exempt the Lockscreen Settings app, it causes all these problems.
Note that this problem has nothing to do with the app, it's the Immersive Mode setting to blame, on which any setting change at all will cause these same problems (to be fair, conena's app does preemptively discourage this)
Solution
Use a Substratum overlay to hide the navbar instead; do NOT use GravityBox to do that by setting navbar height to 0, or qemu.hw.mainkeys=1 in build.prop (which doesn't work, BTW). Next, backup your gesture bar data and wipe the data of the app, then restore the bar data – just don't fiddle with that Immersive Mode setting again!
Well, some explanation is in order because it wouldn't make for a great thread title:
I am running the last stock Oreo build on this G8441, which is 47.1.A.12.20, for the primary reason of being able to use rovo89's Xposed Framework because the original XPrivacy module that's vitally important to me does not run on any of the EdXposeds or LSPoseds.
Using systemless Xposed with the latest Magisk version (and older ones too, nothing changes) I find that if I were to set a lockscreen to anything other than "None" and reboot, I will have times where I simply can't see the display when pressing the power button -- but weirdly enough the touchscreen still keeps taking touch input! The only way around is to remove the lockscreen, reboot, then set your locking method and try not to have it restart for any reason.
It's quite obvious that systemless Xposed is causing this problem (Xposed can't be installed normally on this firmware version) because this problem can be reproduced even without any modules active. But I'm at a complete loss as to what's actually causing this lockscreen interference, because I've tried taking system logs with and without Xposed and there's simply nothing at all different except it taking insanely long times for the display to activate upon unlock (but the touch input working just fine for some reason?) and there's a small, dim red LED near the proximity sensor that stays stuck as long as the display is.
Please help me, I'm absolutely out of ideas -- and no, I can't upgrade to Pie, I have to stay on Oreo for the sake of the XPrivacy module.
So it seems like 47.1.A.12.75 is the last problem-free Oreo version for normal Xposed Framework, and I wouldn't mind using that, if it weren't for the fact that there doesn't seem to be any VoLTE-activating SIN file for India for it below 47.1.A.12.270. There's a 2G phaseout in progress with the largest carrier and it's only a matter of time before there'll be no fallback network and I'll have to have VoLTE at any cost.
My stock Pixel 5 has been slowly going downhill and I was considering installing a custom ROM in an attempt to breath some new life into it. One of the things I've greatly missed since Google introduced an update is being able to hide the nav bar and use the FluidNG app to customize my gesture navigation. Would installing a custom ROM give me this option again? Or is this limitation something baked into AOSP?
skytbest said:
My stock Pixel 5 has been slowly going downhill and I was considering installing a custom ROM in an attempt to breath some new life into it. One of the things I've greatly missed since Google introduced an update is being able to hide the nav bar and use the FluidNG app to customize my gesture navigation. Would installing a custom ROM give me this option again? Or is this limitation something baked into AOSP?
Click to expand...
Click to collapse
Default AOSP roms do not have that function. I'm using the FNG app as well with a magisk module that disables the native gestures. It's "Fullscreen/Immersive Gesture Tweaks." On the page, there's a disclaimer about Fluid but it's wrong. My settings are Fullscreen > low tolerance > disable back swipe on left and right side. Obviously you need root on any rom that supports Magisk.