Problems with Ant+ connectivity

I've had no issues with either my Garmin HRM-Run4 strap or my Wahoo TICKR strap connected via Ant+ but I have to say the comments here have scared me off buying a Stryd for the time being.

I made a 2h bike ride and I can see 2 dropouts (1 min and 30s) of my bepro power meter. I can also see a single dropout of my Garmin HR belt. I am on 2.90

Same issues for me with the HRM Run 4 and the Fenix 5 non sapphire. The connection is fine while you are running with your watch in close proximity to the chest strap, but as soon as you put some meat inbetween the sensor and the watch it loses the connection, which is what happens when I do interval training and walk for a bit. My arms drop down by my side and the connection starts dropping out. Very annoying for me because the whole reason I bought the chest strap was for interval training because the OHR couldnt keep up with the rapid HR changes.

I'd expect more from a £500 watch.

Same issues for me with the HRM Run 4 and the Fenix 5 non sapphire. The connection is fine while you are running with your watch in close proximity to the chest strap, but as soon as you put some meat inbetween the sensor and the watch it loses the connection, which is what happens when I do interval training and walk for a bit. My arms drop down by my side and the connection starts dropping out. Very annoying for me because the whole reason I bought the chest strap was for interval training because the OHR couldnt keep up with the rapid HR changes.

I'd expect more from a £500 watch.

I'm on my second f5 and I can confirm that this one is the same as my previous and yours. I went for a normal run today and it was fine. Like you I sometimes drop my arm on intervals and that's when I get the dropouts. I've contacted Garmin about it all. At the moment I'm thinking of keeping the f5 rather than switch to something like the 935. Either Garmin will sort the issue with a firmware update or it's a design flaw and I'll just have to live it, which I think I can.

I think it is important to make Garmin aware of the issue. We must make them aware that many of us are experiencing the problem with a range of ANT sensors. Stryd has removed the 5/5S from their supported devices list due to the poor signal reception (technically it does receive a signal like the 5x and 935 that are listed and supported). My first interaction with Garmin support was a mess - they denied any issue and tried to blame me but a second email complaint yielded the following:

"We are working toward determining a cause for why some are experiencing this, but many are not. While I do not have an estimated time of resolution, I have added your information to our case investigation. Once there is a solution, you will be contacted via email."

Please don't rely on those of us that have complained to Garmin but also submit your own complaint and support request. At the very least it means that you will be contacted directly by Garmin if/when there is a solution (although I suspect it is a hardware design flaw that will require replacement with an improved design).

I think it is important to make Garmin aware of the issue. We must make them aware that many of us are experiencing the problem with a range of ANT sensors. Stryd has removed the 5/5S from their supported devices list due to the poor signal reception (technically it does receive a signal like the 5x and 935 that are listed and supported). My first interaction with Garmin support was a mess - they denied any issue and tried to blame me but a second email complaint yielded the following:

"We are working toward determining a cause for why some are experiencing this, but many are not. While I do not have an estimated time of resolution, I have added your information to our case investigation. Once there is a solution, you will be contacted via email."

Please don't rely on those of us that have complained to Garmin but also submit your own complaint and support request. At the very least it means that you will be contacted directly by Garmin if/when there is a solution (although I suspect it is a hardware design flaw that will require replacement with an improved design).

Well I've had two f5's with the same issue now; one was a Sapphire from Cotswold and the other a silver from Amazon uk. including yourself I think I've come across at least two or three others on here that are seeing the same issue.

Like you say, we must all submit an issue with Garmin. I've just filed mine this morning.

If I were using a Stryd I think this would be much more of a deal breaker. I spoke with a guy from Stryd last week and he said that they're actively looking into it with Garmin but at the moment the ball is in their court.

I don't believe that Garmin will leave it as a bug. Probably they will improve it in the next FW releases. Or at least I hope so. I send my issue to garmin support. But what is in your opinion the best way to report an issue? I am affraid that if I report it to the polish support, they will suggest factory reset and all that stuff. How to report the issue directly to the developer team?

I don't believe that Garmin will leave it as a bug. Probably they will improve it in the next FW releases. Or at least I hope so. I send my issue to garmin support. But what is in your opinion the best way to report an issue? I am affraid that if I report it to the polish support, they will suggest factory reset and all that stuff. How to report the issue directly to the developer team?

Are you experiencing dropouts too then? I was asked to do a reset the first time I contacted Garmin, which I did but as I expected it didn't fix the issue.

Yes, see post #23. The answer with factory reset was a joke. Garmin support almost always answers "please update FW and perform factory reset" within the first try. I would guess its kinda autoresponder.

Yes, see post #23. The answer with factory reset was a joke. Garmin support almost always answers "please update FW and perform factory reset" within the first try. I would guess its kinda autoresponder.

Because I tried it last time I think this time I'll just say that I've done it :)