Fenix 5X - 9.72 Beta Release

and once again no mention of fixing any of the elevation issues

I can't believe it!

You can activate elevation correction per activity i Garmin Connect web. I cant find it in the app.

I think I have found an issue.

The caching of of location for next sun event calculation on my watch face (Europilot series) has stopped working. I check this against a couple other watch faces and the next sun event calculations are not working, which I suspect is due to writing/reading/caching location values from the watch storage.

I'm aware of needing to acquire GPS and caching it after enabling a watch face. The sunrise/sunset is not working despite having a lat/longlong and having completed a few activities. It is also not working for a few different watch faces, including Europilot, which I wrote.

When I get back from vacation, I will have to fire up my dev machine and see what's actually happening.

Is anyone else having a similar issue?

KSodhi - As of CIQ 3.0.0, a new permission is needed in the watch faces in order to cache the location data (Actually related to GDPR).. Developers were able to add this starting with the 2.4.6 SDK, but some may have missed it, and they haven't made the change to their app (clicking one checkbox and re-publishing.)

See This Blog Post for more info.

You can tell if the WF has the required change,by looking at the "permissions" section for the WF in the store, and you'll see

• GPS location
  

as one of the permissions if it can cache or even use the current location. Contact the developer if they don't have the needed permission set.

My 5x has started to restart everytime I connect it to GCM. Just the first time and just after it "connects" the "Garmin" folder because I always get a "Did not eject correctly" error.

KSodhi - As of CIQ 3.0.0, a new permission is needed in the watch faces in order to cache the location data (Actually related to GDPR).. Developers were able to add this starting with the 2.4.6 SDK, but some may have missed it, and they haven't made the change to their app (clicking one checkbox and re-publishing.)

See This Blog Post for more info.

You can tell if the WF has the required change,by looking at the "permissions" section for the WF in the store, and you'll see

• GPS location
  

as one of the permissions if it can cache or even use the current location. Contact the developer if they don't have the needed permission set.

Excellent information, Jim.

I will update my watch faces.

Thanks again.

KSodhi just enabling positioning permission is all that's needed.
Other app types like data fields and widgets can also require this.

Just tested and no elevation fix. I was short about 800ft or 40% of my total workout.

KSodhi - As of CIQ 3.0.0, a new permission is needed in the watch faces in order to cache the location data (Actually related to GDPR).. Developers were able to add this starting with the 2.4.6 SDK, but some may have missed it, and they haven't made the change to their app (clicking one checkbox and re-publishing.)

See This Blog Post for more info.

You can tell if the WF has the required change,by looking at the "permissions" section for the WF in the store, and you'll see

• GPS location
  

as one of the permissions if it can cache or even use the current location. Contact the developer if they don't have the needed permission set.

Is there a common place/way to inform all watchface/application/widget developers so they could make changes and prevent possible battery drain + other issues?

Did someone tested the 9.72 about battery drain with the complex WF.? I mean wf like gear min or my watch.

??????