Crash reports collection Q1 2026

sky-runner

@gkaempfer said:

Latest firmware 2.56.28. I believe that it happened when I receive an incoming phone call.

One of the crashes I experienced before 2.56.28 was triggered by an incoming text notification. So this might not have been fixed after all.

HonzaS

I got restart few days ago during walking activity and again it was triggered by incoming call. So it’s not repaired. Already wrote it HERE in Q2 hotfix topic.

isazi

@HonzaS send logs if it happens again and I’ll open a new bug report

HonzaS

@isazi Thanks! I will do that. I sent logs and chat with support, but it seemed to me, that they can’t create ticket. They recommended me for next time use help center/feedback through suunto app.

stromdiddily

@HonzaS oh man, I was hoping this was gone for good. I haven’t seen this for a month but have been taking some time off

sky-runner

@isazi Yet another crash today. It was clearly triggered by a received phone call notification on the watch. I’ve just uploaded logs using the feedback feature in the app.

Honestly, I no longer trust this watch! I think this was my 6th or 7th crash since I owned Vertical 2 (since April 2026). If there is no guarantee that these crashes will be fixed for good in the upcoming software update, I am done with Suunto! If it can’t be reliable during activities, nothing else matters!

HonzaS

@sky-runner It´s sad. I switch from Garmin because of these restarts. But I had to buy a Wahoo for cycling, because Suunto doesn´t support radar and some sensors.I also moved to intervals.icu because now I have two ecosystems. V2 was good for half year, but now I don´t trust it too. Hope that users will send logs in proper way and it will be fixed.
I have more activities on bike, records on V2 just for Zone sense, but on these rides I never had crash. It was while walking activity and cycling commuting. So for now, I have no logs to send. I also tried one whole day walk recording without GPS, but I had only one incoming call :-))).

Gergo

Dear All,
I have a Race 2 and I have the exact same problem… random reboots.
I received the second replacement yesterday, stil the same (after turning it on, did the phone pair (Google Pixel 10), watch FW upgrade to 2.56.28, customized a few things and after 1 hour during a phone call the watch vibrated breafly, Suunto logo appeared and it rebooted itself.
I cannot beleive that all 3 devices have a hardware defect… first one was manufactured on 2026 week 18, first replacement 2025 week 52 and the second 2025 week 51.

For me it seems that the reboot is not a full reboot, just some kind of module reboot because it seems quicker. But maybe it is just a feeling.
If reboot happens during an activity, the HR and elevation data is not recorded…

Does anyone know how to access the logs from the watch so I can take a look? Suuntolink does not work with Race2 as far as I know.
Thanks iadvance
Gergo

Egika

@Gergo there will be another fix FW soon, to address more known crash issues.

Woodster

@Gergo Hi - I get the logs via the Suunto VSCode extension - see comment here:

https://forum.suunto.com/post/200233

Hope it helps

Gergo

@Woodster @egika thank you both of you, will check soon !! have a nice day. Gergo

Gergo

@Egika my watch just had a reboot, grabbed the logs via VSCode. Is there an address where I can send the logs?
Thank you in advance
Gergo

elbee

@Gergo said:

@Egika my watch just had a reboot, grabbed the logs via VSCode. Is there an address where I can send the logs?
Thank you in advance
Gergo

You don’t have to grab the logs via VSCode.

How to send crash logs:

Open the Suunto App.
Go to your Profile.
Select Help, then choose Feedback.
Select your watch and describe the reboot issue.
Submit your feedback and follow the instructions in the app to send the battery logs.

Egika

@elbee said:

@Gergo said:

@Egika my watch just had a reboot, grabbed the logs via VSCode. Is there an address where I can send the logs?
Thank you in advance
Gergo

You don’t have to grab the logs via VSCode.

How to send battery logs:

Open the Suunto App.

Go to your Profile.

Select Help, then choose Feedback.

Select your watch and describe the reboot issue.

Submit your feedback and follow the instructions in the app to send the battery logs.

Is the reboot from @gergo battery related?
The battery logs are used to track specific unusual battery consumption cases.
Otherwise it makes sense to send logs from the profile tab -> settings -> Send logs to Suunto.
Then inform one of the testers in this forum by PN about the time and date logs were sent and the account email address.
Sending logs makes sense up to around 10h after the event in question. After this time, they will be overwritten cyclically.

elbee

@Egika said:

Is the reboot from @gergo battery related?

No it isn’t. I just copy past what I got from suunto support, changed one line but not the other. Thanks for pointing out. I edited my original post.

You don’t have to PN to the testers. You can also send an email to support@suunto.com. But there is no guarantee they can find the logs. They lost mine, and now they want me to resend the logs for an issue that happened 2 weeks ago. If only you would get a reference number after you send the logs, like every other company does…

Egika

@elbee said:

@Egika said:

Is the reboot from @gergo battery related?

No it isn’t. I just copy past what I got from suunto support, changed one line but not the other. Thanks for pointing out. I edited my original post.

You don’t have to PN to the testers. You can also send an email to support@suunto.com. But there is no guarantee they can find the logs. They lost mine, and now they want me to resend the logs for an issue that happened 2 weeks ago. If only you would get a reference number after you send the logs, like every other company does…

Right! you can also use the official support email. It is less personal and has less feedback than using the forum contacts we have here.