Latest firmware, WHR still broken. Someome have similar issue?
Latest firmware, WHR still broken. Someome have similar issue?
The HR on my Fenix 7S Pro Solar is currently tracking correctly, so I don't think it's something inherent in the watch or firmware.
I'm on the latest (non-beta) version.
I haven't installed any CIQ fields or faces, which could be a factor too?
I have installed watches and the connectIQ app and have no problems at all, which is why I recommended a good reset for those who have problems, perhaps after several overwrites a bug has been created (not that the firmware released by garmi doesn't have bugs XD )
so I did a hard reset and the problem is still there. It took about 6 minutes for the heart rate to settle to the real rate
the fact that both you and Yerk have the same problem makes me think it is a firmware problem, do you have the normal 7 or the pro?
I have a fenix 7s pro.
20.22
Fenix 7x sapphire solar
How do you know your wrist reading is correct? Have you compared it to your chest strap reading?
try to install, from connectIQ the app aux. heart rate, which allows you to control simultaneously (put a data page with 2 data fields with above wrist frequency and below the app aux heart rate that will detect the chest band, but do not enable it in the settings otherwise it does not find the app) the 2 frequencies, I used it a lot to control the speed of Elevate 5
Mine seems fine besides maybe some questionably low readings for the first 8 or so minutes. Im not entirely sure if that's me just warming up though.
Have you tried strapping your watch down correctly? It's not jiggling or slipping around?
As far as I understand this bug (I have it too on Fenix 7s SS) - firmware goes nuts when HR changes rapidly, like during interval training. I assume, Garmin tried to implement some kind of heuristic algorithm and it does work in, say, 75% cases, but in other 25% - it messes everything up.
So, on old FW versions there was common optical sensor lag, but it did eventually catch up to HR change, in 5-10 seconds or so. Now however, it tries to "predict" rapid HR change to eliminate this lag, but sometimes guesses wrong - and there is no fallback mechanism in the algorithm, that would fix incorrect prediction, so watch recodrs locked HR for a few minutes until some "bump" in HR makes algorithm understand it outputs wrong values.