I have the same on Garmin Chronos v 8.30. The optical heartrate in a RUN activity behaves as if 24/7, I.e. It takes a reading for a few seconds then shows ---. Some time later again a reading etc. this does NOT happen in non-RUN apps (hiking, bike etc). Seems related to the Run app. I reported the issue to Garmin support last Saturday, and also sent it to the Beta-feedback. The behaviour started the first run after 8.30 installed itself.
So we're now supposed to wait through next beta cycle to get a crucial feature back that used to work before. Nice.
Apparently the issue is IQ related too. Oh well, it's getting colder so I'll just use the strap anyways from now on. Hopefully gets fixed until next summer.
So we're now supposed to wait through next beta cycle to get a crucial feature back that used to work before. Nice.
Apparently the issue is IQ related too. Oh well, it's getting colder so I'll just use the strap anyways from now on. Hopefully gets fixed until next summer.
Yes I know that. The point was that if I want to sign up for beta testing it should be to test new features, not to bring old ones back. Especially a crucial feature like this.
Anyway good that there is at least a way to fix it.
The 'beta' adds one fix and no new features. Just because it's named a beta doesn't mean you are signing up for beta testing. If they called it 5.40 release you'd be happy, right?
The 'beta' adds one fix and no new features. Just because it's named a beta doesn't mean you are signing up for beta testing. If they called it 5.40 release you'd be happy, right?
I'm gonna have to disagree with this; I'm with JTH9 here. Good on Garmin for a quick investigation and FW update, but it is a B-E-T-A. No matter if its publicly available or not, the sheer fact that it's a beta indicates it IS NOT the same as full release FW. My take (probably wrong, but my humble opinion)- they hunted down the bug with OHR and fixed a few 1s and 0s to kill said bug, BUT they aren't sure what else they may have messed with in changing those 1s and 0s. So, instead of sending it out as 5.4 as you state (which would indicate they are fully confident of its stability) they dropped it as a quick release beta.
I agree with the premise that if its that big a deal you CAN download the beta, but again, you're downloading a beta. It even says on their updates and downloads page Although this software is believed to be reliable, it has not yet been released for production and should be used at your own risk". Yeah, a disclaimer but the truth none-the-less.
OHR is a big deal for me too as I upgraded from my F3 to the F5 not only for the size but also for the OHR (so I could get rid of my Mio Link, despite the fact it is a better OHR tracker based on algorithm, in my opinion- I have no interest in a strap). But after weighing the pros and cons, I'm gonna run with my Mio Link paired to the F5 (like when I had my F3) until the next production FW comes around. The watch thinks it is a strap and it replaces my OHR readings. It was either this, delete my Connect IQ apps from the watch (no thanks), or download the beta with the possibility of other unknown issues (no thanks again).
Now, if in a week there aren't a ton of people screaming about the beta breaking this or breaking that, I may consider grabbing it up, but for now I'll stay with the current FW (btw- the fact that the current production FW is buggy doesn't give me great confidence that the beta will be MORE stable).
Then again, I'm usually wrong (or so the wife says). ;)
I think the beta label is only there because they released it quickly and didn't do there normal amount of testing. Beta also give them a get-out if something else comes up but as you say, from the reports it seems to fix the issue so if anyone has OHR issues then I suggest loading it (or just use a strap, MIo Link etc)
