9.33 live - despite the battery problems?

I am a little speechless right now. The 9.33 has gone live, although the battery problems have been reported for several weeks?

My 900 Euro watch (Epix2), which is sold with > 10 days battery life, doesn't manage 4 days with the current version.

What is the point of a beta programme if these error messages are not taken seriously?

With the beta version 9.2x, the watch's runtime was far over a week, with the jump to 9.3x I can see the battery drain as soon as the watch is in Bluetooth range of my Android phone. 25% per day is normal now. 

  • Did a 40 minute run today and lost 6% only during this run from my freshly charged 7s. So a 1h run would have been around 9%, which is close to the 10% I lost yesterday.

  • Garmin 7X. Looking at Device Sync Audit in GCM I see exactly 8 syncs every minute - 4 of them show uploading 1 file and another 4 - downloading 1 file which seems to be SEGMENTS.

    Every more or less senior software engineer would tell you that polling is never a good strategy. And yet, that is exactly what Garmin seems to be doing here.

    I should add that disabling segments isn't a good solution for me. That is one of the main features that I use. 

  • Again what I wrote in answering to you in the thread about the users, who don't have battery problems:  I still think more information is needed if you really want to find an answer. 

    While we now know it's a 7S, still:

    "Which Multi-GNSS do you use? Automatic as default? Probably the one they advertise as SatIQ? Try w/o Multiband and GPS only for reference and keep suggestion from ramon_73 in mind. Battery Graph will help you to see which action had which impact.

    Also as for the light: Did you check whether the setting you made is made for Activities also? Do you have Gesture enabled? Then it may depend on how you walk if it switches on or not. *LOL*

    AND most important: Do you synchronize live? Thread "Battery Dran with 9.33 Simplified" seem to hint that some Users see a HUGE impact with synchronizing permanentely even without Strava. And do you have Strava? Seems to be a problem for at least some."

    And as for silentvoyager here: there is at least one very precise idea where this could come from.

    Yes, that should all be GARMINs problem and not your but you are the one with the problem, and battery drain seems to me like a gamechanger problem. Lucky me is not one of the stricken, BUT I almost never synchronize. and - again - there seem to be some real issues if you read the problem reports of the users. And no - no commitment by GARMIN yet. No good.

    : 100% agree to your conclusion. That even might be one of the major contrbuting facts for this dreaded problem.

  • I originally had All and Multiband GPS for running enabled. After advice from Garmin I used Automatic. No change. I might try GPS only but I run in an inner city setting and GPS signal can be pretty bad here due to often narrow roads of up to 5 floor buildings. Currently doing a running programme with a sports physician and need ok running data for this.

    The light is off when I run unless I raise my wrist. The way I hold my arms when running I can see the light is off. It's also on lowest and shortest setting as I don't need more in the dark.

    No segments, no strava. It's all disabled and I've never used either. Don't even have a Strava account. I use Runalyze and Smashrun and the sync with those only happens after I finished and saved the run.

    Hmm.. how do I know whether I synchronize live? That's a setting I can't find. I do take my phone along and sync an external HR sensor to it while running (like to compare data, watch uses internal HR) so I suppose the watch might be connected to phone as well. The run only syncs after I finished running though. Thus if there's a way to disable this then brilliant. Alternatively, I wonder if there's communication if the app on the phone is actually closed down and not only inactive in the background.

    I'm on iOS thus I don't think I can see how many connections the watch and app make compared to android. I also cannot  disable bluetooth for only the watch on iOS. That's a bummer.

    Btw, Garmin support sent me a questionnaire related to battery drop and 9.33.  Seems like they do something.

  • Btw, Garmin support sent me a questionnaire related to battery drop and 9.33.  Seems like they do something.

    Thats good news at least.

    As for GPS only mode: that was just an idea to check wether it impacts your battery life. Obviousely it is not a proper solution since e.g. for your use case the other modes are designed and neccessary for proper performance.

    Hmm.. how do I know whether I synchronize live?

    Just disconnect your watch from BT during run. Than you will see the differnce clearly too. That also being not the solution but a way to narrow in to the problem.

    Suggestion: Load "Battery Graph" widget onto your watch, take a run exactly as before, note the result. Than try the same with GPS only. Than with GPS on Auto or Multiband again but with phone disconnected. The result will tell you what is most influental for your battery and thus help you to fill in the questionnaire to give as many known facts as possible. 

    Do I hear you saying: shouldn't they have tested those quite trivial use cases themselves in advance? Yepp. 100% true. But alas, no they didn't obviousely.

    Think I stated before: happy me don't have issues with battery life but than: I don't have smart phone connected. If I had to bet on it: as for what I read in other threads, this could be the main issue. We will see, I'll keep my fingers crossed for you.

  • Thanks a lot, something to try.

    If I disconnect the watch from BT then I also can't use my running app with HR sensor anymore. But: doing this during a walk tomorrow might be an option. Lets see what happens then. And if I see a bit drop in battery when BT is enable when walking then disabling would probably offer an answer for running as well.
    Or I find out it's a running/cycling only problem.

  • If I disconnect the watch from BT then I also can't use my running app with HR sensor anymore.

    You don't have to disconnect the watch from BT. There is an option to disconnect from the phone only (and only during an activity), which can be configured in Power Manager. Basically, you can create a new power profile where you can tweak various power related settings and then use that power profile in a specific sport without affecting other sports. 

  • Thx for explaining that, I wouldn't know for I'm not using sync or BT most of the times - that is: almost never..

    Also Don't consider all of the suggestions as a solution or even a workaround but only as a temporary means for diagnostic reasons so to get a clearer view at the problem. You bought the gadget with all features and are fully entiteled to use all features as you please of course.

  • What if I said I think my battery life is better with 9.33? Day 5 after a full charge with everything turned on and it says I have 14 days left. With 8.xx I was topping out at 12 days. Now, it could well be that the estimate is wrong and will adjust itself in a couple of days, so we'll see .. 

  • Then I'd agree as you may find in my ealier statements also in the thread for the users with no battery problems.

    But number ending ...399 obviousely has a problem esp. on tracking as have many others and after reading some of the threads it seems to correlate with the usage of the syncing feature but maybe not only.That can't be ignored.

    For myself I'm sure it is slightely better especially prediction improved too.