Hi, since the last update to 6.0.1 and android wear 1.4.0.2580363, calls and notifications are randomly not silenced in my Moto X Style / Pure . Sometimes it works , sometimes it doesn't. I already tried restoring to factory defaults the watch and installing android wear again. Any idea? Thanks !!
Alber12 said:
Hi, since the last update to 6.0.1 and android wear 1.4.0.2580363, calls and notifications are randomly not silenced in my Moto X Style / Pure . Sometimes it works , sometimes it doesn't. I already tried restoring to factory defaults the watch and installing android wear again. Any idea? Thanks !!
Click to expand...
Click to collapse
I'm still suffering this issue even after sending the watch to Motorola. It seems like a last version bug. Any workaround? Thanks in advance.
Alber12 said:
Hi, since the last update to 6.0.1 and android wear 1.4.0.2580363, calls and notifications are randomly not silenced in my Moto X Style / Pure . Sometimes it works , sometimes it doesn't. I already tried restoring to factory defaults the watch and installing android wear again. Any idea? Thanks !!
Click to expand...
Click to collapse
I have that problem quite often. Usually I try toggling that setting on and off. If that doesn't work I'll reboot my phone and maybe watch. Usually one of those things takes care of it. Very annoying though!
Related
I've updated to the new Connect app, and the app on the phone works fine, but none of the new features will sync to the watch. I've tried restarting the watch, resetting the watch, uninstalling and reinstalling both Android Wear and the update to the Connect app (on a Moto X, so I can't fully uninstall Connect).
Anybody seeing this? Maybe I need to do all that in a particular order?
I am having the exact same issue. Using a Moto X 2014. The app updated and works on thr phone but none of the new features will sync
In the same boat as well...
Same with me. Running lg g3. I've read the issue is the phone that your 360 is connected with. Some people paired their 360 with a different phone and then the new watch faces finally appeared. But once they would try to pair their 360 back to their current phone, the watch faces would still not show.
No problem here on my Nexus 5
you won't see anything different on the phone after the motorola connect update in terms of the Body app. However, if you go into the start menu on the watch itself, you should see moto body features such as calories, steps, heart activity, and heart rate. hope this is helpful.
Won't work on my S4 either, tried everything. Bummer!!!
Works fine with my s4. Try restarting phone?
ditto
Same issue on my moto x 2013. Can't do anything to get them to show up. Done everything short of a hard reset on the phone
same here, nexus 5 on lollipop
I had the same problem. I use it with my Nexus 5 running an AOSP Lollipop Build.
Solved it by uninstalling the Motorola Connect App and reinstalling. After that everything new appeared on the 360.
Hope this helps :good:
mc-paulo said:
I had the same problem. I use it with my Nexus 5 running an AOSP Lollipop Build.
Solved it by uninstalling the Motorola Connect App and reinstalling. After that everything new appeared on the 360.
Hope this helps :good:
Click to expand...
Click to collapse
Many thanks this worked for me. I was dreading having to do a factory reset.
Edbogue
My watch updated to lollipop last night but today I've noticed that it's not vibrating with any notifications, at all, is anyone else experiencing this issue?
Edit: I've also noticed it's not vibrating with wear mini launcher either
Have not had this problem, I just tested with mini launcher.
Have you tried rebooting, and if that doesn't work resetting?
Factory reset fixed this issue for me.
It's working now but it's very faint...
No vibrations at all
I've noticed that my Moto 360 has stopped vibrating, even when selecting a watch face or restarting. The factory reset did not solved the problem.
Do you have any suggestions?
My watch was on:
Android Wear version - 1.3.0.2166028
Play Services = 7.8.99
Android OS = 5.1.1
As you can see it was stuck on the old version of Google play services for some reason 7.8.99 for some reason. This is a software glitch that my watch had but my girls moto 360 was just fine.
My watch would glitch out and crash many times a day.
It is the newest update to the android wear app that does not like google play services 7.8.99. Nothing i did could force an update so i had to revert to an earlier version of android wear app and the watch worked just fine.
What finally fixed my watch was the update to 6.0.1 that happened for my watch last night. These are the steps to take to make it happen smoothly.
1: With the newest version of android wear on the phone do a factory reset to your watch.
2: Place the watch on the charger and go through watch setup.
3: Once done syncing take the watch off the charger and connect it to your home wifi. Then go into setting and check for an update.
If no update repeat steps 1-3
4: If the update starts downloading go into the android wear app and disconnect the watch. Turn off bluetooth as well just incase.
(This is because it is the app itself that causes the phone to crash. The watch will then hook up to wifi and finish the download...it will also be faster)
5: Put watch on charger wait a while and the download should be ready. Make sure it is over 80% and start update. I recommend keeping it on the charger.
After its done you should be all good to go. All versions should be up to date. Mine is running great!
Hope this helps everyone!
Doesn't work for me. Tried three times.
I have a different one here, all good but for the android wear app keep crashing while scrolling down in 'watch storage' after the 6.0.1 update.
Factory reset watch, cleaning app cache didn't help.
GuyInDogSuit said:
Doesn't work for me. Tried three times.
Click to expand...
Click to collapse
does your watch see the update now?
moeozman said:
I have a different one here, all good but for the android wear app keep crashing while scrolling down in 'watch storage' after the 6.0.1 update.
Factory reset watch, cleaning app cache didn't help.
Click to expand...
Click to collapse
forget and reset watch. leave the watch on the charger and let it sync everything. it can take a very long time. i recommend doing it while you sleep. just let it sit and it should be fine
No, still doesn't see it.
Sent from my Nexus 6 using Tapatalk
hello guys, since some days i am getting this "unfortunately , android wear has stopped working" notification again n gain on my watch i also formatted the watch but it dint help, and solution please???
Aghh. I get this almost every time my watch disconnects from phone when it's too far. The whole watch starts acting weird, notifications popping out of nowhere, everything vibrating and then it all stops. Doesn't happen if I disable bluetooth on my phone manually tho.
muzaffarkhan95 said:
hello guys, since some days i am getting this "unfortunately , android wear has stopped working" notification again n gain on my watch i also formatted the watch but it dint help, and solution please???
Click to expand...
Click to collapse
Don't know if this is relevant, but on my S7e running the Nougat Beta, I was getting the same constant Android Wear message. Turns out that with my phone resolution set highest was causing it. Went back to FHD and it fixed it.
I'm using note 10+ snapdragon version, recently did OTA update and receive Samsung UI 3.0. After a week of usage, problem randomly appear. Video auto rotate not working when I turn my phone. During a phone call, when i place the phone near my ear, screen doesn't turn off and I start hearing my own voice, it's very interrupting.
It has a temporary fix which is restart the phone. But after a while issue will reappear. I've tried clearing cache. I've tried factory data reset and problem still will appear randomly. My phone was totally fine when I use Samsung UI 2.5!
Anyone experience same issue or have a fix?
Did you reset
Sunny026 said:
Did you reset
Click to expand...
Click to collapse
I wiped the whole phone bro
Also got this issue on a note 10+.
Did you find a resolution to the issue?
Same here, N9750 (Snapdragon).
same problem, some solution
I have same problem. Any solution for this?
Please help me
Thanks
Happened for me before,i downgrade to android 10, factory reset than update to android 11.