Does anybody else use permissive mode on android ? For me I have issues waking from sleep. I have to press the power button lots of times to get the screen on. Anybody have a fix ? I want to use permissive mode to reduce screen burn.. I'm using tiles to activate permissive mode and I'm on stock android 8.0 non beta.
you meant immersive not permissive right? because you were talkin about gettin rid of the navbar and statusbar to avoid screen burn ins
Same issue for me, enabling immersive mode on Oreo causes an issue when waking up the device if it has been sleeping for awhile. I have been using immersive mode since paranoid android on an old nexus device so using the phone without it enabled feels awkward.
I had the same issue. Tried to reverse immersive mode in terminal emulator, but got an error. Ended up just flashing stock once again.
What I did was tick the "System Awake" to ON in developer settings. Works like a charm every morning. Now and I can finally turn off my alarm without wanting to literally throw it across my room since the device wouldn't turn on after a long night.
Related
Hey,
I upgraded my device from a Nexus 5. In my Nexus 5 I had an option in the Settings to create a schedule for silent times (or priority only). Before I did the switch, I had a setting on to put the device on silent mode at 21:30. Now, in my OnePlus3, I notice that it also goes silent at 21:30 every day (it probably automatically migrated this setting along with the other settings when I first set up the device). But in the OnePlus 3 I no longer have a setting to disable this schedule... This is extremely annoying, because when the device goes into Silent mode I can't even turn up the volume with the volume rocker, I have to physically push the alert slider to "silent" mode and then back to "all notifications" mode.
The device is not rooted and I'd much rather keep it this way if I can.
I hate the fact that there something going on that I can't switch off...
Ideas? Tips? any thoughts will be highly appreciated.
Several people have reported this problem and I have it as well. You are correct that it comes from transferring the settings from your previous phone to the OP3 which has no way to control do not disturb settings through software. None of the suggested fixes have worked for me. My hope was that the new OTA, which apparently had notification fixes would stop it, but it did not. The only thing that has been reported as working all the time is wiping the phone entirely and setting it up as new without transferring your old settings. If you still have your old phone, you could change the settings on it to remove all dnd settings, use it for a bit so that it backs up and then try setting up your OP3 again. I plan on doing that or starting new and fresh later this week.
Edit:
Here's the other thread on this. Looks like the problem exists for people who did clean installs as well. http://forum.xda-developers.com/oneplus-3/help/disturb-settings-t3400979
Had this problem, too. I did transfer the settings from my old phone, but I had no DND settings active on this device (in fact I never ever used DND). The only way to get out of this silence loop was to restart the phone and set the slider to priority and back to all.
daClaus said:
Had this problem, too. I did transfer the settings from my old phone, but I had no DND settings active on this device (in fact I never ever used DND). The only way to get out of this silence loop was to restart the phone and set the slider to priority and back to all.
Click to expand...
Click to collapse
That didn't fix it, the behavior returned after a while.
Apparently this is a big issue:
https://forums.oneplus.net/threads/do-not-disturb-notifications-problem.451989/
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.
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
For the last 3-4 days I've noticed Playstore has dark mode enabled at night but is back to white during the day time.
Does anyone know where the controls for this feature is? I prefer dark mode fulltime but can't seem to find a toggle or way to control it.
My device is stock, unrooted with Android 9 August security patch.
Go to Developer Options and look at the Night Mode settings. I think your phone is set to time of day.
HKSpeed said:
Go to Developer Options and look at the Night Mode settings. I think your phone is set to time of day.
Click to expand...
Click to collapse
Thanks this worked. Surprisingly I had no idea this os had a 'night mode' feature. Everything is always white. but hey now I know.
Double post.