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

Software Bug in WHR / Firmware (66bpm issue) (now fixed in WHR 2.40 update)

Former Member
Former Member
I spoke to Garmin today regarding the heart rate being stuck at 66 bpm after I updated my firmware to 3.20 and my WHR to 2.30. Even restoring to default has not caused the heart rate sensor to pick up any changes.

Apparently, a lot of other people are experiencing this and they told me that another software update may come out soon to address this since it's not a hardware issue. *sigh*
  • I had the 66 bug this morning. Seemed to occur sometime after taking the watch off the charger. Went away after I rebooted my watch.

    (received it last night and updated to latest firmware including WHR 2.30)
  • I got this after I updated - you can fix it thankfully by either rebooting as suggested above or by turning the heart rate tracking off then switching it back on.
  • Former Member
    0 Former Member over 9 years ago
    I got this after I updated - you can fix it thankfully by either rebooting as suggested above or by turning the heart rate tracking off then switching it back on.


    I've done both and it still stays at 66 :( it's definitely a software issue but I'm surprised the error has been so persistent despite the reboots, restore defaults, and what not.

    I wonder if there is a way to roll back to the previous firmware...
  • I've done both and it still stays at 66 :( it's definitely a software issue but I'm surprised the error has been so persistent despite the reboots, restore defaults, and what not.

    I wonder if there is a way to roll back to the previous firmware...


    If you follow the instructions here you should be able to roll-back to 3.10 or 3.13b
    https://forums.garmin.com/showthread.php?336850-Follow-these-Instructions-to-get-a-stable-FR235-(Must-Read)
  • Okay I got the dreaded 66 bug again, and this time I had to reboot to get rid of it.
    It appears to happen each time I charge my watch up :/
  • Okay I got the dreaded 66 bug again, and this time I had to reboot to get rid of it.
    It appears to happen each time I charge my watch up :/


    Just experienced the same. After charging it was stuck on 66. Rebooting fixed it.

    I only experienced this issue when I received the watch and updated to 3.10. With 3.13b I never had that issue, not even once.
  • I had this issue with 3.10 and it is still present in 3.20.

    With 3.10, rebooting didn't help but just tried it with 3.20 and it is working again. It may have been coincidence.
  • Former Member
    0 Former Member over 9 years ago
    I have my FR 235 on backorder & I'm expected to receive it 12/16. I have been following this forum in the meantime and I hope I don't receive one with the "66 bug". I can't help but wonder if this is actually a hardware issue with some units, and not a software issue. A lot of people have had this problem with the different sw versions and a lot have had no problems at all. Wouldn't it make sense if it's a sw issue the trouble would be across the board? I think if I have this problem I'm going to exchange mine immediately.
  • Former Member
    0 Former Member over 9 years ago
    I have my FR 235 on backorder & I'm expected to receive it 12/16. I have been following this forum in the meantime and I hope I don't receive one with the "66 bug". I can't help but wonder if this is actually a hardware issue with some units, and not a software issue. A lot of people have had this problem with the different sw versions and a lot have had no problems at all. Wouldn't it make sense if it's a sw issue the trouble would be across the board? I think if I have this problem I'm going to exchange mine immediately.


    i do not understand this bug and since i have not been following thru the posts. i do not think i am encountering it on my current watch. it definitely shows some heart beats above and below 66.

    I have one 235 coming in today and I am trying to check it out too.
  • The bug is where the 235 gets "stuck" on a HR reading of 66bpm. Happened to me yesterday morning after taking the watch off the charger. Rebooted the watch and it went away. I haven't seen it return yet. Also haven't put it on the charger.

    I highly doubt it's specifically a hardware fault, and if it is that'd certainly justify warranty replacement.

    As with many things, take what you read with a grain of salt. Some stuff just is a much bigger deal to some people than it is to others.