Fenix 6 Series - 20.87 Public Beta

Hello Fenix 6 customers,

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

Please email the Garmin Outdoor Quality Team if you find issues in software after installing this update: [email protected]

If you’ve participated in the Fenix 6 Beta Program previously, you’ll notice a few changes from how we have managed this in the past. And further down the line, we’ll have some additional improvements to the Beta Program (more on that later!) Notably, this forum post is now the primary resource for reading the change log notes – they are not available on another webpage. (There will be more options for viewing change logs after we implement the additional improvements to our beta program.)

The links to download the software update are listed below. Select the link specific to your watch model. Please note that your computer will download a .zip file when you open this link. This zip contains the software update, as well as a folder with the file necessary for backdating software, and instructions for this process if you choose to do so. Remember, backdating software will reset all settings.

Use these links to download the zip for your watch to update to version 20.87:

Change Log for version 20.87 (changes since 20.86):

  • Fixed issue where the Sleep Widget was not accessible when Widget Glances were turned off.
  • Fixed intermittent issue where shutdowns would occur in the strength Activity.
  • Fixed intermittent issue where stress and sleep data would not get properly collected.
  • Other minor improvements and bug fixes.

Instructions for updating software:

  1. Download the .zip specific to your computer, using the links above.
  2. Connect the watch to your computer.
  3. Unzip the folder and copy the included gupdate.gcd file (from the System_x.xx folder) to the Primary\Garmin folder on your watch.
  4. If there is a Sensor Hub_v*** folder, place the gupXXXX.gcd file into the \GARMIN\REMOTESW folder of the device. Please note, not all Beta releases will include an update.
  5. If there is a ANT_BT_BLE_v*** folder, place the gupXXXX.gcd file into the \GARMIN\REMOTESW folder of the device. Please note, not all Beta releases will include an update.
  6. Disconnect the watch from the computer and it will prompt you to update software.

After updating, your watch will be running the following software versions. These can be confirmed on the Menu – System – About pages. New versions are indicated in red.

System Software: 20.87

GPS: 5.30
Sensor Hub: 18.00 *If you have been participating in the Beta Program, you may already have this sw
ANT/BLE/BT (Pro models): 6.15 *If you have been participating in the Beta Program, you may already have this sw
ANT/BLE (non-Pro models): 3.01
Wi-Fi (Pro models only): 2.60

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

  • I hope it isn't the intention moving forward. It's a right faff logging into GC Web just to look at one piece of sleep information when all the other metrics are available in the mobile app at the press of a button.

    Like you say; it's in GC web so there's no technical reason why it can't be displayed in the app & yes you are quite correct; the sleep movement data hasn't been polarised by Garmin's interpretation of the biometric data to gauge the quality of sleep it was simply reporting the level of movement during the sleep period so it's actually quite useful; well to me anyway

  • I don't have any battery issues either. There are things broken for everyone but this is not one of them. 

  • Yeah, new watchfaces never come to old watches imo. Have never seen that yet. Then you have to get a third party one but those often are slower and slow the system down. 

    PS: I wonder how long we will have to wait for Health snapshot which according to DCR will come to the F6 line. Love to see my HRV at this moment. 

  • Installed without problems on my Fenix 6X Pro Solar. Thanks for fixing the sleep widget. Slight smile

    Any comment regarding the intermittent Training Effect problem? Did a ~6k walk this morning (with 20.87 beta) and that was correcly reported as Recovery.

  • Just found first bug - the counters for device usage widget were not reset after a power down / recharge / upgrade cycle

  • I never had any issues with beta just now after installing this update. My user profile was messed up, quick controls layout was reseted, wifi won't connect, my watch face reseted, all sensors deleted, heart rate zones, lactate threshold and resting heart rate also was deleted or abnormal. Maybe later I can find more settings messed up. Also someone can confirm on the stock watchface with the 3 circles at the bottom are the same colour? I remember before update their was same colours but maybe I'm wrong.

    Just a bit overweight lol. 

  • Also someone can confirm on the stock watchface with the 3 circles at the bottom are the same colour? I remember before update their was same colours but maybe I'm wrong.

    Never used that watchface before but flipping to it briefly on mine the top two are red, bottom is white.

  • On my device the device usage widget counters were reset (after charge/saving files/upgrade to 20.87). But with 20.86, and not visible on the DU widget, only in usage_hrly.log, the "Time with Pulse Ox" had kept adding up to total almost the entire uptime of the watch, which is impossible battery-wise and I am sure PulseOx is off. The widget is in the loop, I occasionally look at it. 

  • 65535/10, suggests a missing/default max value for weight. Is you weight correct in Connect, and are you still a tad on the heavy side after syncing?

    [Edit] Sorry, wasn't reading carefully enough. All sensors deleted and settings gone, means your settings file is gone. If you have a copy of \Garmin\Settings\settings.fit you can get them back. But do contact beta team by email. This should not happen.

  • Really? Batteries deteriorate over TIME, but shouldn't deteriorate over NIGHT. Also some people managed tot urn back time by reverting to the last FW version that doesn't have the battery drain issue, and voila, the battery was "new" again...