Crash & Reboot During Activity :(

[Nigel Taylor 0]

Happened today, in flight mode, following a 25k route (pushed to SA from Plotaroute via QuantifiedSelf), in ‘good’ mode.

Only 3.79km in, just coming up to second RoutePoint and the vibration seemed odd, glanced at Watch and it said “Suunto 7” on screen, and was going through reboot process.

After waiting for Watch to restart, I opened up the Suunto App again, and it seemed to never want to find a lock, just showing the greyed out arrow with line through it, a couple of miles away from where I was (nowhere on the route)…but when I got bored of waiting and decided to just click start, it immediately had a lock and showed me in correct place on map.

Was a bit wary checking watch at every km notification and the 3 or 4 RoutePoints reminders I had set up, in case was another crash, but the continuation of my run was tracked just fine. On getting home, the two parts both synced and I was able to merge them and no data is lost, so all good, its not as though I was tracking a race and lost time.

What I have noticed, is that when I created and exported the route from Plotaroute, (with the POI’s option on WayPoints, so it only includes the directions I’ve added myself)…the RoutePoint that I crashed at, I’d inadvertently added my instruction text as a “LABEL”, so the direction text was the quite lengthy, “Turn right onto New Hey Road, A640” default that was already there…whereas every other point I’d added, I’d just put the text I want to see in the ‘directions/notes’ field…and then I just add a symbol to tag that I want that POI to be included as a notification.

So…is adding LABELs potentially a bad thing, or was there perhaps some buffer over-run because of the long description??

Here’s the source route…
https://www.plotaroute.com/map/1503782

If you click to view directions you can see the big list of default directions, and the ones I’ve used have the little blue man symbol on them…the watch crash occurred close enough to that second turn instruction as to seem significant to me.

What I also discovered is if you’re doing a 25k route, but start your watch from 0 a few km’s in, the run doesn’t seem half as far!!

[isazi]

@nigel-taylor-0 if the issue is the long label should be easy to have it repeat, and if it’s repeatable then someone at Suunto can have a look at it.

[Nigel Taylor 0]

@isazi said in Crash & Reboot During Activity :

@nigel-taylor-0 if the issue is the long label should be easy to have it repeat, and if it’s repeatable then someone at Suunto can have a look at it.

Hopefully someone at Suunto sees this and runs a quick test.

[Nigel Taylor 0]

Another Watch crash whilst following a route today.
No “large labels” this time and the crash didn’t coincide with a notification as it did last time.

In best mode, with airplane, no phone.
10mile route with six route points defined in plotaroute and xferred to Suunto via Quantified Self…crashed after only about 1.5miles…felt an unexpected short vibration, looked at watch and it was going through reboot.

After recovery…took a longish time to get a gps lock (it put the arrow with the line through it back to where I’d actually started from for a while)….but then navigated the remainder of the route just as solid as usual.

Both bits of the route got synced after I reconnected to phone, so just combined them with GoldenCheetah and all good.

Is there a way to merge the two activities in Suunto land?

Any ideas on how to avoid this crash whilst navigating? ‍️

[eurohiker]

@nigel-taylor-0 happened to me on 2 different watches. Only happened on 10km+ hikes though and for me it’s typically an anomaly ive done 30+hikes with the watches. It’s annoying that it saves to the diary and you cannot resume it like you can with Strava.
Any tech item is subject to crash at one point, a safeguard is a priority in my eyes.

[Brad_Olwin]

@nigel-taylor-0 I am not having crashes but will continue to test. I have very few apps installed, it might be an app that is interfering somehow.

To merge activities you can use a web tool, then upload to QS and send the file to SA. Or, on Android SyncMyTracks might work? On iOS RunGap will sync to SA.

[Nigel Taylor 0]

@brad_olwin said in Crash & Reboot During Activity :

@nigel-taylor-0 I am not having crashes but will continue to test. I have very few apps installed, it might be an app that is interfering somehow.

To merge activities you can use a web tool, then upload to QS and send the file to SA. Or, on Android SyncMyTracks might work? On iOS RunGap will sync to SA.

I have no apps installed.

I’m ok merging, I just combine the activities in GoldenCheetah as I use that to grab the offline sync from my Stryd and merge that also.

It’s just the pain of waiting a couple of minutes for the watch to reboot, and then what seems like a slow GPS lock after reboot, and then having to run without knowing how far I’ve covered unless I happened to notice relatively close to the crash.

Its not a massive deal, only happened twice…but when I’m using watch for navigating is the time I’m least wanting a crash!

[Brad_Olwin]

@nigel-taylor-0 The watch should not crash! period. To help, immediately after the crash send logs to Suunto and copy Dimitrios here, note the time that the crash occurred in the post here and when the logs were sent. As I said, on production firmware I have 0 crashes, had quite a few during testing but perhaps something was missed.

[A Former User]

Today it happened to me for the first time. I was recording a walk (airplane mode, 10s + FT, locked buttons) the watch vibrated and immediately restarted. Fortunately, the recording was saved.
Later at home I realized that several settings were changed after that hiccup, e.g. Touch-to-wake was off (it was on) and Power saver tilt was on (it was off). Weird.

watch updated to PXDZ.210716.001.A1
no further apps installed

[Martin Vrska]

@walker The last time it happened to me, I had the same thing.

[cicciorunning]

It also happened to me a couple of times during the recording of the run … but yesterday while swimming in the pool, it stopped constantly, I restarted it … shortly after it turned off and now it does not turn on anymore. … I also tried to connect to the charging cable but the same thing happens, the Suunto 7 logo appears for a few moments then black screen and intermittent vibration … Any idea?

[DMytro]

@cicciorunning water damage maybe?

[Brad_Olwin]

@cicciorunning It could be a bad cable. I would try another cable and then contact support.

[Jm0n12]

@brad_olwin

[Jm0n12]

@brad_olwin There was a malfunction while using the treadmill, airplane mode and after 20 minutes the watch reset. After starting, the record was saved.