This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Crash and bootloop at start race

Hi,

Yesterday I finished a half marathon with my Forerunner 955. However, when crossing the starting line I started the run activity which instantly caused the watch to crash to a black screen get stuck in a boot loop. I spent my first kilometer or so with my phone fiddling with the settings until I found that the watch would exit the bootloop when turning off the event sharing feature. I also had PacePro and Livetrack active, these didn't seem to give any problems later on.

After disabling it the watch started as normal and I could finish the event, although I missed the track misses the first part of the race (and my PR Disappointed).

For info: I'm running version 22.24.

  • Same happened to me today twice Disappointed

  • Do you think it was the "Event Sharing" feature which caused the crash?

  • same here. had the problem when testing out Live event sharing just before marathon day. the Garmin community on Reddit forum seems to suggest also this feature is the problem and it is basically unusable. Sad, really that a feature that is so useful just doesnt work and crashes the watch. I had to hard reset the watch and reload the backup for it to work again,

  • I had basically the same thing happen to me at the start of a race 3 days ago. It would show a blue triangle then say something about live track or event starting (can't remember which since I was actively running and it was switching screens quickly) then it would go blank as if it was off and then finally show my regular watchface before starting the loop again. The first thing I tried to get it to fix itself was to power it off, but it wouldn't power off. So then I turned off LiveTrack and Live Event Sharing and synced my watch. That fixed the problem and I was able to record the rest of my race. My watch is a Forerunner 255s and it is also running version 22.24.

  • Look at beta 23.18 out today seems to have a fix