Fenix 5/5S - 5.84 Beta Release

Hello Fenix 5S/5 users,

We have new beta software ready for your upcoming adventures!

Please read the 'notes' and 'installation instructions' in the 'Updates and Downloads' page found in the link below. We look forward to your feedback.

Fenix 5S: http://www8.garmin.com/support/downl...s.jsp?id=11661
Fenix 5: http://www8.garmin.com/support/downl...s.jsp?id=11663

Please send all bug reports to [EMAIL="[email protected]"][email protected][/EMAIL], and indicate which model of the fēnix 5 series you have in the subject line.

Note: Please allow for the updates to propagate across all servers. There is no need to post that the link does not work. It will after a bit of patience.

5.84 Change Log Notes:
  • Improved the connection reliability of ANT sensors during activities.
*Strength workouts are still not available via Garmin Connect. Only the capability to accept these workouts has been added. This feature will be available in the very near future
  • ANT fix doesn't work for me. See graph. Run Fenix 5 WIFI with scosche rhythm+ heart rate sensor. First half-run on right arm (opposite to watch) second half-run on left arm (same as watch).
    Disappointing result :(


    We musn't lose sight of the fact the ANT uses 2.4GHz to communicate. That means it either needs line of sight, or something for the signal to bounce off in order for two devices to communicate. If the watch is on the left side of the body and the device is on the right, chances are very good that it's not going to work properly as 2.4GHz isn't very good at propagating through the human body.
  • Former Member
    0 Former Member over 7 years ago
    ANT fix doesn't work for me. See graph. Run Fenix 5 WIFI with scosche rhythm+ heart rate sensor. First half-run on right arm (opposite to watch) second half-run on left arm (same as watch).


    Couldn't get any good results with left arm watch and right arm Scosche regardless of device. That never worked. Not with my 910xt, Fenix3, Fenix3HR, Fenix 5, 935. You always need to wear it on the same side. Nothing to do with the ANT dropouts. BTW, are you sure that your Scosche is connected as ANT-device and not as BT? Because mine always connects first via Bluetooth...
  • I agree with ferbpen, and to that list I would add the Suunto Ambit 2 (which uses ANT+, not BT). I ran a race wearing an FR 620 and the Scosche on my right arm, and the Ambit 2 on my left arm, running an app to help with pacing. The heart rate track was great on the 620 and dropout city on the Ambit. I don't think it means anything in terms of the fix.
  • We musn't lose sight of the fact the ANT uses 2.4GHz to communicate. That means it either needs line of sight, or something for the signal to bounce off in order for two devices to communicate. If the watch is on the left side of the body and the device is on the right, chances are very good that it's not going to work properly as 2.4GHz isn't very good at propagating through the human body.


    Sure. But it works with my Fenix 3 for two years without any, I really mean any, any dropout. I expect a follow-up model be at least as good, as the older type.
    By the way, I delete the BT sensor connection and make sure it connect over ANT+
  • Confirmed bugs:

    - Control Menu Items (Holding the light Buttom) goes away after each sync


    Holy cow. Just came back from a run. Saw that the watch isn?t connected to the phone, pressed the light button and all control items are gone (except flash light). ....Garmin what the heck are you doing???

    Is there a way to get the menu items back??

    Edit: last question is solved. Saw that I can add them manually.
  • ....Garmin what the heck are you doing???


    I think a lot of people keep forgetting that you are putting beta software on your device! If the bugs happens to be in the production software as well, by all means, rant about them.. but for beta software there is only need for bug tracking and telling them politely :)
  • Have you read above? It's not firmware related...or at least it not seems to be.

    And: I have written dozen of emails concerning wrong ascent/descent (including links to all fit files and excel sheet), concerning Garmin segments kills a third party MTB app. The developer of the app has written too including a link for a solution that already exists for an other device. This bug is known for months. And have I got answers? Is there a communication?

    ....sometimes it is hard to stay polite.
  • I just came back from a 1hr+ run with both my HRM-Run and my Stryd, and after analyzing the resulting FIT file I have not found any improvements on the Stryd connection reliability. The dropout rate is in the same numbers as it was with v5.40 (2-3% of the total records for speed source coming from the GPS instead of the footpod, 1-sec recording enabled).
    It might have improved compared to the previous beta (5.83) where I had a gazillon dropouts from my HRM-Run (the Running Dynamics data) vs this run which was dropout free, but definitely not any visible difference from the latest prod firmware.
    I don't even get disappointed anymore when Garmin does not deliver...
  • I hope soon will better works on the production version , because disconnect with mobile phones is annoying at night during deep sleep.
  • Couldn't get any good results with left arm watch and right arm Scosche regardless of device. That never worked. Not with my 910xt, Fenix3, Fenix3HR, Fenix 5, 935. You always need to wear it on the same side. Nothing to do with the ANT dropouts. BTW, are you sure that your Scosche is connected as ANT-device and not as BT? Because mine always connects first via Bluetooth...
    I have zero problems with Rhythm+ (right arm, above bicep) > Spartan Ultra (left wrist), nor with Rhythm+ > 5X in the same placement. That's testing both ANT+ and Bluetooth, both of which operate in the 2.4 GHz spectrum. Before those, it was the same placement with an Ambit3 Peak Sapphire; no problems.

    When I had a fenix 5 (three, in fact), I tested the distance I could walk before the Rhythm+ would drop connection, in open air / line of sight, and it was right at 14 feet with ANT+. Bluetooth was around 17 feet. With the 5X, it's more than 30 feet, and through two walls. The 5s and 5 have a seriously bugged ANT+ and Bluetooth implementation.