S9P crashing randomly

Brad_Olwin

@DF130 Delete the custom sport mode and remake it, perhaps it is corrrupted

jjpaz

Today I have suffered one watch reboot during activity.
First time in 13 months using S9P.
When I have arrived at my activity finish point I saw the watch in the time screen.
Activity was saved partially: track, heart rate, etc. Altitude numbers weren’t saved but altitude graph is in the App.
Looking at the track and map in Suunto App the reboot happened just 300m before the finish (activity was 9.7km and 58min long) when it was planned 10K…
I have sent watch registry to Suunto in the App.

isazi

@jjpaz if you sent logs, send me a message with the time you send them and your email, and I can open a ticket with Suunto.

jjpaz

@isazi perfect, I have sent you the info.
Hope ir helps
Thanks!

DF130

@DF130 Just as an update, deleted and re-built the custom running mode, but had another crash a few mins into my run. Could start a new activity, though, which was an issue with previous crashes. Anyway, hard reset it is… And a happy New Year everybody!

jjpaz

The problem has happened to me again.

I have started activity (this time with S9B in one hand ans S9P in the other). At 3km, I feel the S9B vibration but S9P doesn’t vibrate (autolap), the display was on time screen.
The last time was around 4 weeks ago, perhaps is memory getting full in that period?

S9B has worked perfect. I’m a little bit dissapointed with the “little” problems of S9P since last year.

Registers sent to Suunto (via SuuntoApp) at 14:12. Issue was at 13:29.
Hope developers could solve the bug.

jjpaz

@isazi NEWS! I have noticed this in the activity file:

TrainingPeaks:

Selección_691.png

Intervals:

Selección_692.png

Heart rate stops measuring seconds before the reboot. Perhaps it’s related or can help developers.

From the first 0 sample until the end: 16 seconds.

I have checked my other failed actitivity, same behavior: hertrate drops to 0 then watch reboots after 16 seconds.

isazi

@jjpaz I will report this, I think I have your email in PM already.

isazi

@jjpaz said in S9P crashing randomly:

The last time was around 4 weeks ago, perhaps is memory getting full in that period?

I don’t know, my watch is active from July 2021 and never crashed, but developers are investigating this issue.

sartoric

@jjpaz said in S9P crashing randomly:

NEWS! I have noticed this in the activity file:

Oh, you died …

jjpaz

@sartoric

New S+ feature!!! Autosave when died!!!

jjpaz

@isazi Yes, you have my email and username.
If developers need more info you can contact me, no problem.

Do you perform soft resets periodically?
Perhaps soft resets “clean” memory and avoid the issue.

freeheeler

@jjpaz
I don’t do that on a regular basis. only if I have the feeling the watch is having issues… which is very rare in my case.

jjpaz

Is very interesting start analycing .FIT files.

These are the last entries in the “after crash” .FIT file:

