Hi, I have returned to using my 235 after an absence of about a year (Apple Watch—nice device, but in the end I prefer the Garmin stats.). In the intervening period there have been firmware updates, all of which I have applied to the 235.
But something weird is happening.
My 235 rarely gets a HR fix for me, whereas it always used to. Let me explain a little more. I leave the watch (non activity tracking) on my desk between runs. When I am getting ready to run I put it on my wrist, get changed, potter around etc., probably up and down stairs a couple of times—so I'm usually fairly warm. When I go outside to run, I'll enter the activity screen and get a GPS fix within seconds. I then walk maybe 200 yards or so to the start of my route, and very rarely has the watch got a stable HR by then. The attached picture is a good example of what happens if I start to run before the fix. Note that even though I had to stop at around 3.5 miles for a crossing, it still didn't pick up the correct HR thereafter.
But here's the thing. If I switch the watch completely off, and then back on again, it generally can fix. I have noticed two behaviours that may be contributory factors.
1. When I pick up my watch from the desk and put it on, even if I toggle to the heart rate reading rarely do the green lights come on (I prise it up at the edge to peek!). When they do it seems to start its 'hunt' around 100 BPM and goes upwards from there. Since my resting heart rate is 45-50, and even after walking/milling around only up towards 60, it's never going to get it then.
2. When I switch on from cold it starts the hunt at 72 but immediately drops lower and can then get a fix.
I guess I could simply get used to switching on and off between runs but this shouldn't be necessary on an expensive and high tech piece of kit.
Any ideas whet might be going on here?
Thanks,
David ciq.forums.garmin.com/.../1471735.png
