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?
  • Have you tried 3.30 yet? If I remember correctly you had/have what seems to be the exact same problem as me.


    I am waiting for a replacement Fenix 5 and should be able to test later this week.
  • Former Member
    0 Former Member over 8 years ago
    I am waiting for a replacement Fenix 5 and should be able to test later this week.


    Fingers crossed for you. I've had two f5's and both have behaved exactly the same in regard to the Running Dynamics drops. Hopefully it's a software update to fix it.
  • Former Member
    0 Former Member over 8 years ago
    Sorted, I think

    Looks like 3.30 has sorted my Running Dynamics dropouts. Can post some before and after screen grabs if people want to see. Looks like my f5 won't be getting replaced by a 935 :) .. unless it doesn't play well with my Stryd when it shows up.
  • Former Member
    0 Former Member over 8 years ago
    cambridge resort

    I would't regard the issue as resolved until you've had at least five typical workouts without any dropouts. For each of the last betas I was happy to finally see the issue "resolved" until it reappeared on the next run. Do fast and slow workouts (different extent of wrist movements relative to chest!) and see if it is consistently resolved. I got a 935 now and will be doing some comparisons next week.
  • Former Member
    0 Former Member over 8 years ago
    I would't regard the issue as resolved until you've had at least five typical workouts without any dropouts. For each of the last betas I was happy to finally see the issue "resolved" until it reappeared on the next run. Do fast and slow workouts (different extent of wrist movements relative to chest!) and see if it is consistently resolved. I got a 935 now and will be doing some comparisons next week.


    Two runs in and so far so good. I've always been able to reproduce the issue by dropping my arm whilst running and having tried that on two separate runs now all is looking good so far. Fingers crossed anyway.
  • Former Member
    0 Former Member over 8 years ago
    Since 3.30 the connection to my hrm-run seems a lot better. I do lose connection if I put a lot of flesh between my watch and the sensor, for example by putting my watch arm up behind my back. Looking on the 935 forums this is the same for those guys though so isn't a Fenix 5 specific thing.
  • Former Member
    0 Former Member over 8 years ago
    Zero Improvement

    First run after the 3.3 update: Zero improvement. Actually one of the worst runs so far. There are various long drop-outs (50+ seconds) with my Stryd. Same thing with a bike ride and my powermeter. This is so frustrating. A USD 600 watch and basic functionality is nowhere near a working state.
  • Former Member
    0 Former Member over 8 years ago
    First run after the 3.3 update: Zero improvement. Actually one of the worst runs so far. There are various long drop-outs (50+ seconds) with my Stryd. Same thing with a bike ride and my powermeter. This is so frustrating. A USD 600 watch and basic functionality is nowhere near a working state.


    Have you raised this with Garmin support yet? Have you got a Garmin hrm that you can test with? Personally I don't have a Stryd, yet, but my hrm-run connection now seems stable.
  • I got an answer from garmin support (google translate from polish, I am to lazy to do it manually) :)

    At the moment, we had several similar tickets. The problem is currently being investigated by developers and all efforts are being made to remove connection problems that occur in some configurations.

    At the moment, nothing else than waiting for new software updates. Unfortunately, I am not able to give you the exact date when it will be published. Fenix 5 is a new watch so updates are coming quickly.

    I apologize for any inconvenience.
  • For the record. Stil get drops in heartrate. Version 3.30, sensor: Scosche Rhythm+ (See Graph)