Around 1:19:51 my HR spiked insanely high (179 bpm - my max is about 185bpm) when I was actually just trotting along at a leisurely pace and even walking a bit. Usually I would just ignore it as a glitch but it went on for several minutes and I certainly didn't feel like my heart was about to burst out of my chest.
Hello,
I had not seen the crossover effect until last 4.10 update. Since then, 3 out of 3 runs cadence locked with HR for the entire run.
I do not know if it happened to some of you... or if it is any change in the update that have this negative effect.
Until now OHRM worked, with some peaks, ups and downs, but usable. Now is useless obvioulsy.
I've only done 2 runs so far since the update, one indoor at recovery pace, one outdoor a little faster than marathon pace, and HR data was great for both.
So I updated my FR235 to 4.10 on Sunday and thus far it's transformed what I found was a good product (on 3.30) into a piece of trash :(
Prior to the upgrade I never had any major issues- well except for battery that is- but since Saturday's upgrade it has done the following;
1) Sunday morning- froze completely lost recorded activity and sleep and decided it was Saturday afternoon.
2) I then ran a half marathon with it refusing to record- or even see- heart rate
3) Monday morning- it froze again, an alarm didn't go off as well. Then for good measure it decided it was Sunday afternoon until I got outside to get a GPS signal which set the time correctly.
Has anyone else experienced the same? Anyone have any suggestions? I haven't yet done a hard reset, waiting to see what happens tomorrow morning, but not impressed with the FR235 and Garmin's ability to screw up updates.
Something's definitely not right! Does your firmware version (as reported in Settings: About) say 4.10? Have you tried pressing and hold the light and turning it off and on again? If so then I would suggest a non-vol clear, ie set it back to factory settings to see if that fixes it.
Around 1:19:51 my HR spiked insanely high (179 bpm - my max is about 185bpm) when I was actually just trotting along at a leisurely pace and even walking a bit. Usually I would just ignore it as a glitch but it went on for several minutes and I certainly didn't feel like my heart was about to burst out of my chest.
After owning my FR235 since November without much issue during activities, it has, since 4.1, done the same both at the beginning and mid runs where it just goes off scale high, well above cadence. I stop jogging to let it settle back about 10 or so beats but it then goes straight up as soon as I move. Nothing different on wrist location or tightness to before but now makes the calories burned for the activity nonsense with no easy way to correct it. Not saving the activity does not appear to help as the high HR still is recorded by GC and just puts the error into daily steps.
This is on top of the often funny excursions of HR outside of activities it is appearing to make the OHRM redundant.
Well since the last update (4.10) the HR sensor doesn't work at all when I do "other activities".
I'm doing fitness classes like bodypump, bodycombat, bodyattack ,rpm... before the update the HR sensor worked pretty well but now it shows me an average HB of 60 - 70 for each activities... far too low of course.
I went also for a classic run 2 days ago and everything goes well, the HR was pretty acurate.
Just happened last night to my sons 235. Been working issue free since we got it with 3.2 and now with latest software. Any chance I can still restore?
After owning my FR235 since November without much issue during activities, it has, since 4.1, done the same both at the beginning and mid runs where it just goes off scale high, well above cadence. I stop jogging to let it settle back about 10 or so beats but it then goes straight up as soon as I move. Nothing different on wrist location or tightness to before but now makes the calories burned for the activity nonsense with no easy way to correct it. Not saving the activity does not appear to help as the high HR still is recorded by GC and just puts the error into daily steps.
This is on top of the often funny excursions of HR outside of activities it is appearing to make the OHRM redundant.
Exactly my story. No issues untill the upgrade. After the upgrade it is a mess. Out of 5 activities, only one had correct HR results. The problems varied from "no HR at all", to "HR between 68 and 73 despite heavy exercising" to "HR over 150, immediately after my first steps".
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:
