Fenix 6 Series - 17.72 Public Beta

Hello Fenix 6 customers,

Edit (6/17 12:30 PM): Non-Pro models: We have identified a crash that occurs when scrolling past a CIQ widget, if the Widget Glances setting is enabled. For now, you can avoid this crash by simply disabling the Widget Glance setting (via Menu - Widgets). Our teams are working to resolve this issue as soon as we can. I apologize for the inconvenience.

At this time, we believe that Pro models are not affected by this crash. 

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.

17.72 Change Log Notes:

  • Added the ability to rate the perceived effort and feel of a Run, Bike, or Swim activity. The prompts appear during activity save. Go to [Activity] Settings > Self Evaluation for options.
  • Added sleep tracking widget with sleep score and insights by Firstbeat AnalyticsTM.
  • Added metabolic calories into the total calories reported in the calories data field and recorded in the activity file.
  • Added setting to enable/disable workout audio prompts.
  • Updated workout audio prompts for hundredths distance precision.
  • Updated Intensity Minutes determinations to align with guidance from CDC.
  • Improved feedback on stress level readings.
  • Improved calorie calculations for activities using a power meter.
  • Improved results for daily Body Battery calculations.
  • Improved visibility of Climb Pro alert page.
  • Improved power meter calibration and settings.
  • Improved layout of target card page. (Only applies to tactix Delta – Solar Edition with Ballistics)
  • Fixed issue where compass would become unresponsive during SUP activities.
  • Fixed issue with incorrect energy values on range card. (Only applies to tactix Delta – Solar Edition with Ballistics)
  • Fixed issue with manual time setup during initial setup.
  • Fixed display issues when editing data field layouts.
  • Fixed issue where recovery sets would not be properly displayed during workouts.
  • Fixed issue where a Suggested Workout could draw with a nearly blank diagram.
  • Fixed issue with editing data screens for Ultra Run app.
  • Connect IQ improvements and bug fixes.
  • Other minor improvements and bug fixes.

Current beta peripheral software version numbers below. New versions are indicated in red.

GPS: 5.30
Sensor Hub: 8.00
ANT/BLE/BT (Pro models): 6.11
ANT/BLE (non-Pro models): 2.11
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.

  • It's easy to always complain. Now something positive. Looks like the track when running has massively improved with this firmware. If this remains as is it's goodbye to my bowl of spaghetti runs Smiley

    Now:

    Previously:

  • Well this is good but proves very little. You should compare two Fenixes, one with 17.72 the other with an older firmware, run few times with those and then swap firmwares (upload 17.72 to the one with the older one and revert to the older one on the one with 17.72) and run few more times.

  • Of course, but I don't have two. A cycle ride on Saturday with this firmware also looked very smooth. All earlier rides and runs were of the spaghetti bowl type. Thus this is new. Were these two outliers? We'll see.

  • Of course I know, don't worry.

    I would just like to thank the anonymous who downvoted my reply, which is just the correct scientific method to assess the validity of a statement. Congratulations, that says a lot.

  • I'm still waiting for the next hike under dense tree cover, but my last runs with 17.72 and 17.73 seem to have improved a little the GPS track, at least in those segments along narrow road with building on both sides.

  • It may be just my impression but it seems satellite fix got better, too. I hiked yesterday in a narrow canyon and at a certain point I stopped for lunch, pausing the Fenix. When I resumed, I though it would take a long time for the watch to get a fix (if any), but as a matter of fact it took only one minute or so. 

    Last time I hiked with 16.60, in similar conditions, when I resumed the watch got a fix 20 minutes later.

    Note for self: never stop recording when you're in a canyon...

  • Don't worry about downvotes. Might just have been an unintentional mis-fingering with a touch screen. Anyway, long run tonight with stretches of poor and good signal. Lets see what i get out of it.

    I just had a look at a short walk last night. This one looks a lot better as well. Of course it's still jiggly as the mode of movement is a lot slower than running and more datapoints are added over a shorter distance. But there's very little crossing road multiple times or cutting through buildings. I'm very carefully optimistic.

  • Don't worry about downvotes. Might just have been an unintentional mis-fingering with a touch screen.

    Yep, on an iPad I just managed to report my own post as abusive instead of edit. Although it just saved someone else time I guess….

  • Look i am not the guy who downvoted, i actually never vote... However... Ok the scientific approach, it's just bit too strict! Even if with same device, the comparison between old and new firmware looks already good enough... Actually it is very significative, will tell people what to expect with the firmware change on their own device, before and after! That's it

  • Ok the scientific approach, it's just bit too strict!

    Well, in my opinion you can't compare two runs taken in different days. Maybe one day you had 30 satellites in view, maybe the other day you have only 12. As for the switch between firmwares, it is just to rule out that one of the watches is inherently better than the other. Since I work with sensors, I know more than well than two sensors built in the same way, even in the same batch, can behave very differently when subject to the same environmental conditions.

    Finally, as for the several runs, you need that to build up a little more statistics to try and establish a rule. Otherwise it's like you just observe a picture on the wall that falls down and conclude that all pictures fall down.