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.
Related
Hey there. I was wondering if it's possible to double tap to lock screen inside apps? For instance - I'm in a gallery and when I double tap it locks the screen.
The double tap lock screen function works fine when you're on the home screen, but not in any app.
Not that I know of since with Android, the app (activity) that has the focus on the screen accepts all the taps.
You could try swiping down near where the status bar would be to make it appear and then double tap that. That's how I get it to work with Nova launcher. Well, I don't have to swipe down since the status bar is there. I just double tap the status bar to turn off the phone.
I use knock to turn on the phone.
Use it with Nova as well.
Sent from my LG-D850 using Tapatalk
iBolski said:
Not that I know of since with Android, the app (activity) that has the focus on the screen accepts all the taps.
You could try swiping down near where the status bar would be to make it appear and then double tap that. That's how I get it to work with Nova launcher. Well, I don't have to swipe down since the status bar is there. I just double tap the status bar to turn off the phone.
I use knock to turn on the phone.
Click to expand...
Click to collapse
Didn't even thought about it, I'll stick to this method for now. Thanks
Danielsbee said:
Didn't even thought about it, I'll stick to this method for now. Thanks
Click to expand...
Click to collapse
There's also a reason they don't have this feature added. What if you were trying to play a game and everytime you tapped the screen too quickly it turned off? Or you were going through some menu fast enough that it registered you tapping two different options as a double-tap. There would have to be some sort of per-app filter like the stock rom has for hiding the nav buttons in certain apps. Not saying this idea couldn't work, because if you or someone else ever gets it working I'd be glad to use it!
acparker18 said:
There's also a reason they don't have this feature added. What if you were trying to play a game and everytime you tapped the screen too quickly it turned off? Or you were going through some menu fast enough that it registered you tapping two different options as a double-tap. There would have to be some sort of per-app filter like the stock rom has for hiding the nav buttons in certain apps. Not saying this idea couldn't work, because if you or someone else ever gets it working I'd be glad to use it!
Click to expand...
Click to collapse
That's true, but I was asking the question because when my phone is flat on the table or something with gallery opened, it's uncomfortable to slide your finder to the back of the phone to lock the screen so I wanted to know if there's a chance to lock it with tapping. But when I'm playing games, it's different story - I already have my fingers on the back of the case so it's no longer uncomfortable to lock it.
Danielsbee said:
That's true, but I was asking the question because when my phone is flat on the table or something with gallery opened, it's uncomfortable to slide your finder to the back of the phone to lock the screen so I wanted to know if there's a chance to lock it with tapping. But when I'm playing games, it's different story - I already have my fingers on the back of the case so it's no longer uncomfortable to lock it.
Click to expand...
Click to collapse
That's where I'd say swipe down to show the notif bar and then double tap the notif bar. That's what I do so I don't have to pick up the phone to turn off the screen. Then, using a knock pattern, I can turn on and unlock the phone via the knock pattern. Don't have to double tap the phone to wake it up and then unlock it (either via pattern or pin). Instead, with knock, just knock the pattern and it turns on and unlocks all at once. Love it!
iBolski said:
That's where I'd say swipe down to show the notif bar and then double tap the notif bar. That's what I do so I don't have to pick up the phone to turn off the screen. Then, using a knock pattern, I can turn on and unlock the phone via the knock pattern. Don't have to double tap the phone to wake it up and then unlock it (either via pattern or pin). Instead, with knock, just knock the pattern and it turns on and unlocks all at once. Love it!
Click to expand...
Click to collapse
Yeah. Like I said previously, I'll be using this method
If you use Xposed and G3 tweakbox, there is an option to double tap the nav bar to lock the screen as well.
This will give you a place at the top and bottom of the display to lock the screen when in an app (or using a launcher replacement).
Artimis said:
If you use Xposed and G3 tweakbox, there is an option to double tap the nav bar to lock the screen as well.
This will give you a place at the top and bottom of the display to lock the screen when in an app (or using a launcher replacement).
Click to expand...
Click to collapse
I don't see why to use that option to 'enable' it when it is already enabled and working in default.
Danielsbee said:
I don't see why to use that option to 'enable' it when it is already enabled and working in default.
Click to expand...
Click to collapse
By default it works on the status bar (top of the screen). The option in G3 tweaksbox allows it to work on the Nav bar (bottom of screen) as well which is not enabled by default.
Artimis said:
By default it works on the status bar (top of the screen). The option in G3 tweaksbox allows it to work on the Nav bar (bottom of screen) as well which is not enabled by default.
Click to expand...
Click to collapse
Oh then it's a nice option to enable then.
I got confused about the nav bar, I thought it was the status bar.
But the tweaksbox requires root which I don't want to do :s.
You don't need to pull down the notification bar at all to double tap to turn the screen off.
You just double tap the very top of the screen where your notification bar would be.
Is there a way to adjust the delay in auto hide of the navigation and notification areas?
Additionally to anyone using immersive mode. Does it sometimes prevent the phone from waking for a moment? I push the power button or fingerprint sensor and the screen doesn't wake. Double clicking power will open the camera though
blcklab said:
Additionally to anyone using immersive mode. Does it sometimes prevent the phone from waking for a moment? I push the power button or fingerprint sensor and the screen doesn't wake. Double clicking power will open the camera though
Click to expand...
Click to collapse
Works great for me. I downloaded Nougat / Oreo Quick Settings from the play store and followed the instructions to make it a quick setting toggle. And then ran this command https://forum.xda-developers.com/showpost.php?p=73629247&postcount=2 which said fixed lag...
Thanks. Will test that on my pixel. I assume it'll respond the same as 2 xl
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.
Anybody else having issues with the pixel screen not turning on? I get haptic feedback when I touch the screen but the screen doesn't come on. I have to hold down the power button to reboot. It only does it every now and then, I think it's the immersive mode that's causing it.
I am using double tap to lock (Nova Prime) and double tap to wake (settings > system > languages, inputs and gestures),
and once in a while, my double tap to wake (I presume during deep sleep) takes several taps to register.
I'm having the same issue too. Haven't found a solution yet.
Sent from my Pixel 2 XL using Tapatalk
Az Biker said:
I am using double tap to lock (Nova Prime) and double tap to wake (settings > system > languages, inputs and gestures), and once in a while, my double tap to wake (I presume during deep sleep) takes several taps to register.
Click to expand...
Click to collapse
mirwolf said:
I'm having the same issue too. Haven't found a solution yet.
Click to expand...
Click to collapse
I'm using Nova Prime too, but not the DTTL feature, and I'm not seeing this issue. I am using the DTTW in Settings (8.1). Have you tried toggling off DTTL in Nova for a while? Stranger things have happened.
v12xke said:
I'm using Nova Prime too, but not the DTTL feature, and I'm not seeing this issue. I am using the DTTW in Settings (8.1). Have you tried toggling off DTTL in Nova for a while? Stranger things have happened.
Click to expand...
Click to collapse
I'm not using Nova' DTTL, just DTTW in settings. Also using immersive move with system tuner. Not quite sure why i can't get it to wake when it happens. Ambient display turns off and its just a dark screen. Fingerprint reader registers because you can feel the vibration, but the display remains off. I tried flashing 8.1 again and reinstalled magisk, but the issue is still there. happens randomly.
mirwolf said:
I'm not using Nova' DTTL, just DTTW in settings. Also using immersive move with system tuner. Not quite sure why i can't get it to wake when it happens. Ambient display turns off and its just a dark screen. Fingerprint reader registers because you can feel the vibration, but the display remains off. I tried flashing 8.1 again and reinstalled magisk, but the issue is still there. happens randomly.
Click to expand...
Click to collapse
I believe there is a problem with Oreo and immersive mode. I had the same thing happen to me. Screen would go black if I pushed the power button but finger print scanner worked as you could feel the vibration. Also if you press lock again you get the screen lock sound.
Sent from my Pixel 2 XL using XDA Labs
Anyone found a solution to this issue. I'm having the same problem. Exactly as described.
Zetanator said:
Anyone found a solution to this issue. I'm having the same problem. Exactly as described.
Click to expand...
Click to collapse
Remove Magisk manager and remove Root entirely. Rooting is what caused it for me, I guess I had an older version of Magisk manager installed so I went to the official Magisk thread and downloaded and installed the latest Magisk manager app then flash the Magisk zip file via twrp and I haven't had a problem since
mackentosh said:
Remove Magisk manager and remove Root entirely. Rooting is what caused it for me, I guess I had an older version of Magisk manager installed so I went to the official Magisk thread and downloaded and installed the latest Magisk manager app then flash the Magisk zip file via twrp and I haven't had a problem since
Click to expand...
Click to collapse
Thanks I appreciate the help. I ended up going back to stock. The issue got progressively worse.
I too have this issue, I'm almost positive the phone does this when when the screen times out. If I press power button to turn it off I never have the issue. I only think that's what causes it but i think there's more to it, like having magisk and being rooted. Just assumptions. I also noticed that when this happens Android thinks the screens on, I have an app that lets me use active edge to turn on flashlight and it turns light on even though the screen isn't actually on. Even in battery settings it shows my sot being higher than it should.
I experienced the issue. I did have the immersive mode, rooted with magisk, edge sense, and was using substratum. After I installed an up to date module for edge sense in Magisk manager, I haven't seen it since. I think it's the previous outdated Magisk module that's doing it. Could be the base Magisk module as well.
Same issue here... very frustrating. I dropped $6 on this launcher primarily for just the tap to sleep / wake feature on my Pixel 2 XL and can't wake it. It's locked in a deep sleep. I'm forced to press the power button once and then it just wakes to ambient screen on double tap afterwards. THEN...double tap again to wake. Did I just waste my money? Anyone get a solution to this yet?
I just want to add that I have the same issue but I'm not rooted. Using an immersive mode app. Really hoping this isn't an issue on P.
robnhl said:
I just want to add that I have the same issue but I'm not rooted. Using an immersive mode app. Really hoping this isn't an issue on P.
Click to expand...
Click to collapse
I've solved this issue for me. I'm using Navigation Bar Hider from the Play Store to force immersive mode. I had to deselect the system UI-type apps from the NBH settings. Since I did that I haven't had any issues waking up the phone. I basically deselected all of the system apps then went back and selected things like Chrome, Calendar, etc.
Me too... With inmersive mode but only when have less of 10-15% of battery .....
Enviado desde mi Pixel 2 XL mediante Tapatalk
Hi,
I've configured my S4 to use full screen gestures instead of navigation buttons. This used to work fine.
Recently I noticed that the gestures not always work. When an app is in full screen mode, the first time I try such a gesture, the notification bar becomes visible for a short time, and usually the app responds to the gesture. When I do it again the gesture is acted upon by the system as intended.
Does anyone recognize this behaviour? Did I miss a new setting?
sciurius said:
Hi,
I've configured my S4 to use full screen gestures instead of navigation buttons. This used to work fine.
Recently I noticed that the gestures not always work. When an app is in full screen mode, the first time I try such a gesture, the notification bar becomes visible for a short time, and usually the app responds to the gesture. When I do it again the gesture is acted upon by the system as intended.
Does anyone recognize this behaviour? Did I miss a new setting?
Click to expand...
Click to collapse
I'll have to check. I know mine does this in-game, but that's expected. I'll check in other apps.
sciurius said:
Hi,
I've configured my S4 to use full screen gestures instead of navigation buttons. This used to work fine.
Recently I noticed that the gestures not always work. When an app is in full screen mode, the first time I try such a gesture, the notification bar becomes visible for a short time, and usually the app responds to the gesture. When I do it again the gesture is acted upon by the system as intended.
Does anyone recognize this behaviour? Did I miss a new setting?
Click to expand...
Click to collapse
So mine is the same way, when in a full screen app the first swipe only shows the bar, then the second swipe does the action. My guess is it's so you don't accidentally close a full screen app? Not sure. I think mine has done this since I switched to gestures.