Fenix 5x 2.90 software bugs encountered please answer if you get them too

How many threads are you going to start about this? Also, the search feature can be your friend if you let it be

How many threads are you going to start about this? Also, the search feature can be your friend if you let it be

The other thread received a load of posts about bugs people encountered. I fail to see the relevance in their answers, nor do I see the relevance in yours. Your futile attempt to correct my netiquette might look less hypocritical if you answered said question. Does the bold writing not show up for you? Perhaps you'd like it bright red? Let me know, thanks.

So asking it in multiple threads isn't at all annoying and will yield different results. Got it..

But hey, I'm "off topic" so to answer your original question(s) - NO (bold so the answer to your question is easily identifiable to the masses)

So asking it in multiple threads isn't at all annoying and will yield different results. Got it..

But hey, I'm "off topic" so to answer your original question(s) - NO (bold so the answer to your question is easily identifiable to the masses)

I'm not interested in what you have to say; you are a hypocrite, I don't take moral lessons from bad people. I won't be reading/responding to you further. You are now blocked.

I'm not interested in what you have to say; you are a hypocrite, I don't take moral lessons from bad people. I won't be reading/responding to you further. You are now blocked.

I'm truly sorry to have invaded your "safe space" on the forum. Carry on

I have noticed these errors. Can you please tell me if you experience these too?

• 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. This thread is specifically about these bugs, please use the other if you want to list general bugs you've been having since the new firmware.

Hello

I tried to replicate these issues, using your methodology. I could not get the watch to crash or misbehave in the same manner you have. I would try resetting back to defaults and see if the issue persists. If it does, you may have a hardware problem.

Thank you! In case it requires a specific order to replicate the crash, this is exactly what I pressed --

Start button
--> Navigate
--> Courses
--> Select a course
--> Do course (but do not "start" course with the "start button")
--> Press the down button a few times to scroll through the data fields
Hold the menu button
--> Navigate settings
--> Data screens
--> Down button a few times
Back button repeatedly until I got back to the watch face
Down button a few times to scroll through the widgets and then the back button to go back to the watch face

This usually results in the watch face showing the second hand moving as normal but the buttons cease to do anything. If it doesn't crash by that point, I can open the "save location" app and exit it, then open the "walk app" and exit it, then repeat the above with the navigation app, wait five minutes and it'll always crash shortly after.

I've already reset the watch once and it's annoying if I have to do a hardware reset every watch update, but I guess I should be thorough. I'll try again and see how I get on.

The watch does not seem to crash if I load a round-trip course or I set the watch to create a course based on a given location. The crashing only seems to occur with imported courses. If it were a hardware fault, I don't see why it would be selective.

I emailed the Garmin beta test email and the response from them was much better. They have said to press the "backlight then back then backlight then back" as a means to get the watch to turn off, but it doesn't seem to work. As such, I'm unable to give them a usable error log. Does anyone know of another method to shut down the watch when it crashes? Holding the backlight button works but that forces it to turn off instantly and does not write usable information to the error log.

As a get me by, I have started a course as per the instructions above, waited a minute (hopefully long enough for a problem to show up but not long enough for the watch to cease functioning altogether), I then shut down the watch and sent the error log. There is indeed something in the error log, so hopefully it caught the problem!