Moto X, 4.2.2 stock, rooted
When receiving a an email, message, or whatever (e.g., Gmail, snapchat, kakaotalk, google voice), the active notification appears as normal (vibrate/sound + screen display), but then the phone repeatedly displays the notification until it's unlocked. I do want the initial notification, but just the one. After the initial notification, further notif. only display the screen (no sound/vibrate).
When there isn't a notification, it doesn't display the clock over and over again as if I'm picking it up, so it's not like it's being moved around or something.
It did not used to do this, but I'm not sure exactly what setting/app/whatever would have caused this.
'Active notifications' has an option to disable certain apps or turn off completely, but there are no 'repeat' or 'lockscreen' settings located there, or in individual apps.
When I googled/searched for the issue (key words: active, notifications, repeat, stop, android, alert), I found these related posts, which seem to describe what I'm experiencing (albeit on different phones). Edit: ah, I can't post links yet, if you would like to look at them, please google the parts-of-the-url below
s4-active-message-notification-doesnt-stop-coming-up-lock-screen
android-kit-kat-moto-x-repeated-notifications-for-the-same-email
Has anyone else had this problem? What settings, if any, can I check for to disable these unwanted (repeated) notifications or how else might I go about it?
This isn't a bug or an issue, it's a feature. It's something called "breathing" notifications.
Every so often, the phone will give you the notification again just to be sure you saw it the first time. There is no way to remove or alter this feature through Active Display's settings.
If you are looking for an equivalent to Active Display, a good one (and the only one I know of) is DynamicNotifications by GreatBytes.
Have you tried swiping the notification to the side? That should dismiss it.
Sent from my XT1053 using Tapatalk
It seemed to me it wasn't normal behavior, as I don't remember it happening when I first got the device, but if you say it's intended, I'll go with that.
DarkWolffe: you say "every so often". The notifications are appearing every 5 seconds or so. Is this inline with what your own experience? If I can't change that interval from the native settings, might the app you linked be able to? It seems that DynamicNotifications is made for devices that don't already have Active Notifications. (perhaps I'm supposed to disable AN and only use DN?) Thank you for the link, though, I'll check it out.
scottjb: Ah, I figured that out sometime after making this post, but thank you for that tip. It's useful when I may actually see the phone, but when I'm away from the phone or sleeping, for example, I'd prefer it not to behave that way. I realize it's an AMOLED screen, so the battery really shouldn't be affected too much, but it doesn't feel right to have it turn on over and over again so often.
Knowing they're called "breathing notifications" has allowed me to better search for related topics. It seems that turning the phone over or putting it in a pocket will stop the breathing. I'd still prefer if I could change the interval somehow, but I'm satisfied to have figured most of how it works out.
The interval of the notifications seems to change over time. When you first get a text message etc it seems to flash the notifications more often, after some time I believe it slows down a little. You can have the feature disabled at night, my ringer is silent from midnight to 9 am and my active notifications are disabled from 1 to 7 am. When disabled at night it only stops it from displaying on its own, if you move the phone it will still display the clock and any notifications.
LG Pulse with KitKat 4.4.2 same issue
I don't have a Moto X, I have the LG Pulse from Virgin Mobile Custom. My notifications do that, too! I have KitKat 4.4.2. I have never experienced this and I certainly would NOT make it a default nor intended action. Mine start out at the first notification + sounds, then 10 seconds later, 15 seconds later, 20 sec, 25 sec, etc. It is very annoying and there is no option in the system settings nor individual app settings to stop that behavior. I may just have to turn off notification sounds as this is ridiculous.
You can try setting the "sleep at night" option, and adjust the time to be on all the time (1am to 12am).
I believe this setting is supposed to suppress the breathing notifications. Though, it won't stop it from showing if you move the phone around... I know this cause my phone charges on my bed at night and when I roll around, it triggers AD, even though I have sleep mode on.
Hope it helps!
tapa'd on my moto x
Damn Tapatalk, won't let me edit..
tapa'd on my moto x
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
This has been happening randomly for a few months. I can go days when notifications are fine and they come through on my phone immediately. Then, for no reason, there are days when no notification show at all until I wake my phone.
They're clearly being blocked and my phone only attempts to pull them in when I wake it. Like a doze setting
It all started around the time Marshmallow 6.01 landed on the phone.
All battery saving optimisation settings are off.
All notifications are set to on.
I have tried EVERY app that I can find to set the Google heartbeat interval to a lower time. None solve the issue.
Factory reset doesn't fix it.
I have (always on) fiber internet so idle timeout settings on the router cannot be to blame for killing the Google heartbeat check.
I have tried it on mobile data only and it is the same
Other people online have had the same issues on other Samsung devices but I can't find anyone suffering from this on the Note 5.
Could it be an issue (somehow) with my Google account, since all notifications have to be pushed through this?
Worried that if I get a new phone I'll still have the same issue.
Any help would be appreciated.
are u using greenify??? what android u have 6.0.1 ??? did u try on smart manager / battery / to not optimize app u want get notification????
N920c/64g/cc n7 port v3/ arise sound/ doulby /xposed greenify+powernap+amplify
Not got Greenify.
Not enabled any power saving at all.
All apps are set to notify
Either the phone is blocking notifications randomly, or my Google account is.
Hello, I am not receiving notifications for Snapchat and various other apps on my new Galaxy S10+ Unlocked Version on Verizon. I turned off all the battery optimizing features, made sure it doesn't get put to sleep, etc. I believe the problem to be Doze because when I used ADB and turned off Doze it began to get notifications and they were also received instantly. Any advice or help would be great, thank you.
I am seeing this issue, but only for select apps. It was working fine before but now it just doesn't notify me on some apps, even after I unlock the phone and display is on(not in deep sleep). Mine is Exynos, not sure what is causing it yet.
Hi, I've had my Redmi Note 10 Pro for 3 weeks now, and since the update to MUIU 12.5 loaded last week my alarms have stopped working. They seem to be set up in the Clock app, but they don't go off - and before anyone says I just slept through them, they don't appear as missed notifications.
Has anyone else had this problem?
I've got a feeling my phone shuts down overnight, I mean completely. I woke up at 3 this morning (cramp!) and while my toes were slowly uncurling themselves I checked my phone, and it was completely shut down. I restarted it, and this morning the alarms worked ok. I've disabled the useless 'always on' screen, and un-set the DND, anyone else having this problem? (MUIU 12.5.1.O)
FOUND OUT THE PROBLEM - for some reason the 'schedule on/off' {in Settings-Security) had been set to power the phone down at 1:30am, and reboot at 5:30. Presumably because I hadn't put my lock code in at 5:30 (zzzzz, 'nuff said), the alarms didn't register. But weird though, I don't recall changing the power settings like this