= TYPE=5 NAME=record NUMBER=20
--- timestamp=1043065778=2023-01-19T12:29:38Z
--- position_lat=481284491=40.3408000 deg
--- position_long=-45354435=-3.8015648 deg
--- distance=273400=2734.00 m
--- altitude=5907=681.4 m
--- cadence=86=86 rpm
--- speed=2920=10.512 km/h
--- temperature=17=17 deg.C
--- vertical_speed=0=0.000 km/h
==
= TYPE=5 NAME=record NUMBER=20
--- timestamp=1043065779=2023-01-19T12:29:39Z
--- position_lat=481284644=40.3408128 deg
--- position_long=-45353938=-3.8015232 deg
--- distance=273700=2737.00 m
--- altitude=5907=681.4 m
--- cadence=86=86 rpm
--- speed=2920=10.512 km/h
--- temperature=17=17 deg.C
--- vertical_speed=0=0.000 km/h
==
= TYPE=9 NAME=record NUMBER=20
--- timestamp=1043065780=2023-01-19T12:29:40Z
--- distance=274100=2741.00 m
--- altitude=5906=681.2 m
--- cadence=86=86 rpm
--- speed=2920=10.512 km/h
--- temperature=17=17 deg.C
--- vertical_speed=0=0.000 km/h
==
= TYPE=10 NAME=lap NUMBER=19
--- timestamp=1043065780=2023-01-19T12:29:40Z
--- start_time=1043065462=2023-01-19T12:24:22Z
--- total_elapsed_time=318307=318.307 s
--- event=9=lap
--- event_type=1=stop
--- lap_trigger=0=manual
--- total_timer_time=318307=318.307 s
==
= TYPE=0 NAME=event NUMBER=21
--- event=0=timer
--- timestamp=1043065780=2023-01-19T12:29:40Z
--- event_type=1=stop
--- timer_trigger=0=manual
==
= TYPE=0 NAME=session NUMBER=18
--- timestamp=1043065780=2023-01-19T12:29:40Z
--- start_time=1043064862=2023-01-19T12:14:22Z
--- event=8=session
--- event_type=1=stop
--- sport=1=running
--- first_lap_index=0=0
--- num_laps=2=2
--- min_heart_rate=95=95 bpm
--- avg_heart_rate=130=130 bpm
--- max_heart_rate=144=144 bpm
--- avg_speed=2980=10.728 km/h
--- max_speed=3180=11.448 km/h
--- total_timer_time=918400=918.400 s
--- total_elapsed_time=918401=918.401 s
--- total_distance=274100=2741.00 m
--- max_altitude=2850=70.0 m
--- min_altitude=2840=68.0 m
--- training_stress_score=102=10.2 tss
==
= TYPE=0 NAME=activity NUMBER=34
--- timestamp=1043065780=2023-01-19T12:29:40Z
--- num_sessions=1=1
--- type=0=manual
--- event=26=activity
--- event_type=1=stop
--- local_timestamp=1043069380=1043069380
==
# CRC: expected=0xE833, calculated=0xE833

We can see the last samples (without heartrate nor HRV, last 16 seconds) and at the end we can see a “STOP” event.
So it seems that the watch stopped itlself the activity and then reboots, is that correct?

= TYPE=0 NAME=session NUMBER=18
--- timestamp=1043065780=2023-01-19T12:29:40Z
--- start_time=1043064862=2023-01-19T12:14:22Z
**--- event=8=session
--- event_type=1=stop**
--- sport=1=running
--- first_lap_index=0=0
--- num_laps=2=2
--- min_heart_rate=95=95 bpm
--- avg_heart_rate=130=130 bpm
--- max_heart_rate=144=144 bpm
--- avg_speed=2980=10.728 km/h
--- max_speed=3180=11.448 km/h
--- total_timer_time=918400=918.400 s
--- total_elapsed_time=918401=918.401 s
--- total_distance=274100=2741.00 m
--- max_altitude=2850=70.0 m
--- min_altitude=2840=68.0 m
--- training_stress_score=102=10.2 tss

==
= TYPE=0 NAME=activity NUMBER=34
--- timestamp=1043065780=2023-01-19T12:29:40Z
**--- num_sessions=1=1
--- type=0=manual
--- event=26=activity
--- event_type=1=stop**
--- local_timestamp=1043069380=1043069380
==

DMytro

@jjpaz I think so (too lazy to check the code tho), but its a feature built into suunto watches, s.t. no matter what (i.e. battery dead/crash/etc) the activity is saved.

isazi

@jjpaz never a soft reset, but sometimes if I have to travel by airplane and carry many watches in my luggage I turn the watch off.

Ketoohs

Today during the night my watch crashed (it was the second crash in about a year (first one was about half a year ago) , and when I woke up it said it has recovered…
The problem was, that it did not wake me, as alarm was removed…

@isazi I sent logs at around 6:00 AM CET…

Dimitrios Kanellopoulos

@isazi can you PM me on teams the TP?

isazi

@Ketoohs send me a PM with your username on SA.

DF130

@DF130 Latest update, managed a hard reset and reconfiguration, but that did not help either. Now I am just using the stock running mode, so far no issues (and not with any other sports, where I admittedly only use stock modes). So somewhere between custom modes (or the specific customisation I had chosen, “target” screen maybe?), S+, and a bunch of sensors (Suunto heart rate belt and Stryd), the conditions for a crash seem to develop…