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.

  • Ok_Bus5113@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I was good (ultra 2) when I went to 10.1 and 17.1 on watch and iPhone. Then Apple pushed 17.1.1 and I’m back to battery drain. For example got less than day with 10.1 and 17.0.x. Then got 4 days on 10.1 and 17.1.0. Now down to 1.5 days on 10.1 and 17.1.1. This is horrible.

  • ramosl1@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    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.

  • OhGodItsRyan@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    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.

    • ConsistentShip714@alien.topB
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      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

    • OhGodItsRyan@alien.topB
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      New development for me in this mess. Over the last two days, when fully charged, my watch will hang on 100% for 3-4 hours, then drop 2-3% per hour after that.

      Seems like how WatchOS 10.1.1 measures battery capacity remaining is just terribly optimized.

  • Looking_Out_To_Sea@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    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).

  • AudiA32015@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    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.

  • dangggboi@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    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

  • BaBaDoooooooook@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    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.

  • Jmco1@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    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.