Fenix 6 Series - 20.00 Public Release Candidate

Hello Fenix 6 customers,

Our next beta version for the Fenix 6 series is now available! 

Please ensure that you are downloading the correct beta software for your specific device.

Instructions for installation are available below the change log on each of the above pages.

20.00 Change Log Notes:

  • Added ability to turn off recording an activity during a golf round.
  • Added an alert to notify user when battery is critically low during a music sync.
  • Added HRV Support from chest strap for Yoga and breathwork.
  • Added pop-up to Pulse Ox Measuring feature if the device detects too much movement and cannot get an accurate measurement.
  • Added support for new biking activity profiles: eBike, eMTB, Cyclocross, Gravel Bike, Bike Commute, Bike Tour, and Road Bike.
  • Added support for the HIIT activity profile and workouts.
  • Added support for the Pickleball profile.
  • Added support for the Padel profile.
  • Added support for the snowshoe activity profile.
  • Added support for the tennis activity profile.
  • Added new tips to indicate which activities support Incident detection.
  • Improved accuracy of Surf wave count algorithm.
  • Improved Explore Sync app waypoint load times.
  • Improved Lactate Threshold and Altitude Acclimation algorithms.
  • Improved measurement loading UI when taking an SpO2 measurement.
  • Update the altimeter’s auto calibration to be either be “On” or “Nightly”. Setting to “On” will calibrate at night, activity start, and continuously during activities. Setting to “Nightly” will set the device to only calibrate altitude at night. (Models without DEM maps will not perform continuous calibration during activities)
  • Fixed issue with alarms intermittently not going off when the device is set in Max. Battery Mode.
  • Fixed display issues on the device after navigating to a point initiated by the Garmin Explore App.
  • Fixed issue where selecting a single point on a map that contained multiple items would not display the items properly.
  • Fixed issue that would corrupt open water swim activity files.
  • Fixed issue where PacePro bands would not be recognized by the device.
  • Fixed issue with updating aviation data over wifi.
  • Fixed issue with activities reporting incorrect Activity Calories and Training Effect data.

Current beta peripheral software version numbers below. New versions are indicated in red.

GPS: 5.30
Sensor Hub: 11.01
ANT/BLE/BT (Pro models): 6.11
ANT/BLE (non-Pro models): 3.00
Wi-Fi (Pro models only): 2.60

Please note, the beta updates released on these forums are not compatible for APAC region devices.

Please send all bug reports to [email protected], and indicate which model of the Fenix 6 Series you have in the subject line

We know this post states it is a public release candidate, yet the URL states it's a beta.  This is simply a method of delivery for public beta.  We use the same channel and therefore the 'beta' term follows each of these links.  We only note it is a public release candidate so that you are aware it's the proposed version to go live to the public.  

  • That’s been my feeling too. I initially had it asking me to calibrate at the start of each activity but I soon got sick of that. Now, I have it set to do the nightly calibration and auto-cal. It works fine. 

  • That’s been my feeling too. I initially had it asking me to calibrate at the start of each activity but I soon got sick of that. Now, I have it set to do the nightly calibration and auto-cal. It works fine. 

    I completely agree.  I was really reluctant to lose the Altimeter Calibration schemes available in 19.20 - they were working well for me.  Well, probably more accurate to say that I had become comfortable working with the idiosyncrasies.

    After some initial angst, and some compulsive manual calibration after initial install of 20.00, it seemed that logically thebest settings would be nightly calibration and auto-cal.

    It's working very well so far.  Elevation was rock solid during the day despite dramatic lowering of Baro Pressure, and recalibration at night went without a hitch.

    So... put this old dog in the "I Like It" camp.

  • What I can understand, the possibility to save a manual calibration is working again after last two betas. You know when before start of an activity, first get a gpx fix and then open control wheel and do a elevation manual calibration, back to activity and start it.

    Great!

    I haven't seen any unreal drops or straight increases during activity that I had maybe half a year ago that made me turn off auto cal during activity.

    Great so far!

    During night with the first two betas I had an increase of elevation every night by 100 m, to 143 m. With last three betas my elevation is down by around 5 m every night, to exactly 36 m.

    The value in it self is OK, but I would really like to understand it. I don't think my phone has a GPS fix with that DEM elevation.

  • What is your experience guys with this version (20) regarding the incorrect low VO2, training load, intensity minutes issue that plagued us since 19.20? The changelog claims it is fixed but what is your real life impressions so far?

  • With this version something strange happens with calibration.

    Let's say I live on the 4th floor, 250 m above sea level, then in the morning I go down the stairs, get my bike and start the activity to bike commute. The altimeter on the watch face shows correctly 238 m, while the "elevation" field on the bike commute activity still shows 250. I have to manually calibrate, then its shows the correct elevation.

    Is it just me or that happens to you too?

  • I had the same experience with the 19.xx betas.

    I have altitude on my watchface. At home the altitude where I sleep is 47m. DEM at home is 43m. I drive daily a few km to the same park to walk the dog. DEM in the car park is 15m. With the watch on the wrist, 1m above the ground, and with reference to other DEM data I prefer to set the watch altitude to 17m in the car park.

    Every day I could see altitude reduce on the watchface during my drive. Once I arrived in the car park and started my Walk activity the altitude would jump from (say) 17m on the watchface to 47m or 43m or similar - the figure last seen 15 minutes earlier. Even though the watch tracked the descent on the watchface it's like the calibration ignored the new value

    Now, on 20.00 I have switched to continuous calibration. The altitude at the start of the walk is now correct every time, without manual calibration. I have saved a couple of GPS locations in the car park with my preferred altitude of 17m and the watch seems to know of and use these points for automatic calibration.

    Things may be more complicated if you start an activity 4 floors below where you sleep and you want two altitudes registered at the same coordinates, but certainly there is some weird stuff going on if you calibrate at start of activity, before the watch has even gained a GPS lock. Since the altitude is already offered before GPS has got a look in I guess the chances of a correct value being offered are quite low.

  • Both my altimeter and floor count get stuck - double whammy!

  • As long as you don't live on the 10th floor it works OK. And when you do live on the 10th floor and put your watch in battery saver mode at night, it won't calibrate at night, and should work OK too. It would help if Garmin would explain this mechanism better for all the folks who don't sleep on or near ground level.

    All in all I'm going back to some earlier version because of a handful of minor issues that annoy me, Garmin suggested a full reset & wipe because they can't be reproduced, but that didn't fix any of them. 

  • I have saved a couple of GPS locations in the car park with my preferred altitude of 17m and the watch seems to know of and use these points for automatic calibration.

    I've seen this mentioned a couple of times now, how do you actually save a location with the altitude you set manually?

    I can't seem to find it in the manuals. :-)

  • I have a 945 but more or less the SW is similar to yours, I follow you because sooner or later I will switch to Fenix6 titanium, from Friday I am in 8.20 which is equal to yours 20.00 and the altimeter has the same options . I noticed the very close correlation with atmospheric pressure, I live on the fifth floor at about 113 meters, when the weather turns to rain I go up even 20 meters, then when the sun comes back I go back down, but I think it is the correct functioning of the barometric altimeter, not I use the connection to the phone but I can finally correct the altitude by hand, the weather has been stable for 2 days and I am always at 113/115 meters.