S9B crash, not all data saved

[Stefan Kersting]

@isazi ok, i will try that, thanks for your help

[isazi]

@stefan-kersting now to understand why it crashed. If you send the logs very soon after it happens the people at Suunto may investigate the issue and find if there is a bug, but it may be too late now.

[Stefan Kersting]

@isazi why is it too late now? The support is closed now…

[Stefan Kersting]

@isazi sendt the logg to the support. I checked the logbook too and the logg on the watch is empty and looks like that

[isazi]

@stefan-kersting because the logs only last few hours, so they need to be sent just after the event happens, and then you just need to write support the time you sent logs and from which account.

[isazi]

@stefan-kersting this is the activity summary that is empty because it was not saved before the crash.

[Stefan Kersting]

@isazi ok, then this activity is lost…

[isazi]

@stefan-kersting not totally, you have something in SA, and if you check the FIT file there’s probably some information that can be recovered also.

[Stefan Kersting]

@isazi in qs i see there is eg the ascent information but not in SA. So ascent information is very important to get
But i also see that the Heart Rate is nit saved, just the average…

[isazi]

@stefan-kersting I did see the HR values in your SA activity though, so the samples are there.

[Stefan Kersting]

@isazi actually that’s right. Weird that the app shows it, the watch doesn’t, at the same time calories are not calculated…

[isazi]

@stefan-kersting so while the activity is going on the watch adds data to the “activity file”, such as elevation, coordinates, HR, etc. At the end it computes some statistics and adds them to a header.

What I understand is that in case the watch experience a crash, you end up with empty or incomplete header. Now SA and other applications can compute some stuff on their own, but for some things they rely on the header. This is why you have some data but not all of them.