Sports & Fitness Archive

Forerunner 230/235 Heart Rate Stuck on 66

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

Heart Rate Stuck on 66

Former Member over 9 years ago

My 235 has developed a fault today, whereby the 24/7 heart rate is stuck on 66bpm, with no heart rate at all available during activities.

A quick forum/web search shows that a few people have had the same issue - Has anybody managed to find a solution yet, or is it a trip back to Garmin?

I've already tried updating to 3.13 (even reverting to 3.10 first, as I was already running 3.13 beta), restoring factory settings and the obligatory turning the HRM on and off, but nothing has shifted the issue.

Fast falling out of love with this device, after being over the moon with it a week ago. I was even overlooking the short battery life and the fact I couldn't pair my HRM strap with it (not sure if it is fault on watch, or strap) not to mention the cosmetic scratch on the LCD screen underneath the glass.

Hopefully, just teething trouble, as, when it was working, this was one *** of a running watch.

0 Former Member over 9 years ago

Looks better to me. Have initialized a few HR measurements and no artificial 72bpm appeared.

I sure hope it stays that way for you. I'm at work and can't try it for a few hours yet. If anything changes, please keep us posted.

0 Former Member over 9 years ago

Hi Everyone - Sorry for the trouble! We've got a new beta that should resolve this bug. You can find it here:

http://www8.garmin.com/support/download_details.jsp?id=9920

How could Garmin release hardware and software like this. Does not one test this stuff out. Over the holidays thousands of people got dissapointed and Garmin is just now getting around to fixing this mess. Both my Vivosmart HR and now the FR235 were plagued with this crap.

Sorry but there is little excuse for this.

0 Former Member over 9 years ago

How could Garmin release hardware and software like this. Does not one test this stuff out. Over the holidays thousands of people got dissapointed and Garmin is just now getting around to fixing this mess. Both my Vivosmart HR and now the FR235 were plagued with this crap.

Sorry but there is little excuse for this.

You said "were plagued", as in past tense. So, the beta to update your WHR sensor from 2.40 to 2.41 worked then? When you check your HR, it isn't defaulting to 72 anymore?

0 Former Member over 9 years ago

You said "were plagued", as in past tense. So, the beta to update your WHR sensor from 2.40 to 2.41 worked then? When you check your HR, it isn't defaulting to 72 anymore?

I will not know till I get home.

Is this beta 2.41 working for others, if so it should work for me. Just really disappointed right now. My new Vivosmart HR suffered from the same problem, the past tense came from it as it was returned. Getting tired of messing with it, if it is working you people need to push out another update.:mad:

0 Former Member over 9 years ago

Still on 66 after 2.41 update?!

Hi Everyone - Sorry for the trouble! We've got a new beta that should resolve this bug. You can find it here:

http://www8.garmin.com/support/download_details.jsp?id=9920

Mine is still stuck on 66 after this update. Followed directions, then toggled off/on the HRM setting, then powered off/on, then did the long press power off/on. My system settings confirms that the WHR is updated: 2.41 (1.01.82). Anyone else seeing the same situation? Bummed

Edit: Just submitted the Feedback Report Form inside the update ZIP file. Hoping that detailed info (watch serial number, Garmin Connect account, etc.) will help Garmin figure out whether it's a hardware issue for me

0 Former Member over 9 years ago

Mine is still stuck on 66 after this update. Followed directions, then toggled off/on the HRM setting, then powered off/on, then did the long press power off/on. My system settings confirms that the WHR is updated: 2.41 (1.01.82). Anyone else seeing the same situation? Bummed

That is just great! Good to see Garmin has a handle on this! LOL!

0 Former Member over 9 years ago

Mine is still stuck on 66 after this update. Followed directions, then toggled off/on the HRM setting, then powered off/on, then did the long press power off/on. My system settings confirms that the WHR is updated: 2.41 (1.01.82). Anyone else seeing the same situation? Bummed

any reason your last sync is on Friday 8th when you are in NJ? Upload time zone: https://connect.garmin.com/modern/settings

0 gpb11 over 9 years ago

It's odd is that this is a problem for SOME people but not for others.

When I first got my watch it'd do the 66bpm lock when taking it off the charger. Easy to clear with a power cycle.

It hasn't happened even once since applying the WHR 2.40 update.

I'm sure it's annoying to have it keep happening, I hope they get it fixed for the instances the prior fixes didn't address. (suggests there may be multiple causes?)

0 Former Member over 9 years ago

any reason your last sync is on Friday 8th when you are in NJ? Upload time zone: https://connect.garmin.com/modern/settings

Hmm. I don't see a last sync issue on my page and the setting is correct (Eastern -5:00 GMT). Maybe it's based on your time zone when viewing my profile?

Anyway, my FR235 time has been off in the past week simply due to fact that I am trying the long press power off/on in futile attempts to "unstick" the 66 bpm and that seems to clear the GPS cache along with the accurate time/date.

0 Former Member over 9 years ago

Maybe it's based on your time zone when viewing my profile?

Must be (I am GMT+11 incl summer time at the moment.....used to live in NJ)

I am pretty anal trying to understand how the time part works as it is causing differences for me between data in the reports and inconsistencies with MFP. I cannot quite understand why GPS time is even required if you can synchronize to GC regularly.