Because the name was the problem

 

Great stuff! For a while I was afraid time was running out for this android variant due in no small part to qualcomm's lack of interest in any Snapdragon Wear 2100 SoC successors. Now we have Intel as a chip alternative and also this announcement. Google apparently thinks otherwise....

 

Not a huge surprise that they would get phased out, possibly would be good to get a third year out of them, but maybe that's naive in today's tech world.

When I was outlet shopping at the weekend they had the original connected for £745, so clearly they have a few left to shift. I would be annoyed to buy one now and not get updates

 

Wanted to see if anyone else has notice on boot that Android Wear is still coming up. I have a couple other Android watches and noticed that they boot and show the new Wear OS logo and animation.

 

Wonder why they didnt update the Tag like lets say my Nixon Mission. I am guessing we will see an update from Tag in coming days to match up with the name change. The boot animation would come from a firmware update/system update, if I had to guess.

 

I dont receive any notİfications after this update on my connected 45. Any ideas why?

 

Where have the watch faces disappered to in the new Wear OS???......

 

Today I applied the watch version of this upgrade bringing wear OS to v2.10. No noticeable differences at this time. Still no update posted for my iPhone version of the app however. Interesting.

 

Solved notification problem by resetting to factory settings and repaİring with wear os from scratch... had to download all imstalled applications manually again...

 

I got the update in the app store when i refreshed the update section. Works pretty sweet to me!

 

I see the update now as well. Apparently it won't update the phone app until the watch app update has been applied. The app does have more functionality and shows a tag specific picture. No watch face updates though. I also never used the feature...

 

Interestingly, after the upgrade I began having the disconnect issue! So I followed google's instructions:
1. first, try booting your phone
2. if that doesn't work, try booting your watch
3.if that doesn't work, unpair, reset your watch to factory, re-pair.

After booting the phone, things appeared to be more stable, but when I woke up this morning the watch was disconnected again. So, I booted the watch and so far after 3 hours its been stable. Fingers crossed that I won't have to try a factory reset...

 

I made the 3 points, but now, when I receive a call, the watch disconnect.
In older versions of SO the watch was ok

 

I just tested this and I'm not seeing the same disconnect behavior. I have:

CM41 watch
iOS v11.2.6
iPhone Wear OS app v3.0.318 ROW
Watch Wear OS v2.10.0.188487362
Watch Android OS v7.1.1

HTH!

 

My BT connection is dropped constantly after this update, plus even when connected I can't access advanced settings in Wear... My user experience is going downhill...

 

This is insane... My 45 keeps rebooting after update to the watch Wear OS. The interface is so sluggish it's almost useless... A factory reset is unacceptable diet me at this point.

 

I did a reset because my watch was disconnecting often. Now when I try to reinstall Strava, I authorize on the phone the access but on the watch I get an error saying “Error retrieving authorization code.” Anyone having a similar issue?