Hi,
I broke the damn touchscreen on my nexus 4 with paranoid. Until I can get it fixed or get another phone I'm using adb and an bluetooth mouse to navigate, but I can't get the statusbar to come down because Immersive mode is enabled. Has anyone an idea how to do this with adb or otherwise?
Thanks
Related
Simply put, dragging down the settings & notifications, as well as using the pie controls doesn't work if you're using immersive mode & a mouse. USB or Bluetooth doesn't matter. To me it looks like the input is being registered below the bars, but I'm no dev so take that with a grain of salt.
Anyone happen to know of some way to solve this or do I just have to hope that the devs sort it out in the future?
Hi guys a noob here!
So here's my problem: I rooted my phone and all that (still stock android) however during my time using my phone rooted i decided i wanted to use my phone in full-screen, as i already installed gravity box with xposed installer, i used gravity box's 'expanded desktop' mode and i have turned off expanded desktop however the navigation bar is gone. Any ideas whats happened? What do i do to get it back?
Try to check Gravity Box´s Expanded desktop settings.
Maybe there is something set to prevent navigation buttons to be toggled after turning Expanded desktop off.
Davoss said:
Try to check Gravity Box´s Expanded desktop settings.
Maybe there is something set to prevent navigation buttons to be toggled after turning Expanded desktop off.
Click to expand...
Click to collapse
I've looked around in gravity box yet i haven't found anything that could be causing this problem, anymore ideas?
I just RMA'd my phone after thinking this was a hardware issue. I use the custom navigation bar app by paphonb and my phone lags trying to unlock it using both fingerprint reader and hardware power button. Sometimes not even unlocking after multiple attempts. Is there any command i can run through adb to fix this issue?
Visit here: https://forum.xda-developers.com/pixel-xl/help/android-oreo-immersioln-mode-problems-t3666479
Cristiano Matos said:
Visit here: https://forum.xda-developers.com/pixel-xl/help/android-oreo-immersioln-mode-problems-t3666479
Click to expand...
Click to collapse
I tried to use the global policy_control immersive.navigation=apps,-com.google.android.googlequicksearchbox command however it keeps returning an error reading that the command is not an identifier
jordando said:
I tried to use the global policy_control immersive.navigation=apps,-com.google.android.googlequicksearchbox command however it keeps returning an error reading that the command is not an identifier
Click to expand...
Click to collapse
The 4th last comment on the link above is a Tasker method that works flawlessly. It sets navigation on when screen is off so when you unlock your phone it's not in immersive mode so it unlocks as normal plus you can have or not whichever apps you like in immersive or not. I never used Tasker until I read that comment, I couldn't live without it now
Sent from my Pixel XL using XDA Labs
I downloaded Tiles off of the play store. I had tried shortcutter and that worked but the phone wouldn't wake up or would take forever to wake when full immersive mode was enabled. Got rid of shortcutter and got https://play.google.com/store/apps/details?id=com.rascarlo.quick.settings.tiles. Have to enter the adb command but works flawlessly. Screen wakes as normal and no bugs. I'm stock non root
Sent from my Pixel XL using Tapatalk
Ive been trying to work around issues similar to this myself.
Ive already noticed screen burn on my pixel, due to the (almost constantly) black navigation bar.
Originally i used oreo tiles in the app store (as mentioned above)to enable immersive mode, but had horrible response time when trying to wake my phone up (common problem).
Then i tried enabling immersive through terminal emulator in the app store by typing "su" and then "settings put global policy_control immersive.navigation=apps,-com.google.android.googlequicksearchbox" and for the most part it worked, but i would often get stuck in apps. i would swipe up to press the back button and instead of sending the back action the nav bar would immediately hide again. this would leave me to swipe up and trying to double tap back super quick before it went hidden.
For the third attempt i used the twrp Oreo aroma mod installer in the themes and apps section to completely disable the nav bar and attempted to use LMT for navigation, but LMT would occasionally crash and not allow me to return to the app drawer to restart the service. So that was a failure.
I ended up using "nav bar apps" to simply recolor the nav bar based on the application that is open, so instead of stationary black, it changes colors.
Just sharing my experiences, maybe youll catch something out of it that will help you.
So, while I have my phone on my desk the Always on Display will occasionally disappear leaving me with a blank screen. The only thing that gets the phone to wake is any type of alert/notification or physical push of the power button. I have Double Tap to check phone enabled, and when the AOD is active it will work, but when AOD does its little disappearing act, it wont.
Anyone else having this problem?
I know that the AOD is set to turn off when the phone is in my pocket and I determined that the sensor is in the top left part of the screen, but there is nothing blocking the sensor when AOS decides to turn off. I'm almost certain the issue is tied to that feature... unless I just have a defective phone.
EyeBeeNY said:
So, while I have my phone on my desk the Always on Display will occasionally disappear leaving me with a blank screen. The only thing that gets the phone to wake is any type of alert/notification or physical push of the power button. I have Double Tap to check phone enabled, and when the AOD is active it will work, but when AOD does its little disappearing act, it wont.
Anyone else having this problem?
I know that the AOD is set to turn off when the phone is in my pocket and I determined that the sensor is in the top left part of the screen, but there is nothing blocking the sensor when AOS decides to turn off. I'm almost certain the issue is tied to that feature... unless I just have a defective phone.
Click to expand...
Click to collapse
Have you been messing with Immersive Mode where you hide the nav/status bars?
mine does this occasionally too. not sure why. i assumed it was an unfortunate side effect of setting my phone to immersive mode.
Did you install Greenify? I experienced a similar issue with Greenify installed.
byproxy said:
mine does this occasionally too. not sure why. i assumed it was an unfortunate side effect of setting my phone to immersive mode.
Click to expand...
Click to collapse
You can fix the immersive mode causing hangups by running this command.
adb shell settings put global policy_control immersive.full=apps,-com.google.android.googlequicksearchbox
can use .full for full immersive, .navigation to hide nav bar, and .status to hide status bar
Thanks for the tips, all. I am not running any third party apps to alter anything stock on the phone. I'm not exactly sure what immersive mode is or how to activate it, but I haven't changed any settings in the phone other than your typical changes like font size, wallpapers and notification tones.
I do have an app called Calls Blacklist to block unknown and private calls, which Ive been getting a lot of lately. Perhaps that app's not playing nice with the AOD?
henderjr said:
You can fix the immersive mode causing hangups by running this command.
adb shell settings put global policy_control immersive.full=apps,-com.google.android.googlequicksearchbox
can use .full for full immersive, .navigation to hide nav bar, and .status to hide status bar
Click to expand...
Click to collapse
do i need to undo the adb command i used originally?
byproxy said:
do i need to undo the adb command i used originally?
Click to expand...
Click to collapse
No should just be able to run the command I posted above
I narrowed it down to the Call Blocker app. Just applied the November security patch and now it happens everytime the app blocks an incoming call. I haven't uninstalled the app yet, but when I do I will update the thread to confirm my theory.
Thanks to everyone for their input.
I'm on Oreo and have enabled the navigation dock. Also turned off the navigation bar.
But there is no setting to completely block the bar from appearing.
Many a times while typing, the bar pops up making the entire typing a mess.
Am I missing something?
Is there any way to completely turn off the navigation bar?
Open adb and fastboot commands.. runb adb shell
Type wm overscan 0,0,0,-122 you have to play eith the last number to get it perfect for you