Fenix 5X - 3.22 Beta Release

Strava Segments are still broken

Hey all!

Strava Live Segments still don't work right. I described the issues in detail here:
https://forums.garmin.com/showthread.php?374806-Fenix-5X-2-96-Beta-Release/page4

Unlike I first thought, beeing behind or ahaed of you PR doesn't seem to affect the bug that the "Remaining Distance" field doesn't change its value.

What's even more annoying is that the watch starts navigation for each segment no matter if I cancel it before it starts or not. Sometimes it switches to the map screen and becomes unresponsive so that it's hard to stop the navigation manually via the Settings.

My guess is that these bugs were introduced after FW 2.9 as I don't remember seeing them before I installed Beta 2.96.

No resting hr measurements at the moment. Optical hr is otherwise working fine.

Anybody else getting this error where the map doesn't redraw and slowly starts to vanish during navigation?

Odd navigation freakout

After upgrading the 5X fw to 3.21/3.22, I went for another run with both the 5X and the 935. The results were surprising. Both watches were set to GPS+GLONASS, 1 sec. recording, auto pause off.

The good: The pace records of the two runs were nearly identical. I don't mean "close enough that I can live with it," but nearly identical. This image shows the paces side-by-side: . This is the closest I've seen with these two watches, and by far the smoothest pace track I've seen on the 5X. It makes me wonder if they made a change to the GPS filtering for runs in 3.21/3.22, which would be in line with what Garmin Support told me at the end of April when they claimed a software fix for the pacing issues was imminent. Overall, both watches struggled with parts of the track. The 5X marginally more so than the 935 at the beginning, and vice versa toward the end. The only exception being where I stopped to deal with the 5X navigation freakout (described below). The tracks are viewable here: http://www.mygpsfiles.com/app/#6gMxKwG2

The bad: The 5X had a strange freakout at about 19 minutes through the run. I wasn't using the 5X for navigation (I was using a course on the 935), but when I looked down at this point, the 5X was showing the map and was saying "calculating" as though it were routing to a POI, back to the start, or some other location. I held down the menu button to get to settings and try to stop navigation, but I saw only one a single option: "Settings." I then pressed the back button, but instead of backing out to the data screens it did a new lap, showed the lap screen, and then returned to the single "settings" option. At this point I had stopped to fuss around with the watch, and this is where the track shows me dancing around in a little circle, despite standing still. Unable to get back to the data screens, I just finished the run with the watch on the "settings" screen. When I finished and pressed stop, and only then did it show me more settings options like "Settings for current app," "watch face," etc. And then I was able to back out to the data screens and actually stop the run. I don't know why this happened. It is possible that my wrist somehow bumped some buttons that went into navigation, but I doubt it.

Anybody else getting this error where the map doesn't redraw and slowly starts to vanish during navigation?

Yes!! Happens for me almost for every activity after 7-10 minutes. Map (page) is so absolutely useless for me...

" />">

This way I also had.
It is probably a problem with the memory management.
At me: Resignation from IQ of the data field and IQ watchface - it is OK.

Hi guys

I am having the same map issues as described above. I find it won't have to redraw if you zoom out and load it before you start the run but using a detailed map is then useless.

I also experience the strava live segments bug where it starts navigating despite of cancelling and I can't remember seeing this before 2.96

Yes!! Happens for me almost for every activity after 7-10 minutes. Map (page) is so absolutely useless for me...

" />">

Exactly same here thing. I've noticed it when I 1st added Stryd data field. Thought it was related with footpod problems but I seen know I was not alone. I've mailed the issue multiple times to the beta team.

I think there a a lot of 5x users (all?) affected by this issue and the fw team is aware of that and working on a fix (I hope so...)