Fenix 7 Crash / Reboot while Navigated Activities

+ 1 for  sw16.22

and +0.75 :-) for sw18.16

I haven’t used navigation in a while. Doing a long trail run tomorrow and planning on navigating a course. 

im on 20.22. Is this still crashing for people on the latest? Is it reproducible or just randomly will crash?

Seems like there is a mix. I used to get crashes on 19.xx when navigating but yesterday did 3.5 hours run with navigation and it didn't. This was a first one on 20.22 for me. So who the heck knows.

IMHO they fcked something up with the update process itself and it’s keeping files it shouldn’t which causes the issues, since it appears to be completely random which device has issues and which doesn’t. It’s not like every user has the same problems, but I don’t own the watch to gamble. It shouldn’t depend on luck wether you’ll have a properly working 700$ watch or a 700$ paperweight after updating.

I know that it’s always possible to downgrade. But in the first place it is not intended and second of all it is only possible if someone offers you a link to the older firmware and last but not least it is a big hustle, it is annoying, it wastes my time. 

IMHO it is absolutely ridiculous. Why don’t they only release a firmware update every half year or even less. I would be completely satisfied, if it would at least be without bugs.

No crashes on 20.22 so far. I had roughly 12 hours of cycling activity with navigation.
So it kind of looks good. There's one catch though: I changed the way I'm creating routes from "popularity" to "follow roads" in garmin connect.

Theoretically I could try to create a route with "popularity" to confirm my hypothesis but I just can not tolerate those reboots any more. 

duksomi said:

I can recommend 16.22… never have an issues with WiFi, music streaming, workouts, navigating. All works fine. Good luck to y’all.

OFFTOPIC

Hey,  there must be a Garmin curse. Just hours after I said hallelujjah for sw 16.22 realized there was a bug with this version,  too.

Could you please check whether your watch shows the same bug? If WHR is set to ON, but does not find your pulse, because it is eg. on the sleeve of your jacket then GESTURES does NOT work.

forums.garmin.com/.../1912663

duksomi said:

It’s not like every user has the same problems, but I don’t own the watch to gamble. It shouldn’t depend on luck wether you’ll have a properly working 700$ watch or a 700$ paperweight after updating.

Exactly. It seems that their software is so complicated that bugs are completely random, and they do not solve problems, only specific cases.

How to explain that one person during 4-5 hours of activity performed regularly, has no problems, and another person during the same activity (and probably with the same settings in watch) lasting 1 hour the watch restarts twice.

Apart from many strange behaviors of Garmin as a company and approach to customers, they should deeply consider hiring a group of good programmers to rewrite the software to be bug-free and above all stable.

I simply tell you that if I find a bug which is repeatable and all my settings on the watch is available for Garmin per request, it is just a question of good intention & brain capacity to eliminate it

Or if  Garmin call my finding not a bug, just a feature how stupid one is to call something a feature which hinders the users not helps him.

I even may consider to beg for a time slot for a chat with someone from Burrell family to explain that they should focus not just the aviation business line. 

To be honest I am shocked about the realization pf how muxh impact the late Gary Burrell must have had while he was active in Garmin’s everyday’s operation.

Code quality there is a disaster.
Every company goes the same rabbit hole these days...

I used the V20.22 and completed the activity without any reboot incidents. Will let you know if they return