Fēnix 5X – 3.41 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/download_details.jsp?id=11665

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.41 Change Log Notes:
  • Added support for pre-defined Alarm labels. (Menu > Clock > Alarm Clock > Select an alarm > Label)
  • Added support for new VIRB remote commands available on Virb cameras.
  • Added support for adding widgets through the context menu. (Scroll to a widget > Menu Key)
  • Fixed an issue where the HMD configuration won’t match what is being displayed on device.
  • Fixed an issue where the activity summary could display blank lines if no heart rate was recorded during the activity.
  • Fixed an issue where certain options were missing from the context sensitive menu for CIQ widgets.
  • Fixed an issue where the activity summary information for multisport profiles only represented data from the last leg.
  • Fixed a potential issue where the device could freeze when dismissing multiple smart notifications.
  • Fixed a potential issue where the Training Effect value on post activity summary won’t match the value shown on Garmin Connect.
  • Improved the consistency of routing results when using segments with courses.
  • Fixed a potential issue where certain CIQ watchfaces could crash the device. (Requires Display 2.20)
  • Fixed an issue where the distance remaining field would not update when using segments.
  • Fixed an issue where the map wouldn’t feel responsive when the user was off-course at the beginning of a navigation.

Send all bug reports to [email][email protected][/email]
  • I'm not in a position to prove anything, but your track looks pretty good to me (i didn't inspect it point by point thou). Those sharp cut edges might be something due to smart recording?

    Cheers

    i use one second recording.... how can you say that is pretty good? look at the picture... tracked with fenix5x gps+glonass 1sec and edge1000 gps+glonass 1sec
    @Iron_Cingh When you say 'accuracy', what are you referring too? Is the distance or speed wrong? Or is your comment a reference to the track plotting?

    the track... squared cornes, spikes on straight roads
    https://goo.gl/photos/No37U3uvXuyC8vgW7
  • Former Member
    0 Former Member over 8 years ago
    Doesn't work for me...


    Odd, because it works fine for me on 3.41.
    I don't experience the '5sec' issue others are having either.
    I set gestures to 'on', timeout setting to 'no timeout', ensure my 'do not disturb' setting is as desired, then flick my wrist and the backlight stays on until I manually turn it off.
  • i use one second recording.... how can you say that is pretty good? look at the picture... tracked with fenix5x gps+glonass 1sec and edge1000 gps+glonass 1sec

    the track... squared cornes, spikes on straight roads
    https://goo.gl/photos/No37U3uvXuyC8vgW7


    Share that with Garmin like I have been doing since the beginning. That's the only way to get them to acknowledge the problem.
  • Former Member
    0 Former Member over 8 years ago
    Garmin will never acknowledge there is a GPS accuracy problem because they clearly don't think there is one.

    The Fenix 3 was no different; hundreds if not thousands of replies in threads about poor GPS accuracy and not one comment about it by Garmin.

    It is clearly "working as intended" within whatever tolerance Garmin have set for it and I think we just have to accept it or use a different GPS watch if you NEED the accuracy; the Forerunner 935 for example is proving to be more accurate despite being basically the same watch internally (which leads me to conclude that the poor GPS of the Fenix watches is a "feature" of the metal in the design).
  • i use one second recording.... how can you say that is pretty good? look at the picture... tracked with fenix5x gps+glonass 1sec and edge1000 gps+glonass 1sec

    the track... squared cornes, spikes on straight roads
    https://goo.gl/photos/No37U3uvXuyC8vgW7
    Your problem here is Garmin connect is rubbish at displaying GPS tracks as it removes many points. If you export your track as a gpx and load via some other utility it looks much better. Here it is displayed using http://www.gpsvisualizer.com/




    Looks pretty good to me. In fact it looks better than your top image.

    Don't confuse the rubbish track that Garmin connect displays with GPS inaccuracies.
  • Odd, because it works fine for me on 3.41.
    I don't experience the '5sec' issue others are having either.
    I set gestures to 'on', timeout setting to 'no timeout', ensure my 'do not disturb' setting is as desired, then flick my wrist and the backlight stays on until I manually turn it off.
    Definitely odd, since the beta team confirmed the behaviour I am seeing and you are not is correct. I did not believe it but here is their reply:

    Hello John,
    This is by design. When on the watch face the " No Timeout" is not honored.

    Thank you
    James
    Outdoor Quality Team


    So, if I need to use the watch after dark and need to keep referring to the time, I cannot keep the backlight on for more than a minute even if I want to. I'll need to get use to using the gestures every minute.
  • Your problem here is Garmin connect is rubbish at displaying GPS tracks as it removes many points. If you export your track as a gpx and load via some other utility it looks much better. Here it is displayed using http://www.gpsvisualizer.com/




    Looks pretty good to me. In fact it looks better than your top image.

    Don't confuse the rubbish track that Garmin connect displays with GPS inaccuracies.


    That looks much better indeed. I have seen this argument before- if that is the problem, I would be surprised why Garmin havent done something to fix this.
    Still, my 935 looked much better, while using Garmin Connect...
  • Your problem here is Garmin connect is rubbish at displaying GPS tracks as it removes many points. If you export your track as a gpx and load via some other utility it looks much better. Here it is displayed using http://www.gpsvisualizer.com/




    Looks pretty good to me. In fact it looks better than your top image.

    Don't confuse the rubbish track that Garmin connect displays with GPS inaccuracies.

    ok... look at this exported fit to trainingpeaks. lap 4
    http://tpks.ws/3QB7V
  • Definitely odd, since the beta team confirmed the behaviour I am seeing and you are not is correct. I did not believe it but here is their reply:

    Hello John,
    This is by design. When on the watch face the " No Timeout" is not honored.

    Thank you
    James
    Outdoor Quality Team


    So, if I need to use the watch after dark and need to keep referring to the time, I cannot keep the backlight on for more than a minute even if I want to. I'll need to get use to using the gestures every minute.


    What an answer! LoL!!!!! I don't know if to laugh or to cry! 😂😰
  • That looks much better indeed. I have seen this argument before- if that is the problem, I would be surprised why Garmin havent done something to fix this.
    Still, my 935 looked much better, while using Garmin Connect...
    Garmin may not consider this something to be fixed. I guess they remove points from long tracks to avoid slow display times for slow systems, and do not do it in a very intelligent way. I am not trying to say that the F5 is as good as the 935 for example, just that garmin connect should not be used when considering track accuracy. Always compare tracks using the same tool, and one which is going to use all recorded track points.