Watch crashed mid activity

olymay

Title says it all really, my S7 crashed during a run today. This was the first crash (or even hint of a wobble) since the update at the end of 2020. In fact the watch has been so stable recently that I initially thought it was user error.

The crash happened during a trail run, as I was using the middle button to switch screens. This is something I often do during a run, so is nothing new.
As I switched past the altitude graph, it stalled and hung, and would not let me progress to the map screen. I could back out of the Suunto App and get back into it, but it was slow and kept sticking on the graph.
Eventually it crashed out and gave me a warning that activity tracking had been interrupted and I should restart the watch. After realising that my activity was indeed stopped I restarted the watch as instructed, and it behaved itself.

I have two questions…

As I restarted the watch (not a reset, just a restart) is it worth taking a bug report and sending it in?

My activity is now split into two. This is not ideal at all. Is there a way to join them together into the one activity it should have been in the first place?
(i have looked for this on the forum already but found some conflicting and confusing answers).

Many thanks

@olymay Also happen to me few months back, only one time. You can try to download the .FIT files and combine with: https://www.fitfiletools.com/, but take care, like I asked here, I can’t know if exist a method to preserve TSS, etc. When I cut (section remover) some of my activities these infos are loss

@olymay said in Watch crashed mid activity:

As I restarted the watch (not a reset, just a restart) is it worth taking a bug report and sending it in?

@dimitrios-kanellopoulos said in Display turn off after few seconds of an activity:

But next time it happens please use the Android wear app, and press take bug report. The logs wont be rotated until you charge the watch over 80%

olymay

@flypg cheers. I’ve combined the two files using the website you linked, but I have not been able to figure out how to get this new .fit file into the Suunto App.
It will sync it to Strava for me, but I want the data in SA to be accurate first and foremost.

I’ve taken a bug report from the watch. I haven’t charged it since being home, so does that mean the data will still be there? Also, what do I do with it now I have it?
@Dimitrios-Kanellopoulos are you the person to ask about this?

@olymay said in Watch crashed mid activity:

@flypg cheers. I’ve combined the two files using the website you linked, but I have not been able to figure out how to get this new .fit file into the Suunto App.
It will sync it to Strava for me, but I want the data in SA to be accurate first and foremost.

When you upload the two files on the website, after press GO, the service offer you two options, one of this is to donwload the new “merged” .fit file.

Now you need to go to QS > Services and there you can find a option to Upload FIT file to your Suunto app (4rd item from left to right), select the new “merged” .fit file and wait. That’s all.

But again, I don’t know how to preserve the TSS and other values that I mentioned on the other thread. On my previous activity that I needed to cut/remove a section I manually added these values, estimating these from previous similar actvities. It’s not too precise, but for me is enought. You can keep the 2 “good” activities to compare the values until you are sure to delete them.

olymay

@flypg nice one! That worked a charm!

But I see what you mean about certain bits of data being lost (TSS, steps etc). The altitude data has also gone a bit bonkers, but I can live with that.

As I have the original two activities still, I can easily add together the steps. But I am assuming it is not that simple for TSS?
This is not a route I have done before, nor is it a distance I have done for a very long time, so I don’t really have anything previous to compare it to.
Any tips?

Nigel Taylor 0

@olymay Were you following a route stored in the watch?

I’ve had two crashes, BOTH whilst navigating. Although I’ve also navigated successfully on MANY occasions.

I can’t see how it really can be this (and I suspect at least one of the crashes was related to a large POI label), but on both occasions where I crashed, I had synced the route to the watch via QS.

I use RunAlyze to route upload to Suunto since, and have not had a repeat (although I’ve NOT repeated the two specific routes that caused a crash (since deleted from the Watch and from SuuntoApp), either uploaded via QS or RunAlyze).

Its highly unlikely to be that - but its a process I’ve changed and it feels like its not going to crash now.

Good luck!! I know I was very nervous the next few runs after a crash, whether navigating or not. The reboot and getting going again seems to take an AGE!

olymay

@nigel-taylor-0 this is the first crash I’ve had during an activity (or at all for that matter) since the big update last year (September?) where Suunto fixed the issue of the watch crashing whilst following a route.

I follow a route almost every time and have been doing so for months. I either create my routes in the Suunto App, or in Komoot (now I have the hang of it I really do love this!). Sometimes with turn by turn on, but mostly with it off.
However, I do not have any POIs at all.

I initially tried to restart the activity without rebooting the watch and it got GPS lock really fast as usual, but would not get a fix on my HR, which is odd as it’s meant to be monitoring that 24/7.
The reboot took as long as it usually does, and after giving it a minute to settle down, when starting up the Suunto App it was as speedy as ever. HR was already locked on, and GPS took only a few seconds (I was in the middle of a field at the time, so nothing obstructing it at all).

@olymay said in Watch crashed mid activity:

@flypg nice one! That worked a charm!

Nice!

But I see what you mean about certain bits of data being lost (TSS, steps etc). The altitude data has also gone a bit bonkers, but I can live with that.

As I have the original two activities still, I can easily add together the steps. But I am assuming it is not that simple for TSS?
This is not a route I have done before, nor is it a distance I have done for a very long time, so I don’t really have anything previous to compare it to.
Any tips?

Yes, exactly. I imagine that this data is created and calculated on the S7, that mean that need to be regenerate again on the watch based on the new FIT information, but I not have idea if this is possible or if I’m right. Sorry

olymay

@flypg Cheers dude, I really do appreciate the help.

Regarding the TSS calcs, do any of the other Suunto users (or maybe the developers) know how this works and if there is a way I can recover this data?

Mff73

@olymay said in Watch crashed mid activity:

@flypg Cheers dude, I really do appreciate the help.

Regarding the TSS calcs, do any of the other Suunto users (or maybe the developers) know how this works and if there is a way I can recover this data?

to me (and just to me), i think TSS is SA calculation (or SuuntoCloud one, but calculated after activity).
So, if you have GPS track and/or HR values, then TSS should appear.
I have recently imported external fit file with QS to SA, without TSS value in it, and TSS is in my SA activity (based on HR).

olymay

@mff73 both activities have HR data, as well as GPS track, duration, pace, etc.

However, the first activity (the one that crashed) does not have TSS, calories, or steps recorded.

I’ve also noticed another quirk with joining the activities together… in the merged file, the second part of the run has been added as manual laps, not auto laps. This is fine in Suunto App (although looks odd) as it still has the correct total distance.
When I add it to Strava however, it shows the correct duration, correct GPS track, but it ignores the distance of the second activity.