Related
Options

Fenix 6 Series - 20.86 Public Beta

Julianna_ODQA
over 3 years ago

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.86:

Change Log for version 20.86 (changes since 20.85):

  • Added prompt to reboot if GPS is unresponsive.
  • Fixed an issue that could prevent device from booting up properly.
  • Added a new tip to notify the user that the Wrist Heart Rate Sensor is disabled. This tip will be displayed whenever accessing a heartrate-related glance while the wrist heartrate sensor is turned off on the device.
  • Updated name of the Endurance Horseback activity to be Horseback.
  • Fixed Run/Walk detection algorithm to properly calculate running & walking times.
  • Fixed an intermittent issue where the device would report inaccurate activity distance data.
  • Fixed intermittent shutdowns that would occur in the Strength activity.

Instructions for updating software:

  1. Download the .zip specific to your computer, using the links above.
  2. Connect the watch to your computer.
  3. 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.86

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.

  • 0 over 3 years ago

    I think I've found a bug. After a higher intensity training two days ago, now all activities are marked as "recovery" when displayed on watch right after stopping the activity itself, but when reviewing them in GC they're correctly categorised. For example this morning I've ride the indoor bike with a TE of 3.6/0.2.

    On the watch: recovery
    On GC: tempo

    When accessing the activities history on the watch it now correctly tells it's been a Tempo training effect

  • 0 over 3 years ago in reply to bellostom

    yes, in my case switching sensor mode from auto to altimeter will give me a better accuracy. I did it sometimes but I am still using the automode on beta in order to check improvement or degradation. I am checking the altitude accuracy with also the local weather station, to verify the air pressure variation could be the root cause of the error. The error level is highlighting this is not the case.

  • 0 over 3 years ago in reply to Frankysour

    Having reported the sleep widget problems to outdoor beta and reporting the curious nap handling (only in the forum) I received a reply today from the team to request files from my watch regarding sleep. So it seems they are keeping tabs on the forum discussions and will make contact if they need more information.

    They asked only for files from the Debug and Sleep folders. Weirdly (?) my sleep folder was empty. Maybe this was due to synchronizing with Garmin Express before accessing the folders. Anyway, I've sent them what I have.

  • 0 over 3 years ago in reply to eezytiger

    One of the other threads I reported issues with Sleep and outdoor beta asked for my Sleep folder which was also empty.

    Around 10PM last night I got another email regarding the moving wake time then random nap I posted a few pages ago on this thread. Again a request for Sleep folder and its empty again.

    Shame if its supposed to be logging this data, but actually not.

  • 0 over 3 years ago in reply to 5135968

    Well I am not having instances of naps recording, either real or supposed by the watch, however... I do have a working widget and an empty sleep folder... I wonder... Would you know from where the widget takes the data it shows? They must be stored somewhere in the watch I guess...

  • 0 over 3 years ago in reply to Labronico

    Sounds similar like the problem I wrote about on page 10 in this thread. When a slow Base run falsely was reported as Tempo in the watch directly after the activity. Then showed as Base in the watch history and Connect.

  • 0 over 3 years ago in reply to +tof

    I doubt this can make any difference, unless you are running/cycling/etc in a completely flat location and use barometer mode. Pressure change is the thing that creates fluctuations to the altimeter and leading to extra meters added either to D+ or D-. Even if you manually switch to altimeter mode there is nothing preventing the altimeter to be off, once pressure changes. 
    What would help, is if Garmin had implemented a correct auto calibration algorithm during activities, that offsets pressure changes. They have clearly failed in that department. Suunto's fusedalti is an example of how it should be done

  • 0 over 3 years ago in reply to Frankysour

    No idea sorry about the widgets data source - my guess is that the watch builds a .FIT file while the widget is in the 'sleeping...' state

    I suspect Sleep folder is emptied after each sync...?

  • 0 over 3 years ago in reply to bellostom

    If you have a DEM on the watch and the reported altitude vs. DEM deltas too much from the expected result it should be reasonably easy to filter pressure induced altitude changes from genuine altitude changes.

  • 0 over 3 years ago in reply to 5135968

    Correct. Suunto and Coros for that matter have managed to do it without having DEM available, with some clever algorithm that uses the GPS altitiude along with (I assume) the GPS chipset's vertical error value. 

    Unfortunately Garmin just does not allocate the appropriate people to provide a decent solution. They have the data, but not inclined to acknowledge this as a non working feature they have provided