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
11 months 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 1339905

    I'm on 19.09 and I cannot see any "ANT+ heart rate" in Garmin Connect plots. So I suppose it's a field generated by a Connect IQ data field? Whereas with 19.09 and FitFileViewer, you automatically get "heart rate", "wrist heart rate", and "external heart rate" without installing anything extra.

  • 0 9 months ago in reply to 1339905

    Are you on beta for Connect as well? Because I can't find what you're referring to...

  • 0 9 months ago in reply to 1339905

    19.09 is Beta - should this be discussed here?

  • 0 9 months ago in reply to Woody

    The thing is beta forum is kinda dead community and this bug is affecting both stable and beta releases so not only linked to beta fw.

  • 0 9 months ago in reply to afarnedi

    yes, but as we can see in this actual case, only people with the beta-software are able to use the view mentioned. And, as noted in the beta-forum: "If you would like to share bug reports, please do so in the respective Public Beta or Public Alpha forums.".

    When nobody is discussing the bug in the beta-forum - maybe nobody will fix it. ;)

  • 0 9 months ago in reply to Woody

    garmin's tech guys reading "stable" community are the same reading "beta" one, garminsierra to name one; I was personally in contact with him due to this bug, I've made a lot of tests following his requests and believe me, they just don't care if you report here or there, the important is to report the issues somewhere.

  • 0 9 months ago in reply to afarnedi

    i've had so many (often obvious) issues that i discussed in the "stable" community that where never even replied to that i will not believe you. ;)
    Including the HR Bug this thread is about. I've had similar issues with my Fenix 6, which no body was interested in. Best part was when the support told me that i should throw away my fenix if i am not satisfied with the wrist HR.

  • 0 9 months ago in reply to Bitti

    As I wrote two days ago, I'm using the ANT+ HRM Data Field available for download here:

    apps.garmin.com/.../7c83d402-4b68-4f0a-b167-7139788a19b3

  • 0 9 months ago in reply to oBuTTuSo

    I'm not sure...I did the 'regular' 19.09 Beta update, current CIQ version on my watch is 5.0.0.

  • 0 9 months ago

    The heart rate monitor bug is unchanged (or perhaps worse?) in 18.26.  A 4-mile 'hard tempo' run was recorded at a max HR of 136, and immediately after stopping/saving my run, my indicated HR jumped to 150 (which is closer to my actual HR.  

    After a full power-off and power-on, the HR on the following run appears less broken - only wrong tor the first 11min of run.  

    Either way I'm still waiting for a fix.