Related
My nexus 5 was recently updated and my moto 360 is barely usable. I would sometimes miss notifications before this update but recently it's been a lot worse. Sometimes the watch face disappears completely and it's just a blank screen. I'm also getting errors saying that fit needs android wear to update.
I've tried doing a factory reset as well with no luck
isamu982 said:
My nexus 5 was recently updated and my moto 360 is barely usable. I would sometimes miss notifications before this update but recently it's been a lot worse. Sometimes the watch face disappears completely and it's just a blank screen. I'm also getting errors saying that fit needs android wear to update.
I've tried doing a factory reset as well with no luck
Click to expand...
Click to collapse
uninstall the wear app then reinstall it
I've noticed that after the update some notifications doesn't wake up the watch or make it vibrate, when you use the "try notifications" from the Android wear app just 4 of them wake up the watch, i hope that with the next update al notifications are shown in the watch .
This may sound stupid but it worked for me. I was only getting some notifications too. Tried setting new watch faces and syncing from my phone but nothing fixed it. This is what fixed it for me. I changed the watch face from the watch itself, and then hit the little settings gear on the watch face, edited something, and then selected the face. All notifications worked after that.
Hi all
I've recently started using my Moto 360 again alaong with my HTC M8 running the Radium 1.4 ROM. I set the watch up and all was working perfectly. I then noticed the watch was not receiving any notifications, this was after I had been out for a while with the watch at home. The only way I could figure out re-enabling them was to factory reset the watch then set it up again. I don't want to have to do this every time I go out without the watch etc. I had similar problems with the watch not pairing via Bluetooth with my phone after it had already been paired. The only way I could get it to pair was again to factory reset. This issue seems to have gone away now and it's just the notifications that seem to be a problem.
Any advice would be appreciated.
Thanks
Looks like ROM issue!
Sent from my SM-N9005 using Tapatalk
nijom said:
Looks like ROM issue!
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Happens with ever ROM I've tried
stevoh84 said:
Hi all
I've recently started using my Moto 360 again alaong with my HTC M8 running the Radium 1.4 ROM. I set the watch up and all was working perfectly. I then noticed the watch was not receiving any notifications, this was after I had been out for a while with the watch at home. The only way I could figure out re-enabling them was to factory reset the watch then set it up again. I don't want to have to do this every time I go out without the watch etc. I had similar problems with the watch not pairing via Bluetooth with my phone after it had already been paired. The only way I could get it to pair was again to factory reset. This issue seems to have gone away now and it's just the notifications that seem to be a problem.
Any advice would be appreciated.
Thanks
Click to expand...
Click to collapse
Hello,
It is actually an issue with the recent Android Wear app update...just read all the comments from 360 owners. Mine will not connect either.
Cheers
Well at least it was nothing to do with my phone/watch/ROM. Must have been updated recently as it's been fine! Back on form
Cheers
jschill31 said:
Hello,
It is actually an issue with the recent Android Wear app update...just read all the comments from 360 owners. Mine will not connect either.
Cheers
Click to expand...
Click to collapse
stevoh84 said:
Well at least it was nothing to do with my phone/watch/ROM. Must have been updated recently as it's been fine! Back on form
Cheers
Click to expand...
Click to collapse
After 4 Android Wear updates they finally fixed the connection issue. I sent them several bug reports and I swear they didn't even look at them.
Cherrs
Nexus 6
I'm still having problems where my Moto 360 won't show notifications (text, email, phone calls). I've tried every recommended solution. After a factory reset it works for maybe 30 minutes and then stops. One thing I've noticed (and I don't know if it's related or not) is that the Android Wear version on my Phone (Galaxy S5) is 1.3.0.2284253 and on my Moto 360 it's 1.3.0.2166028. Shouldn't they match?
Ramer said:
I'm still having problems where my Moto 360 won't show notifications (text, email, phone calls). I've tried every recommended solution. After a factory reset it works for maybe 30 minutes and then stops. One thing I've noticed (and I don't know if it's related or not) is that the Android Wear version on my Phone (Galaxy S5) is 1.3.0.2284253 and on my Moto 360 it's 1.3.0.2166028. Shouldn't they match?
Click to expand...
Click to collapse
For anyone who runs across this at some point, I solved the problem (at least for me). I unistalled Light Manager and now I'm getting all notifications.
Arrrgh mine has started doing this again! It had been fine for a few weeks. Seriously needs sorting out
I just got a new Moto 360 2 days back, and noticed this issue soon after it updated itself maybe to 5.1.1. I restart my phone everytime i face this issue which seems to fix it. Also android wear shows an error message mentioning notification sync is not working.
aayushjoshi said:
I just got a new Moto 360 2 days back, and noticed this issue soon after it updated itself maybe to 5.1.1. I restart my phone everytime i face this issue which seems to fix it. Also android wear shows an error message mentioning notification sync is not working.
Click to expand...
Click to collapse
Still isn't resolved for me sadly and restarting the phone doesn't work. I'm just flashing a new ROM to see if that helps. My watch has randomly been saying Google Play Services isn't installed on the phone when it is. Strange happenings here!
I have exactly the same problem! Saying Google play services are not installed, no whatsapp or text notifications until I get an email then they mysteriously appear. also if I toggle notification to priority and back they appear. doing my head in
You need to restart the phone and the watch, not just the phone.
Also can try removing your phone from your watch's bluetooth pair list then also "forget" the watch in your phone's bluetooth menu, then re-pair the two. Should work no problem after that.
I find this only happens if i stray away too far from either device or one of them gets restarted for some reason.. but yeah, restarting both the phone and the watch, removing the phone and watch from both bluetooth lists, and then re pairing, has fixed it every time for me. No having to factory reset the watch or reflash rom or anything drastic like that.
Now if you're phone is always in your pocket/purse which is on you all the time and the watch is on your wrist too and it just drops connection randomly... then i'd say something is messed up with your watch or phone.
Is anyone else having a delay in phone notification? By the time my watch starts vibrating to notify me of a phonecall I have already missed the call on my phone. That's irritating. One of the reasons I got the watch was to let me know when my phone starts ringing. My emails and texts seem to be notifying me just fine. It's just the phone notification.
Ideas?
I have only a small delay like 0,5s. So I think this is not normal. Are you connected by bluetooth or maybe by wifi?
I'm connected by BT. Like i mentioned all of my other notifications are working just fine. It's just the phone notification. I wiped my watch and reloaded everything so i am waiting to see if that fixed anything.
zumstin said:
I'm connected by BT. Like i mentioned all of my other notifications are working just fine. It's just the phone notification. I wiped my watch and reloaded everything so i am waiting to see if that fixed anything.
Click to expand...
Click to collapse
Update: It did not work. Sigh...
zumstin said:
Is anyone else having a delay in phone notification? By the time my watch starts vibrating to notify me of a phonecall I have already missed the call on my phone. That's irritating. One of the reasons I got the watch was to let me know when my phone starts ringing. My emails and texts seem to be notifying me just fine. It's just the phone notification.
Ideas?
Click to expand...
Click to collapse
I have this at times, though not always. I also get it where after I answer the call it continues to vibrate on my watch. hangouts messages do take a few seconds to push to the watch though. that said, this behavior has been consistent with my zenwatch, smartwatch 3 and my hwatch so I think it's just inherent in the platform
kellybrf said:
I have this at times, though not always. I also get it where after I answer the call it continues to vibrate on my watch. hangouts messages do take a few seconds to push to the watch though. that said, this behavior has been consistent with my zenwatch, smartwatch 3 and my hwatch so I think it's just inherent in the platform
Click to expand...
Click to collapse
Same here.
I just tested a call and it was about .5 to 1.0 seconds which is considered very good by my taste. But I did notice SMS and Hangouts does take a few seconds.
Maybe they set the priority like that on purpose.
Same problem for me...
zumstin said:
Is anyone else having a delay in phone notification? By the time my watch starts vibrating to notify me of a phonecall I have already missed the call on my phone. That's irritating. One of the reasons I got the watch was to let me know when my phone starts ringing. My emails and texts seem to be notifying me just fine. It's just the phone notification.
Ideas?
Click to expand...
Click to collapse
I am experiencing the same exact problem with my Nexus 6P - no amount of resetting seems to have fixed the problem. This has been extremely frustrating.
Anyone else figure this out without having to warranty the watch. Mine is a good 3 seconds behind with a Nexus 6. The call can go to voicemail before the watch vibrates.
uniqueflips said:
Anyone else figure this out without having to warranty the watch. Mine is a good 3 seconds behind with a Nexus 6. The call can go to voicemail before the watch vibrates.
Click to expand...
Click to collapse
I'm hoping with the new update to Wear announced today that it will fix the delay. Hoping....
uniqueflips said:
Anyone else figure this out without having to warranty the watch. Mine is a good 3 seconds behind with a Nexus 6. The call can go to voicemail before the watch vibrates.
Click to expand...
Click to collapse
it has nothing to do with the watch, I've got a sw3 as well that behaves the same with my 6p. previously I had a zenwatch, and it had the same delay with my n6 and later the 6p
I believe it's the android wear app itself. If you can find the AW 1.3 apk from apkmirror or the like, you should see a difference. Hopefully the new OS update will help alleviate the issue.
Same here with HW Watch Active. Phone get instant Message since Doze Settings on Marshmallow were edited, Watch still delayed...
I am having problems as well. Sometimes I would get notifications on my watch, other times the notifications would be delayed. I just tried and I am not even getting calls to my watch. I had to perform a factory restart twice now in order to get it to work. Why is that? I have a Huawei watch sync with a Huawei Mate 9. I would figure they both should work seamlessly.
any advice would be appreciated
rimz808 said:
I am having problems as well. Sometimes I would get notifications on my watch, other times the notifications would be delayed. I just tried and I am not even getting calls to my watch. I had to perform a factory restart twice now in order to get it to work. Why is that? I have a Huawei watch sync with a Huawei Mate 9. I would figure they both should work seamlessly.
any advice would be appreciated
Click to expand...
Click to collapse
Did you find a solution? I am experiencing the same issue, the incoming calls are not working and I also cant therefore receive calls directly on the watch. I am using an updated Huawei Watch with the HTC One M8, which is also updated to Android 6.0, with the latest version of Android Wear.
Cheers
Badelhas said:
Did you find a solution? I am experiencing the same issue, the incoming calls are not working and I also cant therefore receive calls directly on the watch. I am using an updated Huawei Watch with the HTC One M8, which is also updated to Android 6.0, with the latest version of Android Wear.
Cheers
Click to expand...
Click to collapse
The incoming calls seem to have fixed itself. However, what really solved the issue was that I had to make sure, on my Huawei phone, Android wear was set to close after the screen lock. I made sure that Android wear was always running in the background. Not sure if there is a similar setting on the HTC One M8, but making sure android wear was not in any power saving mode solved the problem for me.
Hope it help,
rimz808 said:
The incoming calls seem to have fixed itself. However, what really solved the issue was that I had to make sure, on my Huawei phone, Android wear was set to close after the screen lock. I made sure that Android wear was always running in the background. Not sure if there is a similar setting on the HTC One M8, but making sure android wear was not in any power saving mode solved the problem for me.
Hope it help,
Click to expand...
Click to collapse
I fixed the issue with a "wipe partition cache" procedure. Thanks
I've had a Smartwatch 3 for a couple years without any issues. The watch connects without me doing anything, and notifications come through at the same time as my phone.
I bought a Huawei Watch Tuesday, went through the two system updates, and then did not receive notifications. A factory reset fixed that for about 36 hours.
Since then, I've done about 10 factory resets, tweaking settings in the Wear app and on the watch each time. Sometimes, I could get the watch to receive notifications temporarily. That would stop after an hour or so. Pushing one of the sample notifications from the Wear app doesn't work, but most of the time I can change the watch face from the Wear app. Other weird things:
-Sometimes the Wear app will show nothing. Not even give me options to add a device.
-When I click "Calling Setup" on the watch, sometimes it will ask me to give Message+ (the Verizon messaging app) permission. Whether I accept or not, it will eventually tell me the watch isn't connected to the phone (even though the Wear app says it is).
Today, I exchanged the watch, and am having the same issues (and the grey circle where the charging icon appears won't go away). I really, really want to be able to use this watch, so any help would be very much appreciated. Here's a quick rundown of what I've tried so far:
-Cleared Wear app data and cache.
-Removed Smartwatch 3 and Huawei watch from app thinking it might be confused with 2 in there. Re-added the Smartwatch 3 independently after this, and it still worked.
-Checked permissions on phone and watch.
-Removed Google Play Music playlist, thinking syncing may have been bogging it down.
-Switched default text apps.
-Uninstalled Wear app.
-Tried different Watchmaker faces.
Watch and phone (LG G3 on Verizon) are running Marshmallow.
Can you think of any experiments before I give up?
Uninstall Wear and re-install. Then resync and pair the watch again.
Thats all I can think of.
As an update, I cleared cache in each app on my phone individually and uninstalled non-essential Wear apps. This has notifications flowing normally.
However, if I disconnect the phone/watch for any reason, it takes hours for notifications to start coming in again.
Any thoughts on how to trigger notifications after reconnecting? Toggling the connection and options in the Wear app doesn't help. I can't figure out what eventually allows notifications again.
Hi guys, I have problem with incoming notifications on my watch after the watch is not paired with my smartphone a few hours.
The watch don't receive incoming notifications, but the bluetooth connection is there.
After a factory reset my watch works good again.
I need help, please..
flyalligator said:
Hi guys, I have problem with incoming notifications on my watch after the watch is not paired with my smartphone a few hours.
The watch don't receive incoming notifications, but the bluetooth connection is there.
After a factory reset my watch works good again.
I need help, please..
Click to expand...
Click to collapse
I think we're experiencing the same thing. I bet if you gave it a few hours, you would start to receive notifications. I wonder if this is an issue with the watch. Does anyone not experience this?
acadmus86 said:
I think we're experiencing the same thing. I bet if you gave it a few hours, you would start to receive notifications. I wonder if this is an issue with the watch. Does anyone not experience this?
Click to expand...
Click to collapse
At night, when my smartphone is paired with watch, it's about 8 hours, I get a different notifications to my smartphone but to Huawei watch they don't come.
At morning I do a factory reset.
sleep mode for BT or wifi or...... ? battery optimized app on Marshmallow ?
Since the latest Android Wear update a few days ago, my watch appears connected to my Honor 7, but I don't receive notifications anymore.
I can change the watchface from the phone, i can find the phone from the watch, so there is communication.
If I disconnect the watch, delete android wear from the phone, restart and do a new connect with the watch, it works again, i receive all notifications again. Until, I shut down the watch or restart the phone, then nothing again.
Resyncing apps via Android Wear on the phone does not help. Any clues?
Honor 7 with MM6.01 (b371) and M1D63M on watch.
fritsprive said:
Since the latest Android Wear update a few days ago, my watch appears connected to my Honor 7, but I don't receive notifications anymore.
I can change the watchface from the phone, i can find the phone from the watch, so there is communication.
If I disconnect the watch, delete android wear from the phone, restart and do a new connect with the watch, it works again, i receive all notifications again. Until, I shut down the watch or restart the phone, then nothing again.
Resyncing apps via Android Wear on the phone does not help. Any clues?
Honor 7 with MM6.01 (b371) and M1D63M on watch.
Click to expand...
Click to collapse
Interestingly I am experiencing the exact same at the moment.. Oddly enough it worked just fine yesterday, but not two days ago or today...
Thanks for replying, now at least I know this is not just me.
I am also having the same problem. I need to disconnect and reconnect several times in a day to get notifications. I thought the latest update was just security fix but i think it has messed up the core functionality as well.
for me, even the watch face cannot be changed from phone.
Funny I ignored this thread until it happened to me just today
Sent from my E6653 using Tapatalk
i'm going crazy....same issue happened to me!!! i'm looking forward to find a solution ASAP!!!
Same is happening to me. I've tried all of the above as well but no success keeping the notifications from disappearing.
Interestingly though, I also have an app installed called Feel the Wear which lets you set different vibrations on the watch for different types of notifications. I only use one custom vibration for hangouts. Whenever I get a hangouts message, I still get the custom vibration on the watch but the message itself doesn't hit the watch.
Sent from my Nexus 6 using XDA Free mobile app
Well, apparently this is becoming an issue. I don't think Sony is to blame, because it started just after the latest Android Wear update, my watch was working perfectly before that. Anywhere I can download a previous version? Then I will install that version and don't allow it to update for now until Google has fixed the issue........
Just this morning I received an update OTA on my watch to version M1D63X, but unfortunately no changes to the notification problem........
Just connected again with my z1 compact, works well, everything fine with the notifications. Therefore it must be something to do with the honor 7 or with mm6, because my z1 compact runs on lp5.1
Same on my watch + Xperia Z3 Compact. There must be some problems with Android Wear app, many of my friends have the same problem. Notifications work after reconnecting but not for a very long time.
Also incoming mails are notified a couple of times in a row for some time, f.e. I get banggood offers mail which is notified on the phone and on the watch, then in the next 5 minutes there goes another notification about the same mail, and again, and again... until I dismiss that notification. Drives me crazy so I just immediately swipe e-mail notification when it arrives (I don't want to block the app).
Hoping for a quick fix...
Every time this problem occurs I simply restart the watch and phone at the same time. Fixed the problem every time. Restarting the watch alone does not help.
Also can confirm that the watch indeed is connected to the phone, no notifications go through to the watch. Had a song successfully identified by Shazam on the watch while the problem was present...
After yesterday upgrade my OnePlus X to android 6.0.1 - Sony SW3 stops receiving notifications. There is info at android wear app, that synchronization was shut down and i have to restart phone to resolve that problem. After restart it works for some time and then the same problem. I think that some program is shutting down by android but i dont know where i can find it, and what it is. Anybody? App that sends notifications to watch?
Same with me. I only get the notification by the app Feel the Wear and having custom vibrations on Gmail, Whatsap and Facebook. But no notification on the watch itself. Also since the last 2 updates.
Since flashing a Nougat rom on my Nexus 6, I have been receiving all notifications on the watch. It's only been a few days but so far so good. Still not a fix for anyone stuck on MM but try flashing Nougat on your phone if you have the option.
Edit: I flashed a couple of different Nougat roms which requires two separate factory resets of the watch. not sure if that had anything to do with notifications coming through.