Apple Watch battery drain problems will soon be resolved with a new watchOS update

Apple Watch battery drain problems will soon be resolved with a new watchOS update.
Are you in any way impacted?

Since the release of watchOS 10.1, if your Apple Watch 9 or an older model has been having trouble with its battery life, you should know that help is on the way. Apple is working on a software update to address this issue.

According to an internal Apple memo obtained by MacRumors and distributed to Apple Authorised Service Providers, a solution to battery drain is “coming soon”. Nevertheless, the document just provides that information, leaving us with no other information.

It’s unclear what exactly is causing the issue, how many people it’s affecting, or what the software patch will do to make things better, but at least something is being done about it now.

It’s easy to locate concerns regarding the issue of battery drain: check out Reddit or the official Apple Support Forum, for instance. Several models appear to be affected by the problem, including the watchOS 10.1-powered Apple Watch Ultra 2.

software defects


Naturally, watchOS 10.1 was intended to address issues rather than bring in new ones. Additionally, it made possible the new Double Tap functionality included on the Apple Watch 9 and Apple Watch Ultra 2 models from this year.

Although it’s rare for an update to release without any problems, bugs are quite common with upgrades like this one, so it’s still disappointing that the user experience has been so severely compromised for what appears to be a sizable portion of users.

It’s difficult to say for sure how many people are seeing this, but based on the posts to which we’ve provided links above, it appears that these are not unique incidents. We wrote our evaluation of the Apple Watch 9 using watchOS 10, thus it doesn’t mention the battery problem.

Apple is having issues with more than just watch updates. The issue that is causing some iPhones to inexplicably turn off overnight is still unfixed, and it may have been brought on by the release of iOS 17.0.3.

 

Leave a Comment