i have all the last updates, but... got a cadence lock on todays run :(
Confirmed :mad:
1 marathon and it worked perfectly for me. 1 easy trot yesterday and within 2km my HR was apparently hitting 185 bpm. I had to switch off the OHR for the run.
Garmin Support has been useless on this. My HR was working great until the 4.2 update then it is total rubbish. I am just going to return mine to the vendor. No need to keep messing around with this.
Garmin Support has been useless on this. My HR was working great until the 4.2 update then it is total rubbish. I am just going to return mine to the vendor. No need to keep messing around with this.
What have Garmin support said or suggested you try?
I'm just about to email them as I'm getting frustrated that my HR works everywhere EXCEPT when I am out running since the 4.2 update
After the update, it's taking a long time for the heart rate to start up during an activity....sometimes as long as five minutes. A bit frustrating. Anyone else have this issue after the update?
After the update, it's taking a long time for the heart rate to start up during an activity…
That's probably due the update of the WHR module to 2.60, which stopped the Elevate sensor from returning (meaningless) numeric values before it managed to properly lock on to the user's current heart rate, and not due to firmware 4.20.
Anyone else have this issue after the update?
Not five minutes. One minute, maybe. Which would you prefer – false/inaccurate/unusable HR values early, or only real HR values and only when the sensor is ready, when getting quicker/better actual performance out of the sensor is not something you can have? I prefer the latter.
ASmugDil- can I suggest that you only comment about things you have first hand experience with? You seem to like to post general assumptions based on what you read in posts, and without anything more! :)
ASmugDil- can I suggest that you only comment about things you have first hand experience with?
My first-hand experience is that in the Heart Rate widget, the heart icon used to become solid within five or so seconds – indicating that the widget has received a confirmed value from the sensor – but the value was invariably 72. It doesn't happen after the WHR module has been updated to 2.60; the heart icon just blinks for a long time. That is my logical conclusion, not something I've read somewhere.
I'd be happy to be proven wrong if you, as a Connect IQ developer with intimate knowledge of the internal workings, care to point me/us to either Garmin's documentation of what has changed, or an app you've written to demonstrate how the sensor is actually behaving.
That's probably due the update of the WHR module to 2.60, which stopped the Elevate sensor from returning (meaningless) numeric values before it managed to properly lock on to the user's current heart rate, and not due to firmware 4.20.
Not five minutes. One minute, maybe. Which would you prefer – false/inaccurate/unusable HR values early, or only real HR values and only when the sensor is ready, when getting quicker/better actual performance out of the sensor is not something you can have? I prefer the latter.
In your scenario,I would choose accuracy...the problem is that my accuracy is the same as prior to the update.....but with an up to five minute delay in getting hr going for an activity.
Did another run today with my FR235 in the left wrist and my Sony Smartwatch paired with the Polar H7 and Ghostracer on my right wrist. The results are very close with negligible diferences. So the problemas I had after the update seems to be gone (I don't know why) and I'm a happy costumer again (at least for now...).
