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

HR/ANT+ dropouts may be fixed with Sensor Version 5.8

Former Member
Former Member
There is another topic regarding an upgrade to sensor version 5.8.
I took this upgrade today via Garmin Express.
Later on I did an indoor cycling workout with the Garmin ANT+ speed sensor and using on board HR.
For the first time I did a workout (33 minutes ling) without any dropouts.

For those with this ANT+/HR dropout issue, please take the upgrade and report back.

Hopefully you can have a workout that looks as clean as mine.



ciq.forums.garmin.com/.../1318902.png
  • Anyone tried this with 3.50, is situation any better now?
  • Former Member
    0 Former Member over 7 years ago
    Anyone tried this with 3.50, is situation any better now?


    The problem in this thread is not listed as fixed in 3.50
  • Well thank you for providing that insightful comment.
  • I'll try it this weekend on 3.50 but doubt a fix is in here. 3.5 went GA pretty quick from the 3.43 beta. We're probably going to have to wait for a sensorhub update for a possible fix and that wasn't updated with 3.50. And those sometimes seem to get rolled out without notice outside of general updates.
  • Just to clear out topic of 3.50 - no it does not fix anything mentioned in this thread (and it does not promise so, at least not in the post). Waiting for updated sensorhub.
  • Former Member
    0 Former Member over 7 years ago
    Well thank you for providing that insightful comment.


    You are very welcome. I hope I have helped.

    You should not expect Garmin to deliver firmware to contain a fix that they never said was included. Garmin is clear at listing what is fixed in each version. My comment was meant to help as I thought you were not aware of what was listed as fixed in version 3.50.

  • Former Member
    0 Former Member over 7 years ago
    No, you have not helped, you just stated a fact that anyone able to read can read for them self and most probably already has read it if he/she is on this forum. It was about as helpful as stating that a sun is going to rise tomorrow morning, but I guess Poe’s law strikes again.

    I can expect whatever I want to expect. I don't know why you think that you should be the person to decide what my expectations should be and besides that, my question wasn't directed at Garmin but at other users having these problems.

    So, what you are claiming is that when Garmin releases a new firmware there are never any undocumented changes? Only changes always are the ones listed and never anything more? Do you know that for a fact or is that just your opinion?


    I don't know what your issue is. We are all in this Forum trying to help each other. You are being counter productive and insulting. Stop it.
  • Former Member
    0 Former Member over 7 years ago
    No, you have not helped,


    I'm the one who started this thread. started this thread with the excitement that I did a 30 minute workout without any ANT+ drops. I wanted to share with the Forum and see if they were experiencing the same thing.

    Unfortunately what we found was that the problem still occurs, as other forum members have reported, and as as I have seen with all my subsequent workouts.

    Garmin has also chimed in and what we know is they are trying to reproduce the problem and come up with a fix.

    This Forum and thread have been helpful to me, forum members as well as Garmin as they can see the problem is wide spread.

    I also have an ongoing ticket with Garmin, which I have opened some time back in February.

    Member had746 does not think I am helpful, quite insulting. However for the good of all in this forum I will continue to post to be as helpful as I can in a productive manner.But please, let's respect each other and not insult each other.
  • I didn't notice it was you that started this thread and indeed this thread has been really helpful. I was referring to its not in change log comment. I thought you were messing with me and it looks like I overreacted. Sorry.
  • I didn't notice it was you that started this thread and indeed this thread has been really helpful. I was referring to its not in change log comment. I thought you were messing with me and it looks like I overreacted. Sorry.



    With tongue a bit in cheek let me point out that accepting responsibility and acknowledging over-reaction, and for the love of g-d APOLOGIZING is not normal public forum behavior.

    You two public forum combatants should consider yourselves extraordinary for reaching this point. <insert golf-clap>

    Chris