HR/ANT+ dropouts may be fixed with Sensor Version 5.8

I.e. my point - these resets are happening all the time - it just plenty of users do not notice them - since there is conscious efforts to hide them in firmware.

I have the same impression. Since 3.40 and 3.50 were introduced the oHR is behaving as if it is forced to measure all the time by applying an unknown pattern. This causes false measurements during activity, higher rates in rest, recording of 255 when the oHR is switched off, higher battery consumption and I don't know what else. For me it is obvious that they tried to solve the issue of this topic and they created numerous others that did not exist before.

My onboard HR crashes every single activity, does my head in, I'm waiting for John Lewis to stock the new VA3M and swap it, (though there is no indication the hardware is any different in the new model)

While I really want to believe that there is software/firmware fix for these dropouts - the more I read about it and observe my own unit - the more I feel that it is hardware problems - watch goes through proper hard-reset. Yes, firmware already trying to mask HR reset by setting it not to 0, but 80 (or something around that number) and that will mask drops/resets while you are walking around - they are clearly evident during exercise with elevated heart rate. Same could (or I would say should) be applied to GPS precision, altimeter etc.

I.e. my point - these resets are happening all the time - it just plenty of users do not notice them - since there is conscious efforts to hide them in firmware.

Curious, how do you know this. Do you have inside information?

Curious, how do you know this. Do you have inside information?

Indeed, I should have been clear here - those are all my own speculations/observations. And yes - I really like device (well concept) - good, minimalistic look (I would prefer buttons too, and Garmin has the answer - 645 and the others, but for daily driver - looks are important), really good support for sensors (again in concept) and plenty of features at the okay price.

And yet again - in concept, since it counts floors - so-so (I do not really mind it), MoveIQ - I turned off long time ago (while I want it - can live without it too), sleep tracking - only within specified hours (and again I am okay with that), HR broadcast - does not work with my head unit (I am not okay with that, but as we know watch has bigger problems to deal with HR).

Oh well, looks like my love (of the concept) speech turned into complain one :-)

So all we have left - sit tight and hope all those problems are solvable in firmware.

Any updates on the timeline for a permanent resolution?

I've been told that they expect to have the update rolled out within 2-4 weeks from now. Whether it will actually fix everyone's issues...

I was hoping for Garmin-Blake to give us some better time line. Its been a week since he stated - "timeline for a permanent resolution very soon".

Its probably next week, month or next year... who knows

I was hoping for Garmin-Blake to give us some better time line. Its been a week since he stated - "timeline for a permanent resolution very soon".

You can always pickup the phone and call them--as I did just yesterday--but you're not going to get a better answer than the one I just gave you. They're in the test-phase of the potential fix, with an expected release between the end of the month and early-ish-June.

My apologies for the radio silence but this is due to us still not having a firm release date to share. I truly understand the frustration this issue is causing and can confirm that this has been given a very high priority. The information provided here has aided us in investigating this, and it has unfortunately taken quite a while to lock down multiple causes and problematic scenarios. Thank you for your continued patience.

I purchased my Vivoactive 3 and sensors in March. I really wish I had found this forum first and found out about this problem ahead of time. It would have changed my purchasing this decision.

If the next firmware fix does not resolve the issue, Garmin management needs to seriously consider the DAMAGE that this issue is doing to the Garmin brand and find an appropriate solution for Garmin customers that are experiencing this issue.

After this experience, I am uncertain if I will ever purchase a Garmin product again. (This watch and sensors were my first Garmin purchase)

Thanks to Garmin-Blake for communicating what he can on this issue.