Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

18.20/19.18 HR bug still here

afarnedi
over 1 year ago
  1. Hi, despite the information received from @Garminsierra that the bug was 'probably' fixed in 18.20, I have to say that today  I had a run after a couple of weeks of recovery after a flu and I was running with +30sec X minute slower than my normal pace and HR was around 140 BPM. All of a sudden, out of the blue, without changing my pace despite the very relaxed feeling, HR jumped at 185bpm, that's also exceeding my max HR possible for my age and my training level. I had to deactivate WHR and switching it on immediately after to get it working properly. After further 10 minutes same situation. Now, the thing is, i could also accept this and just don't care about that obvious bug, if not that all statistics are very much dependant by HR. I'm referring to vo2max, performance condition, rest hours, endurance score, suggested daily training etc etc...well Garmin, I'm sure you know that's probably the BIGGEST bug ever since here the whole reliability of the watch is under discussion. this is a sport Watch, probably the best out there, but if HR is not working properly, well, we're far from being an entry level watch. Furthermore, a friend of mine was running with a 69€ watch and HR was just perfect, consistent, stable and reliable. 
  • 0 9 months ago in reply to Saganist

    Soft reset helps but only for some time. After 1-2 days problem returns.

  • 0 9 months ago in reply to 8331975

    So basically, reboot the watch every day if you want accurate data

  • 0 9 months ago in reply to Saganist

    It's not normal with watch such expensive watch. But it's true, this is some kind of temporary solution.

  • 0 9 months ago

    Soft reset does not help, I tried it yesterday before some pyramide intervals. The problem persists. The usual lag in the beginning and the lag during intervals. If they at least gave access to older software versions.
    To be clear, if it worked in the past without any extra "measures", why would we need to do resets, warm-ups etc. to make it work now? 

    Here's the example, although I have the feeling Garmin simply doesn't care anymore. Also, one more flaw, the watch even struggled with GPS twice or three times to catch up with the increased pace in the beginning of some intervals.

  • 0 9 months ago in reply to manueleltoro

    Has to be super frustrating! Especially since it did work, it's an expensive watch, and HR basically effects everything advanced the watch does. Frustrating they don't seem to be addressing this seriously, and neither do reviewers. I know it's a pain, but have you tried a hard reset yet. Basically sync, then wipe the watch as if you were going to sell it , then set it up again.

  • 0 9 months ago in reply to Saganist

    I did the hard reset. After that the same problems occur.

  • 0 9 months ago in reply to Saganist

    Reset does not help. The cause is bad HR algorithm which remains same after reset.

    I agree that Garmin's passivity and avoidance of this serious issue is astonishing.

  • 0 9 months ago in reply to 8331975

    Not a good sign, the fact they aren't addressing this is the very reason I'm not buying a new watch yet. Regressions or regression testing needs to be higher on the backlog for the software or sensor firmware team.

  • 0 9 months ago in reply to Vizi

    If it's the algorithm then why was it working fine before, that's the real question...others also seem to see the issue specifically when playing music from the watch. Seems to be either a bug in the sensor firmware, or system software, or maybe they stopped paying someone for an algorithm or lost some lawsuit and had to remove an algorithm. If you look at the forums it's across the Forerunner x55 and x65, plus the Fenix 7 and Epix 2 lines. Either way the silence is telling. Best thing to do is pressure reviewers like Desfit, DC Rainmaker, Quantified Scientist, etc... to review the WHR again after updating, not initial software release.

  • 0 9 months ago in reply to Saganist

    Because HR worked better before. It got worse after software updates. People have been complaining for a while, but in last 6 months there is so many user complaints that Garmin hesitantly responded that they will investigate it. However, nothing was done to fix it until now.