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

Watch series 0 updates to 4.1 now after pairing with X

JohnR

JohnR

macrumors regular
Original poster
Sep 4, 2007
220
97
Elizabethtown, Kentucky
So I got the iPhone X, set up as new iPhone, unpaired my Watch from my 7+ (which never would "see" an update to WatchOS 4) and now the Watch has an update to 4.1

So did the 7+ have an issue or did the X fix something?

Anyone else have this happen?
 
There seems to be a problem upgrading from OS 4.0 to 4.1 with a 7+ iPhone. I was unable to do this with my gray 3rd series Edition AW and was advised to unpair and re-pair the watch. I unpaired but could not re-pair. After 3 hours at the Apple Store, they finally re-paired the watch but a number of the built-in apps failed to load. Now they sent it out for "repair," but I doubt it's the watch that has the problem.
 
I have series 0 and have an iPhone 7 plus. I had no problems updating to 4.0 and 4.1. Did them on the day the updates came out.
 
JohnR said:
So I got the iPhone X, set up as new iPhone, unpaired my Watch from my 7+ (which never would "see" an update to WatchOS 4) and now the Watch has an update to 4.1

So did the 7+ have an issue or did the X fix something?

Anyone else have this happen?
Click to expand...

I have a series 0 that I just updated to 4.1 and it is paired to my iPhone 6.

Sid Note: how does the series 0 get along with the iPhone X? Have you noticed any issues? I’m planning to updgrade from the 6 to the X soon, but hoping to get another six months or so out of my series 0 Watch.

Sean
 
sean000 said:
I have a series 0 that I just updated to 4.1 and it is paired to my iPhone 6.

Sid Note: how does the series 0 get along with the iPhone X? Have you noticed any issues? I’m planning to updgrade from the 6 to the X soon, but hoping to get another six months or so out of my series 0 Watch.

Sean
Click to expand...
My series 0 was rendered useless after pairing with my X and updating. I now get 4 hour battery life :-(
 
uhslax24 said:
My series 0 was rendered useless after pairing with my X and updating. I now get 4 hour battery life :-(
Click to expand...

Have you given that a few days? When you pair a watch it has to sync a lot of data and index it. Not unusual for battery life to suffer for a few days after.

Sean
 
uhslax24 said:
My series 0 was rendered useless after pairing with my X and updating. I now get 4 hour battery life :-(
Click to expand...

I haven't paid attention to it. I do know that previously battery life wasn't good to begin with. A lot of times I turned off bluetooth just to prevent the battery from losing all it's juice. I'll keep better track of it, but I don't know if it's me or what, but it seems that the battery lasts longer.
 
JohnR said:
I haven't paid attention to it. I do know that previously battery life wasn't good to begin with. A lot of times I turned off bluetooth just to prevent the battery from losing all it's juice. I'll keep better track of it, but I don't know if it's me or what, but it seems that the battery lasts longer.
Click to expand...

this happened to me on a first-time pairing of a S0 to my iphone6. 4h is just about the length of time the watch will run if some app is continuously running in the background. while it's a "microsoft" solution, apple's technical support had me unpair and repair the watch, but set up as a new watch, and then warned me to add back apps 1 at a time. the fact is that i don't really need any apps on the watch, so i just skipped that. after the repairing the watch has been fine - about 12h runtime in normal mode and around 24h runtime in theater mode.

i have a feeling the Kardia app might have screwed things up, as it just gave a spinner for a while and then told me that it was not approved by the FDA in the US.

anyway you probably have to do the same thing. major PITA and if you are using apps then an even bigger PITA.
 
joeblough said:
this happened to me on a first-time pairing of a S0 to my iphone6. 4h is just about the length of time the watch will run if some app is continuously running in the background. while it's a "microsoft" solution, apple's technical support had me unpair and repair the watch, but set up as a new watch, and then warned me to add back apps 1 at a time. the fact is that i don't really need any apps on the watch, so i just skipped that. after the repairing the watch has been fine - about 12h runtime in normal mode and around 24h runtime in theater mode.

i have a feeling the Kardia app might have screwed things up, as it just gave a spinner for a while and then told me that it was not approved by the FDA in the US.

anyway you probably have to do the same thing. major PITA and if you are using apps then an even bigger PITA.
Click to expand...

I had a similar problem last year with what I suspected was a runaway third party app. I did not un-pair/re-pair or set up the watch as new though. I simply removed all the third party apps I wasn't using, and hoped the problem was with one of those apps. Then I made sure I had the latest updates for the remaining apps. Sure enough, my battery life returned to normal. This is why I wish Apple gave us better usage information for Watch apps, just as they do for iOS apps. You can check battery usage on the iPhone to get some insights. If an app is using a lot of battery for background processes, it might also be actively talking back and forth a lot with the watch app.

Sean
 
sean000 said:
I had a similar problem last year with what I suspected was a runaway third party app. I did not un-pair/re-pair or set up the watch as new though. I simply removed all the third party apps I wasn't using, and hoped the problem was with one of those apps. Then I made sure I had the latest updates for the remaining apps. Sure enough, my battery life returned to normal. This is why I wish Apple gave us better usage information for Watch apps, just as they do for iOS apps. You can check battery usage on the iPhone to get some insights. If an app is using a lot of battery for background processes, it might also be actively talking back and forth a lot with the watch app.

Sean
Click to expand...

i did try to delete apps and then restart the watch, but no joy... since it was a used watch, and it seemed unlikely that a fresh install could go so wrong, i contacted support to try to find out if the battery was shot. they ran some kind of remote diag; you'd think that part of that diag would show CPU usage history but if it did, they did not want to share any info about that. at any rate they told me the battery was fine (but iPhone diags have said the same thing and it was clear my battery was shot.)

anyway i agree it would be nice to get better battery logging stats on the watch. i briefly tried to get Xcode going to see if i could do any analysis on the watch but the problem resolved itself before i got into it.
 
  • Like
Reactions: sean000
uhslax24 said:
My series 0 was rendered useless after pairing with my X and updating. I now get 4 hour battery life :-(
Click to expand...

Perhaps research more before asserting Your watch is "rendered useless" because of Updating. It could be due to a number of things. Such as indexing, syncing and requiring a re-pair, or pending how much you use your Apple Watch, it could be in need of a battery replacement. Furthermore, set up Apple Watch as a new device versus restoring from backup.
 
Relentless Power said:
Perhaps research more before asserting Your watch is "rendered useless" because of Updating. It could be due to a number of things. Such as indexing, syncing and requiring a re-pair, or pending how much you use your Apple Watch, it could be in need of a battery replacement. Furthermore, set up Apple Watch as a new device versus restoring from backup.
Click to expand...
I have done all of these things. Thanks, though.
 
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