Related
You ever finding yourself picking up the phone, swiping down to unlock and the actual ring doesn't show up till AFTER you swiped? It's starting to be really annoying. Usually happens after a long standby as opposed to having used the phone recently. Sometimes even though the ring shows up it doesn't register my swipe the first time at all, even if done firmly.
How the hell can you develop muscle memory with a device that doesn't always react the same way to your input?
I hate having to slow down to cater to my device's (special) needs... It's driving me nuts
I'll be putting it up on swappa tomorrow if I can't find a solution.. if anyone wants, XT1058 bootloader and carrier unlocked
I switch phones a lot so nbd. I hate android's lack of consistency. Plagued every single android flagship device I've ever had in various ways. I think it's time I try WP8 =)
I'm less then 24 hours after a fresh wipe (RSD lite). Running very little apps. Nothing frozen in titanium, just rooted with TWRP recovery.
scorpion667 said:
You ever finding yourself picking up the phone, swiping down to unlock and the actual ring doesn't show up till AFTER you swiped? It's starting to be really annoying. Usually happens after a long standby as opposed to having used the phone recently. Sometimes even though the ring shows up it doesn't register my swipe the first time at all, even if done firmly.
How the hell can you develop muscle memory with a device that doesn't always react the same way to your input?
I hate having to slow down to cater to my device's (special) needs... It's driving me nuts
I'll be putting it up on swappa tomorrow if I can't find a solution.. if anyone wants, XT1058 bootloader and carrier unlocked
I switch phones a lot so nbd. I hate android's lack of consistency. Plagued every single android flagship device I've ever had in various ways. I think it's time I try WP8 =)
I'm less then 24 hours after a fresh wipe (RSD lite). Running very little apps. Nothing frozen in titanium, just rooted with TWRP recovery.
Click to expand...
Click to collapse
never had this issue unless you are referencing the active notifications which has nothing to do with android. If you are talking about pressing the unlock button then the unlock icon appearing and swiping that down (which is the only part that is part of android, then I have never seen this happen. If you are talking about active notification (which i assume you are because it swipes down while the android unlock screen swipes to the right i believe) then yes sometimes it doesn't appear for me but not in a lagging since. In that it just doesn't recognize i want active notifications to pop up. But its typically not when it has been in standby for a while but when i have been moving it a lot like in my hand. Either way, it typically pops up for me before i can even see the screen.
edit: android lockscreen unlocks in all directions not just down.
jayboyyyy said:
never had this issue unless you are referencing the active notifications which has nothing to do with android. If you are talking about pressing the unlock button then the unlock icon appearing and swiping that down (which is the only part that is part of android, then I have never seen this happen. If you are talking about active notification (which i assume you are because it swipes down while the android unlock screen swipes to the right i believe) then yes sometimes it doesn't appear for me but not in a lagging since. In that it just doesn't recognize i want active notifications to pop up. But its typically not when it has been in standby for a while but when i have been moving it a lot like in my hand. Either way, it typically pops up for me before i can even see the screen.
Click to expand...
Click to collapse
When you pick up the phone, the unlock ring appears. I'm saying the time it takes for it to appear is not consistent. This makes it impossible to develop the muscle memory needed to consistently unlock your device fast. It makes me feel like my phone can't keep up with me, something I've never had a problem with on the...dark side.
I wasn't referring to this as this as the sole reason as why I think android is consistent, but just one example out of many. Inconsistent scrolling, dropped frames during transition animations, app open times varying wildly even if precached, etc. I just don't think I'm an android guy, I can't ignore the crappy UI handling. Some people don't even perceive it as lag but for me it just jumps in my face every time. BUT that's subject matter for a different topic.
double post delete pls
scorpion667 said:
When you pick up the phone, the unlock ring appears. I'm saying the time it takes for it to appear is not consistent. This makes it impossible to develop the muscle memory needed to consistently unlock your device fast. It makes me feel like my phone can't keep up with me, something I've never had a problem with on the...dark side.
I wasn't referring to this as this as the sole reason as why I think android is inconsistent, but just one example out of many. Inconsistent scrolling, dropped frames during transition animations, app open times varying wildly even if precached, etc. I just don't think I'm an android guy, I can't ignore the crappy UI handling. Some people are used to it and don't even perceive it as lag but for me it jumps in my face every time. BUT that's subject matter for a different topic.
Click to expand...
Click to collapse
if you want to keep up with muscle memory then click the unlock button on the right and then unlock by swiping the lock on the screen like all the other phones on the market. It will work every time all the time with 100% accuracy/consistency. If you don't like the active notifications that Motorola built into the phone then don't use it. The inconsistency you are describing here is Motorolas fault, but it is their first shot at active notifications so I expect more bugs than I have seen so far.
But as i said before, mine either doesn't pop up or pops up before i can even look at the screen so I don't have the problem you do. And when it doens't pop up its typically because Im playing with in my hand then decide i want to use it and I have been tossing it all around. If it is sitting still or in my pocket and i pick it up it pops up the ring faster than I look at the screen. I doubt it but maybe it has to do with the twrp rooting method.
If I have to resort to that, 95% of what moto X brings to the table for me, is gone. At that point I might as well be using a nexus for the awesome dev support.
I would rather try to troubleshoot the issue since it IS software. It is evident because the method which you described brings up the phone instantly anytime anywhere so the hardware capability is there... i guess... lol.
No issues on mine, active notifications with and without notifications works every time, before the phone is completely flipped or out of my pocket, the pixels are fully lit. I'm stock non rooted though, but it works every time as it is intended.
Sent from my XT1058 using XDA Premium 4 mobile app
No issue for me either. When I pickup the phone or take it out of my pocket, the ring is there. And I've experienced zero lag either in UI transitions or opening apps.
I've never experienced anything like this before. The performance of my X has been flawless.
I tested it a little bit more and I found you are right. I didn't notice it because I don't grab my phone and instantly try to unlock. When I did let it sit for 10 minutes or so and had the screen not flipped over so I could watch it there was a noticeable 1 second time difference as opposed to when I laid it down let the screen go dark then pick it back up. But for me I really had to grab my phone and try to unlock it before bringing it to my face for it to not pop up in time for my unlock swipe.
Sent from my XT1060 using xda app-developers app
So my dad just picked up a Moto X today on Verizon, I've had my DE edition on VZW for about 2 weeks now. Well, I was over at his house today showing him some stuff, and I noticed his phone announced calls and texts all the time, even when not driving, and asked him if he wants to answer. I of course turned off Moto Assist, but it still announced calls and asked if he wanted texts read back. (It would announce who texted and ask if he wanted to listen, or ignore. Not sure if mine does this, I had Assist off before today) I went through every single option on his phone. I'm guessing the Moto Assist is bugged into thinking he's always driving, but the little icon never shows up in his notifications, and I actually turned off Assist and it was still doing it. Cleared data too. I tried everything. Reboots, turned on and off GPS, etc.
The rub is, we both actually LIKE it on all the time. It's nice to just have the phone on the desk and hear who's texting and the message without having to touch the phone. It's nice to be able to answer the phone on the coffee table without grabbing the phone, or even moving.
Is there anyway to enable this functionality all the time? (Or disable it on my dad's phone for that matter) Has anyone else run into this 'issue'? (If my dad hadn't seen my phone, he would have never known it wasn't supposed to be like that all the time.) Any ideas?
I too would like to see this 'feature' as a option, and I hope it can be enabled [on purpose] in the future. (If Motorola doesn't have sense enough to make it an option, maybe a ROM developer can.)
I searched and found this:
We're aware of a rare condition when calls and text will be announced even when you can't see the "drive mode" notification on the status curtain. We're fixing this in the next upgrade. (The simplest way to get out of this situation -- and it's not that simple -- is to leave Assist's drive mode settings on, get in a vehicle, allow drive mode to kick in again. When you do that, Assist will get back to the correct state. After the issue is fixed, you should rarely encounter the issue again. Yeah, I know. Not something anyone is eager to do but we wanted to put it out there.)
Click to expand...
Click to collapse
http://forums.androidcentral.com/motorola-droid-maxx/314715-assist-driving-problem.html#post3072243
FWIW I first thought your dad's phone might be stuck in "car mode" as thought it was in a car cradle, but that would have a steering wheel icon in the notification area. I actually tried car mode by using the "car mode on" app to force it on. It seemed to put my phone in car mode, but that alone did not cause the phone to announce calls, etc.
Thanks man! I actually found that post as well earlier today, it looks like it is indeed a bug with Moto Assist. Funny thing is, my dad has it left on and I called him this morning after he drove to work, and it's still working. IDK lol, but he likes it so whatever.
I would LOVE to be able to do this while playing video games, or working, or whatever though. Motorola better just make a toggle switch... it's not like it's hard.
Is anyone experiencing their phone waking up and waiting for you to ask it something? It's happened just sitting on the counter, my pocket or streaming music/podcasts. It happens at least one or more times a day, I tried retraining it for my voice a few times but still happens.
FSRBIKER said:
Is anyone experiencing their phone waking up and waiting for you to ask it something? It's happened just sitting on the counter, my pocket or streaming music/podcasts. It happens at least one or more times a day, I tried retraining it for my voice a few times but still happens.
Click to expand...
Click to collapse
Go retrain it once more in a completely silent room. You should be able to hear nothing except air moving (fan, a/c, etc.). Then report back.
FSRBIKER said:
Is anyone experiencing their phone waking up and waiting for you to ask it something? It's happened just sitting on the counter, my pocket or streaming music/podcasts. It happens at least one or more times a day, I tried retraining it for my voice a few times but still happens.
Click to expand...
Click to collapse
Biggest thing is keep it at arm's length. Like really, extend your arm to the fullest, and then speak normally. Try it.
natezire71 said:
Go retrain it once more in a completely silent room. You should be able to hear nothing except air moving (fan, a/c, etc.). Then report back.
Click to expand...
Click to collapse
jhnl33 said:
Biggest thing is keep it at arm's length. Like really, extend your arm to the fullest, and then speak normally. Try it.
Click to expand...
Click to collapse
The last time I walked out to my garage to be away from any noise, I'll try again today and make sure I hold it at arm's length(tried that on initial setup)
FSRBIKER said:
The last time I walked out to my garage to be away from any noise, I'll try again today and make sure I hold it at arm's length(tried that on initial setup)
Click to expand...
Click to collapse
Good luck! I had the same issue as you in the beginning. I uninstalled updates and reinstalled to try to make sure previous cache and settings were cleared and re-trained at arms length and now it works pretty well!
FSRBIKER said:
The last time I walked out to my garage to be away from any noise, I'll try again today and make sure I hold it at arm's length(tried that on initial setup)
Click to expand...
Click to collapse
also, make sure you use the same pitch and cadence when saying it. If i want the phone to pick up my voice easier, i can say ok google now when training it in slightly different ways. But then my phone also comes on and thinks im saying it when no one has said anything close to ok google now. If you make sure everything sounds the exact same when saying it, i didn't run into any problems. But i can't wake the phone up when i first wake up in the morning lol. I always try but i apparently sound like death whenever i first wake up.
jayboyyyy said:
also, make sure you use the same pitch and cadence when saying it. If i want the phone to pick up my voice easier, i can say ok google now when training it in slightly different ways. But then my phone also comes on and thinks im saying it when no one has said anything close to ok google now. If you make sure everything sounds the exact same when saying it, i didn't run into any problems. But i can't wake the phone up when i first wake up in the morning lol. I always try but i apparently sound like death whenever i first wake up.
Click to expand...
Click to collapse
I agree, try using the same voice for all three samples. I know that early on people were suggesting you say it with slightly different speed etc but I have found it is best to try to say it the same all three times and let the software in the Moto X handle slightly variations automatically.
Mine wakes up all day sitting on my desk at work. I do talk about Google a lot, but I never say my phrase. It's funny some of the stuff I see it type...
Sent from my XT1060 using Tapatalk
This is an interesting thread for me. I had the Note 3 (hi galaxy) and Nexus 5 (ok google). Both of them would think I was talking to them when I wasn't, and I have almost the opposite problem with the Moto X. I have a hard time to get it to listen. I re-trained, re-trained, re-trained.. My wife's phone works flawlessly. I do love that we train our voices because she uses here touchless control all the time right next to me and my phone has yet to mistake mine for hers.
Maybe I need shorter arms.
OK quick update, I uninstalled the Touchless Control update and retrained my Moto X again in my garage this morning. It's been about 7 hours and it hasn't once yet turned itself on. I streamed music, have been in congested areas with people, a business meeting and it's working perfectly now.
I'm going to wait for 24 hours to make sure it's still working correctly and then install the update to the app.
About ready to scream!
The touchless control on my Moto X Developer Edition is extremely sensitive. Anytime anyone talks in the office that I work in, the dang phone comes on and waits for someone to give it a command. All anyone has to do is say "OK" and it does this even when I don't want it to. I've tried retraining the phone multiple times and it doesn't seem to help me out at all. I'm going to be so glad when the Lollipop update finally rolls out for this phone so I can get retrain this with a different launch phrase that will not be so easy to trigger on my phone. In the meantime, has anyone been able to get the sensitivity adjusted on this phone? If so, how? I'm thinking of going to Cyanogenmod 12.1 until Lollipop rolls out for the XT1060,
Any help that I can get on this would be greatly appreciated.
Cindy
Hi everyone,
I have had the Moto G 2nd Gen for about 10 days now and I have noticed that notifications from several apps (Exchange email, Gmail, Whatspp, Facebook...) are either delayed by a few hours or don't come at all. This happens on both Wifi or my network. Has anyone else experienced this ?
I have tried the following with no success:
1- disable Wifi optimization
2- factory reset phone
3- Installed PNF No-Root and set hearbeat to 5min
4- Cleared data & cache of apps
My phone is not rooted running 4.4.4
Thanks
Yes I am having the same problem this is my thread on the subject:http://forum.xda-developers.com/moto-g-2014/help/notification-problems-t2875216
I have tried 1, 2 and 4 of your attempts to fix it to no avail.
Before I reset the phone all notifications showed the correct time that they should have come, for example if I slept the phone at 10:40 and a notification came at 10:44, I then woke the phone at 10:50 the phone would immediately buzz and sound but it would say the notification came at 10:44 in the notification draw.
However after the factory reset of the device in the same situation the notification draw would show 10:50 but I know that is wrong because WhatsApp for instance will say the correct 10:44 timestamp on the message in the app.
Notifications when the phone is awake come through perfectly every time.
The problem is actually not limited to just notifications, I play music from my phone, when the the phone is awake it plays perfectly, when you sleep the phone, the music will carry on playing but occasionally it will have a hiccup where it will stop playing for a split second then carry on, and sometimes at the end of a song you expect the next song to start but it never will, if you then wake the device the song will start playing like nothing was wrong (exactly how the notification problem is).
I don't know what the problem is I suspect something to do with bad software or faulty hardware if there is a specific part of the hardware that only comes into play when sleeping (I don't know if there is or not).
What are the specifics of your phone? Mine is a XT1068 8GB Dual SIM Retail GB completely stock 4.4.4, the system version is: 21.11.14.titan_retgb.retbgall.en.GB retgb, will be good to know if this affects specific versions of the phone or any version, to narrow down the problem.
The problem is also completely random I cannot 'make' the problem happen it just does.
Mine is the same as yours XT1068 8GB Dual SIM Retail GB 21.11.14.titan_retgb.retbgall.en.GB retgb.
I also have the same problem with music, I also noticed this with chromecast, it seems to loose connection after playing one track.
I contacted Motorola assist and they said replace the phone. I'm not sure if replacing it will solve the problem, I'm guessing this is a software issue. I
I got it from Amazon UK, I'm thinking of returning this and going back to my Galaxy Nexus and wait for the new Nexus phone.
Because we have the same software version I more strongly suspect this is a software issue now, I'm not sure what to do, I don't really want to return the phone as I will be left phoneless and a replacement would just come with the same software.
Another option would be to re flash to a different software version (an international version) but that will invalidate the warranty.
Not really sure what to do, would be good hearing if any retGB people are not having any problems, if any are reading this thread? or if any non retGB are having this problem.
jay2the1 said:
Yes I am having the same problem this is my thread on the subject:http://forum.xda-developers.com/moto-g-2014/help/notification-problems-t2875216
[...]
The problem is actually not limited to just notifications, I play music from my phone, when the the phone is awake it plays perfectly, when you sleep the phone, the music will carry on playing but occasionally it will have a hiccup where it will stop playing for a split second then carry on, and sometimes at the end of a song you expect the next song to start but it never will, if you then wake the device the song will start playing like nothing was wrong (exactly how the notification problem is).
I don't know what the problem is I suspect something to do with bad software or faulty hardware if there is a specific part of the hardware that only comes into play when sleeping (I don't know if there is or not).
What are the specifics of your phone? Mine is a XT1068 8GB Dual SIM Retail GB completely stock 4.4.4, the system version is: 21.11.14.titan_retgb.retbgall.en.GB retgb, will be good to know if this affects specific versions of the phone or any version, to narrow down the problem.
The problem is also completely random I cannot 'make' the problem happen it just does.
Click to expand...
Click to collapse
For notification problem read description of https://play.google.com/store/apps/details?id=com.andqlimax.pushfixer.noroot&hl=en
and yes I also have same problem for play music my phone is XT1068 16gb retaildsdsall.en.03.retin
I think you should create new thread for play music problem, seems like we all have that
bhavin192 said:
For notification problem read description of https://play.google.com/store/apps/details?id=com.andqlimax.pushfixer.noroot&hl=en
and yes I also have same problem for play music my phone is XT1068 16gb retaildsdsall.en.03.retin
I think you should create new thread for play music problem, seems like we all have that
Click to expand...
Click to collapse
:\ it doesn't look like that app fixes it even when changing the interval to 1min.
I've sort of found a way to at least make it happen to test stuff, using 2 devices I have installed Telegram on both and set each device up with different numbers so I can message from one device to the other, using the other device to the Moto G if I send messages sometimes the notification is instant, sometimes it is a minute later, there is no pattern on whether it will receive it instantly or delayed, however waking the device will always make the phone buzz if it is delayed.
If I add my tablet into the mix (tablet and Moto G on the same number) the difference is very stark, sending 5 quick fire messages the tablet buzzes for every message, the Moto G may buzz for the first and maybe the 2nd but then nothing for the other 3, or none at all, or none and then double beep on the last message or a little time after the last message. (all this is on WiFi)
The best news is that it has eventually beeped within a couple of minutes for every message, but in a conversation on WhatsApp a couple of minutes is a long time.
Again if the phone is awake or playing music while sleeping it works perfect a beep for every message every time (WiFi Again). (I know PNF is only a partial fix for WhatsApp and Telegram but I can't test it easily with Gmail and the main concern is WhatsApp as I want those messages without delay)
It's definitely something to do with keeping the phone 'active', if it's playing the music it works, if it's doing nothing it is literally like it's sleeping on the job.
I'm going to test on 3G but seems to work almost perfect so far (I haven't really used my phone on 3G much as I'm normally on WiFi)
@katkat911 can you tell me about your WiFi setup it isn't TP-Link is it? because I'm wondering if it could be a WiFi setup issue as my phone originally couldn't even detect my router until I changed some settings. (I know you have the problem on 3G too)
Apologies if this is a bit rambly I want to put my casual findings out there in order to let others have the information.
Been testing on 3G, after the phone is slept all notifications work perfectly for 10 minutes with the phone buzzing a second or 2 after my tablet, if you sleep the phone and send a message after 10 minutes the phone will only buzz after 30 minutes from being slept (ie the heartbeat).
I've reinstalled PNF app and will experiment more tomorrow, still not sure how I will fix WiFi but I think a little more experimentation is required (yet doesn't make sense why my tablet always works 100% and the phone doesn't when using the same router)
jay2the1 said:
:\ it doesn't look like that app fixes it even when changing the interval to 1min.
I've sort of found a way to at least make it happen to test stuff, using 2 devices I have installed Telegram on both and set each device up with different numbers so I can message from one device to the other, using the other device to the Moto G if I send messages sometimes the notification is instant, sometimes it is a minute later, there is no pattern on whether it will receive it instantly or delayed, however waking the device will always make the phone buzz if it is delayed.
If I add my tablet into the mix (tablet and Moto G on the same number) the difference is very stark, sending 5 quick fire messages the tablet buzzes for every message, the Moto G may buzz for the first and maybe the 2nd but then nothing for the other 3, or none at all, or none and then double beep on the last message or a little time after the last message. (all this is on WiFi)
The best news is that it has eventually beeped within a couple of minutes for every message, but in a conversation on WhatsApp a couple of minutes is a long time.
Again if the phone is awake or playing music while sleeping it works perfect a beep for every message every time (WiFi Again). (I know PNF is only a partial fix for WhatsApp and Telegram but I can't test it easily with Gmail and the main concern is WhatsApp as I want those messages without delay)
It's definitely something to do with keeping the phone 'active', if it's playing the music it works, if it's doing nothing it is literally like it's sleeping on the job.
I'm going to test on 3G but seems to work almost perfect so far (I haven't really used my phone on 3G much as I'm normally on WiFi)
@katkat911 can you tell me about your WiFi setup it isn't TP-Link is it? because I'm wondering if it could be a WiFi setup issue as my phone originally couldn't even detect my router until I changed some settings. (I know you have the problem on 3G too)
Apologies if this is a bit rambly I want to put my casual findings out there in order to let others have the information.
Click to expand...
Click to collapse
I agree with you that it has something to do with phone going to sleep. My WiFi router is Netgear. I have they same problem with every other WiFi network and also on 3G. I didnt have this problem on my previous phone Galaxy Nexus.
PNF doesnt seem to work at all.
Notification problem is proved. I also have the issue. that 10 mins theory is absolutely right. as both of you have done good research, I would suggest one of you create a question at https://forums.motorola.com/hives/e3ec93b1d7/summary and summarize all your findings. Some one from Motorola will respond definitely. I see this as a deep sleep issue with the kernel. Once submitted, you can share the link of your thread here. I and others will comment confirming this as a common problem.
You may have to first register with your moto id or may be google id.
anshumandash said:
Notification problem is proved. I also have the issue. that 10 mins theory is absolutely right. as both of you have done good research, I would suggest one of you create a question at https://forums.motorola.com/hives/e3ec93b1d7/summary and summarize all your findings. Some one from Motorola will respond definitely. I see this as a deep sleep issue with the kernel. Once submitted, you can share the link of your thread here. I and others will comment confirming this as a common problem.
You may have to first register with your moto id or may be google id.
Click to expand...
Click to collapse
I have posted this on the Motoral forums here https://forums.motorola.com/posts/dbb4806484
I have been experimenting again today, the problem is significantly worse on WiFi notifications are much slower than on 3G, the problem seems completely unreplicable, sometimes notifications come though aOK even after I have left the device sleeping for an hour (using WiFi) or sometimes the notification will be delayed for several minutes even if it has only just been slept (again using WiFi), 3G on the other hand there is a definite 10 minute cut off from sleeping the device.
I've had PNF installed since last night and it doesn't help WiFi at all, but 3G it might, I say might because sometimes after 10 minutes (even an hour later) if I send a notification I do receive it straight away (something that never happened before I installed PNF) but then sometimes it doesn't and it's delayed for several minutes again.
I will join the Moto forum and add my weight to that when I get back to my computer as you need to sign in with a Google account.
I've also noticed that if the phone is sleeping whilst charging notifications work flawlessly in much the same way playing music while the device is sleeping they do. I've posted this finding in the Moto forums as well.
Fingers crossed we get a solution :fingers-crossed:
jay2the1 said:
I've also noticed that if the phone is sleeping whilst charging notifications work flawlessly in much the same way playing music while the device is sleeping they do. I've posted this finding in the Moto forums as well.
Fingers crossed we get a solution :fingers-crossed:
Click to expand...
Click to collapse
I have also noticed that. It seems that many are having this issue, so far no reply from Motorola
Motorola might be investigating about it. Yesterday i went back to dalvik from art. I tested the notifications the while day. On Wi-Fi, i didn't see the delays any more. In 3g many tests were successful even after 1hr of deep sleep. Only at 4pm India time i found a delay of 22 mins for whatsapp notification. There i also realized that it had switched to 2g due to bad signal in that room. I was definitely having problem when i was on art. Last night i also got the ota for build 23. I see that the kernel is updated. I will monitor one more day and report here.
Motorola has at least seen the post even with no reply, I just hope they are busy behind the scenes working out what is wrong so they can fix it.
I've never used ART (I'm completely stock), and all the problems are still happening today, unfortunately Telegram is being DDoS'd today so haven't been able to test anything out.
It will be interesting to hear if the update you received helps in any way, esp with the updated kernel, since your retGB device received it hopefully ours may do soon too.
As far as I can tell it doesn't affect calls and SMS, but I simply don't use SMS or calls at all (WhatsApp ftw) so my testing has been the odd 'prank' phone call from my 2nd phone and it rings every time, but it's not enough to confirm if it's a fluke or if in fact it does not affect phone calls/SMS.
SMS and calls won't be impacted due to this. It's mostly related to deep sleep state of the phone. It will impact data connectivity mostly.
I have been testing as and when possible after the update. On Wi-Fi, I didn't see any delays for WhatsApp, Facebook notification, exchange mails through nine app even if the phone was in sleep mode fur an hour or so. I saw 1 min delay in Viber twice.
anshumandash said:
SMS and calls won't be impacted due to this. It's mostly related to deep sleep state of the phone. It will impact data connectivity mostly.
I have been testing as and when possible after the update. On Wi-Fi, I didn't see any delays for WhatsApp, Facebook notification, exchange mails through nine app even if the phone was in sleep mode fur an hour or so. I saw 1 min delay in Viber twice.
Click to expand...
Click to collapse
That's good news, hopefully the update has indeed fixed it, there's no indication when the update will hit the UK but if it does fix it then ASAP I hope.
anshumandash said:
SMS and calls won't be impacted due to this. It's mostly related to deep sleep state of the phone. It will impact data connectivity mostly.
I have been testing as and when possible after the update. On Wi-Fi, I didn't see any delays for WhatsApp, Facebook notification, exchange mails through nine app even if the phone was in sleep mode fur an hour or so. I saw 1 min delay in Viber twice.
Click to expand...
Click to collapse
How is the phone with the new OTA update ? are notifications still delayed?
There's still no word from Motorola
katkat911 said:
How is the phone with the new OTA update ? are notifications still delayed?
There's still no word from Motorola
Click to expand...
Click to collapse
In a different thread Motorola amin had mentioned that they are investigating the notification delay issue. I don't see much delays after the update. There are few mins here and there, but mostly good. If you haven't received the update yet, check the ota thread and update manually. It's the same update. Then see if you find any improvement.
I got the OTA update yesterday and I'm still having the same issues
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