Fēnix 5S/5 – 4.02 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.FYI, beta updates are not compatible with APAC devices.

Fenix 5S:http://www8.garmin.com/support/download_details.jsp?id=11661
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. :)

4.02 Change Log Notes:
  • Improved the VIRB widget to accurately reflect the settings available on the connected VIRB, which may vary with model.
  • Fixed an issue where the device backlight would not work as expected when Do Not Disturb was enabled.
  • Made various bug fixes and code improvements to improve stability.

Send all bug reports to [email][email protected][/email]
  • Its been a while since we've had a Beta update: 02/06/17

    Does the silence mean that we can expect a significant update which will cure all of our issues or have the Garmin Geeks simply run out of ideas?


    Probably mean a cat or bunny tracking app is on the way :D
  • Probably mean a cat or bunny tracking app is on the way :D

    :cool::cool:
  • They've probably abandoned the beta programme as they don't get nearly as much constructive feedback as they do abuse... :confused:
  • Its been a while since we've had a Beta update: 02/06/17

    Does the silence mean that we can expect a significant update which will cure all of our issues or have the Garmin Geeks simply run out of ideas?


    Well, there was talk of all day stress/HRV tracking via the wrist sensor and rep counting for the strength activity. Here's hoping... :cool:
  • They've probably abandoned the beta programme as they don't get nearly as much constructive feedback as they do abuse... :confused:


    If there was some transparency regarding what was being worked on (even what was recognised as a fault) there would be far less frustration. Sometimes a beta is released like this last one which was a jump to version 4 and is so vague in the description that it's pointless for beta testing. They would get far less "abuse" if they treated their user base with more respect. In addition, it doesn't seem like they care what is written here as there is almost never a response in the thread. The feedback is provided by emailing the team but that brings me to another gripe. When I do email them they often ask questions that I already answered in the email I sent. I don't think it's unreasonable for people to feel vexed especially when simple features don't work after months. In my case my watch won't stay connected to my phone in my pocket when I'm out running.
  • If there was some transparency regarding what was being worked on (even what was recognised as a fault) there would be far less frustration. Sometimes a beta is released like this last one which was a jump to version 4 and is so vague in the description that it's pointless for beta testing. They would get far less "abuse" if they treated their user base with more respect. In addition, it doesn't seem like they care what is written here as there is almost never a response in the thread. The feedback is provided by emailing the team but that brings me to another gripe. When I do email them they often ask questions that I already answered in the email I sent. I don't think it's unreasonable for people to feel vexed especially when simple features don't work after months. In my case my watch won't stay connected to my phone in my pocket when I'm out running.


    You do make some good points, but there are so many user variables that it is not clear cut whether the issue is as a result of user expectations being out of line, or connected phones being dodgy, or a bug. There have been clear cases where a user upgrades his old Android phone and the BT connectivity issue is solved. I have a iPhone 6 and connectivity is around 30m, same as my fenix3 and fenix3 HR.
  • You do make some good points, but there are so many user variables that it is not clear cut whether the issue is as a result of user expectations being out of line, or connected phones being dodgy, or a bug. There have been clear cases where a user upgrades his old Android phone and the BT connectivity issue is solved. I have a iPhone 6 and connectivity is around 30m, same as my fenix3 and fenix3 HR.


    I have an IPhone 5s that worked fine with the fenix 3hr and suunto spartan ultra