Fēnix 5S/5 – 3.11 Beta Release

WE'VE CLOSED THIS THREAD SINCE WE'VE NOW RELEASED BETA 3.22

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 links below for your specific device. We look forward to your feedback.

Fenix 5S: DO NOT UPDATE YOUR FENIX 5S TO 3.21 BETA UPDATE
Fenix 5:http://www8.garmin.com/support/download_details.jsp?id=11663

Please send all bug reports to [email][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. :)

3.11 Change Log Notes:
  • Added support for hiding the distance to next field, shown by default on the map page while navigating. (Settings > Navigation > Data Screens > Map > Data Field)
  • Added support for viewing navigation data pages on the Head Mounted Display (HMD).
  • Improved the reliability of LiveTrack.
  • Fixed an issue where the unit could crash if one were to remove all data pages for an activity profile.
  • Fixed an issue where invalid golf scorecard files were being uploaded, if one were to pause their golf round before connecting to Express.
  • Fixed an issue where coordinate entry was not working correctly for Russian and Hungarian.
  • Fixed an issue where the Golf app was not available in the app list.

Send all bug reports to [email][email protected][/email]
  • Well then, whoever is in charge of quality control for beta releases isn't in for a good day.

    As for those of us with the F5, the sensor hub update is good. Range for BT from the app to the watch nearly doubled. External sensors connect with zero hiccups (so far).
  • Woohoo, new firmware! And somehow I anticipated this by bringing the cable to work. :)


    I bring my cable with me to work every day for this very reason haha
  • only one cable :confused:

    :) I am paranoid, with one cable at home and one at the office


    I'm paranoid too - but not paranoid enough to pay that sort of price for a second cable!
    Um, even though I bought another HRM Run strap, another quick fit silicone band and the leather band.

    Oh, and another F5 because I really want Silver but it wasn't available till May so I'm currently wearing the Slate Grey model...
  • Fenix 5S users,

    Our apologies for the Fenix 5S 3.21 software. It was not a software build for the Fenix 5 or the Fenix 5X, it was in fact a build for the Fenix 5S that was mistakenly put in the .zip file.

    We are working through a solution now to recover your device. Again, our apologies for the mistake. We did verify the Fenix 5 software is accurate at 3.11, which is what should have been available for the 5S as well.

    We will post the solution here (if possible) and respond to emails that come to our [email][email protected][/email] beta box.


    So I'm hit... I updated before the issue was identified. I hope a fix will be possible. If not - then what?

    Edit: Send an email asking what to do if no if fix? I'll post the reply once the solution is known...
  • Well it's going to be a brave person who is first to install the next beta. Surely it would make sense for the beta team to do the update in the same way we have to and check it all out first!

    In positive news, connect to my phone is much more stable. It would alert me that it was disconnected every time I did an activity (normally 2 or 3 time) Just tested with a 23 mile ride and didn't disconnect once.

    It still doesn't list my HRM-Tri strap in the list of sensors though. It is connected for activities but I can't unpair or repair. Very strange!
  • Oh well, I use the 5S as development devices. Cant sideload apps anymore :-(
  • Former Member
    0 Former Member over 8 years ago
    Any improvement for those using Stryd or other sensors? Has it fixed the Running Dynamics drop out issue?
  • Any improvement for those using Stryd or other sensors? Has it fixed the Running Dynamics drop out issue?


    No improvements for me with this beta. Still having Running Dynamics drops. In addition my VO2max has decreased over the last two weeks from 52 to 44. After almost every run I see a drop.

    Strange thing is, that Stryd always worked fine, without dropouts.
  • Still no improvements in BT range though there is a new HUB.

    Every morning when I take a shower I leave my iphone charging (same spot) and go with the watch in the shower, about 7m distance. With this update the watch disconnect and reconnects in the same spot as with the previous builds. What I could notice is that it takes longer to realise it is not connected, like waiting longer to make sure before showing the message. How can I check that? Scrolled to the weather widget which shows that I am disconnected but the watch has not yet displayed the warning sign.
  • Former Member
    0 Former Member over 8 years ago
    No improvements for me with this beta. Still having Running Dynamics drops. In addition my VO2max has decreased over the last two weeks from 52 to 44. After almost every run I see a drop.

    Strange thing is, that Stryd always worked fine, without dropouts.


    Shame about the running dynamics. Are you using a hrm-run or tri version 4? From what I've read on these forums the guys that have earlier versions don't seem to have any issues.