If I set a schedule, do not disturb turns on, but it does not turn off in the morning, I've only seen it work once.
What about everyone else?
It works fore me as expected. No problems.
Sent from my XQ-AT51 using Tapatalk
Same with me. It often doesn't turn off in the morning.
How can they mess up software between phones lol.
I've had it with Asus on the rog 2. Things don't work for me and perfect for some others, but not all.
It works normally for me. It might related to an application.
Envoyé de mon XQ-AT51 en utilisant Tapatalk
I'd have no idea what app might be doing that.
I've also had issues with scheduled DND not working - turns on normally but doesn't turn off at the scheduled time
If you are like me and migrated from another Android phone to Sony XPeria 1 II and restored your backup onto the new phone, then you probably have issues with the "Do Not Disturb" you had in the old phone. I was going bonkers trying to figure out why it didn't work. Changing the schedule profile didn't fix it either. What finally fixed it was deleting the schedule altogether and then creating a new schedule. Then it worked as intended.
Also, ticking "Alarm can override" option messes up the schedule as well.
I have the same problem even when I set 2 schedules hoping the 2nd one will work as a backup... I don't think I imported the schedule from old phone settings. Anyway i will delete and create a brand new schedule. Fingers crossed.
prindacerk said:
If you are like me and migrated from another Android phone to Sony XPeria 1 II and restored your backup onto the new phone, then you probably have issues with the "Do Not Disturb" you had in the old phone. I was going bonkers trying to figure out why it didn't work. Changing the schedule profile didn't fix it either. What finally fixed it was deleting the schedule altogether and then creating a new schedule. Then it worked as intended.
Also, ticking "Alarm can override" option messes up the schedule as well.
Click to expand...
Click to collapse
The function works properly, it's just that the indicator stays on. Maybe it's by design, to show that a schedule is active, regardless if at that moment notifications are enabled or not. My do not disturb schedule ends at 10 am, at that moment I get all notifications of the night before, but the indicator is still on.
Riona69 said:
I have the same problem even when I set 2 schedules hoping the 2nd one will work as a backup... I don't think I imported the schedule from old phone settings. Anyway i will delete and create a brand new schedule. Fingers crossed.
Click to expand...
Click to collapse
Unfortunately didn't work for me most of the time as phone stayed in DND mode (even though alarm will sound) and frustrating since I missed a lot of calls since I don't get any ring sound or notifications sound.
Sho-Bud said:
The function works properly, it's just that the indicator stays on. Maybe it's by design, to show that a schedule is active, regardless if at that moment notifications are enabled or not. My do not disturb schedule ends at 10 am, at that moment I get all notifications of the night before, but the indicator is still on.
Click to expand...
Click to collapse
As stated above, the phone is on silent mode. Notifications are there but no sound. I have to turn off DND manually and it is frustrating!
Just to report in: I've definitely had issues with DND. I thought it may have been a magisk module or something that I've done, but I think it's clear that it's something going on with the ROM itself. The only things I migrated from my old phone was text messages. Everything else was new data. Unless every random person in this thread happens to be doing the same weird thing that prevents this, the ROM itself has issues.
A user (cmahey) from Reddit mentioned that in the main DND menu there's a 'Default duration' option, just set it to 'Ask Every Time' and problem solved. I have tested for 2 days and seems to be working!
Riona69 said:
Unfortunately didn't work for me most of the time as phone stayed in DND mode (even though alarm will sound) and frustrating since I missed a lot of calls since I don't get any ring sound or notifications sound.
As stated above, the phone is on silent mode. Notifications are there but no sound. I have to turn off DND manually and it is frustrating!
Click to expand...
Click to collapse
You are right, I always have my phone on silent, but I saw the notifications coming through, so I assumed that it worked properly.
I did some reading, many brands seem to have this problem. And I did some testing and found a working solution (at least on my device): If you go to Settings, Sound, Do not Disturb, go to the schedule that you set and go to it's properties. there you will see a setting which translated from Dutch should be something like The clock can ignore the endtime. It's the setting under the Endtime. Disable this setting. Now it should work properly (I tested only one day now, so no guarantees)
Riona69 said:
A user (cmahey) from Reddit mentioned that in the main DND menu there's a 'Default duration' option, just set it to 'Ask Every Time' and problem solved. I have tested for 2 days and seems to be working!
Click to expand...
Click to collapse
Will try this!
Well that didn't work......guess I'll just stick to manually turning DND off. At least it turns on at night time, which is the main thing.
After I installed the latest firmware update (194) it is working correctly since 2 days.
Sho-Bud said:
After I installed the latest firmware update (194) it is working correctly since 2 days.
Click to expand...
Click to collapse
Bummer, on day 3 it didn't turn off automatically
Related
[Q] Priority notification mode turning off on its own, even on "Indefinitely"?
The last few nights I've noticed that when I wake up, my phone is no longer in priority notification mode. At night, I set it to priority only and choose "indefinitely"...even verifying that it's on that setting by going back to it...and when I wake up, it's in normal mode.
I have no "Down Time" hours set and see no other settings that seem to imply turning it off automatically...
Anyone else have this issue?
Thanks!
jeffreii said:
The last few nights I've noticed that when I wake up, my phone is no longer in priority notification mode. At night, I set it to priority only and choose "indefinitely"...even verifying that it's on that setting by going back to it...and when I wake up, it's in normal mode.
I have no "Down Time" hours set and see no other settings that seem to imply turning it off automatically...
Anyone else have this issue?
Thanks!
Click to expand...
Click to collapse
Yes I'm having the same issue as you described. Noticed it 2 nights ago and thought I was disabling it in my sleep, lol.
Any work arounds? I'm thinking of doing a factory reset but not until I've exhausted all possible solutions. Hope this is an actual issue and not just 1 or 2 stray scenarios
Yaqoub_H said:
Yes I'm having the same issue as you described. Noticed it 2 nights ago and thought I was disabling it in my sleep, lol.
Any work arounds? I'm thinking of doing a factory reset but not until I've exhausted all possible solutions. Hope this is an actual issue and not just 1 or 2 stray scenarios
Click to expand...
Click to collapse
I never figured it out. Switched back to using Light Flow for notifications...
jeffreii said:
I never figured it out. Switched back to using Light Flow for notifications...
Click to expand...
Click to collapse
Okay last night I uninstalled Light Flow which seemed to have been the problem causing this behavior. It seems to automatically want to disable priority mode but I don't know what exactly is triggering it, but uninstalling Light Flow seemed to have retained priority mode all night long with no issues upon waking up.
I also updated my review on the Play Store to address the issue, hoping for a fix soon. Hopefully you figure out your problem, mine was caused by a notifications app from what I've tested so far. Will see if it holds up tonight as well.
jeffreii said:
The last few nights I've noticed that when I wake up, my phone is no longer in priority notification mode. At night, I set it to priority only and choose "indefinitely"...even verifying that it's on that setting by going back to it...and when I wake up, it's in normal mode.
I have no "Down Time" hours set and see no other settings that seem to imply turning it off automatically...
Anyone else have this issue?
Thanks!
Click to expand...
Click to collapse
Having same issue, no additional notification apps installed. Stock android on nexus 6 no root or anything yet. Thought I was loosing my mind thinking I never set it. Happens almost every night. Seems like a bug.
I'm having the opposite. On boot, priority mode is enabled even though it was off on shutdown. I turn it off then throughout the day I notice it come on again. I haven't been able to track anything down yet. I don't use lightflow.
Are there any logs that I can see that might tell me what is turning it on? There are no Downtime schedules.
Pure 3.95 / Franco r7
Yaqoub_H said:
Okay last night I uninstalled Light Flow which seemed to have been the problem causing this behavior. It seems to automatically want to disable priority mode but I don't know what exactly is triggering it, but uninstalling Light Flow seemed to have retained priority mode all night long with no issues upon waking up.
I also updated my review on the Play Store to address the issue, hoping for a fix soon. Hopefully you figure out your problem, mine was caused by a notifications app from what I've tested so far. Will see if it holds up tonight as well.
Click to expand...
Click to collapse
So I finally got tired of Light Blow being buggy on the Nexus 6 and uninstalled it a few days ago...two nights in a row I set priority to "indefinitely" and when I woke up I found it had been turned off...so I don't think it's Light Flow causing the problem.
I have moto x with Lollipop. I cannot get the sleep mode to work correctly. I am getting notification sounds at night waking me up. Yes all my settings are set correctly with Downtime and Sleep Mode. Am I missing something? Anyone else experiencing this with Lollipop?
As much as I love Lollipop, as much as I love the Moto X, downtime and priority notifications are a mess. They should've just disabled one or the other... I've been tinkering with mine all day to get it to work with my meetings on my calendar.
Slipperybrain said:
I have moto x with Lollipop. I cannot get the sleep mode to work correctly. I am getting notification sounds at night waking me up. Yes all my settings are set correctly with Downtime and Sleep Mode. Am I missing something? Anyone else experiencing this with Lollipop?
Click to expand...
Click to collapse
Same exact issue as you. Even though in priority mode I have all 3 option turned off (call/texts etc) I still get notification sounds coming through. I have tried every possible combination without success. The new notification system is the perfect example of "fixing" something that wasn't broken to begin with.
My only solution that I've found to work is to use Power Toggles as a widget. It let's you select 4 volume settings and has worked without a hitch. Hopefully the issue just a bug... But I won't hold my breath for a transparent or timely fix.
Give Power Toggles a try, works great!
So here is what I did. I completed a factory reset and it works now, but don't do a factory reset. Here is why it works. I went to the sounds and notifications, app notifications. I have hangouts and Gmail set to priority meaning it will alert me even when it is set to priority mode only and notifications are set to silent. Stupid me for changing that to begin with. Check that area.
Slipperybrain said:
So here is what I did. I completed a factory reset and it works now, but it don't do a factory reset. Here is why it works. I know the sounds and notifications, app notifications, I have hangouts and Gmail set to priority meaning it will alert me even when it is set to priority mode only and notifications are set to silent. Stupid me for changing that to begin with
Click to expand...
Click to collapse
Believe it or not, I double checked those too. They are greyed (unchecked) so I shouldn't still be receiving the notifications. I factory reset may have been what fixed it for you. Speaking generally, it's ridiculous that anyone would have to do that in order to have things work as they should. But I guess you can say there are always some bugs whenever a new update is rolled out - it's frustrating nonetheless.
http://tomhorsley.com/rants/doze-mode.html
I'm definitely reverting back to 5.1.1 when I get the time and energy to fool with it .
sounds like that was written by someone who hasn't even tried marshmallow yet. I have yet to experience any missed notifications, alarms or any issues relating to time in any way. If some apps are being affected by this then its a sign to the developer to fix their ****ty code because all of my apps relating to time at all have been working just fine and alot of them are still the same version they were on lollipop. Doze has improved my batter significantly. It sounds like this article was probably written by a developer who cant code properly and instead of improving his skills he'd rather complain and convince everyone to stay away from updates because he is unwilling to evolve. Even the article looks like it was written in paint...
I had indeed a wrong time bug some days ago...really strange and worrying, a reboot fixed it. First time ever since Android Froyo that I experienced something like that.
That author seems to think that Marshmallow's Doze is a horrible thing that breaks all apps that rely on background services, namely alarms and notifications, and couldn't possibly be fixed in 10 years (rather than a few months) due to Google's horrible mistake (rather than devs not fixing their code).
Frankly, it sounds like a bunch of hyperbole.
Sent from my ALCATEL ONE TOUCH Fierce using Tapatalk
He's wrong about how doze works. And if he's in the camp that doesn't understand it nor wants to rewrite his app. Then yeh he's the idiot group that Google is targeting and was writing garbage code anyway.
lol complete nonsense, my alarm has worked everyday since i flashed M, even on dev previews...the only issues i have with M are really the "slow to connect wifi when using toggles" and the weird wifi consumption on battery stats
Another annoying issue on M is that if your leave your phone longer in standby mode (display off), wifi turns off and you stop recieving notifications until you turn your phone on again. This is with wifi set to "never turn off", etc.
Kustaa said:
I had indeed a wrong time bug some days ago...really strange and worrying, a reboot fixed it. First time ever since Android Froyo that I experienced something like that.
Click to expand...
Click to collapse
This actually happened with me a couple of days back, I was travelling, so I put my phone connected to a power bank and went for a nap, woke up to see phone switched off, switching it on throws me a 2nd September date set on my device. Had to manually set the date as no network was available to automatically set the date from servers.
Ubichinon said:
Another annoying issue on M is that if your leave your phone longer in standby mode (display off), wifi turns off and you stop recieving notifications until you turn your phone on again. This is with wifi set to "never turn off", etc.
Click to expand...
Click to collapse
This I had been noticing these days just because of WhatsApp Web. When in standby, WhatsApp Web shows phone not connected error. Just waking the phone reconnects to the WiFi, but happens every 30-40mins.
I have a feeling that folks who never see these problems have their phones charging at night and doze mode doesn't happen when you are charging. I have no convenient way to charge my phone near my bed, so it is not charging and totally idle all night. Email and messaging completely stops. Only the stock alarm clock works. My medication reminder stops working. It might as well be turned off completely. Plus when you do wake up and turn on the phone, all the pent up alerts come through and scare the hell out of you. I hate doze mode.
Settings -> Battery -> ... (menu)-> Battery Optimization --> All apps --> Select whatsapp, etc... and select not optimized.
Test again.
You're welcome.
I already disabled optimization in the battery settings for all the apps that weren't working. They still don't work after sitting overnight. It looks as if that setting has absolutely no effect.
Claghorn said:
I already disabled optimization in the battery settings for all the apps that weren't working. They still don't work after sitting overnight. It looks as if that setting has absolutely no effect.
Click to expand...
Click to collapse
This is a real problem. I tested this on a Nexus 5. The device seems to enter Doze after about 1 hour and this is what happens.
What does work in Doze mode:
- Telephone: call can be heard.
- Alarm: alarm can be heard
What does NOT work in Doze mode:
- Receiving mail notifications directly: it seems to wait for the maintenance window. There is no "ping" from my GMail. No lock screen notification until I picked it up. I turned off battery optimalization as suggested. Like Claghorn says, it doesn't make a difference. When I was sleeping, the time difference between sending the mail and getting a notification can be hours. That is not acceptable: I want to determine whether or not I get a message. I got no control over Doze, except plugging it in. Also, when it sits on the desk at work I need to pick it up or turn the screen on every so often, because I don't know if it "dozed" off again.
Works partially:
- Notification light: It works once mail passes through the maintenance window. It does NOT work before the maintenance window.
I tested all of this with a unrooted, updated Nexus 5. Topic Starter and Claghorn have good points. Why can't I turn this off? I don't want this. I want notification on time, with ping, right now. If I don't I will turn the volume off or set priorities. They could have told me this behavior in a mail or during the update. Important mail from work, family comes in hours late. Not happy with this at all.
Tried all sorts of things, nothing seems to help. And no, battery optimalization is either not enough or has nothing to do with it. I love the Nexus 5. Marshmallow seems to be much smoother than Lollipop. I was happy with the update until I discovered this. Now, I am fustrated. I expect the phone to inform me when I need to be informed. Most days I don't need to save 10% of power anyway. For the first time I want to either root the phone and go back to Lollipop or even Kitkat. I don't know what else can be done. Fustrated.
Dennis de Swart said:
This is a real problem. I tested this on a Nexus 5. The device seems to enter Doze after about 1 hour and this is what happens.
What does work in Doze mode:
- Telephone: call can be heard.
- Alarm: alarm can be heard
What does NOT work in Doze mode:
- Receiving mail notifications directly: it seems to wait for the maintenance window. There is no "ping" from my GMail. No lock screen notification until I picked it up. I turned off battery optimalization as suggested. Like Claghorn says, it doesn't make a difference. When I was sleeping, the time difference between sending the mail and getting a notification can be hours. That is not acceptable: I want to determine whether or not I get a message. I got no control over Doze, except plugging it in. Also, when it sits on the desk at work I need to pick it up or turn the screen on every so often, because I don't know if it "dozed" off again.
Works partially:
- Notification light: It works once mail passes through the maintenance window. It does NOT work before the maintenance window.
I tested all of this with a unrooted, updated Nexus 5. Topic Starter and Claghorn have good points. Why can't I turn this off? I don't want this. I want notification on time, with ping, right now. If I don't I will turn the volume off or set priorities. They could have told me this behavior in a mail or during the update. Important mail from work, family comes in hours late. Not happy with this at all.
Tried all sorts of things, nothing seems to help. And no, battery optimalization is either not enough or has nothing to do with it. I love the Nexus 5. Marshmallow seems to be much smoother than Lollipop. I was happy with the update until I discovered this. Now, I am fustrated. I expect the phone to inform me when I need to be informed. Most days I don't need to save 10% of power anyway. For the first time I want to either root the phone and go back to Lollipop or even Kitkat. I don't know what else can be done. Fustrated.
Click to expand...
Click to collapse
A quick suggestion -
You may use Doze Mode Editor and edit the script so that your phone never enters Doze mode.
That way you can enjoy Marshmallow without Doze.
Sent from my Nexus 5
Achilles. said:
A quick suggestion -
You may use Doze Mode Editor and edit the script so that your phone never enters Doze mode.
That way you can enjoy Marshmallow without Doze.
Sent from my Nexus 5
Click to expand...
Click to collapse
Thanks, I will look into that. I'd like to keep Mashmallow as a whole if possible. I think it is a good update in general.
OK, I've looked at the doze mode editor thread and I find that the descriptions of the parameters I can set to be totally confusing, however, the flowchart pointed at in that thread seems to indicate that if I set the "inactive_to" value to something like 24 hours, then all the other doze mode nonsense is unlikely to ever happen (because I'll probably turn on my phone at least once every 24 hours). Does that seem like the best way to essentially turn off doze mode?
Claghorn said:
OK, I've looked at the doze mode editor thread and I find that the descriptions of the parameters I can set to be totally confusing, however, the flowchart pointed at in that thread seems to indicate that if I set the "inactive_to" value to something like 24 hours, then all the other doze mode nonsense is unlikely to ever happen (because I'll probably turn on my phone at least once every 24 hours). Does that seem like the best way to essentially turn off doze mode?
Click to expand...
Click to collapse
I will look into this over the weekend. I find it odd that there isn't simply a switch to turn Doze off, which is a pity. It seems to me it's part of saving energy in general. A switch under Battery would do nicely. It should not be this complicated. That said, I think the UI of Marshmallow is silky smooth, much better than Lollipop. Marshmallow in general in good. It' just this that annoys me.
i'm baffled by google's aversion to end user config. This kind of b.s. is how I found xda and drove me to become a chronic flashaholic. All or nothin I guess.
ElwOOd_CbGp said:
i'm baffled by google's aversion to end user config. This kind of b.s. is how I found xda and drove me to become a chronic flashaholic. All or nothin I guess.
Click to expand...
Click to collapse
I get the feeling Google assumes the customer is a developer. A few examples:
- The Nexus 5 does have a notification light: I didn't know until I read 5 reviews and even then I couldn't find any documentation on it. Needed an external app to get it working.
- Battery indicator: I like to have small numbers indicating battery charge: it could be done by hacking KitKat and Lollipop I think. Then at Marshmallow finally there's a (hidden) switch.
- I don't recall having any user guide in the Nexus 5 package. Not that I needed one. But some landing page doing a walkthrough would have been nice. Although there are some walkthroughs in every app
Not fatal flaws, but you wonder why does it need to be that difficult. It scares people away. Not me. I handed the Nexus 5 to some friends on numerous occasions and most found it too "empty". As for me, I want all developer stuff on. So it suprised me, there is no Doze fine tuning. Again, overall I give the Nexus a 8 or 9 out of 10. It fits me. In general I like it. So it's just constructive criticism. The empty layout and raw speed of the Nexus 5 works good in development of apps afterall.
Last night I ran an adb command (generated by the doze mode editor app) to set inactive_to to 24 hours (86400000 milliseconds). I then set an alarm for the next morning in the "Alarm Clock Plus" app (which completely ceased to function after Marshmallow showed up). This morning, the alarm actually went off on time, but the big "Dismiss" button it draws on the screen was totally non-functional. I had to hit the power button to get control (which then caused a popup saying alarm clock plus was non-responsive). I have no idea what caused all that behavior, but at least the alarm actually went off.
Also, with doze mode essentially disabled (in theory anyway), the power dropped from 100% in the evening all the way down to 97% in the morning.
With the exception to facebook and game type apps, Google's apps are the only ones I find that excessively waste resourxes and need to be forced to sleep. If they would get off the constant location polling, media scanning, and logging or at least tone it down a bit some they wouldnt need to implement thier half baked versions of solutions that they hijacked from xda devs
Hi, I had this issue where onplus 3 was automatically going to silent mode, to get it back to normal i had to slide the alert slide all the way up and then down.
I found that this was happening because of true caller. I had enabled "Block spammer" where all the spam calls automatically gets rejected.
I observed that when ever a call is rejected the phone goes into silent, This is the only reason why phone goes into silent mode automatically.
Temporary fix: disable the Block spammer option
And you know what..... I have truecaller installed on my phone
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
Doesn't resolve it
I have the same problem, but no truecaller or anything installed. So this doesn't resolve my problem.
I don't think truecaller is the problem. I have experienced it and true caller was not installed.
It hasn't happened for a week now.
It happens to me everyday, no trucaller installed.
Wysłane ze zmywarki
Hello.
I also have this problem and I don't have TrueCaller installed.
Anyway, thanks for trying to help and sharing your experience.
This started to happen to me after I updated to Oxygen 3.2.1.
Dont know if the update introduced this, but that is when I first noticed it. I had about 6-7 occasions in last few days where I noticed that the phone is in silent mode although slider was set to full notifications. I then had to move the slider to silent and back to normal to fix it.
I dont use or have true caller installed here.
Same issue here
Same here, no true caller installed but phone went into silent mode at least 3 times within the last 2 days.
OxygenOS-Version 3.2.1
Not sure if anyone has figured out the solution yet, but I think I've narrowed down the problem a bit more: my phone goes to silent mode the same time each day, and I've noticed it's the same time that my previous phone would automatically go into silent mode (since it was set up to do that). It seems like since I've gotten my OP3, google or some kind of account backup must have remembered by previous auto silent setting and applied it here.
Orion9k0 said:
Not sure if anyone has figured out the solution yet, but I think I've narrowed down the problem a bit more: my phone goes to silent mode the same time each day, and I've noticed it's the same time that my previous phone would automatically go into silent mode (since it was set up to do that). It seems like since I've gotten my OP3, google or some kind of account backup must have remembered by previous auto silent setting and applied it here.
Click to expand...
Click to collapse
I don't know if that is true, because I have the same problem but I never had any of my previous phones set up to go into silent mode at any time.
KRISTIJANJE said:
I don't know if that is true, because I have the same problem but I never had any of my previous phones set up to go into silent mode at any time.
Click to expand...
Click to collapse
Same me. And the silent mode is kicking in for me as well.
Wysłane ze zmywarki
Restarting the phone temporarily fixes this problem for me.. But missing many important calls due to this bug
HatRiGt said:
Restarting the phone temporarily fixes this problem for me.. But missing many important calls due to this bug
Click to expand...
Click to collapse
I just had another goint into silent bug. First one today.
I read somewhere that a possible solution is to factory reset the device and choose not to restore any setting from previous device when configuring Google account.
HatRiGt said:
Restarting the phone temporarily fixes this problem for me.. But missing many important calls due to this bug
Click to expand...
Click to collapse
+1 and no true caller installed
FYI guys, this is why i don't use truecaller anymore:
http://www.ethow.com/2015/10/how-Truecaller-works-is-what-you-might-not-like.html
http://www.theregister.co.uk/2016/0..._vulnerable_to_privacy_bug_security_bod_says/
Orion9k0 said:
Not sure if anyone has figured out the solution yet, but I think I've narrowed down the problem a bit more: my phone goes to silent mode the same time each day, and I've noticed it's the same time that my previous phone would automatically go into silent mode (since it was set up to do that). It seems like since I've gotten my OP3, google or some kind of account backup must have remembered by previous auto silent setting and applied it here.
Click to expand...
Click to collapse
I have the same problem (22.00 every night my phone goes into Silent mode) and my thoughts were also going along the lines of some Google profile setting from previous (Moto X) Android transferring across somehow. I did/do like it when I set a Silent time window during the night, however the OP3 does not come out of Silent in the morning (I then slide Alert up and down).
Seems a SW bug. And Hard Reset without transferring Google settings seems like I'd lose out on other things/settings that I've put in place over the years....
Same happened to me, had a priority schedule on previous phone at 22:00 and it got transferred over when I did the Google transfer thing. No idea how to change it, and I'm too lazy to do a factory reset since it means going to the bank to get my banking app activated
The most annoying to thing is that I lose keyboard sounds on SwiftKey even when I go back to normal mode from the scheduled Priority mode...
It has happened to me many times. I thought it was my old Do Not Disturb setting but today it happened around lunchtime.
So I just got a GS8. Fantastic phone. The only issue I am noticing is that when the phone enters "Do not Disturb" mode, it does not exit as scheduled. Typically it is set to turn on at 10 PM each night and turn off at 6 AM the next day. (save for the alarm that goes off at 5 AM). The alarm goes off fine. The phone, however, stays in "Do not Disturb" mode well past 6 AM and until I turn it off. Anyone else notice similar behavior? Could this result from the phone being connected to the A/C charger? I ask because when I set "Do not Disturb" to turn on and off at work it does so just fine. At work the phone is not connected to a charger.
I'm blanking on what it was, but I was running an app that was causing this issue. I've looked through my Google play library and just can't recall what it was. Might have had something to do with volume control. Start by removing anything you aren't using. If the problem persists, try removing anything that sounds like it could interact with audio or notifications until you find it. Worst case, factory reset, confirm issue is gone, then add things back until issue recurrs. I'll try again to jog my memory.
rcobourn said:
I'm blanking on what it was, but I was running an app that was causing this issue. I've looked through my Google play library and just can't recall what it was. Might have had something to do with volume control. Start by removing anything you aren't using. If the problem persists, try removing anything that sounds like it could interact with audio or notifications until you find it. Worst case, factory reset, confirm issue is gone, then add things back until issue recurrs. I'll try again to jog my memory.
Click to expand...
Click to collapse
This gets weirder and weirder. So, I am coming from a Mate 9. on that phone I could set multiple Do Not disturb profiles. So I had one set for overnight (10 PM to 6 AM and one set for work hours (7 AM to 3:30 PM). Although the GS8 only allows one profile, it seems to have "remembered" the second profile. I say this because the phone went into "do not disturb" at 7 AM. I am not even sure how that's possible. I did restore apps via the google, but I cannot think of anything else besides what you are recommending. I may have to do a factory data reset as you recommend and set everything up.
anl2304 said:
This gets weirder and weirder. So, I am coming from a Mate 9. on that phone I could set multiple Do Not disturb profiles. So I had one set for overnight (10 PM to 6 AM and one set for work hours (7 AM to 3:30 PM). Although the GS8 only allows one profile, it seems to have "remembered" the second profile. I say this because the phone went into "do not disturb" at 7 AM. I am not even sure how that's possible. I did restore apps via the google, but I cannot think of anything else besides what you are recommending. I may have to do a factory data reset as you recommend and set everything up.
Click to expand...
Click to collapse
You could turn off the built in Do Not Disturb and use an app like Do Not Disturb Plus to control the DND schedule.
rcobourn said:
You could turn off the built in Do Not Disturb and use an app like Do Not Disturb Plus to control the DND schedule.
Click to expand...
Click to collapse
You know, as long as I have had an android phone and I didn't think to do that. I should have. One issue I need to deal with is whether turning off the built-in Do Not Disturb disables that suspected hidden profile. If so, then I am good to go, if not, then I need to do the factory reset before using an app from the playstore (probably gives me more options than what Samsung allows).
Thanks.
rcobourn said:
You could turn off the built in Do Not Disturb and use an app like Do Not Disturb Plus to control the DND schedule.
Click to expand...
Click to collapse
Resetting the device did the trick. rather than restoring apps from the Huawei Mate 9, I started fresh and downloaded apps from the app store. A pain, but it worked. Thanks again.