I noticed the following: Despite being switched off manually including all automatic rules, I keep finding my phone in do not disturb mode. It even switched itself back on in background while I'm writing this...
Does anyone experience the same thing? What is causing this? Is there a solution to that?
I'm running stock B19 su rooted with BeastMode kernel vR46 on A2017G.
Hello,
I am having the same problem that you have describe. The only way to fix it is by rebooting the phone. and Re-Enable using volume keys.
Make sure you don't allow any other apps to access it. You will find the apps that have permission next to the schedule options in the DnD screen. Daydream was my main cause of frustration here.
DND is broken on b19. As a work around you need to establish another rule when the DND state is to be off.
Related
Anyone else notice this? I set the DND automatic rules to Alarms Only from 10pm to 6am, Sundays through Thursdays. The phone will automatically turn on DND at 10pm, but for some reason it never switches off at 6am. Once I notice, I can manually turn it off but that defeats the purpose of having an automatic rule in place. I've noticed this on both the March and April updates, but I'm pretty sure it worked properly before that.
Heinous said:
Anyone else notice this? I set the DND automatic rules to Alarms Only from 10pm to 6am, Sundays through Thursdays. The phone will automatically turn on DND at 10pm, but for some reason it never switches off at 6am. Once I notice, I can manually turn it off but that defeats the purpose of having an automatic rule in place. I've noticed this on both the March and April updates, but I'm pretty sure it worked properly before that.
Click to expand...
Click to collapse
I am having the same problem, did you ever find a solution?
I noticed this the other day on my 6P. It works properly in Safe Mode (you can tell when you adjust the volume control as it displays the rule name instead of the generic 'until you cancel it'). This means some app I had installed was messing with it.
I tried deleting a lot of apps but none made a difference. I ended up doing a factory reset and all is well. I have reinstalled almost all of my apps and it is still working. The only ones I have yet to install that deal with notifications are Tasker, and DLink and Samsung camera apps. Yet I deleted them before the reset and it didn't change anything.
Previous to me noticing this, I had set up a Tasker profile to read my notifications to me; in this case all notifications. I have a feeling this may have broken something (Android is so brittle), but odd that the behavior persisted after disabling Tasker (and even uninstalling it).
stevetrooper said:
I am having the same problem, did you ever find a solution?
Click to expand...
Click to collapse
No, I think it just fixed itself at some point. I am Having the same issue again on my new phone (Xperia XZ), so I'll post here if I figure it out.
Oops I just posted the same question before finding this thread. Having the same problem on my 6P which was upgraded from M to N. I have a 5X too that I started fresh on N (stock image flash) and it works fine on that one, just not on my 6P. Not sure if it's the upgrade M to N or specific to the 6P.
I tried deleting the rule and re-creating it but it doesn't help.
(if a mod could please merge the 2 threads)
http://forum.xda-developers.com/nexus-6p/help/coming-disturb-mode-using-auto-rule-t3496957
I have this same issue. I had it on the Pure Nexus ROM too. Now I'm on stock 7.1.1 and the DND still doesn't turn off when it's supposed to. Annoying AF.
Not sure what we can do about it, I'm thinking not use the rules and instead use an automation app to do it, the likes of MacroDroid, Automagic, etc. Don't know if such apps would require root to turn DND on/off though.
It happens since marshmallow, sometimes a reboot fix the issue and sometime you have to turn off the automatics rule manually turn on and off the DND and reboot.
I get this issue when DND is set on automatic rules and i change it to on or off manually (only sometimes).
Interesting, I never had a problem on M, it only started for me after I upgraded to N.
I didn't have this problem after I upgraded to N, it was the October security update when the problem started for me.
There's a bug filed it seems. Hopefully Google will do something about it. Please vote for the issue to be fixed.
https://code.google.com/p/android/issues/detail?id=226041
Are you using Android Wear? It seams, that after today's update AW app (version 2.0.0.138705214), problem with DND mode went away. Look at Apkmirror for that version, and please report, if it solve this problem you as well.
Srandista said:
Are you using Android Wear? It seams, that after today's update AW app (version 2.0.0.138705214), problem with DND mode went away. Look at Apkmirror for that version, and please report, if it solve this problem you as well.
Click to expand...
Click to collapse
I do use Android Wear and I got the update to 2.0.0.138705214 this afternoon. I will report tomorrow morning if the Automatic rule turned itself off. Thanks for the tip.
It seems that the latest Android Wear fixed the issue for me, at least for now. I hope it sticks. Yes, I use Wear.
sirxdroid said:
It seems that the latest Android Wear fixed the issue for me, at least for now. I hope it sticks. Yes, I use Wear.
Click to expand...
Click to collapse
Same here.
Android Wear update seems to have fixed it for me too.
Yep, it's been working fine for 2 days now.
Same here https://forum.xda-developers.com/nexus-6p/help/disturb-disable-t3556270
Hi guys,
Having an issue with my Note 4 (SM-N910F) international version since the MM 6.0.1 update. I received a further update after the MM 6.0.1 recently and thought the issue would've been fixed but alas, no!
Current version of Software: N910FXXS1DPE7.
Issue is, I have power saving mode turned on and set to: Start power saving "Immediately". However it keeps getting turned off and the screen becomes bright and I could not recognise a pattern how this occurs.
Things tried so far:
-Unticked automatic brightness and dragged all the way to low.
-Smart stay was/is never ticked.
-Auto adjust screen tone is ticked, but unticking that and also leaving automatic brightness turned off still causing power saving to automatically turn off.
-I have tried to check for this issue in Safe mode and it still happens.
Any ideas of what could be causing this? I do not want to do a factor reset for this issue and if it can be avoided after all. Safe mode is somewhat similar isn't it?
I have noticed the issue occur when I start using Gmail app (not the Inbox one), but that is just one scenario.
It seems like the light sensor gets triggered when it faces bright light and turns off power saving mode and screen becomes bright, but just could be a red herring.
Thanks a million!
Bharath
corpuscallosum said:
Hi guys,
Having an issue with my Note 4 (SM-N910F) international version since the MM 6.0.1 update. I received a further update after the MM 6.0.1 recently and thought the issue would've been fixed but alas, no!
Current version of Software: N910FXXS1DPE7.
Issue is, I have power saving mode turned on and set to: Start power saving "Immediately". However it keeps getting turned off and the screen becomes bright and I could not recognise a pattern how this occurs.
Things tried so far:
-Unticked automatic brightness and dragged all the way to low.
-Smart stay was/is never ticked.
-Auto adjust screen tone is ticked, but unticking that and also leaving automatic brightness turned off still causing power saving to automatically turn off.
-I have tried to check for this issue in Safe mode and it still happens.
Any ideas of what could be causing this? I do not want to do a factor reset for this issue and if it can be avoided after all. Safe mode is somewhat similar isn't it?
I have noticed the issue occur when I start using Gmail app (not the Inbox one), but that is just one scenario.
It seems like the light sensor gets triggered when it faces bright light and turns off power saving mode and screen becomes bright, but just could be a red herring.
Thanks a million!
Bharath
Click to expand...
Click to collapse
I have just one problem like yours. When i receive Marshmallow i just update. But Power Saving turns off every reboot. Just back to factory settings and make your wipes. I solve this with wipes and factory.
Tavok said:
I have just one problem like yours. When i receive Marshmallow i just update. But Power Saving turns off every reboot. Just back to factory settings and make your wipes. I solve this with wipes and factory.
Click to expand...
Click to collapse
Thanks. Yeah I am trying to avoid factory reset because can't go thorugh the process of installing apps, setting up all the various accounts etc especially since there is no built in fully restorable backup feature. Family man with kids and have enough IT stuff to do at work.
I'm on stock/non-rooted device also. And this will be my last Samung device, if not the last Android!
I understand you very well. You can use HELIUM apk to make your nandroid backups without root and make easier this tedious work. I don't have rooted my phone but helium makes all faster that, and i use also wondershare mobile go for android and PC.
I hope this helps you and you can resolve your problem. Good luck and regards from Switzerland - (Mexico)
Tavok said:
I understand you very well. You can use HELIUM apk to make your nandroid backups without root and make easier this tedious work. I don't have rooted my phone but helium makes all faster that, and i use also wondershare mobile go for android and PC.
I hope this helps you and you can resolve your problem. Good luck and regards from Switzerland - (Mexico)
Click to expand...
Click to collapse
Thanks Tavok. I did download Helium and wanted to test it out, however my phone is now staying in Power Saving mode since a few days! I have done nothing new, didn't uninstall any app or change any settings as such for it to work. This is bugging me because I want to know what fixed it so that I can re-apply the fix again if need be.
I've also read that some people are complaining about Note 4 getting stuck in Power Saving mode and I hope this is not the case with mine, now that it seems to work as expected.
I will update this thread once I check it out further.
I found out how this power saving mode gets turned off. It is the Location settings. If location is off, the power saving mode stays on (this is what it was set to hence I didn't see the issue happening). But when I changed it back to High accuracy, I started to notice the power saving getting turned off from time to time when using certain applications that require Location accuracy.
This is a bug since the MM update!!
Any ideas how to use Location accuracy and still retain Power saving mode?
I did a factory reset and the issue persisted! I tried various location settings(of the 3 choices) asks none of them helped. When set to any one of them power saving automatically turns off after a while I.e. when location needs to be detected. The only workaround us to turnoff location altogether but that messes with the auto sync of accounts! Grrrrrrrr
I verified with Samsung Tech Support that Location and Power Saving are incompatible on the Galaxy Note 4, even with the latest Android version available for the device (6.0.1) . In other words, Turning on Location while Power Saving is active will disable Power Saving after a short period. Fortunately, the problem is fixed on later devices.
Anybody else having problems with the YotaEnergy application? The screen that notifies me that YotaEnergy has been turned on (YotaEnergy mode extends your battery, etc, etc...) keeps showing up constantly every few minutes while I'm in the process of using the actual e-ink screen, which is no end of annoying. Furthermore, I can't disable YotaEnergy altogether, because it cannot be turned off when my battery is below 50%, ignoring all of my settings telling it not to turn on at all.
Is this a defect in my phone? Can I get rid of the horrible thing altogether?
In case anybody has an ideas, I've now updated to the latest OTA CN update, and the situation seems to be that the YotaEnergy settings are completely locked. Any changes I make are immediately forgotten, and it's permanently turned on. If anyone has any ideas, I'm kind of desperate. I'm on vacation and am hesitant about bricking it in my attempts to fix it. Does anyone know if it sets settings on a plain text settings file? Maybe I can manually change it that way?
Ok I have googled and googled this to find all kinds of people having the same problem. iHeartRadio will play untill screen shuts down then will play for a few then stops playing. So I have looked at wifi settings is set to always. Battery saver is off. Here is one thing I have noticed if I use the aux cable it works fine. I have deleted​ app and data and reinstalled but still
The same. Any thoughts would be appreciated.
PS also swapped ROMs to.
monkeytools said:
Ok I have googled and googled this to find all kinds of people having the same problem. iHeartRadio will play untill screen shuts down then will play for a few then stops playing. So I have looked at wifi settings is set to always. Battery saver is off. Here is one thing I have noticed if I use the aux cable it works fine. I have deleted​ app and data and reinstalled but still
The same. Any thoughts would be appreciated.
PS also swapped ROMs to.
Click to expand...
Click to collapse
Hello...
Maybe go in iHeartRadio settings. Isn't there an option to select "keep app on when screen goes off" or something similar?
Have you tried to unoptimize it? Doze is killing it maybe?
Go in Settings > Battery > three dot menu tap "battery optimization"
On the drop down menu, choose all apps. Tap on iHeartRadio and select: "Don"t optimize".
Hoping it will save your issue...
Cheers...
Like 5.1 says, unoptimize it in the battery settings and then your fine. You have to do that with Google music as well.
I'm having the same issue. It is listed as not optimized.
Amazon Music used to do this on my Nexus 5, but now on the 6P it decided the Iheartradio app will do it instead. The Nexus 5 issue also persisted across ROMs and factory resets.
Maybe it's an app issue that only affects a few people with very specific settings or something?
This is far from an ideal solution but if turning off battery optimization doesn't fix the problem there are apps in the Play Store that keep the screen on when you are using specific apps. You could choose to leave the screen on when using iHeartRadio.
I have read a few posts about Gmail notifications not going through even after turning "optimization off" for the app. And people reporting that doze affects other parameters at the same time that cause notification trouble.
Maybe this case can be assimilated, but in another way.
You can try Killing doze completely and see how iHeartRadio behaves. Open a command prompt and issue:
adb shell dumpsys deviceidle disable
It should return something like:
Deep idle mode disabled
Light idle mode disabled
Check iHeartRadio behavior after that. If it fixed the issue, you know that doze may be the culprit or maybe the app developer didn't implement a new policy for doze and/or when screen turns off.
You can revert the ADB shell command with either:
adb shell dumpsys deviceidle enable
Or with a reboot.
I'd send iHeartRadio developer an email to let them know your issue. If other users already reported it and if they are working on a fix...
Good luck... :good:
5.1 said:
I have read a few posts about Gmail notifications not going through even after turning "optimization off" for the app. And people reporting that doze affects other parameters at the same time that cause notification trouble.
Maybe this case can be assimilated, but in another way.
You can try Killing doze completely and see how iHeartRadio behaves. Open a command prompt and issue:
adb shell dumpsys deviceidle disable
It should return something like:
Deep idle mode disabled
Light idle mode disabled
Check iHeartRadio behavior after that. If it fixed the issue, you know that doze may be the culprit or maybe the app developer didn't implement a new policy for doze and/or when screen turns off.
You can revert the ADB shell command with either:
adb shell dumpsys deviceidle enable
Or with a reboot.
I'd send iHeartRadio developer an email to let them know your issue. If other users already reported it and if they are working on a fix...
Good luck... :good:
Click to expand...
Click to collapse
Thanks I will give it a try.
Hi there, so I updated my ph-1 to the latest Oreo 8.1 earlier this morning and have been experiencing significant delays when unlocking my screen. Sometimes the phone did not respond at all and the screen just stayed black. I had to restart the phone in such cases. Help! I seem to be the only essential phone user in entire Sydney
If you're using immersive mode, that might be the issue. Try disabling that, and see if the issue persists.
I'm experiencing the same. Setting immersive mode to None does help a bit, but it's still not as snappy as before.
And after all the same settings worked perfectly on the 8.1 beta.
Tried to go back, but on official 8.1 the recovery mode only says "no command"....
I am experiencing the same issue too. It doesn't have the delay problem right after reboot, it seems like it delays the unlocking when the phone has been in idle for a while.
And specialty if you use immersive mode with sytem UI make it very long delay
winstonxyz said:
I am experiencing the same issue too. It doesn't have the delay problem right after reboot, it seems like it delays the unlocking when the phone has been in idle for a while.
Click to expand...
Click to collapse
Same issue here. Sometimes takes so long to unlock that I am unable to answer a phone call that comes in before it goes to Voicemail. Usually happens when the phone has been idle for a while.
Update:
Did the dreaded FDR (factory data reset). Installed the "Tiles" app from plasystore and ran the noted adb command to allow immersive mode, tile display, and enable write secure settings permissions. I chose the action to hide the navigation bar within the Tiles app. I ignored the setting to stop on sleep so the app keeps running when the phone screen goes off. In testing it for about an hour the phone seems to unlock without any issue for now and without any delay. I also made phone calls while the phone screen was off and I was able to answer the call easily. So far so good using the Tiles app!
sounds like the expanded desktop Oreo issue. There's a Xposed module DeepScreen Oreo for it.