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

Problems with Ant+ connectivity

Does anybody NOT have problems with third party ANT+ devices and the F5? My experience is as follows:
- Stryd: not usable; tons of drop-outs on runs. Most importantly long pauses of 30-60s with zero values
- Powertap P1 pedals: around 10-20 drop-outs on a 50 mile ride; most of these drops are really short
- Stages: Useless - zero connectivity - tried Bluetooth and ANT+

Wondering if the F5 is just flawed (weak antennas?) or if I got a bad model. Spoke to Garmin support two weeks ago and they asked me to wait for further software updates.

Are there people out there that do not have these kind of problems?
  • Hi,

    A couple days ago I contacted Garmin support stating I had ANT+ connectivity issues that were not solved by resetting the unit and I wanted a replacement one and their response was that I could open a RMA request, which I did, and they accepted.
    All this without even trying to give me additional troubleshot instructions, which made me think Garmin is aware at least some units have issues and they are replacing them without further questions. When I specifically asked if there were anything I could try to solve it their answer was "At this time the unit will simply need to be replaced".

    Now... As I was writing this I received another email, stating Garmin is in the process of solving connectivity issues with a software update ant it was likely my replacement unit would have the exact same issues. They asked me to hold for a while to avoid sending the watch to them and to send (if I wanted to help) the contents of the Garmin folder for their engineers to take a look at.

    So, bottom line, they seem to acknowledge there are connectivity issues and seem confident they will be able to solve it with a software update.

    I'll just send them my Garmin folder and try to keep in touch to see if this makes progress, still annoyed I spent an awful lot of money for a watch that doesn't work.
  • I have Fenix 5 sapphire (currently using FR935) and just for curiosity I tried to look at my old activities and I have to say that I didn't had any dropouts (nothing that I found)
    Now I'm using FR935 so I don't know if anything changed in the firmware since may.
  • I can confirm, that when I put my arm with the watch to my back, it looses connection to sensors. HR and power meter. Still however, cannot find a good reason why to do it during training. Therefore I don't have any comparison to my previous 920XT, as probably never did it. Maybe someone with 935 can check this out?
  • DCRainmaker has posted an update on the ANT+ issue, including Garmin's response. https://www.dcrainmaker.com/2017/03/...ml#bugs-quirks

    tl;dr - Don't expect a fix.

    If I'm reading between the lines correctly, it seems they acknowledge an issue, but point the finger at third-party devices (Stryd) for being inconsistent? "We do anticipate future designs to improve support for identified third-party devices that are not consistently meeting expectations today.?

    What a joke.. class action lawsuit anyone?
  • Former Member
    0 Former Member over 8 years ago
    The reply to DC rainmaker is a joke. The problem is not just focused around 3rd party sensors. I have dropouts using Garmins own foot pod and I'm also loosing pulse readings when i stretch my arm. I can easily provoke pulse dropouts just by taking letting my arm with my watch on, down by my side or behind my back. And that is with the bulk blue Garmin triathlon pulse belt.
  • Do you have any examples where you experienced a Garmin Footpod dropout? I wouldn't mind comparing yours with mine.
  • "We do anticipate future designs to improve support for identified third-party devices that are not consistently meeting expectations today."


    Yeah, blame third-party devices which, by the way, do work flawlessly with other Garmin models (Stryd works with F5X, F935, F735XT with no issues). IMO, Garmin is the one "not consistently meeting expectations today"

  • To be clear on that quote, Garmin is taking responsibility there - they aren't blaming Stryd. I think it's just a comma placement/wording issue that's confusing.
  • I stand corrected then, thanks for the clarification
  • Still the answer from Garmin is not one that inspires confidence that they will take care of their existing customers. I understand that 3rd party integration testing is really difficult as there are just so many potential combinations, but Garmin should be better and this situation highlights some test gaps in their internal process. I am a little surprised that they don't work more closely with some of the 3rd party vendors for early testing.