Fenix 6 Series - 20.41 Public Beta

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.41 Change Log Notes:

  • Updated the software update process to allow the user to defer the installation. This replaces the automatic install during the user's sleep window.
  • Improved altitude calibration.
  • Fixed intermittent issue where device would freeze when starting a round of golf.
  • Fixed issue that would cause device shutdown when editing HIIT data fields.
  • Fixed issue where the device would create empty golf scorecards.
  • Fixed issue where the activity timer could be enabled on the Map-App. (Pro models)

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.

  • Former Member
    0 Former Member over 3 years ago

    Thanks for keeping the Fenix 6 series up to date.

    FYI, the incomplete altimeter graph-issue occurs again. In beta 20.04 this did not happen.

    This issue may only apply to users who have Device Upload set to 'off'. I have reported this.

     I

  • Interesting there Anders is I'm using GPS+Galileo too. Swapped over to pure GPS and wills ee if it happens again. (oh BTW when I said smoothing, I meant internal data processing in the watch, not connect - but that's good to know you always don't see it with corrections off)

  • This was my first activity in a couple of months so I dont know if I have had this problem before. Havent seen flat parts in the elevation graphs before this. Not what i can remember.

  • Hopefully there'll be a new version soon, because I really don't want to backdate... Smiley

  • In my view if you ask users to do free testing - which is quite time consuming if providing a good quality report, then I think at least an acknowledgement would be useful.

    I no longer do, because my time is quite valuable, and with no feedback I could be wasting my time.

    So what further information was needed from you that you didn't provide first time round? - the trick to getting a reply shouldn't be to provide reports that are missing information they need ;)

    yes, in deal world we would get feedback to anything we submit but reality is that we're living not in the ideal world. And again, I've used to send feedback to different brands to some products I'm using, in some it was a total time waste as I never heard back, with some I got very nice communication. Garmin is somewhere in the middle, most of the time they don't get back to you, but again, talking about my experience with other Garmin watches not Fenix 6, they actually were corresponding to me and asking for additional information.

    I believe that they are going through feedback, find one which is most useful to them and respond to it, and use the rest as reports and indication whenever something is working or not.

    And sure, if your time is valuable you shouldn't use any testing software, that's what developers emphasize everywhere no matter if it's firmware for a watch or your server's OS. That's why stable software exists.

    Leave the beta testing to the developers. Are you getting paid to be a beta tester=NO, are you getting a working device= NO. Are you getting a trouble free user experience=NO. Stop beta testing if you are not ready to lose the device normal functions.

    Exactly, leave it to developers and to those who're willing to take a risk and help to polish the firmware for the community. That's the point of beta testing.

  • I confirm flat segments in my running sessions immediately after 20.41 fw update (with 20.30 it was ok), however elevation stats seem unchanged

  • Another day another “improve altimeter calibration” update!

    Glad I turned off auto update now from 19.20.

  • For what it's woth, after five day, only one bad cal one morning (170m instead of 140 at home, not a "big" derivation if you read later). I'm happy.

    First time since 19.20.

    All beta after shows me at home at ... 50m ! Every damn morning. Only one time when I cut the bluetooth link with my phone during the night the altitude was right in the morning.

    After all, for my usage, not very boring: I only use elevation in activity, and auto calibration when I start an activity still always worked. But it's better (but useless) if when I wake up I see the correct altitude ;)

  • 8km walk with 20.41. Elevation and gps seems to work nicely, no issues. 6x pro solar.

  • Former Member
    0 Former Member over 3 years ago in reply to Miky

    For notification is not. I've left my watch home this morning because i was in the "engine bay environment" I got home about 1600h afternoon, guess what? My dear Fenix 6 was still buzzing and ringing the 0800h alarm from this morning. Obviously, the battery was almost depleted. Let's just buzz away for eternity. Nice job really as the watch was really hot by the time.