Fenix 5x 2.90 software bugs

Former Member over 8 years ago

I have noticed these errors. Please add yours below; I haven't seen a thread regarding bugs with the current firmware.

If I open the "navigation" app, go in the menus of it but don't start the activity, then exit the app, sooner or later the watch will crash. Even if I start the activity, it has been known to crash. Weirdly, the clock will still work as normal but none of the buttons will work. I then have to hold the backlight button and restart the watch. If the backlight was already on, it will remain on.
The watch doesn't seem to automatically zoom the map unless in navigation mode. Perhaps this is normal, I'm not sure.
If you start the navigation app, load a course but don't start the activity, exit the app and then start the walk app, you'll see it still thinks it's in navigation mode.

The crashing is especially annoying and hopefully it is just a software bug. Read my separate post to replicate the fault.

0 iacchos over 8 years ago

Language setting (other than english) is lost (apparently) each time the watch is synchronized with GC Mobile --> english is therefore the (only) language of the watch :mad:

0 budish over 8 years ago

One bug I noticed yesterday was that I tried to load a course from GC in the running app. The routing mode was set to "Use Map," so the watch needs to process the file in order to identify and mark the course turns. I've done this a few times and each time this processing has seemed to take 20-30s. This time however, the map screen was on "calculating" for at least 3-4 minutes. What I realized is that while the watch is calculating the route, it is not yet "navigating" so if the calculation hangs (as it seemed to do) you cannot select "stop navigation" in order to give up or try again. I think the only way to stop the calculating is to start the run, stop the run, then discard the run. After I started and stopped the run (coincidentally, perhaps?) the calculation finally completed, so I didn't need to discard the run.

Also, a minor annoyance is that there doesn't seem to be a way to see the map while the run is stopped. That would be handy when you're approaching a confusing intersection or poorly marked trail and you want to stop running and look at the map more closely.

0 John Biruld over 8 years ago

Autolap is ON during personal Garmin connect training in running App.

0 b1azk0 over 8 years ago

When watch is set to metric units and a new LT pace is found, it is displayed as "pace value" / "mi"
I would expect to see this in a standard (metric) min/1km format

0 Former Member over 8 years ago

I've made an additional thread as I'm curious as to whether anyone's had the specific bugs I've mentioned. I've edited my original post here so people can simply list the bugs they are having on current firmware. For some reason, some user got awfully irritated by having two threads.

In regards to the other problems here, I will try replicate those faults.

0 iacchos over 8 years ago

Language setting (other than english) is lost (apparently) each time the watch is synchronized with GC Mobile --> english is therefore the (only) language of the watch :mad:

Fixed !! Actualy my setting in GCM was not correct (langage for F5X = english). But I suspect that the last version 2.9fw had overwritten this setting :-(

0 iacchos over 8 years ago

Bug with (Garmin) segments

See here : https://forums.garmin.com/showthread.php?372988-Fenix-5X-2-72-Beta-Release&p=973071#post973071
and here : https://forums.garmin.com/showthread.php?372020-fenix-5X-frozen-gt-Garmin-triangle&p=968857#post968857
(situation is better than with 2.72beta fw, but not ideal...)

0 2goBeyond over 8 years ago

Going to add an issue here. Stryd pairing with the watch is fragile at best, that goes with external sensors of all kinds (since 2.72 beta and now live). My own take is the aggressive trade over from the watch to the app via BT that is messing with other signals (no matter what they are). Just did a run, Styd paired, HRM-Tri Paired. Did about a mile and the run autosaved? That's the best I can explain it, didn't hit a button, but it saved after less than a mile. Lost pairing to stryd on the second run, though the watchface stated it was paired.

I've reported this to the beta team and they have been back and forth with me for over a week (watch BT disconnects that are being reported to the watch...by the BT connection???) chest strap not pairing until you update the connection of the watch to the app. Just a mess since that beta with external sensors.

0 FryeX over 8 years ago

I have only seen one dropout from stryd and it immediately reconnected within a minute. This was with 2.72 beta. No dropouts or no need to re-pair after the updates. If the issues with Stryd persist after reset I might try to get the watch switched. I have Stryd paired as a footpod and my runs use the CIQ data file for recording.

0 etparks over 8 years ago

Can't seem to initiate "pairing mode" -- manual says to hold light button and press select...does not work; only toggles Bluetooth on and off