Suunto 9 Baro crashes / restarts at the beginning of a training
-
@jussim Well, clearly is your S9B, all my runs are in the mornings and I never had a crash, I have had other issues but never a crash.
-
@cosme-costa At least these have always happened with the “lesser” morning jogs only. I’d be doubly pissed, if the actual workouts end up being sabotaged by S9B!
-
@jussim One question, the issue is always happening in the morning? First run in the morning?
Before the run, did you see the “sleep summary” screen in the watch?
I had one issue with that, when I haven’t seen the “sleep summary” screen and I start a new activity: the pre-activity menus are empty, without letters…
Next morning, be sure to see the ‘sleep summary’ screen and sync the watch with App before the activity. -
@jjpaz said in Suunto 9 Baro crashes / restarts at the beginning of a training:
@jussim One question, the issue is always happening in the morning? First run in the morning?
Before the run, did you see the “sleep summary” screen in the watch?
I had one issue with that, when I haven’t seen the “sleep summary” screen and I start a new activity: the pre-activity menus are empty, without letters…
Next morning, be sure to see the ‘sleep summary’ screen and sync the watch with App before the activity.Funny that you should mention sleep summary, that morning I did in fact receive it after finishing the run. I had no idea that you might be able to start an activity without first acknowledging that summary! But I do sync with the App always before the run. It’s a routine every morning, along with syncing sleep data from Oura ring.
I do remember crashes happening on afternoon runs too, for example once or twice it happened after I had ran some 14 km of the planned 17 kms. But for whatever reason, more than 9/10 times it’s the mornings jogs.
-
My Suunto 9 has been in my drawer for a couple months and I decided to take it out and play around with it. Wanna know what it did when I set up an activity with no apps or sport profiles? Ding ding ding! Crashed! We might as well throw these things in the garbage.
-
My Suunto 9 has been in my drawer for a couple months and I decided to take it out and play around with it. Wanna know what it did when I set up an activity with no apps or sport profiles? Ding ding ding! Crashed! We might as well throw these things in the garbage.
-
@TyreseJ4
despite double entry, I respond only once, hope that’s fine
if you could do me a favour, please sync and send logs and pm me.
S9B crash was a topic some months ago and should be solved with latest FW -
Once again. I still wonder if it’s storage related, surely there’s a reason new firmware stores only about 20 hours worth of activities? I’ve taken a custom to observing watch right at the start and this crash happened within first steps. Screen went black and watch restarted.
-
@jussim Just to verify: try to delete all the old activities or perform a factory reset. That should free storage if that is the problem.
-
@jjpaz said in Suunto 9 Baro crashes / restarts at the beginning of a training:
@jussim Just to verify: try to delete all the old activities or perform a factory reset. That should free storage if that is the problem.
Sure thing! I haven’t done a factory reset yet because I find it a bit too much of a chore to set things up again. But maybe at one point. In the mean time I’ve been experimenting with deleting older activities: trying to find out the point at which the watch starts removing old activities and trying to stay “ahead of it”. Haven’t been too successful, it would seem like…
-
@jussim said in Suunto 9 Baro crashes / restarts at the beginning of a training:
… this crash happened within first steps. Screen went black and watch restarted.
Exactly the same happened. Within first steps, before the activity was showing heart rate, the watch went blank.
-
Oh wow, yet another one and so soon, too. Jesus Christ this is killing me.
-
@jussim I have been following your painful travel here. All I can think of is that you must have a defective unit. No-one else seems to be experiencing this.
I will try a few activities with my old S9B (if the new owner agrees to borrow it…) next week and see if I can reproduce it.
-
@BrunoH
@jussim
I was using my S9B few times during summer and autumn and never had a crash.
I start to think it could indeed be an isolated defect and not a firmware bug.living sideways
-
@freeheeler My son’s S9B just did an awesome job on a 8km hike. With single band GPS it recorded just 20 meters more than Vertical and the difference in steps was only 60. I won’t go into other details as the personal details stored in the watch were not mine and Vertical was connected to HR belt.
No crashes, but there was a loooong UI lag after I returned from the activity to the watch display and tried to scroll down to HR display. No HR but blank screen. I doodled for a while and somehow it woke up.
-
Dears, I just want to assure you that this is not an isolated issue. Me myself have reported many crashes and provided logs for lots of them. I am still experiencing restarts. I am just not reporting each and every one here on the forum. Problem was noticed by Suunto and I read in one of previous posts that fix shall come in next FW update.
Best way how to avoid crash is to do a soft restart in the morning and the sync the watch then. That works for me and this is the way how I am securing my key trainings or races. I forget from time to time. My watch are so sweet that they remind me that I forgot to do a soft reset. Guess how…?
Have a nice day and keep high hopes for next FWSuunto S9 Baro Titanium, Ironman l.e.
Suunto Smart Sensor
Wahoo Tickr FIT
Hammerhead Karoo 2Swim Ride Run Rest Repeat
-
@zadow Wich software version are you using? Latest?
Have you tried to downgrade to a previous version to check if the reboots dissapear or, at least, become less frequent? -
@zadow Thanks, that is all kinds of assuring
I guess I’ll be doing that in the future! First though I’m going to see how far I’ll get after doing a factory reset. -
After the last upgrade, I also experienced numerous restarts, which forced me to downgrade and use older but more stable firmware. Since then, everything has been fine.
-
Guess what, five days after the full reset and after eight runs, this happened again. Sheesh.
