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.

  • Unfortunately the standard of bug reporting can be very poor and lacks evidence - this is not a criticism as people are not paid to do this and it's voluntary. And some people are not native English speakers, which can make it difficult for them to get points across clearly. But it's not going to help Garmin fix issues.

    Come on, don't be that guy. I've reported countless bug both here and via email. As you can read above the text just messed up while writing on my phone. I also DID capture the screen on the watch (go figure) but since it was displaying no label at all, I had no reason to attach a screen about it.

    In your long detailed list maybe add: 4) don't be patronising Slight smile

    Peace

  • Tacking on to Mac and others on battery drops. I have not updated to the beta this time, so I'm still on 20.60, but have received an update to ANT/BLE 6.15  through Garmin connect. after receiving that update, I am seeing a battery drop similar to what you, and others are reporting. 

  • Another false sleep showed up today - post exercise HR dip is the typical 'trigger' that I see

    Before, showing wake up time

    false sleep begins at start of post-exercise drop to normal levels

    7 day sleep report before this occurred (all the short sleeps correspond to false sleep detection incidents previously reported)

    After this latest false sleep -false sleep replaces genuine overnight sleep

  • Does this have impact on your other stata and functions, like body battery, training status, recovery time, suggested workouts... If you use any of these, of course Slight smile

  • Does this have impact on your other stata and functions, like body battery, training status, recovery time, suggested workouts... If you use any of these, of course

    Definitely body battery - although I think it's mostly an invented number anyway...

    It can impact recovery time but not always ('your poor sleep delayed your recovery by x hours') - in this case, no

    I don't think it impacts training status. It's hard to say with regards to Daily Suggest Workouts too be honest as they seem to be generated immediately after midnight.

  • Thanks for the detailed answer!

    Well body battery goes up as you fake sleep, makes sense... 

    Quite ironically it advises you not to work out too near to sleep, while you actually take a good nap immediately after working out every day Smiley

  • Quite ironically it advises you not to work out too near to sleep

    It looks like the advice is 'baked in', and not generated dynamically.

    So again, it has a problem here with my exercise and tells me to do it earlier - even though it was in the middle of the day, and my device sleep time is 10PM-730AM which no where close to my 'bedtime' the warning below insinuates.

     ''

  • Yeah... Probably, since it replaces the night sleep with the day (fake) nap, and then considers this one as night sleep, the workout is considered too near to sleep... and of course since the nap is not good and long enough to be a good night sleep... gets a poor score. 

    My hypothesis remains that they are trying to accomodate the needs of the shift workers that sleep during the daytime, however... The fact that a day sleep replaces the previous existing night sleep screws everything up. One take is that the algorithm must be able to account for multiple sleep periods in the day (and of course... Detection itself should be better tuned in order to avoid detecting falsely as in your case)

    Thay a lot to work on the sleep detections, really a lot!

  • How to remove custom workout from strength training? The "delete" item has disappeared from the menu.