Related
OK say I have paired it with a Sony Xperia Z1 compact.
As soon as the screen turns off it loses connection with the phone. It still thinks it's connected (there is no cloud with a line through it on the watch face screen) and when you say ok google it tries to interpret but then I get the screen that says
disconnected and to the right is a little icon of a cloud with a line through it and underneath there are options for built-in functions like "show my steps", show me my heart rate" , etc
If I manually disconnect and reconnect using the Android Wear app on the phone it works again straight away.
Anyone else seeing this behaviour?
I had that problem right at the start. Can't remember how I fixed it
Restart both devices? Uninstall and reinstall wear app on phone? Update to latest watch firmware?
Do you have stamina activated which us turning your Bluetooth off on screen off?
Sent from my D6503 using XDA Premium 4 mobile app
skitty said:
Do you have stamina activated which us turning your Bluetooth off on screen off?
Sent from my D6503 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey that could be it. I do have stamina enabled because the battery in my phone is going down rapidly with the watch connected. I'll turn stamina off and see what happens. Cheers!
EDIT: I think this might be fixed now after turning off stamina mode. I'll need to test furtehr thugh. Thanks skitty
I'm still getting this quite a bit. Is anyone else still experiencing random bluetooth disconnects? It still thinks that they're connected until I try to do a google now search and then it tells me they're disconnected. I tried uninstalling the wear app on the phone and reinstalling. I also cycled bluetooth and that seems to fix it in the short term. Suggestions?
shadeofgrey said:
I'm still getting this quite a bit. Is anyone else still experiencing random bluetooth disconnects? It still thinks that they're connected until I try to do a google now search and then it tells me they're disconnected. I tried uninstalling the wear app on the phone and reinstalling. I also cycled bluetooth and that seems to fix it in the short term. Suggestions?
Click to expand...
Click to collapse
I'm pretty sure, for me, the answer was to disable stamina mode on my xperia phone. I very very rarely see the disconnected message any more.
Cycling BT also used to help for me but all that was doing was temporarily foxing the stamina setting. It always switched itself off again.
I'm having the same issues, here's my post in the general android wear help forum
"So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?"
I have also tried running stock faces vs custom with no change
hasn't happened since 9:00 this morning.. today... yesterday I missed almost every notification
disconnect
Not sure if this is related or if anyone can give advice but for me (HTC one max) whenever my Samsung gear live is disconnected from phone...phone randomly restarts all by itself. Tried factory reset, was fine until I set it up again. Made sure android wear was off...just tried turning off Google now see if that helps.... Anyone else experiencing the restarts? Sorry on phone so messy post...
Woah sorry i forgot about this post. My issue was the stock kernal for cm11. When i switched to another kernal, my issue vanished.
I am having the issue where if my phone is asleep I cant do any searches. Now I know or at least I'm pretty sure that its not the watch or the app but something on the phone. Phone is a galaxy note 3 sprint version running temasek's unofficial cm12 rom. The watch is stock of course. When I get a notification the watch will happily wake up and tell me about it, but when I try to tell the watch a command with the phone sleeping is where the problem presents itself. The issue appeared after a few of the rom updates (happens even with a clean install) and I know he's a busy guy (temasek) but I would like to see if anyone here could help me figure it out to be able to provide a solution to others that are having my same issue. Any and all help is appreciated.
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
I 've had the Urbane for three weeks now, and I'm pretty pleased* with the watch except for a major problem:
I keep seeing that "cloud with a line through it" icon on top of the watch face way to often.
I'm actually looking at it right now - I'm at work, my Urbane is on my left wrist, and my phone is on the desk 20 centimeters away.
Since I haven't heard many others complaining about this, I'm suspecting the problem to be on the phone side - this is a "China phone", an Elephone P3000S (64bit, 3GB RAM) that I bought quickly as a cheap, but (on paper) good spec'd replacement for my broken Sony Z1 Compact.
But nevertheless, I thought I'd asked here if anyone else are experiencing the same?
I've factory reset the watch, I often reboot it, I reboot the phone even more often, and most of the time connection is re-established but lasts only for maybe 15 minutes up to several hours. I have disabled wifi on the watch to see if that improves things - initially I thought maybe it did (as long as I kept the phone nearby, of course), but after a while it seems it's not the case.
Anyone have any other tips? ...Before I replace the phone?
Thanks,
Christopher
*: of course I would prefer a brighter screen (when needed, i.e. outdoors), light sensor, better battery capacity, ...
Try to find out what Bluetooth version the phone has.
grenness said:
I 've had the Urbane for three weeks now, and I'm pretty pleased* with the watch except for a major problem:
I keep seeing that "cloud with a line through it" icon on top of the watch face way to often.
I'm actually looking at it right now - I'm at work, my Urbane is on my left wrist, and my phone is on the desk 20 centimeters away.
Since I haven't heard many others complaining about this, I'm suspecting the problem to be on the phone side - this is a "China phone", an Elephone P3000S (64bit, 3GB RAM) that I bought quickly as a cheap, but (on paper) good spec'd replacement for my broken Sony Z1 Compact.
But nevertheless, I thought I'd asked here if anyone else are experiencing the same?
I've factory reset the watch, I often reboot it, I reboot the phone even more often, and most of the time connection is re-established but lasts only for maybe 15 minutes up to several hours. I have disabled wifi on the watch to see if that improves things - initially I thought maybe it did (as long as I kept the phone nearby, of course), but after a while it seems it's not the case.
Anyone have any other tips? ...Before I replace the phone?
Thanks,
Christopher
*: of course I would prefer a brighter screen (when needed, i.e. outdoors), light sensor, better battery capacity, ...
Click to expand...
Click to collapse
ranf said:
Try to find out what Bluetooth version the phone has.
Click to expand...
Click to collapse
Guys,
Having the same problem as well..... I'm using a Nexus 6 with Bluetooth 4.1 which is also not so far away from my watch all the time..... Really don't know what's going on....
I don't have an Urbane watch (yet) but ran into this issue myself....I downgraded Android Wear on my phone back to 1..0.5 to fix my problem. To get the apk I am using now, see the link below. Before that, my watch would constantly disconnect from the phone for no reason. Best of luck to you all! The Urbane is the BEST looking smart watch out there IMO!
http://www.apkmirror.com/apk/google...roid-wear-1-0-5-1724356-android-apk-download/
Pietje_1985 said:
Guys,
Having the same problem as well..... I'm using a Nexus 6 with Bluetooth 4.1 which is also not so far away from my watch all the time..... Really don't know what's going on....
Click to expand...
Click to collapse
Same here. N6 running CM12.1. Bluetooth works perfectly with car, around home, other devices. I've tried every setting I can think of. Glad to hear I'm not the only one.
Have you tried enabling/disabling the wireless syncing option? I had similar initial issues, had to factory reset and I disabled Wireless Syncing (and deleted the cloud data).
I then setup the phone again and didn't enable wireless sync for a few hours so I knew the phone was setup and working only using Bluetooth.
I knew something was wrong as once the wireless Sync was disabled and the cloud info deleted, my watch said it had lost connection to the phone and I had to factory reset it (even through Bluetooth was enabled still).
I am having significantly more instances of Bluetooth disconnections on this watch that I did with the Moto 360. This especially occurs in my car while driving. I'd bet that the watch disconnects every 10 minutes or so in the car.
Same here ... I have an LG G3 running Lollipop with an LG Watch Urbane running v5.1.1 This is to replce my LG Watch R but these connectivity issues every 10 seconds is highly frustrating ... Looking forward to a permanent fix on this thread ...
I'm starting to see the same thing, no issue while both are on WiFi, but without WiFi my watch is constantly disconnecting. Normally rebooting the watch seems to fix the issue, but really hope this gets fixed soon.
If I get away from my phone watch disconnects, thats normal. But when I get close to phone again, it doesn't connect automatically, or connects too late. Is that normal? This is so annoying.
well im all good not had that at all i get about 25 foot then loose bt soon as im back in 25 foot im good
i have a edge
I have an SGS6 Edge and it is slow connecting. I've found it will connect instantly if I turn BT off and back on.
Has anyone tried using phones wifi terhering instead of bt connection? Maybe that extends the connection distance?
Seems like my problems are solved for the most part. Doesn't disconnect that often anymore. Could be because of recent update to Android 5.1.1 on my Nexus 6 and I factory resetted my urbane! Lookin' good now!!
How about you guys?
I have a Nexus 6P, and the disconnecting with my Urbane is beyond annoying. I'm starting to think that, despite the looks of the Urbane, the watch itself is a pile of poo.
Same issue here. Phone and watch constantly disconnect. If I walk 10 feet from my phone, it disconnects and doesn't reconnect when I come back within range of the bluetooth.
Pleased to report, though, that I went into Settings>Apps>Android Wear and cleared the cache and the phone has been reconnection pretty well. I have the LG V10 and the G3 before that and have found that you have the clear the cache on bluetooth connections every once in a while, and then things start to work smooth again.
Hope this helps someone out there.
I have been having the same problem since I got my new Nexus 6P. On my old phone, an Asus Zenfone 2, I would hardly ever lose connection. I might drop connection once a day. With my new phone, its about once an hour if I'm lucky. I just did a factory reset of both the phone and watch this evening, and so far it seems to have helped but I'm not going to call it fixed yet until I make a whole day without losing connection.
For what its worth, there are tons of people who are saying the BT on the N6P is boned, as well as a ton of people saying the same thing about the Urbane.
I have a Samsung Galaxy S6 and have both Bluetooth and Wifi connected to my LG Urbane however:-
If I go away from phone - within my own house AND well within Wifi range - it LOSES connections to BOTH Bluetooth and Wifi. (Bluetooth I can understand but how come it is losing connection to Wifi)?
Anyone got any answers please?
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
Searched and searched so posting here and will try in general thread in case it's not tied to the watch itself.
Background: IOS user for phone, have to - developer, had Apple Watch (hated it). Got myself a Huawei Watch 2 on a deal and loved everything about it except the useless bezel and tiny screen size. Seeing as I had a great experience, I started a hunt for an LGWS. Hunt because not a single store sold one and I'm in Chicago with LOTS of stores. So online we go. There too - few resellers. Finally found one. New. Manufacture date of May 2017.
The Watch 2 worked flawlessly as functions go. Sycn'd, stayed connected, battery life of full use (all functions on - obviously no LTE), brightness at 8, raise to view on, always on display on... end of the day going to bed around 10:30 still had 50% of battery left at worst! The only issue other than cosmetic that it had was WIFI would not connect so "automatically" so to speak. So when I sent a watchmaker face, I always had to go to settings, connectivity, wifi and wait until the SSID showed connected. Then all is fine. Transferred over and enjoyed.
So the LGWS shows up. I unpair the Watch 2, connect up the LGWS and love it. The display I expected, size is great for me and off to the races. Within an hour it went from 95% to 60%. I figured - setup blues. Ignore it. Let it fully bake and see what happens. Another hour later I'm at 30%... ok onto the charger we go. Did a full charge at 6pm, by 9pm it was flat.
LGWS background: GW 2.8 loaded, Watch 2 was still running 2.0. LGWS - cellular off, raise to view on, display brightness 4, wifi connected...
But here's what I noticed: on my phone, it consistently says disconnected - tap card to connect. I tried that about 20 times, no joy. Rebooted watch and phone... no joy. Reset watch, deleted app on phone and deleted Bluetooth pairing. Re-installed Wear app, re-paired watch, left all at stock settings except shut-off cellular and OK Google listening.
That last bit is the 6-9pm going totally flat.
So. Any ideas here? Things I see - 8 vs 2 OS... obviously IOS (I get it, but why did the Huawei work so well?) and there is nothing I can do about that. Don't know if I can downgrade to 2 to see if that makes a difference... if I do, will it self-update back to 8 when it gets a chance?
I really want to keep this watch - it's exactly what I wanted (short of strap change capability). I sure hope Google doesn't give up on Wear. As a Mac/IOS dev, I can easily say this is a superior platform for the user. Truly great stuff and I want it to improve and keep improving. The iWatch bigots are really missing out!
Thanks in advance for your tips.
Cheers!
Have you tried doing a reset?
When I got mine, it upgraded straight away so I thought "great", it's a clean watch, there can't be anything wrong with it.
Nope..
Apps didn't work.
Battery life was rubbish.
Did a reset when i got a new phone.
Apps worked without issue.
Battery takes me from 5am through to 9pm with 40% left at least, LTE is off but aod is on.
Yes - reset the watch to factory when I deleted the app, pairing etc - went totally to step 0 across the board, short of formatting over the phone itself. But I did one more reset after that last night and charged it all night. So far this morning (wrote most of my note locally last night, posted this morning) I'm holding up pretty well. Nothing running on the watch - bone stock with phone shut off and Ok Google off. 2.5 hours @ 91%. Fingers crossed that this was a fluke. But in my experience today is probably the fluke LOL.
wig said:
Searched and searched so posting here and will try in general thread in case it's not tied to the watch itself.
Background: IOS user for phone, have to - developer, had Apple Watch (hated it). Got myself a Huawei Watch 2 on a deal and loved everything about it except the useless bezel and tiny screen size. Seeing as I had a great experience, I started a hunt for an LGWS. Hunt because not a single store sold one and I'm in Chicago with LOTS of stores. So online we go. There too - few resellers. Finally found one. New. Manufacture date of May 2017.
The Watch 2 worked flawlessly as functions go. Sycn'd, stayed connected, battery life of full use (all functions on - obviously no LTE), brightness at 8, raise to view on, always on display on... end of the day going to bed around 10:30 still had 50% of battery left at worst! The only issue other than cosmetic that it had was WIFI would not connect so "automatically" so to speak. So when I sent a watchmaker face, I always had to go to settings, connectivity, wifi and wait until the SSID showed connected. Then all is fine. Transferred over and enjoyed.
So the LGWS shows up. I unpair the Watch 2, connect up the LGWS and love it. The display I expected, size is great for me and off to the races. Within an hour it went from 95% to 60%. I figured - setup blues. Ignore it. Let it fully bake and see what happens. Another hour later I'm at 30%... ok onto the charger we go. Did a full charge at 6pm, by 9pm it was flat.
LGWS background: GW 2.8 loaded, Watch 2 was still running 2.0. LGWS - cellular off, raise to view on, display brightness 4, wifi connected...
But here's what I noticed: on my phone, it consistently says disconnected - tap card to connect. I tried that about 20 times, no joy. Rebooted watch and phone... no joy. Reset watch, deleted app on phone and deleted Bluetooth pairing. Re-installed Wear app, re-paired watch, left all at stock settings except shut-off cellular and OK Google listening.
That last bit is the 6-9pm going totally flat.
So. Any ideas here? Things I see - 8 vs 2 OS... obviously IOS (I get it, but why did the Huawei work so well?) and there is nothing I can do about that. Don't know if I can downgrade to 2 to see if that makes a difference... if I do, will it self-update back to 8 when it gets a chance?
I really want to keep this watch - it's exactly what I wanted (short of strap change capability). I sure hope Google doesn't give up on Wear. As a Mac/IOS dev, I can easily say this is a superior platform for the user. Truly great stuff and I want it to improve and keep improving. The iWatch bigots are really missing out!
Thanks in advance for your tips.
Cheers!
Click to expand...
Click to collapse
Sorry to bump an old thread how is your usage the last few months? I'm confused between buying this and the huawei watch 2.
Thank you @wig
Sent from my Sony Xperia XZ1 using XDA Labs
No worries. The LGWS has been pretty decent. It seems to me that its bluetooth radio gets confused. For example, when I'm in my car, sometimes the watch disconnects or the car bluetooth disconnects. When I'm in my home office where the WIFI router is, the watch seems to disconnect as well. Beyond these weird edge cases, it stays connected and just works. The disconnecting isn't really bothering me as much as the fact that when it does, it tries to connect over WIFI and drains the battery pretty quickly. I've kind of learned to live with it and the hardware in this watch is better than the HW2. That being said, my experience with connectivity was much better with the HW2. Not sure how it's going now for those who have it. Android Wear has updated both the IOS app and the core OS and apps numerous times since I posted this. So for all I know, HW2 is doing the same thing these days. It does appear Google is trying.
As for the LGWS - go to ebay, find yourself a new one that's super cheap. I ended up getting mine for around $170 which made it a no brainer. One of these days I'll throw a SIM in it just to try it, but have bigger fish to fry at the moment.
Best of luck.
P.S. I just saw you have an android phone - so your mileage may vary and in fact will probably be MUCH better. I'm on iPhone which is 90% of the issue.
wig said:
No worries. The LGWS has been pretty decent. It seems to me that its bluetooth radio gets confused. For example, when I'm in my car, sometimes the watch disconnects or the car bluetooth disconnects. When I'm in my home office where the WIFI router is, the watch seems to disconnect as well. Beyond these weird edge cases, it stays connected and just works. The disconnecting isn't really bothering me as much as the fact that when it does, it tries to connect over WIFI and drains the battery pretty quickly. I've kind of learned to live with it and the hardware in this watch is better than the HW2. That being said, my experience with connectivity was much better with the HW2. Not sure how it's going now for those who have it. Android Wear has updated both the IOS app and the core OS and apps numerous times since I posted this. So for all I know, HW2 is doing the same thing these days. It does appear Google is trying.
As for the LGWS - go to ebay, find yourself a new one that's super cheap. I ended up getting mine for around $170 which made it a no brainer. One of these days I'll throw a SIM in it just to try it, but have bigger fish to fry at the moment.
Best of luck.
P.S. I just saw you have an android phone - so your mileage may vary and in fact will probably be MUCH better. I'm on iPhone which is 90% of the issue.
Click to expand...
Click to collapse
Thank you so much for your reply I think you have sold me the watch. Now I can continue my search to try and find one. Seems at $170 that's definitely a bargain let me know if your wanting to sell ?
Sent from my Sony Xperia XZ1 using XDA Labs