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.

  • Just for testing doesn’t solve any bugs.

    can you test to take of your Fenix after workout for an half hour or similar and see what happens?

  • Just for testing doesn’t solve any bugs.

    can you test to take of your Fenix after workout for an half hour or similar and see what happens?

    I like your way of thinking Slight smile

    Actually I already tried that - it hasn't occurred so far if I do that, although I am not sure if we can draw any conclusions as sleep tracking only works if it thinks the watch is being worn.

  • Hi, of course no good conclusions can come out of this, but at least you avoid screwing your stats... Hope you are still feeding these data to Garmin.

    On Your Previous post, that body battery goes up when you are relaxed is actually ok, as... We all recharge when resting even if not sleeping, the issue is specifically the unwanted sleep detection. Funny is... You have a fake nap, your BB goes up, bit the fake nap replaces night sleep, and the watch considera you had a crappy night and adds to your required recovery hours Smiley 

  • and the watch considera you had a crappy night and adds to your required recovery hours

    The fake naps are always rated poor due to their shortness - from what I can see, for low intensity exercises with short recovery times, the fake sleep doesn't seem to impact recovery times. However with more intense exercises then I do sometimes see the 'your poor sleep increased your recovery time'

    But this didn't happen today.

  • Yes, these involuntary reboots have occured only during runs. Thank you for your suggestion, this will be my first corrective measure, if any. 

  • I personally already introduced a call at Garmin Belgium for this bug 2 years ago…

  • So yesterday after getting a false sleep event again, I noticed / felt my HR had dropped quite low around 7:30PM

    I switched on my Polar Verity Sense and overlaid the display over the live Garmin Connect live feed from the oHR - my HR genuinely dips low as cross checked by the Polar Sensor so the oHR sensor appears to be working well - both hit 43 bpm within a couple of seconds of each other

    And BOOM....

    another sleep event is detected corresponding with the low HR dip 

  • ...maybe Garmin needs to acknowledge in their algorithms that some of the users of their fitness watches are actually... Fit! CryRofl

    I think I have never seen my hr dropping below 56-57... Thinking about quit smoking Open mouth

  • A bigger problem is that I think it really reveals body battery is totally faked tbh - it's so naive it just adds a + figure when it thinks 'sleep' - even when the HR trace clearly shows no sleep! So I end up flatlining at 100 due to the false tracking yesterday

  • Premise is I agree bb is not extremely accurate, however it is surely not based on sleep (at least not only) since I have seen it go up - correctly I would say - if I have for instance a relaxing hour watching tv or reading a book on my couch. This WITHOUT detecting any sleep.

    I think it's based on a combination of low and stable hr with good level HRV, and makes sense to me... When relaxing one actually recharges, that's the whole point actually. 

    This being said, again, not saying it's accurate, only that is not based on sleep time only (probably that's part of the equation but it's not the whole equation)

    Edit (adding some considerations): 

    Most probably the algorithms are more effective for more "average" fit people, that have a rhr in the 60s or high 50s, and corresponding average hr, than for people wich are above average in this as you seem to be (congrats!), But this of course is kind of a bummer, I guess.... Maybe for Garmin one approach could be, if possible, an adaptive algorithm that looks for instance at last month average rhr and HRV, and re-calibrates accordingly? Maybe worth mentioning in your next contact with them? 

    For me (again, not perfect by any means, granted) bb kinda make sense, overall