Garmin! Why has the new update 15.76 messed up so many watches

So many people are posting about problems with the new update 15 76. Why has this been rolled out without proper testing?

It seems the only way to fix these problems is to do a reset and restore from a backup.

For many this will be a daunting business as it takes quite a long time and then causes problems for people trying to re pair with their devices and restore from a backup.

Top Replies

All Replies

  • I've used it a handful of times for actual naps by manually setting the timer, which is an elegant replacement for what I used to do (use the default timer).

    I haven't had any false nap triggers, and I have a desk job. In fact over the weekend I most definitely did fall asleep on the couch (getting older) and the Garmin caught it perfectly.

    I wonder if others' issues tend to cluster together - perhaps it isn't reading HR properly on the wrist for others. Just my two cents, but I've always found Garmin's sleep tracking to work well (it's also worked on my Apple Watches).

  • I think its around expectations.

    When my watch doesn't work as expected I find there is usually a very good reason. 

    i..e I take a nap - there is no tracking - I check HR and stress during that period - there is no drop in Hr and there is no drop in stress - based on this its impossible for the watch to determine a nap took place.

    Am on the couch watching tv - nap is tracked - check HR and stress - the programe was a yawn, so HR dropped, I was still, stress was low - of course the watch thought I took a nap.

    Since the beta I have had 3 naps (all unscheduled - so the watch was auto-detecting) - on two of them the watch was spot on. On the 3rd it didn't catch it - why - HR and stress too high.

    The watches may cost a lot but its for the huge variety of features - not just sleep tracking - you want just that get a vivoactive 5. Its pure insanity to think that the algorithms are going to cover every situations and every person - they are built for the mass average range. The thing to do is check why the watch didn't do what was expected and learn from that i..e don't go to bed and read for 2 hours during yoru sleep profile schedule and stay very still and not expect the watch to record sleep -= maybe move around every 10 mins , so that watch recognizes you are awake and hopefuly HR stays high enough watch confirms you are awake.

    In some ways I think the fitnes watches have it more challenging than apple/ fitbit as they are generally dealing with fitter people whose bodies potentially react a lot quicker than normal/unfit people and I sometimes think that this may be why potentially it can throw up more issues.

  • In general I would say that I am affected by less than 1% of the issues which are reported on this forum and I would also expect that to be the norm rather than an exception. I currently am suffering from the false nap issue at a frequency of up to 5 recorded naps per day. I do find it a little annoying but don't believe that it is screwing with my metrics overall. I think we are now being presented with a representation of the increases in body battery that we were already experiencing. I hope that a but of fine tuning on Garmin's part can sort the issue out..

  • Mine has been doing that with the heart rate also.

  • I do find it a little annoying but don't believe that it is screwing with my metrics overall. I think we are now being presented with a representation of the increases in body battery that we were already experiencing

    +1

    In fact, making the naps and rest periods visible, even if false-positives, is much better than suddenly seeing your night of sleep being nullified.

    I also noticed that the evening report comes about 2 hours being the scheduled sleep mode. Maybe it is a coincidence. What I do now (instead of removing the watch early in the evening) is switching battery saver on when the evenning report comes up, and turning it off before going to bed. This way, the watch has not been starting sleep while I watch TV, game or use the computer late in the evening.

    Similarly, in similar situations during the day, I turn on the Move altert. This way, if there has been a nap falsely detected, I have a better chance of cutting it short before it becomes long enough to replace the night of sleep.

    Overall, the watch is now much better for me in that area, with no downside compared with previous Body Battery, or Recovery influence.

  • Funny thing is though, I never suffered from false sleeps before nap recording was introduced.

  • I just use my watch as intended. I have it on 24/7 and make no changes. For me, it just works. 

  • There is an evening report now?  When did that come?

  • In a recent update. Check the release notes. 

  • So many people are posting about problems with the new update 15 76. Why has this been rolled out without proper testing?

    Bigger picture:

    Take into account the hundreds of thousands to potentially millions (we do not publish the number) of watches in use worldwide between all series that are using the same software version. The v15.xx series software includes: the MARQ Gen 2, Tactix 7 series, the D2 Mach 1 aviation watch, Enduro 2, Fenix 7 original release and Fenix 7 Pro series, and the Epix 2 original release and Epix 2 Pro series.

    Then take into account the number of posts across our entire forums for software bugs being found, The number of posts do not add up to there being 'many watches' with an issue. (Yes, there are legitimate software bugs now being worked on for the next official release in Q1 2024.)

    Software unintentional bugs are unfortunate. Software is rarely perfect. However, for 99% of all users, they are not having an issue and do not see any issues and they are not reaching out to Product Support or posting in our forums.

    In the 4+ years I have been moderating our forums, reality has consistently been different than perception - but only if you take into account the full bigger picture.


    Happy Holidays to everyone.