Fēnix 5X – 3.41 Beta Release

Hi, had the same issue and got it resolved.
De-install the face via GCA
Restart fenix
Install WF again and configure it to your needs.
That should be it.

Up until installing the 3.41 beta, my altimeter seemed to be working fine. Today, it said that I was -21 at -21 feet, when it should read +20 or so. I went into the settings and selected "calibrate by GPS," and the calibration said -18 feet.

Perhaps it's not the beta - it's a very cloudy, rainy day today, which I suppose could be messing up the quality of the GPS signal and contributing to the issue. But that said, the 5X map showed me in the right place, so it seems to be getting an acceptable GPS signal.

Today, it said that I was -21 at -21 feet, when it should read +20 or so. I went into the settings and selected "calibrate by GPS," and the calibration said -18 feet.

Vertical accuracy for GPS will generally be 2 or more times worse than the horizontal - has to do with the math (won't bore you with the details). Given that (despite some expectation from people) 5 meter horizontal would be considered very good, this could easily be 10 -15 meters vertical - so your 40 feet. If conditions where not optimum, the elevation error can be much greater. This is why barometric altitude provides a much better accuracy once calibrated (not without other issue). This is also why you will see options in sites like GC to correct the elevation data (off by default for watches with barometric sensors). The correction is based on datum from sources to match the provided horizontal location to the mapped elevation, rather than use the GPS elevation.

I assume you also know that the altitude will gradually change over time - rate will depend on weather and other things. You will always need to re-calibrate it once in a while. If you know your elevation then manually calibrate it. Lots of discussion on how Garmin handles the air pressure vs altitude problem compared to suunto and others.

Couple of links
http://www.radio-electronics.com/info/satellite/gps/accuracy-errors-precision.php

http://forums.watchuseek.com/f374/altitude-barometric-pressure-abc-watches-explained-266991.html

I agree it is unusual, but I just simply cannot fathom the logic. Why have no-timeout and then not honour it? If I want a short timeout, I'll set it to 4 seconds. If I really want no-timeout, why can't I have this, especially since there is an option for it? Smells of a bug to me. I would love to hear the logic behind the current behaviour since I can see the downside of it without an upside. Yet I cannot see a downside if it behaved the way you'd expect rather than the way it does.

I would have thought the logic was quite simple - preserve battery life, and specifically to avoid the possibility of the backlight accidentally being left on when the watch is not being used. I note the backlight doesn't timeout when using widgets (which follow the watch mode rules), although a widget reverts to the clockface if not touched for 2 minutes.

I would have thought the logic was quite simple - preserve battery life, and specifically to avoid the possibility of the backlight accidentally being left on when the watch is not being used. I note the backlight doesn't timeout when using widgets (which follow the watch mode rules), although a widget reverts to the clockface if not touched for 2 minutes.

Yes, you are right. I would not want the watch to go flat because I accidentally pressed the backlight button in my sleep. Good point.

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]

https://goo.gl/photos/YT2TuAEGweHbf6DC6

after a mountainbike ride...
-still signal lost
-still senseless ascent meters when the activity is saved
-still senseless segments and double segments
-live track doesn't stop (i turned off the phone, then the watch and nothing happened).
-unstarred segments remain active

-still senseless ascent meters when the activity is saved

I get the exact same figure (49152 m) every time I have been using the MTB app. However, it is not the measured ascent, you can check by going into the history on the watch or at Garmin Connect, you won't find the number again. That field is supposed to give the average speed of the ride, it is a bug which is only present in the activity summary page. Still annoying though.