took a risk and did the upgrade was on 5.1 and am on 5.1.1 now. and as others have said it was VERY fast.
This is actually the second time Apple has pushed an update that bricks Apple Watches. So yes, it will happen again.I still can’t believe that an OS update can actually brick an Apple Watch in an unrepearable manner. Causes me to lose some faith in this device. Why? It can happen at all and again and again...
Installing now
Still no ECG feature. I thought for sure the .1 update would have it like the music streaming feature in WatchOS4.1. Probably should have just kept my S3. I’m beginning to doubt it’s coming, especially in 2018 as stated.
I think 5.1 to 5.1.1 users thought it was fast... mine was about 20 minutes total.
Where are the color watch faces? Can't seem to find those
There should be something like DFU mode on this watch, bricking iPhones is almost not heard of AFAIK.
And then there are Macs, *some say here (In forums in the past) that their Macs are bricked, it's very-VERY rare to brick a Mac, especially the ones with a battery inside.
*Those Macs aren't bricked, just non bootable.
Sometimes rebooting the Watch and iPhone seems to resolve this.
You can't DFU a Watch because watches don't have data ports. A watch depends almost exclusively to the connection it has to an iPhone to complete and process the update. If you sever that connection, you will get a bricked device because there is no way to fix the software issue on the watch.
Still no ECG feature. I thought for sure the .1 update would have it like the music streaming feature in WatchOS4.1. Probably should have just kept my S3. I’m beginning to doubt it’s coming, especially in 2018 as stated.
Lol, bricking phones and watches is what they've been doing for a while now. But hey, fast updates, it's all the rage. Lol