Before the last update my battery would easily last all day and night. I’d even have enough to keep it going until the afternoon. Since updating last night to watchOS 10.1.1, the battery on my Series 8 has been awful. I’ve not used GPS or cellular and had my phone with me all day. Anyone else had this issue? I know I only charged it to 88% this morning but I can’t remember the last time I had to top it up in the evening before a workout.
It did for me.
I had new U2 m. Did the update and the battery just dropped. Upgraded to 10.2 and it improved battery slightly but the wrist temp didn’t work. So I had it from Amazon and within the 30 days and I returned it. Since then I had a replacement and it’s been 48 hours and I’ve used 51% with cellular on etc. and I’m using 10.1.1. I did delete some of apps such as tops and depth and any that I would never use. Also some didn’t seem to work properly so that could have been an issue
After updating to 10.1 my watch drained extremely fast. After 2 days of that it stopped taking a charge. Apple charged me $99 plus tax for my battery issues.
I’ve been using macs since ‘88 and iPhones and watches since they came out and never had a problem this serious with them, and to say I’m disappointed with apples reaction is such an understatement that it’s just wrong. I’m angry. I loved having an Apple Watch but as the saying goes, “fool me once, shame on you. Fool me twice, shame on me.” I’m seriously considering going back to nice mechanical watches.
JFC, I left with 96% @ 8.45am. By 12.20pm, I only had less 10%! No workouts done.
For me it mega fixed it
My Apple Watch 6 battery had started draining a little faster than normal. I use it a lot all day long. I turned off Always On and it started lasting all day and into night again. Updated to 10.1.1 2 days ago in hopes I could use Always On again. Now my battery shows 100% at 8 am and dead at 11 am, 3 hours later! Can’t use it at all.
10.1.1 gave me the bug!
I don’t know my s9 is running like beast. Took it off the charger on Friday morning and by this morning I still had 47% and that’s with an hour workout too.
Usually after an update, the system uses a lot of battery to index information. Give it a couple days to see if it gets better
Honestly, this is why I haven’t updated my watch and don’t plan to until I don’t see these posts anymore
I had no problem with 10.1, if fact it gave my AW6 44mm a boost in battery performance to 16 hours with 20% left. So I happily installed 10.1.1 and now the watch is dead within 6 hours 2 days in a row (yes I’ve rebooted it).
I updated to 10.1.1 and the battery drain was worse until I power cycled the watch and battery life is fine now. I had to do the same thing when I updated to 10.1.
What is » power cycled «
Despite what Apple said, there’s no way WatchOS 10.1.1 has fixed battery drain. At least not for everyone.
My AWU2 was an absolute battery champ prior to updating to 10.1.1, but now? No way. Battery goes down 3-5% per hour without me even using it.
My biggest concern with this is the potential longer term degradation this can cause. Some people have stated WatchOS 10.2 beta has resolved this all together, but I’m super hesitant to put a beta on my watch.
I’m using the beta and it’s worse than ever
before i updated it at all mine was dying really fast but i updated my phone and then my watch and its back to normal. im not sure if anyone else had the draining when the update came out before updating but im glad mines normal again. it would be dead by 6pm
Same here, great battery before their battery drain “fix”. Got worse after.
My ULTRA OG is still running like a monster, last charged to 100% Friday at 10:34am, it’s now Saturday 1:34PM, has 13% juice left, 27 hours is pretty solid with what i been using it for, running, workouts, timers, apple music, etc.
Your watch is possibly caught in a sync loop with something in your iCloud account. It’s continuously trying to sync something. This happened to me about a year ago and it ended up being reminders however it could be anything that syncs with iCloud. The issue was on the server side and only Apple tech support can fix. It took about a week working with a senior advisor but one they determined what was caught in the sync loop the fix was quick.
This could be your issue.
How could you figure it out? Did you end up disabling some services?