20+ firmwares later... 955 still broken

Couple years after release. +20 major firmware updates later. VO2 max does not work properly. Lactate treshold detection does not work properly. Many serious bugs from beta verisons still not fixed. Many UX blunders either not fixed or new are created. I bought top device for top money from allegly reputable sport technology manufacturer. And yet I filled I was scam in a third world bazar... or by a modern corporation.

  • If this makes HR start working again i will do it...

  • My point with the complaint is: it is not worth participating in the beta program given that Garmin does not help you fix any errors arising from it.

    Unless you catch the bug very early on in the beta phase, there is little time for them to fix it. That said, some of the  bugs I've reported have been fixed, but they were usually obvious to spot and easy to fix.

  • Unless you catch the bug very early on in the beta phase, there is little time for them to fix it.

    Many bugs reported in beta are ignored by Garmin and released in "stable" versions, which makes beta program useless.

  • Many bugs reported in beta are ignored by Garmin and released in "stable" versions, which makes beta program useless.

    Long term bugs from one release to the next do seem to be ignored in favour of tweaking recent changes.

  • Long term bugs from one release to the next do seem to be ignored in favour of tweaking recent changes.

    While new bugs are getting introduced constantly.

  • A possible explanation for why existing bugs fail to get fixed is that is very difficult to get Garmin 1st tier support to acknowledge and accept a report of a bug. Support seem to prefer to blame the user rather than create a case for further investigation.

    Whilst it has happened to me many times before, notably it has also happened with the last two (albeit minor) bugs I discovered and then reported:

    - FTP on watch will use an old weight value whilst GCM/GCW will not which leads to inconsistency if there has not been a recent weigh in.  Garmin 1st line support failed to identify the problem and insisted everything was working as intended and hung up on me.

    - Audio prompts power alert says "Average power 65535 watts" if the power meter is not connected.

  • I think you make a good point about the bug not getting the right attention. there have been many cases in my many (15?) years of Garmin watches where they claim that it's a hardware but and a quick to offer me a replacement watch when it's clearly a software issue.

  • That has happened to me also.  Most of my Garmin devices have been replaced under warranty at least once.  I don't think the support people understand the products or their usage very well and don't realise what is software vs hardware.  I have however in the past had hardware issues that looked like software problems but not with the 955.

  • I see that there is a new beta release (23.09).  Something that surprises me is that whenever I read the release notes for new software releases I rarely recognise any of the bugs that are reported as being fixed,  For example they don't seem to bear any resemblance to the bugs that are discussed here on the forum, nor ones that I myself have experienced and/or reported, nor do them seem particularly high profile, urgent or important.   I don't understand how Garmin prioritises their backlog of bug fixes.   It seems as though Garmin is quick to give up on longstanding difficult-to-solve bugs such as anything to do with OHR and instead focuses on the easy-to-fix but less important and less impactful defects.

  • YEs....

    What we expect to see:
    Fixed reboot issue

    What we get:
    Fixed light off during night skiing.