I bought the Watch R a week or so ago and I've been trying to work out why the Google Now notifications are so unreliable.
At first, I thought it was just me - I never really embraced Google Now and actually had it turned off on my phone (Galaxy S6 Edge). A few days ago I turned it on, configured it and was expecting to see the odd card popup on my watch every now and then but I've had zip.
So, I thought I'd test the notifications on the watch, from the Android Wear app, but the only notification that works all the time is the phone call. Most of the other notifications just don't pop up on screen and the only way I see them is to swipe the face from above and then they're there. Is this normal behaviour? I thought that notifications were supposed to popup on the screen, like on my phone!
I've reset the phone a couple of times in desparation but it's made no difference. I've unpaired the watch from the phone and re-paired it after forgetting the device. No difference. Removed all the custom watch faces and used only the once that came with the watch and once again, no difference.
I do get notified of text messages and emails with no problem, but nothing from Google Now.
Can anyone please suggest anything?
I have the s6 and I don't receive any notifications except the test phone call. I believe it to be a samsung problem with it killing the wear app from running in the background. watch worked fine with my other phones.
It's ridiculous, my s6 / gwr doing the same thing. Reboot both and things work for a little while, then gradually peters away to nothing. Except for sometimes I'll tap the watch for the time, and some random google now cards will be there, which I dismissed days before! Swipe them away but the same few keep coming back! As for the weather reports, well they've not worked for over a month now. And all this without me touching any settings whatsoever. I've exempted the android wear app from battery optimisation in the s6 too, incase they were that dense they'd overlooked that core app, but doesn't seem to have sorted it. Seems every time these companies update stuff they break it, and don't care about fixing it.!
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.
Got my moto g6 amazon exclusive model a few days ago. I started to notice while the phone was just sitting on my desk and gone to sleep / doze? my notifications were not coming through (around 5-10 mins after screen off). Any notifications within that time would be fine. After that if I had any new notifications, I would get them all in one go after I turned the screen on or moved my phone with moto display. (I turned off the motion sensor feature)
Just trying to get an understanding of whats going on. I have played around with some settings and currently seem to have got it back to normal by setting all my important apps (gmail/whatsapp/twitter...) to not be battery optimised. I also found some notification setting elsewhere that gave the default launcher permissions. I used nova launcher so I gave that permission too just in case, but I think the main fix was battery optimisation.
Just find it odd that I have never had to go into battery optimisation before on my previous phones (nexus 4, wileyfox swift) and notifications have come through fine after long periods of time in sleep mode.
Anyone able to suggest something else that may be causing this, or I could try. I wouldnt have noticed this problem if it wasnt for being at my PC and seeing new emails/fb messages coming in and not getting notification on my phone after the phone had gone into sleep.
-------------
As of typing this I recieved an email that also did not notify on my phone. Only when I picked up the phone I got it instantly. Battery optimisation for apps may not have worked.
Hi,
Could you solve this issue? If so, how?
Thanks.
I had the same issue a few weeks ago after playing around and disabling apps/services I didn't think i needed . I had to re-enable the "Moto" app, go into "Moto Display" and enable "Peek Dsiplay". That fixed notifications coming through the locked screen for me.
Hi, I had a samsung s8+ and just got a new huawei p30 pro, used the phone clone software to transfer my files, that mostly went well, eveb though it said 100% transfered there was a good few apps that didn't seem to transfer onto my new phone.
anyway, since starting to use it properly, i am getting notifications for things like texts, but i havn't has any game notifications yet, i am still getting thm on my s8+ though but i have turned that off now anyway but they were still coming through.
I did notice a couple of apps have mentioned about a battery setting that restricts background data but from what i can see they all seem unrestricted.
also, i keep having to manually set the brightness of the phone and turn auto brightness off, then the next thing the screen looks really dark again, i check and its gone back to auto brightness?
any idea about these issues?
thanks
James