Fenix 5X - 6.83 Beta Release

Compass fixed!

Hey folk, just a report to say that the crazy-compass returns to normal after this upgrade and a re-calibration.

Thanks Garmin.

Hello team ,

What does this mean:

• Improved Training Status and Training Load now updated with heart rate data that is stored on an HRM-Tri or HRM-swim and sent to the watch.
  

I don't see any data about heart rate in training status and training load widget.

Thanks!

No, but heart rate data contribute to those values. Previously they weren't taking into account data sent from the HRM tri and swim after you got out of the water, and now they are.

Dex:
I suppose it means when the HR came from HRMs it was not computed in the training load app. Even I who use all the three of them couldn't have known since I don't use that widget.
It's a very important fix for those who do.

Here, I'm still forced to restart the phone every now and then since auto-upload is not working. I think it's a problem with GCM not with the F5x. On the other hand there IS an upstanding problem with the detection of the HRMs. Notifications sometimes do not come and yet they are synched (handshake time I presume).

gone from having my watchface reset to default settings randomly on 6.0 and earlier versions to now completely breaking after a few hours. When the watch face crashes or whatever it does, i get a default garmin face. the downloaded watch face will not work again until it is uninstalled and reinstalled. rebooting does not fix. using actiface. havent tried other CIQ faces yet but the resetting was a common issue on some others in the past until i settled on actiface and just put up with the annoying random resets.

Did you install both the Display_v256 and System_v683 ? The symptoms you report are what I experienced before updating to these versions, but not since. Without the fix, the data file can become corrupt hence needing to de-install and re-install which removes the data file. The other alternative is to connect the watch to a PC and delete the corrupt data file which is a little bit harder but preserves any watch face settings. But in my experience, this defect was fixed.

Compass Display Settings: Not sure if this is an issue unique to the beta. The compass display does not fully match the North Settings selected. if I select Magnetic North, I would expect the compass to both point and display degrees based on this (N as Magnetic North and showing as 0 degrees) but it mixes both Magnetic and True North. The photo shows this (declination is 13 degrees here). Within an app, the compass behaves the same way - even more irritating is that on the map, the small North arrow points to True North. I would expect, if I select something other than True North (Magnetic, Grid or User), the compass would match this selection throughout.

Did you install both the Display_v256 and System_v683 ? The symptoms you report are what I experienced before updating to these versions, but not since. Without the fix, the data file can become corrupt hence needing to de-install and re-install which removes the data file. The other alternative is to connect the watch to a PC and delete the corrupt data file which is a little bit harder but preserves any watch face settings. But in my experience, this defect was fixed.

yes, i installed all the components in the zip file per the instructions. i just spent 10 minutes trying to get the damn watch cable to connect steady so i could try reinstalling the update over itself. we'll see how long it lasts before resetting.

Imagine me dude... with a brand new RMAed F5x... issues with connection before and issues with connection starting TODAY (3 weeks... the new F5X lasted 3 weeks).
It's a miracle I could install the beta. On top of that, auto-upload didn't work properly with the previous beta. How do I export the logs if GCM doesn't work and USB connection is unstable?
Unbelievable... brand new F5X they just sent me and I had SPECIFIED I needed the new connectors.

• Fixed issue causing the Start/Stop and Lap keys to only clear notifications when they are displayed instead of also performing their general function (for example, starting the timer and recording a lap).
  

Not sure to understand this fixed issue... Does anyone can explain it ? Thx

@iacchos

An active (open) notification would previously "block" the start/stop activity or lap button button during an activity. That is, one press would clear it and then another press required to start/stop. Not ideal if say you pause the activity at a street crossing or similar. Now a single press will both clear the notification and start/stop.