Serious Bug SW 4.19 - update: partly solved. GARMIN (!) see my comment below

My 965 has never randomly reset.

I use Walk, Run, Bike, Bike Indoor, Pool, Strength, Cardio, HIIT.

Any particular activities that cause the issue?

Are you on the Beta-Program? With the old SW 3.58 I also didn't have these issues. It mostly happens with Run, Multisport and Walk - but also occurs sometimes with Yoga.

i am in the beta program and i had never random reset/restart (cycling, walk, and everyday since 1,5 month for sure). Do You have ConnectIQ app installed? or try to do a master reset in the watch , repair /re-set everything MANUALLY (sensors, settings, datafields, everything) and try it again. if doesnt help, call the support for a replace

MarkusD said:

Are you on the Beta-Program? With the old SW 3.58 I also didn't have these issues. It mostly happens with Run, Multisport and Walk - but also occurs sometimes with Yoga.

I use to be on the beta program back when I had a fenix 6X, I found it caused more issues than it was worth.

I gave up and stuck with official release firmware from then on with the fenix 7X, Epix 2 and now the FR 965.

I am also in the beta program and i also never had ever been this problem on any of the betas. 

Luko79 said:

i am in the beta program and i had never been random reset/restart

Well, Garmin had randon reset/restarts. Just one line from the changelog:

• Fixes an issue that could cause the device to reset at random times.

and there are more in the changelog. We all know garmins mediocre software quality, so it doesn’t surprise me when not all bugs are fixed. Most likely they introduced new ones.

1) For me personally I can say that 4.19 was a huge quality of life improvement, on 4.15 I often had restarts during activities, especially when also using navigation and when looking at the map. The most was during two 5 and 6 h hikes I had around 10 restarts in each activity! So far I have not had these restarts during activity anymore, even though I have done long activities with navigation and map screen open to try to trigger it.

2) Is 4.19 perfect and has no more crashes? No, surely not - in fact I reported one on activity save (for me it was when I accepted a new threshold). So definitively report any crashes you got on the beta forum, and provide your RAM.txt file via the secure upload.

3) Is Garmin ignoring the reports in the beta forum? Maybe - at least they have nobody answering/acknowledging the reports. But I think that there might be some developers that check for serious reports (like crashes), and look at the RAM.txt file, and fix it for the next Beta release, even if they never bother to actually respond to the reports and say they fixed it. At least that could be the reason for the 4.19 random restarts fix, as I reported at least two of them, and others reported similar things.

I've had nothing but terrible experience with the FR965 so far! Yesterday the watch reset itself on the first kilometer of a 95km ultramarathon and created an activity of type multisport which lacks all the metrics of a normal run or trail run so I can't peek into the data. This has also happened on a couple of training runs. Also, I caught the watch stopping my activity mid-run without me pressing any buttons. I am thankful that I heard the sound and took a look, otherwise I would have continued running with the activity stopped and I would have lost track of the distance that I've covered. My old trusty Fenix 6X Pro hasn't had any reliability issues. Garmin, this is a complete and utter failure on part of your software teams! Brands like Coros don't churn out a watch every year and don't release a half-baked product just to compete. Fix your damn products, I'm not getting paid to be your beta tester!!!

Today my fr 965 crashed during a track activity. I pressed lap at the start of a 200m interval. At the end, my watch was dead. Had some serieus problem getting it on again.

Well.. gonna file yet an other bug report.

It seems that I have found out what the problem with reset/restarts after saving activities is. The problem occurs regularly - and can be reproduced without any problems - when I press the "Back" button after saving an activity in order to return to the normal watchface. I have also tried different watchfaces to make sure that it is not a specific watchface causing theproblem. That was not the case. Then I remembered that I have defined the "back button" as a "hotkey"  to takes me to the watch view "display design". I used to have this with my 955 and it worked without any problems. I have now deactivated this on the 965 (hotkey back button "Off") and behold: the watch now behaves normally and no longer resets/restarts.
So it is obviously a bug in the software. Please take care of it! Thank you.