That certainly gives those of us who haven't upgraded yet, some hope.Let me add my own experience because today it seems to be completely fixed for me.
So I'm like forget it, all I can do is wait and see. And yesterday, just like that, my battery was completely back up to speed like pre-watch OS 10. So today I re-added my complications, I re-added widgets, and the battery was completely fine too.
- I restarted the Watch and the phone -> did not solve the issue
- I deleted the weather widget -> did not solve the issue
- I deleted all widgets -> did not solve the issue
- I unpaired/repaired my watch -> did not solve all the issue
- I deleted all watch faces, kept the Chronograph Pro watch face with zero complications -> did not solve the issue
- I killed the Watch app on the phone thinking it could be stuck and over communicating (although apps in background are frozen) -> did not solve the issue
- I turned off optimized charging -> did not solve the issue
So no clue. It got fixed by itself. Maybe something server side. Maybe the Watch really needs to settle after an update, but my battery woes have been happening from Monday. That's a long settle period. I'm on Series 7.
I think it's a possible solution. Since the beginning, I suspect something wrong on the iOS17 side.So reddit beta folks said that at some point during the beta this was an issue, and the only fix the dev folks found was to wipe all settings on the iphone and then setup up the settings as new on the iphone, and then repair the watch to the iphone and the issue would resolve. I do not think this is acceptable answer, however i just wanted to share with everyone, as i have not tried it my self, the reports were yes this solved the issues however, very angry beta testers. The bug seems to have made it into 17 / watch os 10
So reddit beta folks said that at some point during the beta this was an issue, and the only fix the dev folks found was to wipe all settings on the iphone and then setup up the settings as new on the iphone, and then repair the watch to the iphone and the issue would resolve. I do not think this is acceptable answer, however i just wanted to share with everyone, as i have not tried it my self, the reports were yes this solved the issues however, very angry beta testers. The bug seems to have made it into 17 / watch os 10
I have hope. Yesterday, I ran out of juice by 7pm.
Today, 40% remaining.
I was down to 62% in just 4 hours this morning, but it took close to 8 more hours to drop from 62 to 40%
Honestly what is the actual point of all the beta releases if they can't catch simple issues like this?
Don't forget the public are there to help out. There should be vast internal testing of every combination of devices they are supporting including real world usageDon't want to defend Apple here. Just try a possible explanation.
On betas you get only a very small number of your overall user base. Typically tech savvy people who participate in the beta program with an attitude like "well, sure the battery drains but it is a beta so I will not report it". So only a small portion of a small portion reports the problems (you can read the beta thread or tldr: some reported battery drain at the first betas and most of them said when we reached the RC: it is ok now).
When releasing to a public is a different game.
As stated before: I would propose catching system information during the beta phase to get this confirmation bias out of the game.
Similar roadmap to me and I thought I'd got on top of it after a full days use on Saturday, but today I'm down to 19% after having it on my wrist for 3 hours with barely any useLet me add my own experience because today it seems to be completely fixed for me.
So I'm like forget it, all I can do is wait and see. And yesterday, just like that, my battery was completely back up to speed like pre-watch OS 10. So today I re-added my complications, I re-added widgets, and the battery was completely fine too.
- I restarted the Watch and the phone -> did not solve the issue
- I deleted the weather widget -> did not solve the issue
- I deleted all widgets -> did not solve the issue
- I unpaired/repaired my watch -> did not solve all the issue
- I deleted all watch faces, kept the Chronograph Pro watch face with zero complications -> did not solve the issue
- I killed the Watch app on the phone thinking it could be stuck and over communicating (although apps in background are frozen) -> did not solve the issue
- I turned off optimized charging -> did not solve the issue
So no clue. It got fixed by itself. Maybe something server side. Maybe the Watch really needs to settle after an update, but my battery woes have been happening from Monday. That's a long settle period. I'm on Series 7.
Mine didn't relapse into the battery draining yet and is still going strong. I'll report back if it does. Try to kill also all running apps on the watch just to see. Maybe one of the third party ones you use needs an update or has issues with Watch OS 10. I still have no clue what fixed it on my side.Similar roadmap to me and I thought I'd got on top of it after a full days use on Saturday, but today I'm down to 19% after having it on my wrist for 3 hours with barely any use
Same here. My series 5 is draining like crazy since watchOS 10 was installed. Yesterday, I turned of AOD and switch to Wake on Wrist Raise. Seems to be doing better for me, still draining faster than watchOS 9 though.Series 5 and the last two days have been pretty horrible (cant remember when it upgraded to WatchOS10 but was towards the start of the week.
Today is 13 and a half hours from 100% to 0% with no real use other than the odd notification alerts
Well guys, I did it... I reset my iPhone settings (this automatically causes the watch to unpair and reconnect with the phone). It's been 4 hours and the battery went from 85% down to 66%. But I did a 45 min. workout and used the watch quite a bit. So I lost 19% in 4 hours. That's about 4,75% per hour but including a workout.Hmm... that seems like one of the last options for me, too. Maybe I'll give it a try today. Or I'll wait for watchOS 10.1 beta later today or tomorrow.
Surprisingly, yesterday I had pretty decent battery life - almost like with watchOS 9! Ended up with about 30% after ~15 hours of usage (including 45 min. workout!). But today I'm back to the old behavior. Put my watch on 3.5 hours ago and did nothing with it: now at 76%...WHAT IS WRONG???
Maybe it has something to do with the weather app (which still doesn't sync my list of cities I have on the iPhone but otherwise is working). Or - as I'm writing - I realized that I used a different watch face yesterday (the new Nike globe thing) and today I'm back to the new Solar one! Hmm...