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]
  • Is this update any different then 2.95 update for the 935? If not is our change log longer because some of the issues are catch up?

    These are probably only lap paces - per 1 km (Check speed graph!). Instant pace is very erratic. As suggested, one can rely only on average or lap pace, but it would be better to have more frequent accurate feedback. I tried 30 sec average (CIQ) and it's not much better than the instant pace.


    As many people (myself included) have said before. Instant pace is best measured with a footpod on ANY GPS watch. I'm not sure why people continue to beat their heads against a brick wall trying to use GPS for instant pace.
  • As many people (myself included) have said before. Instant pace is best measured with a footpod on ANY GPS watch. I'm not sure why people continue to beat their heads against a brick wall trying to use GPS for instant pace.


    I've never used a footpod before. I might end up buying one (it's an investment in itself), but so far I never had a need for one. FR620 and FR630 were perfectly capable to provide quite an accurate and non-erratic pace reading without a footpod. F5 is much worse in this sense. It would be nice to get it close to the performance of FRs. If not, I'll look into buying a footpod. It's not so much I use an instant pace during the run, but looking back at pace graphs it would be nice to understand why your pace has gone up or down (if I do an interval of sprinting I would like to know in those 1min how my pace looks like; is it consistent, etc.)

    Footpod might be an ultimate solution, but the claim that no GPS watch can be used for pacing is simply not true in my experience.

    My perfect case scenario is to avoid the use of footpods and to have a F5 that preforms close to FRs in pace readings, with which I was perfectly happy. Still, regardless of this, I'll keep my 5s as it's a fantastic watch, overall.
  • Former Member
    0 Former Member over 8 years ago
    Maybe I am a moron, but I dont have these directories below

    Garmin\RemoteSW directory
    Garmin\Text directory

    Am I supposed to create this folder under GARMIN?
  • Former Member
    0 Former Member over 8 years ago
    Maybe I am a moron, but I dont have these directories below

    Garmin\RemoteSW directory
    Garmin\Text directory

    Am I supposed to create this folder under GARMIN?


    You should have those directories on the watch when you plug it in via USB.
  • Former Member
    0 Former Member over 8 years ago
    You should have those directories on the watch when you plug it in via USB.


    Cripes I am damn moron. As soon as I read your response I realized I was looking at the Garmin Software on the PC not the damn watch:mad:! HAHA
  • I've never used a footpod before. I might end up buying one (it's an investment in itself), but so far I never had a need for one. FR620 and FR630 were perfectly capable to provide quite an accurate and non-erratic pace reading without a footpod. F5 is much worse in this sense. It would be nice to get it close to the performance of FRs. If not, I'll look into buying a footpod. It's not so much I use an instant pace during the run, but looking back at pace graphs it would be nice to understand why your pace has gone up or down (if I do an interval of sprinting I would like to know in those 1min how my pace looks like; is it consistent, etc.)

    Footpod might be an ultimate solution, but the claim that no GPS watch can be used for pacing is simply not true in my experience.

    My perfect case scenario is to avoid the use of footpods and to have a F5 that preforms close to FRs in pace readings, with which I was perfectly happy. Still, regardless of this, I'll keep my 5s as it's a fantastic watch, overall.


    I've used the 910, 920, F3 and now the F5. While instant pace may have been less 'jumpy' on the 910 and 920 I didn't consider them accurate.

    For example if I wanted my average lap pace to move from 7:40min/mi to 7:30min/mi, I couldn't consistently rely on the displayed GPS pace from any device to do that. YMMV.

    Also true that a footpod is an investment. Not necessarily in your case, but the amount of time spent reading and posting on this forum would've paid for multiple foot pods.
  • Former Member
    0 Former Member over 8 years ago
    Got this installed and can confirm it does correct the alarm issue

    That is awesome.
  • I've used the 910, 920, F3 and now the F5. While instant pace may have been less 'jumpy' on the 910 and 920 I didn't consider them accurate.

    For example if I wanted my average lap pace to move from 7:40min/mi to 7:30min/mi, I couldn't consistently rely on the displayed GPS pace from any device to do that. YMMV.

    Also true that a footpod is an investment. Not necessarily in your case, but the amount of time spent reading and posting on this forum would've paid for multiple foot pods.


    That's why I said that I might invest in one, but only after I give Garmin a few updates and see if they can improve on this. My FR620/630 were very smooth with pace, no spikes, no deep drops.. Again the prob is not so much in an instant pace during run, it's the graph you get after a workout. And here, there is no comparison. FR gives smooth and quite reliable graphs, while F5 has erratic shape, varrying sometimes by +\-50% in a few seconds. I never, ever got paces faster than 3min/km on my FR, and I am regularly getting such readings with F5, followed by paces of slower than 8min/km all in one min. I am fine with some level of inaccuracy - as in the case you described, but not with the pace tracking that varies by factor of 2 in some cases, while I run with the same pace. I never got such behaviour with FR, so this give me the hope.

    I truly believe this can get sorted, as maps look quite good.

    If not, then I'll be here searching the posts about footpod calibrations and how can that help me. (hopefully this can be avoided as I would like to have less sensors I need to worry about)
  • Got this installed and can confirm it does correct the alarm issue

    That is awesome.


    Not for me. Changed the time of my alarm for tomorrow. I didn't sync manually but let the watch do it on its own. Just checked it a few hours later and it reverted back to the GCM time.
  • Not for me. Changed the time of my alarm for tomorrow. I didn't sync manually but let the watch do it on its own. Just checked it a few hours later and it reverted back to the GCM time.


    I would suggest you do a hard reset - long press of the light button until the watch turns off and then turn back on again.

    The alarm is working for me now having done the above.