I might try another factory reset....might. I just found a Google Support page for this exact same issue and it seems like there are a few watch models being reported, so it's not just the Moto 360; as other forum members here indicated also. And it's not just Moto phones, quite a few folks said they have a Pixel.
And no, I am not ditching / tossing my watch. As long as I make an effort to keep my watch & phone within normal Bluetooth range and don't auto-update apps on my watch this bug has slowed way down, and not happening often anymore.
I did that....4 times. No effect and no difference. It's an AW 2.0 bugpersonally I would not be able to keep both in range - especially at work. in this case, I am fortunate not to have aw on my watch since it is a samsung, though there are times I wished I had aw.
maybe uninstall and reinstall the watch app on your phone will help if you have not given it a try yet.
What other models, specifically?I might try another factory reset....might. I just found a Google Support page for this exact same issue and it seems like there are a few watch models being reported, so it's not just the Moto 360; as other forum members here indicated also. And it's not just Moto phones, quite a few folks said they have a Pixel.
And no, I am not ditching / tossing my watch. As long as I make an effort to keep my watch & phone within normal Bluetooth range and don't auto-update apps on my watch this bug has slowed way down, and not happening often anymore.
Nope, actually a decent size house. I just keep my phone nearby all the time now. I used to do that most of the time anyway, so it's not a drastic change for me personally.I will reset mine and see if I can catch the message. But yea, there's no way I can put up with that and be worrying about staying in range of BT. I'd rather quit wearing then. Do you live in a Tiny House, Sajo?![]()
What other models, specifically?
That's what I thought because I have a Huawei Watch and I have the unpair issue as well, from time to time.there are a few different pages on the Google Product Support site and the Android Wear Support site; and not everyone mentions their watch / phone models. I do remember seeing quite a few Moto 360 Gen 2 mentioned and Huawei watches and Zen watches; along with Moto, Huawei and Pixel phones.
My phone is the Pixel XL. Watch is the Urbane, 1st Gen.there are a few different pages on the Google Product Support site and the Android Wear Support site; and not everyone mentions their watch / phone models. I do remember seeing quite a few Moto 360 Gen 2 mentioned and Huawei watches and Zen watches; along with Moto, Huawei and Pixel phones.
It sounds like the bug is specific to certain watches, since people with a Moto 360 and Pixel experience the issue but people with a Pixel and other watches do not. Same for Moto Z phones... it depends on the watch model. Must be something in these certain watches that triggers this bug.My phone is the Pixel XL. Watch is the Urbane, 1st Gen.
No issues here.
I do still shut my watch off in the evening on days I don't charge it. I also don't leave BT turned on on my phone. If I'm not connected to my watch or a vehicle, BT goes off.
Sent from my Pixel XL using Tapatalk
No issues with notifications here. Maybe try unpairing & reset the watch again to start over?Guys, anyone who here is experiencing issues with the notifications? Mine are not getting through (expect calls), I don't know if it's since the last Android Wear app update. I've since bought a new smartphone and had to reset my Huawei Watch but the issue is still happening...
Cheers