Running the other night I stopped the watch to cross the road. When I restarted and hit the next mile marker (it was only a couple of seconds later) the next mile had an average time of 32mm, that dropped to 28 and then eventually settled at 12-13mm where it recorded the next mile taking just over 12 minutes to complete. I was actually running just under 9mm for the run and didn't speed up or slow down (that much!).
Strava seems to have fixed the data, but Garmin Connect still has me down as what the watch recorded for that mile lap.
Mine re-booted this afternoon. Lost 5 hours worth of data from the last synch. Ironically I had had it in broadcast mode to get a more accurate HR trace for the day..:mad:
I reckon that sometimes loading new firmware causes the watch to get into funny states. Not for everyone, but for some. First thing I'd do if I saw a weird side effect right after a firmware upgrade would be to do a non-vol clear AKA factory reset, so you know there is nothing causing an issue
4.10 was a firmware update and not an update for the oHRM sensor which is currently on WHR2.50. Does anyone know if the 4.10 update somehow affected the HR sampling rate? I've been getting some strange readings with HR since 4.10. For example, I woke up this morning at 4:30 AM. From 5:01 to 8:00 AM my HR flat lined at 83. Not only is this reading high, but I had several cups of coffee and was moving around the house a bit. Surely the caffeine alone should have changed my HR. I didn't get a "move" notification either, so it recognized my movements. The HR graph on my watch, mobile and Garmin Connect all show this. I'm wondering if my watch is getting "stuck" now, or did my 235 wait 3 hrs between sampling? Anyone else experiencing anything like this?
4.10 was a firmware update and not an update for the oHRM sensor which is currently on WHR2.50. Does anyone know if the 4.10 update somehow affected the HR sampling rate? I've been getting some strange readings with HR since 4.10. For example, I woke up this morning at 4:30 AM. From 5:01 to 8:00 AM my HR flat lined at 83. Not only is this reading high, but I had several cups of coffee and was moving around the house a bit. Surely the caffeine alone should have changed my HR. I didn't get a "move" notification either, so it recognized my movements. The HR graph on my watch, mobile and Garmin Connect all show this. I'm wondering if my watch is getting "stuck" now, or did my 235 wait 3 hrs between sampling? Anyone else experiencing anything like this?
The only time I had that was when my watch rebooted upon synching as described earlier in this thread. It hasn't done it since though. Was there a chance your watch restarted? Mine basically created a straight line between the two sync points.
The only time I had that was when my watch rebooted upon synching as described earlier in this thread. It hasn't done it since though. Was there a chance your watch restarted? Mine basically created a straight line between the two sync points.
But... having just checked my HR trace for today I had a couple of pretty big gaps in recorded points. 2 hours between 1:03 and 3:03 when I was asleep and 9:40 - 11:20 this morning. Not sure if the watch was stuck or this is a normal sample rate. I had a pretty inactive day today but even so, that seems to be taking low sample rate to the extreme? I'm not sure what happens in GC if the HR sample is the same as previous. Is it ignored so you just get a straight line?
No, my watch didn't restart. Just checked again and I had another flat line reading of 70 bpm from 8:02 to 10:26 AM. The next reading following that was 72 bpm at 11:27. I was cleaning up the house and garage during this time so, non movement isn't the issue. I've been very critical of the HR sampling change following the WHR 2.30 update, but this is just useless now. What puzzles me is this was a firmware update and not an update for the sensor. I also noticed my HR widget stays on for about 45 seconds following the 4.10 update, so maybe it does have something to do with the sampling rate. If this is indeed the case, sampling has now gone from bad to worse. 2 1/2 hrs between readings while being semi-active is worthless! This in turn will render calories burned pointless also. I'm really hoping this is just some kind of fluke and it corrects itself soon.
It makes logical sense though, where typical software architecture is employed
What puzzles me is this was a firmware update and not an update for the sensor. I also noticed my HR widget stays on for about 45 seconds following the 4.10 update, so maybe it does have something to do with the sampling rate.
The Heart Rate widget and the data recording functions are logically at the application level in the firmware, and not at the hardware driver level in the WHR module (in the Sensor Hub). In the case of the issue of the HR being stuck on 66 or defaulting to 71–72, it could be attributed to the WHR module falsely or incorrectly reporting HR readings when requested by the application, which does not know any better when it is being fooled. However, how often the sensor/WHR module is being asked for HR readings is outside of the Sensor Hub's control (although, of course, it could conceivably be programmed to reject frequent requests from the application).
