yet another crash during workout
-
@jtamj no, unfortunately not a thing
but… I had another crash
on saturday my watch did exaclty the same thing. I tried to zoom out map, watch wouldn’t react (rotating crown did nothing), then screen went blank, I was able to wake it up like 2 times (with significant lag after button press) and in the end it crashed… after about 450m of run…
no HR belt this time, so I guess it’s not BT/HR related
-
First crash for me yesterday during a treadmill run, after about 50’, just when a notification popped up…
-
my race 2 crashed again today. i’m on a roll, it’s every other GPS workout now

-
@mich-heller I would suggest to wait for next firmware update, and if it happens again with the new firmware, we’ll forward the bug to Suunto
-
I had a crash on my Race 2 two times.
- One it was during my workout at the very beginning. I used HR belt and didn’t use any map or track.
- Second one was today during my long run with map and track screen active. I haven’t look at the watches at the time of crash. I just felt a vibration (which it has during startup). Looked at the watches and saw the booting logo.
It is very annoying during training, but during race (especially long trail run) it is not acceptable.
Does anyone know how can I get and send crash log to Suunto for investigation?
-
@newegor https://www.suunto.com/en-gb/Support/faq-articles/suunto-app/how-to-send-diagnostic-logs-on-suunto-app/
Note: Your watch needs to be paired with the Suunto app.
Open Profile in the app.
Open Settings and scroll to the last section of the view.
Tap the Send logs to Suunto option and then confirm if prompted.
You will see the notification Sending logs to Suunto until the logs are successfully sent. This may take several minutes. Please do not close the app while the notification indicating that logs are being sent is visible. -
@mich-heller as far as I know, sending logs if you are not instructed to do so, or if you are not reporting a bug here, is not useful, as no one will receive and see them.
-
@isazi
I was always wondering how does it work 
so how does it work exaclty beside exact request from team? if I create thread with bug report like this one, does it make sense to send logs? because I’m doing it after every crash
-
-
I did a run yesterday. It was a 16.5km run, and my watch rebooted total of 3 times. Each time it happened , I had to start a new workout and now I have 3 workouts instead of 1. This is so unacceptable. I am not sure if the watch can handle the background load as I had 3 Suuntoplus turned on, with messages coming in at the same time. But even then this should never have happened . Not just on my race 2, it happened with my previous race as well as Suunto run as well. Such things have never ever happed on my coros, polar or Garmin . I think Suunto really has to work on their software part an prevent such rebooting from happening. If background load is indeed the issue, then they have to work on that part . Just so disappointing! Btw I have already contacted support and also uploaded my logs and they are looking into it .
-