Watch Reboot During Activity After v22.10 Software Update

I'm on taper, shooting for a great performance in the near future, and I can't trust my equipment. An alpha build is even more likely to have issues.

I would absolutely love to help the Dev team at any other time but right now I just need my equipment to perform in a predictable manner.

I see Enduro users have the same problem

https://forums.garmin.com/outdoor-recreation/outdoor-recreation/f/enduro/285121/enduro-rebooting-during-activity

forums.garmin.com/.../system-version-22-76-watch-restarted-unexpectedly

So we can alnost certainly rule out music or maps as the cause as the Enduro has neither.

5135968 said:

So we can alnost certainly rule out music or maps

I agree. I tried yesterday again to reproduce a crash/reboot. I ran for 1h10, with a maps loaded, press lap every 5 minutes (something that I did in a interval training work out with 2 reboot) ....and nothing happened (I must say I was a bit disappointed). Not even a false training effect computed or the absence of results.

My bet is that music, maps are just stressing factor that increase the chance of triggering bugs...the latter could eventually, end out by a reboot...but they could also just change the value of some variable with less noticeable effect -> strange training factor behavior.

If Garmin could at least give some clues on the most heavy task for their watch (algorithmic complexity and memory requirement) we could describe settings that increase the chance to reproduce the bug. (And for those with challenge to come in the near future setting to avoid.

I just had my first random reboot outside an activity and with alpha 22.76. I was just browsing the details of the next day scheduled workout "Stride Repeats" and pressing start to obtain more details of a particular stage of the workout initiated the reboot. I will zip the contents of the whole Debug folder and send it to Chris. 

Same here. I was struggling to get rid off the "upgrade bluetooth connexion" message in my (android) garmin connect app. Suspecting this explain the inability to fetch workout on my stryd app (the one running on fenix 6). When at some point the fetch freeze, and when after 5 minutes I try to get back to the main menu, I got the "blue triangle of the death", followed by the "update logo" of the frustration.

The related log have been send to Chris yesterday.

Note I am still on 22.10 (seeking for reproducibility before testing any possible fix...), my exchange yesterday with Garmin stated that so far (6 days after release) no bug were reported on 22.76, so the issue I encounter was possibly fixed ! I believe I was not so wrong to be skeptical.

2930847 said:

I was struggling to get rid off the "upgrade bluetooth connexion" message in my (android) garmin connect app.

How did you get rid off it? Almost everytime I switch to app / open app I have a message about improved bluetooth connection. When I press to continue / start the process (sorry I don't know what is the button label in english version) it does nothing. Another annoying issue I experience while using Fenix..

Still no crashes although battery life has been abysmal since I moved to the Alphas.

I got 2 days with 22.75 and about 5.5 days with 22.76 with barely any use (no phone connection)

Or to put in another way, I had to recharge twice in under a week. 22.76 died during a non GPS activity that I started with around 17% as shown in the graph below 

(For outdoor team use for graph below: samples = 48755, gtime 1027456876 to 1027944125)

So I have pretty much screwed myself as in my experience when this happened with 19.20, its not recoverabe (unless I can still flash back to 15.20)

Ironically it has NOT crashed...but battery life has been destroyed.  Large post activity drain.

forums.garmin.com/.../large-battery-drain-100-to-5-in-48-hours

Really wish it was possible to get the last non public 19.30 baseline from 2021 as that was super stable with no altitude or sleep 'improvements'. I'd be happy to 'freeze' on that codeline personally. These recent firmware changes have not been worth the loss of stability and now battery life for me.

I am on 22.76. All my activities are with music. Two were with following a course, a few without navigation. No crashes until yesterday when the watch rebooted immediately on starting the course, without having started the activity itself.

BTW, where do I find the debug folder? Do I need to enable debugging?

Via usb go to \Garmin\Debug and copy RAM.txt and err_log.txt 

Upload them here and PM Garmin - Chris so they can be linked to your post above

supportforms.garmin.com/.../

Please also file a bug report for your reboot on the 22.76 alpha thread and also include those two files.