Activity abortion

Mitch9

@Ivan-De-Rasis No, the music control is disabled on my watch.

isazi

If someone reproduces this and send me logs, I’ll open a bug with Suunto.

Mitch9

If someone reproduces this and send me logs, I’ll open a bug with Suunto.

Reproducing is hard. The first time it happened after 2.2 km, the second time (12 days later) it happens after 25.2 km. Both were running activities. In future I don’t want to loose the data and so don’t activate routing and SuuntoPlus.

freeheeler

@Mitch9
ok, I sacrifice, I’ll do it…
any S+, plus route navigation and a bit of bad luck?
anything else?
if you specify your settings I can set it up as similar as possible. sport mode customization? gnss systems, sensors etc… I think all this can have an affect

inkognito

@freeheeler
I am sacrificing most of the time. But it usually happens when I am in the middle of 20+ km long route somewhere in the forrests with weak cellphone signal… So I cannot send logs at those moments and I am affraid that logs will be rewritten once I start a new excercise (which I need to do as I do not want to get lost )

I would preferably choose those SuuntoPlus apps that create autolaps (like Climb, it seems to crash more often). But it also crashed with Burner…

I only use custom sport modes, it happened during running and hiking. I use fields like distance to the end of route, ETA, ETE…

I used GPS + BEIDOU, external HR sensor

I don’t think some of these things really matter… I just think that in some rare cases heavier computations coincide (like navigation + suunto plus) and the old S9 processor cannot deal with that… My friends with newer and faster S9P never had these problems with similar setup…

I also think that we should probably wait for the new firmware where some SuuntoPlus-related tweaks are expected. That might solve it and we don’t need to struggle

freeheeler

@inkognito
actually all the same setup like mine… except that I don’t use beidou, I’m on galileo.

I’ll check with my next activity, most likely on saturday

Egika

@inkognito logs don’t need to be sent at the instant of a problem. You can do so a couple of hours later. Just finish your run and when you get back to your home, bike or car, send the logs. They will have everything needed for the engineers to find out what happened in the previous hours.

Edit: plus inform someone in Suunto or of the field testers in this forum about the issue and time and account you sent the logs from.

freeheeler

@inkognito
I didn’t manage yet to crash my waych with S+, turn by turn navigation and external HR connected.

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!