Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Releases watchOS 6.1.1 With Bug Fixes
- Thread starter MacRumors
- Start date
- Sort by reaction score
if you go to Health app on the iPhone, click on Active Energy -> Show All data -> click on the first entry. Do you see a substantial (more than a few mins) time lag between the current time and last synced time from the watch?
Maybe don't leave it on the charger waiting for 100%? I don't think that's a bug, I think watchOS is trying to not make it 100%.
I don’t think I worded it correctly. My watch will warm up significantly, as if it’s struggling to charge to 100%. It will charge normally to 90 then make an effort to reach 100. I’m expecting a visit to the Genius Bar for a battery replacement in the future, but not this soon if it continues to be an issue.
Like I said, I’m hoping it’s a bug as it happened before on a previous version.
This is the first watch update I’ve had issues installing and I’ve had watches since the series 0 and installed developer betas in the past.
Series 5 running 6.1 downloaded and prepared the update without reporting any issue but refused to install it. Even on the charger at 100% charged it showed the Waiting to Install button rather than Install Now, and when pressed went through the Verifying... process and then straight back to Waiting to Install again with no reported errors.
In the end I had to delete the update through the watch app on my phone and start again from scratch which then went straight through.
Series 5 running 6.1 downloaded and prepared the update without reporting any issue but refused to install it. Even on the charger at 100% charged it showed the Waiting to Install button rather than Install Now, and when pressed went through the Verifying... process and then straight back to Waiting to Install again with no reported errors.
In the end I had to delete the update through the watch app on my phone and start again from scratch which then went straight through.
I installed this directly from Software Update on the watch (Series 5, and no iPhone involved) this afternoon, and it went through in a matter of minutes.
I am also observing an odd issue - that's been there for me every time since S4 (but seems like not everyone is seeing it):
1. Unpair the watch
2. Go to health app - Devices and delete everything (all previous watches) - so now it's an empty list except the phone itself. The deletion step is not relevant as I tested with brand new phone without it as well
3. Pair new watch
4. Go to health app again and observe 2 watches being present. One of them has no data - but that's the watch that appears to be paired. The other one says "This watch is no longer paired" - but that is where all the data goes
I wonder if this has something to do with other problems related to healthd
[automerge]1576093540[/automerge]
Most interestingly if you go and delete supposedly "no longer paired" watch it actually deletes the watch that is paired.
1. Unpair the watch
2. Go to health app - Devices and delete everything (all previous watches) - so now it's an empty list except the phone itself. The deletion step is not relevant as I tested with brand new phone without it as well
3. Pair new watch
4. Go to health app again and observe 2 watches being present. One of them has no data - but that's the watch that appears to be paired. The other one says "This watch is no longer paired" - but that is where all the data goes
I wonder if this has something to do with other problems related to healthd
[automerge]1576093540[/automerge]
Most interestingly if you go and delete supposedly "no longer paired" watch it actually deletes the watch that is paired.
I am also observing an odd issue - that's been there for me every time since S4 (but seems like not everyone is seeing it):
1. Unpair the watch
2. Go to health app - Devices and delete everything (all previous watches) - so now it's an empty list except the phone itself. The deletion step is not relevant as I tested with brand new phone without it as well
3. Pair new watch
4. Go to health app again and observe 2 watches being present. One of them has no data - but that's the watch that appears to be paired. The other one says "This watch is no longer paired" - but that is where all the data goes
I wonder if this has something to do with other problems related to healthd
I sure hope this update quashes some bugs. (I feel like an early adopter even though I waited until Series 5 to jump on the Apple watch bandwagon!)
I came across this article through Google after receiving a notice to upgrade the watchOS on my Apple Series 5 GPS watch. (The on-screen software update notice wasn't very explanatory so I was hoping to learn what the update might do.) At this moment I am crossing my fingers that the update will provide for better reliability/performance.
Unfortunately, my first impression of the Apple watch hasn't been good. I'm actually on my second Series 5 since mid October. I returned the first one thinking there was a defect because even with the WiFi router, iPhone and watch in the same room, the use of Siri and sending/receiving calls was more "miss" than "hit". The problem initially presented as Siri reporting "Uh, oh. I've lost the network connection. Let me try that again" and "I'm sorry but I can't place a call right now. Please try again in a bit".
I tried to report what I thought was a bug-related problem via Apple Chat support and phone support but came away with only the usual troubleshooting steps (make sure the watch and phone are updated, re-pair the watch, reset the network settings on the phone, reset the watch, restore from a clean install vs. the iCloud backup, etc.).
Although I'm new to Mac Rumors, my use of Apple products goes back to the pre-Apple store days. My take on the problem is that the watch doesn't hand off cleanly between Bluetooth and WiFi. Even though WiFi is reported as connected in the watch Control Center, when you go into Settings>WiFi it has at some point during the day — usually more than once — moved the home network down to the list of other area networks (i.e. all the neighbor's).
I found a support doc on the Apple website that states "Only Apple Watch GPS + Cellular models can disconnect from Wi-Fi networks", which if true would mean that my GPS watch has an issue because it reports it is connected to my high-speed network — the same network that runs all the smart devices in my house without an issue — but in reality the watch seems to be disconnecting at will. (This seems to be associated with a period of inactivity and it takes a series of restarts to the watch, the phone, the WiFi and so forth to try to get Siri working again.)
I've done my best to isolate the problem, including making sure everything else in my household is connected via 5G so as not to interfer with the watch on the 2.4G band. My impression is that when the Bluetooth signal is obstructed by walls or just going out of range, rather than hand-off to WiFi the watch either no longer has actual WiFi access *or* it is programmed to remain connected to the phone via Bluetooth at all costs — even when the quality of the connection doesn't justify it). A related issue is the fact that both watches have had significant trouble executing on "Find my Phone". Typically in response to a "Find my phone" request I get the following message: "I can't tell if the phone is nearby.…" This is true even when the phone is sitting in the same room!
I assumed the first watch was defective for the reasons indicated, but having had the same experience on the second watch I can only speculate that the watch and/or iPhone combo (SE) are suffering a network timeout (standby/sleep related?) bug in which the watch cannot successfully activate the connection to the phone. (At one point, I even asked Apple phone support if I would have had better luck with the GPS model and they said that regardless, the user needs to be within Bluetooth range.)
I read another Apple support document indicating that even with the phone off, even the non-Cellular models should be able to dial out over WiFi. With the watch connected to the 2.4G band and the Phone powered up with WiFi enabled, there is maybe a 40 percent success rate with the use of Siri, placing calls, dialing via the keypad and similar. With the phone powered on and the Bluetooth on the watch turned Off (WiFi-only connection), I can sometimes get the watch to perform about 60 percent reliably for a brief period. Within an hour or so the watch will go back to reporting "Call failed" and that I need to "try again later".
Long story shorter, I just applied the update. I hope Apple made some BIG bug fixes otherwise the watch will have to go back.😠
Oh, and on a final note, my current watch has the battery drain issue. My watch simply died on my wrist with less than 12 hours of use and no warning the other day. If my experience is any indication, a lot of these Series 5 watch Christmas gifts will end up being returned. If Apple doesn't fix this soon, they will be making headlines in another month for all the wrong reasons.
I came across this article through Google after receiving a notice to upgrade the watchOS on my Apple Series 5 GPS watch. (The on-screen software update notice wasn't very explanatory so I was hoping to learn what the update might do.) At this moment I am crossing my fingers that the update will provide for better reliability/performance.
Unfortunately, my first impression of the Apple watch hasn't been good. I'm actually on my second Series 5 since mid October. I returned the first one thinking there was a defect because even with the WiFi router, iPhone and watch in the same room, the use of Siri and sending/receiving calls was more "miss" than "hit". The problem initially presented as Siri reporting "Uh, oh. I've lost the network connection. Let me try that again" and "I'm sorry but I can't place a call right now. Please try again in a bit".
I tried to report what I thought was a bug-related problem via Apple Chat support and phone support but came away with only the usual troubleshooting steps (make sure the watch and phone are updated, re-pair the watch, reset the network settings on the phone, reset the watch, restore from a clean install vs. the iCloud backup, etc.).
Although I'm new to Mac Rumors, my use of Apple products goes back to the pre-Apple store days. My take on the problem is that the watch doesn't hand off cleanly between Bluetooth and WiFi. Even though WiFi is reported as connected in the watch Control Center, when you go into Settings>WiFi it has at some point during the day — usually more than once — moved the home network down to the list of other area networks (i.e. all the neighbor's).
I found a support doc on the Apple website that states "Only Apple Watch GPS + Cellular models can disconnect from Wi-Fi networks", which if true would mean that my GPS watch has an issue because it reports it is connected to my high-speed network — the same network that runs all the smart devices in my house without an issue — but in reality the watch seems to be disconnecting at will. (This seems to be associated with a period of inactivity and it takes a series of restarts to the watch, the phone, the WiFi and so forth to try to get Siri working again.)
I've done my best to isolate the problem, including making sure everything else in my household is connected via 5G so as not to interfer with the watch on the 2.4G band. My impression is that when the Bluetooth signal is obstructed by walls or just going out of range, rather than hand-off to WiFi the watch either no longer has actual WiFi access *or* it is programmed to remain connected to the phone via Bluetooth at all costs — even when the quality of the connection doesn't justify it). A related issue is the fact that both watches have had significant trouble executing on "Find my Phone". Typically in response to a "Find my phone" request I get the following message: "I can't tell if the phone is nearby.…" This is true even when the phone is sitting in the same room!
I assumed the first watch was defective for the reasons indicated, but having had the same experience on the second watch I can only speculate that the watch and/or iPhone combo (SE) are suffering a network timeout (standby/sleep related?) bug in which the watch cannot successfully activate the connection to the phone. (At one point, I even asked Apple phone support if I would have had better luck with the GPS model and they said that regardless, the user needs to be within Bluetooth range.)
I read another Apple support document indicating that even with the phone off, even the non-Cellular models should be able to dial out over WiFi. With the watch connected to the 2.4G band and the Phone powered up with WiFi enabled, there is maybe a 40 percent success rate with the use of Siri, placing calls, dialing via the keypad and similar. With the phone powered on and the Bluetooth on the watch turned Off (WiFi-only connection), I can sometimes get the watch to perform about 60 percent reliably for a brief period. Within an hour or so the watch will go back to reporting "Call failed" and that I need to "try again later".
Long story shorter, I just applied the update. I hope Apple made some BIG bug fixes otherwise the watch will have to go back.😠
Oh, and on a final note, my current watch has the battery drain issue. My watch simply died on my wrist with less than 12 hours of use and no warning the other day. If my experience is any indication, a lot of these Series 5 watch Christmas gifts will end up being returned. If Apple doesn't fix this soon, they will be making headlines in another month for all the wrong reasons.
I've bought 2 apple watches.. S0 and S5. Never unpaired with a iPhone6. Health app has me with 32 watches, all but 2 "no longer paired".
Annoys the hell out of me (when I do look), but I'm guessing it's a hack for switching between watches (which I do take the S0 instead of the S5 when I know I'm doing something that could end up with scratches and/or damage). Could also be caused from software updates. Or phone upgrades. Or all 3.
Last edited:
I suspect the problem is the iPhone SE. It has an older version of Bluetooth that doesn’t work well with the watch. That’s what I’ve heard anyway. I have an SE and it’s the same thing. Siri on the watch is next to useless. Takes FOREVER and says “oh oh…” all the time etc. If you upgrade to a newer iPhone with Bluetooth 5 it apparently works much better. I’m probably going to upgrade to the new low cost iPhone rumoured to be coming out March 2020 (the so-called iPhone SE 2). So we’ll see.