S9 Baro, data missing when pressing button for split time in exercise

[Gregor Kržan]

Ok I will…but why is data on Strava correct then? It uses file connected with watch and suunto app where data shown is missing or incorrect !!!

[isazi]

@gregor-kržan the best hypothesis is that because the header is missing Strava is recomputing the data. I would be very annoyed if I was you also, but if it happens so often there must be something wrong with your watch. Did you send your watch to Finland or some local dealer?

[Gregor Kržan]

@isazi I didnt send to Finland because I sent it to official service which is only official service in Slovenia for Suunto.

[isazi]

@gregor-kržan I can only suggest you to contact them again and show them this forum topic also. Don’t know if @Dimitrios-Kanellopoulos can help you with support.

[Dimitrios Kanellopoulos]

Did it take a long saving time ?

What sport mode did you use?

Did you use navigation?

To me the issue is abvious. The watch does not save the activity correctly due to some reason .

So as much possible info you can add it will benefit.

The main question for me is:

• When you finish the activity does the watch save it and present you with the data of the summaries?

According to what I see the watch should crash at that point.

[Gregor Kržan]

@dimitrios-kanellopoulos

Thanks for your reply here. Ok when problems started I used only one sport mode - customized hiking with laps and I thought that was the case. Watch took more time than usual to save exercise and there was only data available for duration and distance I think…no altitude or HR. On Suunto App there were same invalid values as shown above.

Then I took watch to licensed service where they tested it and told me everything is ok. I later did few different trainings and sport modes and in two cases same irregularities happened. First in running with no pauses and second in cycling with 30 min pause. All looks ok on Strava though.

In both cases watch took more time to save exercise then usually does and data is again only duration with pause included plus distance and I think avg speed. No altitude or HR again. No navigation used.

[Brad_Olwin]

@gregor-kržan Another possibility is you have a corrupt sport mode. If only one sport mode is causing the issues you might try deleting the mode and making it again.

[Gregor Kržan]

@brad_olwin no its not the case…as mentioned above…I had problems in hiking, cycling and running

[Mff73]

@gregor-kržan
Maybe worth trying to hardreset again (and eventually a couple of time more). If something is stucked in software, it is the best way to clea’ it. You already did it, but maybe issue might had survived.
Other reset solution : try the shipping mode.
(https://forum.suunto.com/post/46365).
Good luck.

[Dimitrios Kanellopoulos]

@gregor-kržan do you use some Belt ? Maybe some HR monitor is causing this

[Gregor Kržan]

@dimitrios-kanellopoulos I use Garmin belt…yes…you think that could be the case? But I do all trainings with belt so why are irregularities only in some trainings.

[Dimitrios Kanellopoulos]

@gregor-kržan I have seen this in the past. Some belts with spartans would get stuck on saving.

I don’t know how to help here to be honest. I suspect a bug related to the belt that the watch overcomes when saving the activity.

What I can do , is if you can , send some logs and I can create an issue for the watch team.

[Gregor Kržan]

@dimitrios-kanellopoulos ok…would be very grateful…what should I do to help?

[Dimitrios Kanellopoulos]

@gregor-kržan so just after one of those hikes etc press send logs from the suunto app and from the suuntolink. Remember the time around this happened or from Suuntolink pass me back the ID of the logs that i gave you back. Of course you should have connected the watch before and let it sync with the Suuntolink.

So 2 ways

Either Suuntolink -> send logs -> give me the log id

Suunto app -> send logs -> mark the time and will need your account name / id in private.

[Gregor Kržan]

@dimitrios-kanellopoulos Just sent you ID on chat.

[MagoZichele]

@dimitrios-kanellopoulos when the problem happened to me, even if not identical but similar to the one discussed in this topic, I was using the sensor on the wrist of the S9, for the HR