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

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

2.95 Change Log Notes:
  • Added support for Connect IQ SDK 2.3.
  • Added support for managing automatic software updates (Settings > System > Software Update > Auto Update). Setting Auto Update to “Off” will disable downloads of software updates using Garmin Connect Mobile and Wi-Fi.
  • Added support for managing unit settings for pressure, altimeter and temperature from corresponding widget settings menu.
  • Improved altimeter calibration for activities that were paused for extended periods of time.
  • Improved the layout of the alarm page.
  • Improved the activity settings menu by hiding GPS specific settings when GPS is turned off.
  • Improved the reliability of Livetrack.
  • Updated the summary view to include average Pace data for a pool swim activity.
  • Fixed a potential issue where the currently selected watchface may change after a software update.
  • Fixed an issue where the device could crash when applying a FaceIt watchface from the Garmin Connect Mobile App.
  • Fixed an issue where the ‘Uninstall’ option on the Garmin Connect Mobile App would not work as intended.
  • Fixed an issue, where the option to “Copy Activity” was present in the main menu for non-copyable apps like Golf.
  • Fixed an issue, where the unit would crash when creating a custom alert for a new ‘Other’ app.
  • Fixed an issue, where the virtual partner fields, ‘Time Ahead’ and ‘Time Behind’ won’t update during an activity.
  • Fixed an issue, where an empty elevation plot was being displayed during activity review for apps like, ‘Rowing’, which doesn’t record elevation data.
  • Fixed an issue, where alarms deleted on the Garmin Connect Mobile App would not reflect correctly on the device.
  • Fixed an issue, where the user would not get alert popups during a Lactate Threshold or FTP guided workout.
  • Fixed an issue, where GPS could become enabled for indoor profiles after performing an altimeter calibration.
  • Fixed an issue, where the device was calculating VO2 max for activities using Ultratrac.
  • Fixed an issue, where the ‘Do Not Disturb’ window was not updated when travelling across time zone boundaries.
  • Fixed an issue, where the user could not send tracks or waypoints to the device from Basecamp.

Send all bug reports to [email][email protected][/email]
  • The alarm is working for me now having done the above.


    Tried all of this, but alarms are still getting overwritten. Interestingly it's not always the first sync the wipes the alarm set on the watch, but only when a sync is followed by the 'Updating' screen on the watch. My suspicion is that the few of you who are having success with this have not had anything change on the Garmin Connect side that needs 'pushing' to the watch ('User Settings' is the usual thing that shows queued up when on the Garmin Connect website, but equally could be an update to a CIQ app). It seems that all device setting (including alarms) are pushed to the watch and overwrite what has been set manually on the watch.

    Added to all this, the 2.95 beta changelog notes just mention making sure the alarm settings in GC get pushed to the device correctly, not that GC should respect alarms set on the watch by the user (let alone a proper sync where the alarms set on the watch by the user are written back to GC if they are more current).
  • Former Member
    0 Former Member over 8 years ago
    roma ALAMOS

    Tried all of this, but alarms are still getting overwritten. Interestingly it's not always the first sync the wipes the alarm set on the watch, but only when a sync is followed by the 'Updating' screen on the watch. My suspicion is that the few of you who are having success with this have not had anything change on the Garmin Connect side that needs 'pushing' to the watch ('User Settings' is the usual thing that shows queued up when on the Garmin Connect website, but equally could be an update to a CIQ app). It seems that all device setting (including alarms) are pushed to the watch and overwrite what has been set manually on the watch.

    Added to all this, the 2.95 beta changelog notes just mention making sure the alarm settings in GC get pushed to the device correctly, not that GC should respect alarms set on the watch by the user (let alone a proper sync where the alarms set on the watch by the user are written back to GC if they are more current).


    I know this doesn't solve an annoying issue but, is it not easier to set the alarm on GC rather than the watch? Which I assume will not get messed up during syncing/updating?
  • It might also have something to do with where the alarm was created. When I first noticed the issue I deleted the alarms I made on the watch and re-created all my alarms on GCM. I'm personally not bothered. I find it easier to adjust alarms on the phone then on the watch.
  • Former Member
    0 Former Member over 8 years ago
    Any fixes for a Stryd footpod dropouts?
  • Any fixes for a Stryd footpod dropouts?
    Bluetooth or ANT+?
  • Former Member
    0 Former Member over 8 years ago
    Ant+ / bt

    I was REALLY hoping to see ANT+ or BT fixes on that list.

    My powertap C1 power meter won't stay connected, whereas it has zero issues on the 520, 920xt, etc.
  • I was REALLY hoping to see ANT+ or BT fixes on that list.

    My powertap C1 power meter won't stay connected, whereas it has zero issues on the 520, 920xt, etc.


    If this is due to hardware problems than I am afraid it is nothing to be done, weaker antennas and end of story... but I do hope it is a matter of software...
  • Former Member
    0 Former Member over 8 years ago
    Ascent tracking

    Anyone else noting a lack of ascent tracking with this update? I did a ton of stair work Sunday and my watch noted "0" flights which is not possible. I even did a hard reset and it's not tracking them.
  • Bluetooth sensors

    I was REALLY hoping to see ANT+ or BT fixes on that list.

    My powertap C1 power meter won't stay connected, whereas it has zero issues on the 520, 920xt, etc.

    When I got my Fenix 5 with software 2.40 I paired my Stages Power meter via Bluetooth which worked quite well. In the meantime I'm on Beta 2.95. The first week on Beta 2.95 the sensor still worked almost flawlessly. However since a few days I had problems to connect with the sensor and I removed the sensor from the watch and tried to pair it again. Now the only option I get is to pair the sensor via ANT+ which leads to unacceptable continuous drop outs. The connection via Bluetooth is not offered anymore. Is there a specific procedure or trick to add sensors via Bluetooth? Maybe Bluetooth pairing is a problem with Beta 2.95. Did anybody add Bluetooth sensors with Beta 2.95? Thanks for your comments.
  • Former Member
    0 Former Member over 8 years ago
    VO2 and Lactate threshold do not calculate when using the Trail Run activity.