Oddly enough mine did the same. After an hour or so, mine went back to the 71/72 reading when I accessed the widget. I hope you have different results.
Mines gone back now. Starts off low then jumps to 71. Sometimes it stays there for a bit, and sometimes it doesn't. I've had a few weird spikes up to around 130. If I keep checking evry says 30 secs or so its ok, but if i leave it for a few minutes and check again it goes straight back to 71
Mines gone back now. Starts off low then jumps to 71. Sometimes it stays there for a bit, and sometimes it doesn't. I've had a few weird spikes up to around 130. If I keep checking evry says 30 secs or so its ok, but if i leave it for a few minutes and check again it goes straight back to 71
Mine is similar. Checked while sitting down,. Starts off mid fifties, goes to 71 and then comes back down. Usually. Was checking this morning and noticed it had been stuck at 72, even on broadcast HR. Moved the watch around and finally it came back down again. Checked again a bit later. It spiked to 136, then dropped again to the correct HR (around 50 bpm). Just checked again, went to 72 and stuck there for about a minute before coming back down to low 50's after several button presses. Other anomalies. In HR widget I am getting a RHR value of 38 (incorrect), while the "low" value for HR is 42? RHR in GC is 49.
In other words it seems to be all over the place and I don't know what readings to believe....:mad:
Mines gone back now. Starts off low then jumps to 71. Sometimes it stays there for a bit, and sometimes it doesn't. I've had a few weird spikes up to around 130. If I keep checking evry says 30 secs or so its ok, but if i leave it for a few minutes and check again it goes straight back to 71
I see exactly the same behavior. Initialization with 71 or 72bpm, only with subsequent measurement a few seconds later with reasonable values. Also implausible spikes in the 130s or 140s while sitting or walking around.
I see exactly the same behavior. Initialization with 71 or 72bpm, only with subsequent measurement a few seconds later with reasonable values. Also implausible spikes in the 130s or 140s while sitting or walking around.
I've had the 71/72 issue since the WHR was updated from v2.20, but I wasn't getting the high spikes until v2.50 was installed where I'm now getting them daily. This morning I was sitting down on my couch and I checked my HR widget. Started out at 72, spiked to 142 and then gradually settled down to 69. It's discouraging that v2.20 worked so well for me and the last 3 updates that were designed to "fix and improve" the sensor has made things worse. Maybe someone can figure out how to revert the sensor software back, so user's can use the version they are happy with? I no longer care about "being up to date with the current firmware and software updates" if I need to contact support. The updates are the reason I need to contact support!
First I hope that someone from Garmin is monitoring these forums.
I have had my 235 for a month now and I have enjoyed using it. It has tracked my HR well during outdoor and indoor runs. The problems I have are when I am doing the "other" activity. I have been doing p90x3 and the HR will get stuck on 66. When I stop and adjust (tighten the wrist strap) the HR will stay the same or start to track downward. If I power cycle the watch the HR will begin to track correctly in the 140s to 160s. I have not noticed the watch getting stuck on the 66HR or having inaccurate readings unless I am in the "other" activity. I hope this information helps with problem solving. It would be great to not have to power cycle the watch every time I workout with the "other" activity.
Mine gets stuck on 66 in any activity mode and that has happened ONLY since this update. I power cycled it off and back on numerous times and it never helped except once then once it synced- right back to 66. But, I turned it off or power cycled it off last night. Turned it on this AM and so far.. its working. I ran this AM- HR was accurate- I synced it and it has not gotten stuck again.. yet... I am sure it will happened again..
Yes. It had some issues before 1.50 with not tracking during p90x, but now it is getting stuck at 66. Before it would track in the 70's and I could stop and hold the watch on my arm and it would increase, now I have to power down the watch.
