Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

OHR garbage after 18.22/23 - how long we have to wait for a fix?

5258636
over 1 year ago

I can't express fully my frustration with garmin attitude towards customers. A release was sent out with lots of complaints on OHR. 

The last two official updates turned my FR955 solar in a useless paper weight. How can we trust any of the numbers shown by the watch when heart rate is garbage?

All of the sudden there is this talk about warm up and OHR. I have the watch for about 2 years now and never seen such garbage numbers as now. Where did this came from?

It is obvious there is a problem with this updates. How long do we have to wait for a fix? Until the end of quarter? Never?

Now garmin tries do down play the issue and promises some investigation will be done. How about this idea: re-release 17.26?

do you care to share an opinion on how long until a fix?

  • 0 over 1 year ago
    5258636 said:
    How about this idea: re-release 17.26?

    Maybe you can give a try to downgrade like expained here. There also you have the 17.24 and 17.26, to install it in that order. It is important to remark that this procedure is at the user's risk, it is not provided by Garmin.
    On my side, 18.23 works well.

  • 0 over 1 year ago in reply to G141592653589793238

    Why would I downgrade my watch with some unverified files from Internet? No thanks.

    It is garmin's job to deliver on their promises. 

    Maybe for you it works but please don't use this statement everywhere as you do. Each user is different with specific needs but I'm sure nothing this watch should not be able to handle if the advertising was/is true.

    Just saying "for me it works" doesn't help anyone. All this threads on 18.22/23 issues might say something. Some of the issues where reported during public beta for these releases but nothing happened. A release was rushed and was quickly followed by a hot-fix.

     I'm still waiting for an answer on my OP and from what I can see I'm not the only one.

  • 0 over 1 year ago in reply to 5258636

    I could use your same argument: please don't ask for something about going back to a previous firmware when Garmin has never done it. There could also be many users with problems, as I've said in other threads, maybe different hardware versions for the same model? I don't know, guesses. Even in the case that there are lots and lots of reports how many are there, 1% of total model sales, maybe, maybe more, I don't know either but what I'm getting at is that this does not mean that the current firmware and innovations are unusable, or the OHR is garbage. I'm happy with the innovations of the latest versions, and yes, I will keep repeating it when someone else asks: "anyone else with this problem?", at least for me it does not be a problem to test it in the next activites and report if it worked for me or not as I have already done. I understand that you're frustrated because something or everything doesn't work for you, but from there to telling me what I should write you're really screwed up. Again, maybe it's different hardware versions, different zones, luck, and that's why the difference in results. I have 4 Garmin devices and have had no major problems with them. One of them is the 955 Solar, I have two friends also with 955 and they have not reported any problems with these either. And one more recommendation, it would be good if you post to be open to receive answers, whether you like them or not, or add a label "hey, only answers on my same line of opinion..."

  • 0 over 1 year ago

    I also raised this topic on the forum. Ultimately, Sierra did not comment on the topic but provided information that it was related to the new function. But which one? It's still unknown :)

    Overall, it seems that my heart rate is accurately displayed (I use a polar h10 strap). However, I am frustrated by how much this affects the battery life of my watch. I consider this a serious mistake.
    All we can do is wait for the 19.xx version which will hopefully fix this "error"?

  • +1 over 1 year ago

    Please see my update on THIS thread regarding the OHR sensor on 18.2X. I am locking this so we can keep the topic organized and so all announcements can be easily seen.