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

5s plus ANT+ connectivity drop outs

Hi folks,

does anyone beside me see massive drop outs for HRM run and especially foot pods? I own a Stryd and it works perfectly with an FR935 but an my 5s plus I see drop outs over drop outs (in my last 18k run approx. 30 drops!!).

Am I alone? Or is that issue known and beeing investigated already?

0 Agepi7o over 7 years ago

Hi there. I’m having The same issues with my F5+ and HMRun-tri. When you say that turned bluetooth off , you meant of the iPhone, didn’t you?

Thanks.

0 bjoern.schulte over 7 years ago

I opened the WIDGET "circle" and disconnected the phone (which in my case is an iPhone) - on the phone itself I left bluetooth on, because I listened to a book over bluetooth a headset.

0 bjoern.schulte over 7 years ago

Just completed another run. This time with the Fenix 5s plus only (no FR935 as reference - forgot to take it with me :-) ). Same seeting as yesterday: bluetooth connection to iphone switched of on the watch (by widget).
Result: Again a perfect recording! No drop outs at all - everything 100% perfect. Happy me!! ;-)

0 bjoern.schulte over 7 years ago

bjoern.schulte good to hear you are enjoying the Fenix 5s plus

some speculation...

did you in the time between activities, by any chance, power down(restart) the watch ?

there is a very recent discovered bluetooth bug that could be the cause of yours and others sensor drop

this specific fault can only be remedied by turning off-on the Garmin device and is going to need a firmware update

I am waiting for a reply from a CIQ mod, if this fault could be the cause for these drops
...

Hmmm, don‘t remember. That bug you mention is acknowledged by Garmin? The discussions I followed about connectivity issues mainly complain about lost connections in watch mode, if I remember right.

I think I‘ll stick to disconnecting from the phone during runs as long as there is a firmware update addressing this issue.