Toggle sidebar Toggle sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

WatchOS 5.2: All The Little Things!

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Series 3. Want to update it. Watch app says 5 days remaining. WTF?? When I disconnect my Watch from my iPhone it’s not even possible that the watch is downloading the update itself with WiFi like on watchOS 4.
 
Broken Hope said:
Still impressed by how quickly a Series 4 watch installs updates from the Apple logo appearing to the charge animation showing again was all of 3 minutes. That would have easily been a 30+ minute install on my old Series 2.
Click to expand...
Did you install the update over Bluetooth 5 or from an older iPhone's Bluetooth 4.2? Curious about the speed difference. I know the S4 has Bluetooth 5 but reverts to 4.2 if updating from an old iPhone, though the speedier watch chip helps speed things up too.
 
Anyone else having trouble getting the 5.1 update? My girlfriend updated hers but I am not getting the update on the watch app on my phone. It keeps saying I’m up to date with 5.0.1. I have not been running betas, phone is updated to iOS 12.1, and I tried restarting. Or am I missing something?

UPDATE: Looks like the 5.1 watchOS got pulled by Apple this evening as some people are reporting bricked watches with the update.

https://www.theverge.com/circuitbreaker/2018/10/30/18045762/apple-watchos-5-1-update-brick-pulled
 
Last edited:
  • Like
Reactions: iL15hts
Painter2002 said:
Anyone else having trouble getting the 5.1 update? My girlfriend updated hers but I am not getting the update on the watch app on my phone. It keeps saying I’m up to date with 5.0.1. I have not been running betas, phone is updated to iOS 12.1, and I tried restarting. Or am I missing something?

UPDATE: Looks like the 5.1 watchOS got pulled by Apple this evening as some people are reporting bricked watches with the update.

https://www.theverge.com/circuitbreaker/2018/10/30/18045762/apple-watchos-5-1-update-brick-pulled
Click to expand...
My Series 4 became bricked with the 5.1 update.
 
Have 5.1 running on my S3. If 5.1 is re-released, do those of us on the pulled version get issued another update?

I feel bad for those with a bricked watch.
 
Akrapovic said:
Have 5.1 running on my S3. If 5.1 is re-released, do those of us on the pulled version get issued another update?

I feel bad for those with a bricked watch.
Click to expand...

Only if there’s an increase in build number. If they were to release it again and it had the exact same build number you would not be promoted to update.
 
Last edited:
  • Like
Reactions: Akrapovic
batting1000 said:
No, nothing yet.
Click to expand...
I'm really surprised that it hasn't been re-released yet. Must be a fun bug to track down and fix. The WatchOS 5 betas were the first ones that I hadn't been involved with, so I have no idea what I'm missing in 5.1. In due time, I'm sure.
 
I did manage to update to 5.1 when it came out (series 4) and since then I've been getting charging problems.

Put the watch on the charger, it shows the symbol as charging and the screen goes off as normal. A few minutes later the passcode comes up and it stops charging. Take it off the charger and put it back on and the same loop occurs.

Have tried a different chargers too. No idea if this is a bug or a coincidence ?
 
I've been having weird charging on my S4 since I got it - beta or not. I am on 5.1 release now (I came from 5.1 B4)

Yesterday, it was 32% so i charged it. 10 mins later it was 27% and took about 30 mins to get back to 32%. Then it took only 45 mins to get to 90%.
 
csurfr said:
I'm really surprised that it hasn't been re-released yet. Must be a fun bug to track down and fix. The WatchOS 5 betas were the first ones that I hadn't been involved with, so I have no idea what I'm missing in 5.1. In due time, I'm sure.
Click to expand...
The thing is they don't have feedback like they do on an iDevice. Remember, the iPhone, via Bluetooth, does all the talking on what to do next during the update. If during a reboot a bug severs that connection, then there is nothing that can be done to restore that watch because the watch is stuck in some part of the update.

Engineers have to first "build" a watch with USB connection or some kind of feedback system to observe via code what goes down and what goes wrong in order to fix it.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back