Problems with Ant+ connectivity

Hi again.

As i said in the post above, i contacted Garmin support Norway. It ended up with me sending my watch in for service. What they did with the watch i dont know, the shipped a new watch to me as soon as they recived my old.
The new watch was a complete different watch in therms og bluetooth and ANT+ connectivety. I could leave my phone in the house and go in the backyard and still be conncted.
And my HRM tri never had any dropouts during any activities.

After 2 weeks i sold my "new" F5 an bought a F5 plus.
The connectivety is very good with my 5 plus.

How are people finding their RMA replacements?

I had owned an earlier F5, and returned it due to the issues. When I found out from Garmin that they'd resolved the problems, I bought a new one, which was of the newer 'fixed' serial, etc, but the problem was still there. In particular during a cycling activity, you look at the watch for numbers, and the output just shows zeros., and takes about 20-30sec to recover.

Watch #2 returned as a result.

Hi again!

A few weeks ago Garmin swapped me my fenix 5 sapphire for a new one (not a refurbished one i thougth, because it comes in a new box) but the problems are the same... bad ant+ connection, bad altimeter readings (30-40% difference between it and edge 820) and poor bluetooth range (tested with multiple android devices and iphone). I was tired of that and requested a swap for a fenix 5 plus paying the difference between them. They said to send my fenix 5.

My surprise was that they have sent me anothe fenix 5 sapphire NON plus. I didn't open the box and i'll try to swap it for a fenix 5 plus. I dont mind to pay even 200€ for the swap, but i'm sure i don't want a fenix 5. it is a very expensive and useless watch!

How are people finding their RMA replacements?

I had owned an earlier F5, and returned it due to the issues. When I found out from Garmin that they'd resolved the problems, I bought a new one, which was of the newer 'fixed' serial, etc, but the problem was still there. In particular during a cycling activity, you look at the watch for numbers, and the output just shows zeros., and takes about 20-30sec to recover.

Watch #2 returned as a result.

mine hasn't had a single drop out since it was replaced in March

it now works as I'd expect

mine hasn't had a single drop out since it was replaced in March

it now works as I'd expect

Sounds promising - I'm about to arrange for my sapphire unit to be RMA'd. Have you found both GPS and Ant+ are improved?


Thanks

Hi all,

While I don't yet have an Ant+ device connected, I plan to get one for my bike this fall. I just purchased the regular Fenix 5 from the local L.L. Bean store (paid a little extra), but it was so old it was still on software version 2.0. My concern is I purchased old hardware that exhibits these connectivity issues. So my question would be: What serial numbers are effected by these connectivity issues? What is your serial number? I really don't want to have to go buy a device just to test it out.

FWIW Both Ant+ and Bluetooth share the same antenna in the same frequency band (2.4GHz) and likely have some co-existence issues since they are very different protocols. So if you are having trouble with one, it is likely you will have trouble with the other too.

L.L. Bean has very good return policies, so I may drop in and ask the question of replacing it with new stock. This was the last one they had, and was the display model. I was a little annoyed by that, and that I couldn't get a discount from open box.

Sounds promising - I'm about to arrange for my sapphire unit to be RMA'd. Have you found both GPS and Ant+ are improved?


Thanks

I never had an issue with GPS so it's much the same as it was before

ANT+ and Bluetooth are hugely improved

Hi again,

after connecting my watch to the PC I've seen that the creation date of the folders "DEBUG" and "GPS" are 28 April 2017. Most of the other folders like e.g. "ACTIVITY", "ADJSTMTS", ... are dated 16 May 2017. I've also seen that the date of the SNS_ERR.txt file located inside the "DEBUG" folder is dated 09 May 2017. Can I expect that my watch was build somewhere in April 2017 and tested (and shipped) in May 2017?

For the ones who have a "new" device, can you please check the folder creation dates (and probably the SNS_ERR.txt) of your watch? Maybe this gives an indication. Thanks.

Just had my F5 sapphire replaced for a fixed version, only different being this new one is slate grey with the metal band instead. Does anyone know how to identify the improved versions? Big change in serial number? My new one is 53Cxxxx, old was 53Axxxx?

Thanks