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. 

  • I feel the same way. Can't understand there is no word from Garmin about any correction to the problem. I have waited long for this update, but due to possible problems I have turned auto update off and won't update before there is solution available. Some people have sorted battery drain with factory reset, but there is no guarantee that it helps and you lost quite much data by doing it. If factory reset is needed after update Garmin should provide us proper backup functionality which could restore all the data to the state before reset.

  • Yes, I am also irritated here that there is practically no reaction, no answer, no follow-up questions to the error messages during the beta phase on the part of Garmin. That's not how I imagine a beta test.

    The only thing that could be seen was that one of the many messages about the battery problems in the forum changed to the status "ticket" -- but nothing more.

    If you could at least get feedback from Garmin that they are investigating the problem and working on a solution, I would be satisfied. But I personally find this silence very inappropriate and disrespectful towards the voluntary beta testers.

  • Have you guys seen if this only affects Android users?

    I'm on iOS and have no issues what so ever, but I also quit GCM when not in use...

    If battery percentage is correct my Epix will last about 20 days (now on 50% after 10 days) with my current use (semi sick so not much activities, gestures, power save at night, no spo2)

  • I only have an Android device, so I cannot make a comparison to iOS here. The more than doubled power consumption only came with the update to beta version 9.31. I did not make any other changes to the settings, GCM or my usage behavior.

    The increased power consumption seems to be directly related to the connection to GCM. I observe that power consumption is significantly lower at night when I am out of the Bluetooth range of the smartphone – I have no power save activated at night, only DND and night mode watchface. 

    This has also been reported by others, that possibly the watch here permanently triggers the synchronisaton and this leads to the increased power consumption. 

    Maybe this is also a problem that can be fixed by a GCM update - but who knows? It would be nice to hear anything from Garmin here. 

    I guess I'll have to look into this a little more now to see if there's any solid evidence. 

    -----------------

    Edit: So I switched off the BT sync manually and the battery drain is as massiva as before during the last 3 hours. Damn. I am running out of ideas. 

  • I am also astonished about the battery drain. I use it actually for open water swims (one hour a day) and the rest of the day just as smart watch. It looks like it has only have the capycity that was advertised. And the solar "panel" seems to be more or less useless even I am the whole day out in the sun.

  • The battery live with the 9.33 just increased on my Fenix 7X Solar Sapphire. I only use an Android phone. Allday long I have BT on, I sport a lot...yes a lot. Only problem I have is that I should not forget to charge it when I go for a long run. Two weeks without charging is normal for me. Must say it improved a lot after I did a factory reset on it.

  • Unusual battery consumption is probably one of the hardest things to troubleshoot and I do understand the frustration that all of you have regarding battery usage.

    I'm running GCM on Android but have no issues at all. My last charge was 29th at 13:48 (charged to 100%). Time is 11:31 at the moment so almost 94 hours ago. Battery level is 65% which should make the batter last 269 hours (11 days and 5 hours).

    Out of those 94 hours 2 are running activities with GPS configured at max (all + multi band), 1s recording, always on, Stryd and external HRM connected. Rest of the time is in watch only mode, always one disabled with 15s timeout and PulseOX disabled.

    I'm more than happy and never experienced any problems.

    One thing that I would check is how often your watch syncs with GCM on the phone when they are in reach but you don't unlock the phone or open GCM. It can be done by going to the daily summary on the web:

    One thing that I notice is that even if my watch is connected to the phone and receiving notifications it doesn't sync unless there is an event (like exiting sleep mode, saving an activity or manually going into GCM and force a sync). Perhaps there is some configuration in your phone/gcm that makes it syncing very often?

  • That's good to hear. Maybe I will try a factory reset this weekend - with a heavy heart, because I wanted to save myself this work. I don't want to set up everything again.

    Because as it is now, I can not and do not want to use the clock further. The battery indicator reports fully charged "11 days", but already after 24h the battery has only 75%.

    With version 9.24, the daily consumption was at 5 to a maximum of 10%.

    Immediately after the update to 9.31, the drama began, because I remember how I was shocked in the evening that suddenly there was only 40% battery.
    When I read all this, I obviously have to assume that "something" was destroyed by the update itself, so that the clock consumes more power from then on. Some service that was not initialized properly by the update, or something like that.

  • There's still a lot of setting up again you'll still need to do, even if you follow Garmin's guidance - plus, from what I understand you'll also need to wait a further 3 weeks before your HRV baseline is re-calculated before you get proper Training Readiness data.