Forerunner 970 crashes during races and training – anyone else?

Hello Garmin-Hannah, I already contacted support and sent all the information about the crashes.
You should find everything in my profile. My watch was replaced, but the new one exhibits the same behavior.

1. Germany

2. 13.8. Map+CIQApps+Music, extrem laggy, no crash

   17.8. <=17km Map+CIQApps, without Music: laggy, but so-so, no crash       >17km Map+CIQApps+Music, extrem laggy, crash at 22km

   19.8. Music+Map, without CIQ-Apps: laggy, but so-so, no crash

3. Only Runs, Short and Long. I can't see any temporal logic as to when crashes become more likely. Laggy Maps from the first second on.
4. Yes
5. You will find these Information in my comments here

Hi,

I also experienced issues during my first runs, with frequent crashes and display freezes. It seems that version 12.70 brings many improvements.

I suggest updating your watch to run some tests.

Tuonoman 

I had my first "freeze" of my 970 yesterday while during a 4-hour trail run. 

1) was 3 1/2 hours into the run

2) playing music to earbuds from Spotify on the watch

3) had the map displayed on the watch

4) hit lap with 2 miles to go in the run and the lap message never appeared and the watch froze

5) Spent several minutes trying to get the 970 to restart

6) After the 970 finally restarted it allowed me to "resume" the run

I did update this morning. So will see the next time I do a long run. Again it is only occurred once.

Hi Garmin-Hannah,

I installed 12.70 yesterday and did a 12 km run today with CIQApps, navigation, music, and a training plan. The good news: there were no crashes. The bad news: the responsiveness is the same as before. Navigation was unusable because the map wasn't displayed or wasn't displayed completely most of the time. The training plan notifications on the headphones sometimes didn't appear or were too late. The display just seemed sluggish, as if the CPU couldn't keep up.

I'm just worried that the CPU might be overloaded at unpredictable points (due to too many parameters being involved) (e.g., the stack fills up) that it might crash again sporadically and unpredictably.

I'll do another longer run on Sunday and report back.

Thank you so much for taking the time and reporting back on this. Good to know that you were using a ton of other features with it. I can report your findings to the person who is looking at the case and see what he says about it. 

Hi Garmin-Hannah,

Good to read that someone is taking care of this. Thanks for that.

Today's long run unfortunately led to the crash again. 11km without music with CIQApps and navigation were OK, when switching to the navigation page it took about 7 seconds until the map was displayed. Hmm, but OK.

From km 11 I turned the music on. Switching to the map takes about 45 seconds until the map is displayed. Then the map slides out of the screen again while I'm running and is only redrawn every 5-10 seconds. Impossible to find your way with it.

Crash at km 22, reboot. When I continue, the two CIQApps are replaced by a clock and the music can be started again. When I switch to navigation it now takes about 10 seconds until the map is displayed.

For me it currently looks like this: Either music or CIQApps, my fr970 can't do both at the same time. The predecessor, the fr965, has no problem at all with the same configuration.

I'm now going running with my FR965 again, and to illustrate the problem, here's a comparison. With the same configuration as my FR970 — music, the same CIQ apps, and navigation + training plan — when switching to the map, it takes 2-3 seconds for the map to appear. The map refreshes approximately every 1-2 seconds.

Why is the FR965 15 times faster than the brand-new FR970, and the FR965 doesn't crash either?