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

WHR Firmware Beta 2.41 - Fixes issue where HR value could get stuck (now 2.50)

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

In case you missed this.

How is it working for everybody?

Seems OK for me.
  • Strange. Was available to me and I was on 2.41 beta?


    Now I have it! Finger cross...
  • Former Member
    0 Former Member over 9 years ago
    Stuck on 66

    I did this twice. Still stuck on 66. The first time it did not ask to update. The second time it restarted. ???

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

    In case you missed this.

    How is it working for everybody?

    Seems OK for me.
  • Former Member
    0 Former Member over 9 years ago
    it works for me. Thanks

    Go to the HR widget. Press and hold the up-arrow until you get the settings menu. Turn the HRM off. Back out back to the clock by using the back arrow button. Press and hold the power/light button for about 15 seconds, until the screen fades into nothing. Wait a minute or so. Press the power/ light button for about 3 seconds until you see the "Garmin" logo on the screen, then release. Let the watch boot up. Go back into the HRM widget settings and turn the HRM back to "auto".

    The above has got me out of the locked HR problem. My watch just did it, and I'm on 2.41...are you reading this Garmin, fix this garbage, please!


    Yes, it works for me... Thanks
  • Former Member
    0 Former Member over 9 years ago
    My HRM has definitely gone worse with the newest update (2.50). Always when I check the widget it turns first to 70-73 and then to some other value. I see much more blocks of constantly the same HR and then sudden spikes, which are physiologically not explainable.

    It worked OK for me before. Now its just a piece of garbage. Very disappointed.
  • Former Member
    0 Former Member over 9 years ago
    Update?

    Just curious, most of you have updated the original firmware to 2.5, would you do it again?

    I'm picking up a 235 after work today, trying to decide if it's worth updating to 2.5 or waiting. So many issues…

    Thanks

    RC
  • My HRM has definitely gone worse with the newest update (2.50). Always when I check the widget it turns first to 70-73 and then to some other value. I see much more blocks of constantly the same HR and then sudden spikes, which are physiologically not explainable.

    It worked OK for me before. Now its just a piece of garbage. Very disappointed.



    It has been always like that since the beginning. It starts with 72 bpm and then tries to lock into your hart rate. Pls don't confuse ppl.
  • Former Member
    0 Former Member over 9 years ago
    It has been always like that since the beginning. It starts with 72 bpm and then tries to lock into your hart rate. Pls don't confuse ppl.


    That's not true. The 71/72 issue started with the v 2.30 update. 2.20 worked and it was updated to save battery life.
  • Former Member
    0 Former Member over 9 years ago
    FWIW I updated and have had no problems.
  • Former Member
    0 Former Member over 9 years ago
    This is my post 2.50 experience from the other day:

    Just had a steady swim of 4 laps, and when I finished looked at the HRM to see if it had come to life (didn't set activity), and it hadn't. So pressed the HRM widget, and it showed 82, then in the space of about 30secs went down to 72, then shot up to 154, then settled on 98, which would have been about right.

    Are others experiencing this yo-yo effect?
  • Former Member
    0 Former Member over 9 years ago
    FWIW I updated and have had no problems.


    So, you're on WHR2.50 and your heart rate doesn't go to 71/72, then gradually settle on your actual heart rate when you check your widget? What WHR version were you on when you received your 235? I think there are two different groups posting here; pre and post version 3.10/2.20. A lot of people are receiving their watches with versions 3.20/2.30 and have had the 71/72 HR right out of the box. So, this would be "normal" for them. A lot of users had version 3.10/2.20 or earlier and the HR was sampled more frequently and when you checked the HR widget, it went straight to your HR like every other monitor on the market. The earlier version did use more battery, but there's a large consensus that would rather sacrifice battery life if they could return to that higher sampling rate.