Fenix 5X - 4.21 Beta Release

Hello Fenix 5X 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 5X: http://www8.garmin.com/support/downl...s.jsp?id=11665 (A 2.33 Display update is available in the link as well)

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.

*We are aware of an issue where the 'Triathlon' app name could go missing in the app list.*

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.21 Change Log Notes:
  • Added support for accessing Altimeter, Barometer and Compass widgets through the Controls menu.
  • Fixed a potential issue where the device may appear to be frozen when connected to a computer.
  • Fixed a potential issue where certain activities would show extremely high total elapsed time when trying to save them.
  • Fixed an issue where MoveIQ events were showing up in Garmin Connect, even though disabled on device (Settings > Activity Tracking > MoveIQ).
  • Fixed an issue where the watchface being applied was incorrect, when removing inactive ConnectIQ watchfaces using Garmin Connect Mobile.
  • Fixed an issue where the backlight would turn off (outside of an activity), even though the backlight setting was set to, ?No Timeout?.
  • Fixed an issue where the directions displayed on the Dog Tracker widget would not update in real time.
  • Fixed an issue where one could not uninstall the FaceIt App from Garmin Connect Mobile.
  • Fixed an issue where off course notifications were not working as expected when navigating a past activity versus a course.
  • Fixed an issue where the course point arrival message was not being displayed on a connected Head Mounted Display (HMD).
  • Fixed an issue where routes created on Basecamp did not have elevation information after being transferred to the device.
  • Fixed an issue where waypoints created with Arabic or Hebrew characters would not display correctly on the map.
  • Fixed an issue where certain courses downloaded through a CIQ application were failing to load on the map.
  • Fixed a potential issue where the device may appear to be frozen when starting a course navigation using an activity profile that had ConnectIQ data fields configured.
  • Someone could try if barometer lock works in this release? Just put barometer in "barometer mode" and climb some stairs... altimeter should remain steady...
  • Former Member
    0 Former Member over 8 years ago
    I get an error message when installing - "error catched in garmin/apps/logs/ciqlogs.txt"

    Here it is:

    UnexpectedTypeException: Expected Number/Float/Long/Double, given null/Number
    UnexpectedTypeException: Expected Number/Float/Long/Double, given null/Number
    UnexpectedTypeException: Expected Number/Float/Long/Double, given null/Number
    UnexpectedTypeException: Expected Number/Float/Long/Double, given null/Number
    UnexpectedTypeException: Expected Number/Float/Long/Double, given null/Number
    UnexpectedTypeException: Expected Number/Float/Long/Double, given null/Number
    UnexpectedTypeException: Expected Number/Float/Long/Double, given null/Number
    UnexpectedTypeException: Expected Number/Float/Long/Double, given null/Number
    UnexpectedTypeException: Expected Number/Float/Long/Double, given null/Number
    UnexpectedTypeException: Expected Number/Float/Long/Double, given null/Number
    UnexpectedTypeException: Expected Number/Float/Long/Double, given null/Number
    UnexpectedTypeException: Expected Number/Float/Long/Double, given null/Number
    UnexpectedTypeException: Expected Number/Float/Long/Double, given null/Number


  • Former Member
    0 Former Member over 8 years ago
    Instruction to revert back to last public update show:
    • If you would like to revert to the last public release software, drop the gupdate.gcd file found in the System_Backdate_v410 folder in the \GARMIN directory
    However there is no System_Backdate_v410 folder anywhere.

    Suggestions?
  • My 5x don't sync with garmin express and fw 4.21 at all (server communication error) at all. Anyone else this prob or is it only my watch?

    Supplement: After a soft reset, my 5x is syncing with express.
  • Someone could try if barometer lock works in this release? Just put barometer in "barometer mode" and climb some stairs... altimeter should remain steady...


    Just tried by myself.. it doesn't work, altitude changes even if i set barometer mode...the bug is still here, reverting back to 4.10...
  • Former Member
    0 Former Member over 8 years ago
    There's an excellent option to add the Altimeter to the CTRLs Menu.
    Now all we need is a Manual Calibration Menu in the Altimeter Settings Menu (something that bypasses everything else or that comes right up as the very first choice you can take) and we've solved a BIG problem for everyone who rides after swimming and needs 50 button presses to calibrate the altimeter (and the more often you swim the sooner those buttons will break down, trust me).

    Access CTLs Menu via Shortcut Keys (in my case the DOWN long press), get to the Alti, then Settings, then Calib, then hit 20 buttons again to input manual data... it's not optimal but already something. That's what I mean.

    What we need is a way to get to the MANUAL CALIBRATION with the least possible keypresses. Adding the Altimeter to the Controls Menu is a hell of a good start but now we need a way to access its manual calibration.
  • There's an excellent option to add the Altimeter to the CTRLs Menu.
    Now all we need is a Manual Calibration Menu in the Altimeter Settings Menu (something that bypasses everything else or that comes right up as the very first choice you can take) and we've solved a BIG problem for everyone who rides after swimming and needs 50 button presses to calibrate the altimeter (and the more often you swim the sooner those buttons will break down, trust me).

    Access CTLs Menu via Shortcut Keys (in my case the DOWN long press), get to the Alti, then Settings, then Calib, then hit 20 buttons again to input manual data... it's not optimal but already something. That's what I mean.

    What we need is a way to get to the MANUAL CALIBRATION with the least possible keypresses. Adding the Altimeter to the Controls Menu is a hell of a good start but now we need a way to access its manual calibration.


    And a way to calibrate the barometer. This weekend I was able to compare 4 units of fenix5x and none indicated the same barometric pressure by manually calibrating the 4 watches at the same height, the same place and at the same time. 1020mb, 1022mb, 1026mb, 1034mb. The iphone app showed 1019mb
  • And a way to calibrate the barometer. This weekend I was able to compare 4 units of fenix5x and none indicated the same barometric pressure by manually calibrating the 4 watches at the same height, the same place and at the same time. 1020mb, 1022mb, 1026mb, 1034mb. The iphone app showed 1019mb


    I've asked this since the first software release... also as i write above, the barometer lock mode doesn't work, continue to change altitude...
  • is the strava sync fixed? until 4.16 the unstarred segments weren't deleted from the watch
  • This"
    • Fixed an issue where the backlight would turn off (outside of an activity), even though the backlight setting was set to, ?No Timeout?."
    Halleluja Amen! This bug have been on my nerves and prevented me form fully loving my new fenix 5 X but now I guess all will be well again! :p I knew it could not have been a function by design as someone at Garmin support claimed it was! Because it made no sense!:cool:

    Now my main issue is the lack of a barometric lock function. I remember in the early days of the fenix 3 it had the same issue but that was fixed in a SW update in late summer of 2015. So it is a bit funny that the same bug comes back for the brand new fenix 5 model. please fix that as soon as possible. I want stable barometer and altimeter readings that I can trust more!