Fēnix 5X – 3.41 Beta Release

ok... look at this exported fit to trainingpeaks. lap 4
http://tpks.ws/3QB7V

It certainly looks the the watch lost GPS lock several times on lap 4, there is no denying that. I was just trying to point out that the tracks displayed by Garmin connect are often not representative of the true track. Not trying to defend the watch here, just pointing out the fault with Garmin connect which is often attributed to bad GPS when that is often not the case.

It would be a rather unusual situation where you regularly had to check the time on your watch in no ambient light without turning wrist to look at the watch anyway. But assuming you face this situation on a regular basis, one workaround would be to create an Activity, with a single field for Time, and no GPS. This would mean that there would be no timeout.

I agree it is unusual, but I just simply cannot fathom the logic. Why have no-timeout and then not honour it? If I want a short timeout, I'll set it to 4 seconds. If I really want no-timeout, why can't I have this, especially since there is an option for it? Smells of a bug to me. I would love to hear the logic behind the current behaviour since I can see the downside of it without an upside. Yet I cannot see a downside if it behaved the way you'd expect rather than the way it does.

Certain Not Data Showing on 3rd Party Watch Faces

I still don't see data such as altitude, HR, Sunrise/Sunset on 3rd party watch faces. The data shows when I scroll through the selection of faces, but once applied, the data disappears and shows as "no data" on the face.

For CIQ watchfaces and sunrise/sunset here's what works for many:
https://forums.garmin.com/showthread.php?376023-quot-HandsFive-quot-Watch-Face-Issues&p=984097#post984097

The key however is that once a watchface gets the lat/lon, it needs to save that away for times it's not available. (which can happen on any watch and not just the f5x) It's simple to do, but is something that needs to be done by the watch face itself, and it sounds like some watch faces don't do it.

Watch faces that do that "save" have been working fine for me... I posted about this in the CIQ developer forum too with a few more details.

Lot's of problems

O.k...worst firmware build for me for sure. Many problems, but key ones are:
1. CIQ data fields on watch faces still not updating correctly. Have done the stupid "start and activity, revert to watch face, end activity" function and while it initially will load the altitude and sunrise/sunset fields correctly they do not update. No change to any of those fields throughout the day or days.
2. Constant loss of connection to phone.
3. This is a biggie. Have calibrated the altimeter many times, either manually or via GPS. This morning it read -6548m...that's pretty stinking low. Re-calibrated about 1/2 hour ago and now the altitude is -1351m and dropping about 10m every second. Must be one hell of a change in weather coming!

Reporting all to Garmin, but I'll have to go back to v3.3...this one is garbage for me.

For #1, if it's not working for some WF's, it's because they don't save off the lat/lon when they get one to use in cases where the WF can't get the lat/lon (on the f5x, it can only get the lat/lon at a few specific times). This can happen on about any watch depending on when the last GPS activity occurred.. It's a simple change in the code to do this, and something that the developer can add. I posted more info in the CIQ developer forum.

Don't think the CIQ Watch Faces are the Problem

For #1, if it's not working for some WF's, it's because they don't save off the lat/lon when they get one to use in cases where the WF can't get the lat/lon (on the f5x, it can only get the lat/lon at a few specific times). This can happen on about any watch depending on when the last GPS activity occurred.. It's a simple change in the code to do this, and something that the developer can add. I posted more info in the CIQ developer forum.

Don't think that is the problem on the watch faces. Same watch faces I've used, and are using, on the Fenix 3 with no problems. I'm not the coder, but I do know on the Fenix 3 the fields update correctly even when I do not reacquire GPS signal for lat/lon. Therefore they must be saving those fields. I doubt they would change that procedure just for the Fenix 5x. Also when I do get lat/lon again on the 5x the fields still do not update correctly.

Don't think that is the problem on the watch faces. Same watch faces I've used, and are using, on the Fenix 3 with no problems. I'm not the coder, but I do know on the Fenix 3 the fields update correctly even when I do not reacquire GPS signal for lat/lon. Therefore they must be saving those fields. I doubt they would change that procedure just for the Fenix 5x. Also when I do get lat/lon again on the 5x the fields still do not update correctly.

Yes, it's the same problem. On a f3 (and most watches including the f5), the lat/long is available for some time after a GPS activity (it could be hours). That's not the case on the f5x. There are differences in the HW, and what can be gotten and when. All the memory for maps is involved, it seems.

The developer needs to save the lat/lon when it's known and use the saved info when it's not available. Many CIQ watchfaces do this already - and work on the f5x. I am a coder and posted the info in the developer forum about this. Contact the developer, as it's actually a small bit of code that's needed.

Watch face doesn't update

My watch faces doesn't update anymore... they are all stuck on the default setting and ignores my changes made on the setting... help?