Activity abortion

inkognito

@freeheeler Well, I use S+ together with navigation several times a week. And I remember like 3-4 crashes out of 100+ activities… That makes it quite rare and hard to reproduce…

freeheeler

@inkognito
ok, I rarely use navigation… actually only when I do activities where I don’t know the area or when I want to try something new

jussim

What a relief to know that I’m not the only who’s had this problem. I was first thinking it might be hardware failing… Good call on it being linked to SuuntoPlus and limited processing power, that just might be it. First I was thinking it might be related to memory storage getting full mid activity (watch somehow failing to delete older activies).

This happened several times to me this summer. I did hard reset and all seemed fine until again couple of weeks ago. Now I have done a soft reset weekly or so and the problem hasn’t reoccurred again. Good to know that there’s the option to send logs in case it happens again.

Waiting for firmware upgrade!

jussim

Two km into workout I didn’t hear beep for a lap where I expected it and fucking hell, I was greeted with a dreaded arrow pointing down. At least I managed to reset the device. Seems like rebooting the watch three days ago didn’t do anything to prevent this from happening. I did change from GPS+BeiDou to GPS+GLONASS some weeks ago, could it have anything to do with it? Also SuuntoPlus Burner was in use. Maybe I’ll stop using SuuntoPlus functionalities next and see what happens.

Is the debug data lost when you start a new activity? I’ve sent log 1121341147474400 in any case.

isazi

@jussim the watch getting into such issues during activity is quite unexpected though, if your watch is still under warranty I would contact support.

jussim

@isazi I did just that the last summer after this happened more than once. It was all kinds of useless endeavour, when all they had to offer was to advice to restore firmware to factory defaults.

Maybe I should contact them again about servicing, but I’d rather give the new firmware a chance. It’s just too much of a hassle to get the watch sent for inspection, not to mention being without it for a while.

isazi

@jussim I reported the issue with your logs to Suunto.

jussim

A couple of days after a fresh firmware upgrade, it happened again, 1,5 km into a run. Again I had Burner enabled. This time I didn’t have the down pointing arrow, only the watch face.

Great work Suunto!

freeheeler

@jussim
did you send logs again?
I did a couple of runs, no issue with the latest firmware

jussim

@freeheeler Sure did!

isazi

@jussim your bug wasn’t fixed in the latest release, it is planned for a future one.

jussim

@isazi Wow, that’s a relief to hear. Kudos!

jussim

It happened once again and this time I had no SuuntoPlus functionality enabled. Can I keep sending debug logs or are the cause for this already identified and being worked on?

Brad_Olwin

@jussim I think if the settings are different it is useful to have the logs. You can either send your username and the time logs were sent to @isazi or me.

TiagoSPM

Last month, happened once to me: indoor cycling at 15 min, no app on, just cadence and HR belt sensors connected. No more for now.

TiagoSPM

Yesterday I turned on a new app on the same indoor cycling and it happened again, aborted with 2 minutes of action…

Brad_Olwin

@TiagoSPM Please send logs to Suunto as soon as this happens, then either PM me or @isazi with your username and the time logs were sent. We will file a bug report for you.