13.22 Increased Battery Usage Resurfaces After Crash

After having the increased battery usage that came with the 13.xx betas and the 13.22 final fixed by hard resetting my Fenix 7 Saphire Solar the issue reappeared yesterday after the watch crashed when deleting a course.

Another hard reset fixed things and of course I have to spent 1-2h now setting up the watch again. This time around I removed the secure config file I had on my watch since it was part of the beta testing cycles.

I wish there was another way but for now the only way I have found to use 13.22 without losing 1% of batter per hour is to perform a hard reset after every crash.

  • Same, and many other people seem to be experiencing it here and on reddit. I think it's time for Garmin to look into it, I really don't want to do a hard reset and have to spend a whole day reconfiguring my watch all the time. I noticed (and confirmed with other people) that this coincides with frequent connections/disconnections & failed syncs with the Connect app (both on Android and iOS). Additionally, when closing and re-opening the app it will take a while to show the watch as connected.

    For me, the watch also sometimes intermittently disconnects from the phone itself, not just the app. I suspect a software rather than hardware issue.

  • Indeed, that appears to be the issue / one of the issues causing the battery drain. For me battery usage in an iPhone 12 and the whole Bluetooth stack on the phone was negatively affected by the constant dis- and re-connections. This has been temporarily fixed by a hard reset, although I had to reconfigure everything and unfortunately it looks like I will have to do this every time the watch crashes.

    Garmin did actively participate and ask the users for further input during the 13.xx beta cycle and I was quite surprised that 13.22 went public - maybe this had something to do with the release of the Fenix 7 Pro. I hope the fact that we haven't seen a new beta release for the Fenix series so far implies that Garmin is working on a fix but I am not very hopeful. So for now my main focus is to get quicker at restoring the watch after a hard reset to my requirements...

  • Battery drain seems to occur after last several software updates.  Garmin did not offer actual solution at all, afgected users are left to handle the problem themselves. Since this is happening for a long time now, I do not think that Garmin will fix the issue.

  • I do not think that Garmin will fix the issue.

    Since not everyone has this problem, or not everyone with the same software version, I doubt there is a simple solution. It doesn't seem to be due to the software version itself.

    After having the increased battery usage that came with the 13.xx betas and the 13.22 final

    I have with 13.22 one of the lowest battery consumption since the beginning.

  • Whatever the reason, it is repeated for number of users every time. If fixing that issue was priority for Garmin, it would be resolved by now. Which is why I think it will not be resolved going forward as well.

  • Yes, I can imagine that, too.

    Garmin-Chris has already some time ago asked im to send a PN if you are affected by the problem. Have you all done that? I'm sure it's much more helpful to do that than just post complaints here.

    The problem that the backlight of the military watch tactix cannot be deactivated by the user in a controlled way is not fixed yet. A possibly life-threatening behavior of the watch since 13.22. In Europe, you can return the tactix if the behavior is not reversed as soon as possible. This is regulated by European law.

    Quote:
    [deleted]

  • Why is almost every post about existing issues considered as complaint by some users?

    I am not complaining but stating the fact. Feel free to disagree, that does not change the fact thst issue persists for a long time now for some users.

  • „Complaint“ was the wrong way to put it. I just wanted to say that it is more effective to send the data to Garmin than to "discuss" it among users here.

  • Sometimes it is not more beneficial to report directly to Garmin support (since they choose to ignore it). Battery drain has been reported for for a long time to Garmin, even in beta forums, with no result.

  • My guess is that it's the update process itself. Maybe some files are destroyed during the update. Just a guess.