First thing I checked was that the HR widget didn't jump to 72 immediately before normalizing. It appears to be fixed; that is, unless HR was only working because the watch just booted up and happened to have the HR monitor still running from starting up when I checked. Will have to wait a while and check again. But fingers crossed that it's fixed for good.*
*don't think it's fixed after all, it did the 72 thing to me after waiting about 20 minutes to check it again.
Someone posted in another thread that they still had the 72 HR issue after the update. I'm hoping your correct and they just had a fluke reading. I won't be able to download the update until later this evening.
Update: I didn't realize I had my USB cord here at work. Anyway, I just installed the update and it does appear to have corrected the issue. I'll have to wait awhile and check again too. Looks promising though.
Someone posted in another thread that they still had the 72 HR issue after the update. I'm hoping your correct and they just had a fluke reading. I won't be able to download the update until later this evening.
It's looking like I just got lucky that time. I checked again just now while walking around and the HR sat on 72 for about 10 seconds before dropping into the mid 60s and then bouncing between 63-65 for the remainder of the time.
First i checked to see that the HRM was going (green laser under the watch) - yep. Then checked my HR with another method which said 80BPM. Then brought up the HR widget on the 235, which started at 80BPM, then dropped down to 72, and then went back up to 79-80 (over the space of 10'ish seconds).
Perhaps the update that fixes this is related to the elevate firmware and not a general software update?
Yeah. Same here. Odd that they fixed the VSHR a month ago and this update didn't address the same issue with the 235. I think you may be right about the sensor not being updated.
Yeah. Same here. Odd that they fixed the VSHR a month ago and this update didn't address the same issue with the 235. I think you may be right about the sensor not being updated.
Was the sensor updated in the VSHR at the same time? Or should we expect the 72 issue be fixed with a general update alone.
They might have just wanted to push a few other fixes out given it's been a while and the masses here are grumbling.
Still going to 72bpm even though the HR widget usually starts in the right vicinity
Then checked my HR with another method which said 80BPM. Then brought up the HR widget on the 235, which started at 80BPM, then dropped down to 72, and then went back up to 79-80 (over the space of 10'ish seconds).
Same here. I've been cross-checking the HR widget's readings against that from my chest strap HRM, every now and then this afternoon since updating my FR235's firmware to v4.10 a little earlier.
Whether my HR was significantly lower or higher than 72bpm (by about 10bpm) in a given instance, the HR widget generally started off with a reading in the right vicinity while the heart icon flashed, then went to 72bpm as the heart icon became static, and from there the reading gradually moved back to where it started (close to what my chest strap HRM reported at the time) in about ten seconds.
Are people expecting too much. The unit needs a couple of seconds to at least start working out the HR so what issue is it if it starts at 72
It doesn't start at 72. It starts at your actual HR (or perhaps the last recorded value), drops to 72, then moves back up to your HR. It's almost funny to watch.
