Fēnix 5S/5 – 3.22 Beta Release

Updated to the latest beta and had 0 drop outs using HRM RUN4 on running dynamics data and HR data. Arms down the side was fine only when I put my arm round my back did it lose the connection.

That sounds promising. I'd like to think it would still be able to work with my arm behind my back though, it's not like I'm wolverine and made from metal.

That sounds promising. I'd like to think it would still be able to work with my arm behind my back though, it's not like I'm wolverine and made from metal.

But you're made from very lossy flesh which is similarly bad for those microwaves...:)

Thanks for the reply. Is that with an f5, 5s or 5x? Has the connectivity improved with one of the firmware updates? My understanding is that even on 2.90 dropouts are frequent.

The Fenix 5. The range of the BT isn't any larger, but much more stable. The Stryd didn't drop off once during my run. The only thing the beta team needs to do is extend the range.

Bluetooth and ANT+ Distance Tests

I got a bit curious about the distance an f5 (Not f5X. Not f5s.) could keep a Bluetooth or ANT+ connection and ran some informal tests.

First up, fenix 5 Bluetooth to iPhone 6S+.

• Garmin Connect Mobile was left open on the iPhone
  
• fenix 5 using watch face "Digic", configured with phone status indicator
  
• iPhone was placed in an area at home with line of sight of around 36 feet
  

I kept taking steps away from the iPhone, with f5 on my wrist until the phone status indicator switched to "off". I then went forward 1 foot and waited approximately 1 minute and the status went back to "on".

Result

• Bluetooth between fenix 5 and iPhone 6S+: 35 feet
  

Same test as above, but with Scosche Rhythm+ (fw v2.62) as the stationary item.

• No previous external sensors paired; list is clean
  
• Paired Rhythm+ with f5 as ANT+ first
  
• Removed ANT pairing
  
• Paired Rhythm+ with f5 as Bluetooth
  

As above, I kept taking steps back, but this time I watched the pairing status for the Rhythm+ go from "Connected" to "Disconnected". Once it disconnected, I went forward a foot at a time, while waiting around 30 seconds for the connection status to change.

Result

• ANT+ between Rhythm+ and fenix 5: 14 feet
  
• Bluetooth between Rhythm+ and fenix 5: 19 feet
  

The Fenix 5. The range of the BT isn't any larger, but much more stable. The Stryd didn't drop off once during my run. The only thing the beta team needs to do is extend the range.

Has it just improved with this beta then? Were you still getting dropouts on the previous version?

I got a bit curious about the distance an f5 (Not f5X. Not f5s.) could keep a Bluetooth or ANT+ connection and ran some informal tests.

First up, fenix 5 Bluetooth to iPhone 6S+.

• Garmin Connect Mobile was left open on the iPhone
  
• fenix 5 using watch face "Digic", configured with phone status indicator
  
• iPhone was placed in an area at home with line of sight of around 36 feet
  

I kept taking steps away from the iPhone, with f5 on my wrist until the phone status indicator switched to "off". I then went forward 1 foot and waited approximately 1 minute and the status went back to "on".

Result

• Bluetooth between fenix 5 and iPhone 6S+: 35 feet
  

Same test as above, but with Scosche Rhythm+ (fw v2.62) as the stationary item.

• No previous external sensors paired; list is clean
  
• Paired Rhythm+ with f5 as ANT+ first
  
• Removed ANT pairing
  
• Paired Rhythm+ with f5 as Bluetooth
  

As above, I kept taking steps back, but this time I watched the pairing status for the Rhythm+ go from "Connected" to "Disconnected". Once it disconnected, I went forward a foot at a time, while waiting around 30 seconds for the connection status to change.

Result

• ANT+ between Rhythm+ and fenix 5: 14 feet
  
• Bluetooth between Rhythm+ and fenix 5: 19 feet
  

I concur, line of sight connectivity is good. I'm sure that you've seen me posting about Running Dynamics data dropouts, as soon as I put a bit of flesh in the way of that line of sight things seem to go wrong. Maybe my old Fenix 3 hr would have done the same, unfortunately I never tested it. Maybe the 935 would be the same but again I don't know. All I do know is that I've had to Fenix 5's that do it and to me I don't believe they should. I've also seen posts from around four or so people having the same issue (if it is one).

Has it just improved with this beta then? Were you still getting dropouts on the previous version?

Yes, I thought that was stated. Since 2.72 the BT stability has been bunk. Now it barely drops off, but the range is tiny. I'm taking the range someone posted with a grain of salt. Try around 10ft from my watch before the watch drops.

snip...

I'm taking the range someone posted with a grain of salt. Try around 10ft from my watch before the watch drops.

Not sure if that was directed at my testing and results. If so, keep in mind the results I found were from specific devices that you may not have, thus results would be different. I'd expect an iPhone to have significantly more transmit power than a foot pod/HR belt/etc... The Rhythm+, again something you may not have, allowed me to check out one device since it has both BTLE and ANT+.

Regardless, this dropping thing sucks. My Spartan Ultra hasn't dropped signal from neither the Rhythm+ nor the Stryd, not even once. Rock freaking solid. Did Garmin not test this stuff?!

I'm sorry, I didn't mean that to come off as rude, apologies if it did. In my watches experience going that far means it's dropping. If that's the case and you're getting further range before it drops, then wouldn't that mean it's a physical problem with the BT radio? I hope not, because I am really satisfied with the actual watch I currently own. I had a ton of issues with the F3HR I had, returned the F5X I intially bought (you want to talk sensor problems? It had ALL of the problems!) This watch, nearly perfect...other than the BT issues (range). But sincerely, I didn't have a single issue with the Stryd during my run the other day.

Was it an anomaly? Maybe, i'm heading out again tomorrow for another run, i'll report here if I get any dropouts.

Hey are you looking at your data on the web version of Garmin Connect or on your phone? On my phone, dropouts are not so obvious but on the web version you can see big gaps on power, pace etc.