turns off during exercise
-
@alexej19 sync the watch with the app, then it depends if you are using Android (which I know), or iOS (which I don’t).
-
@isazi ios
-
@alexej19 in the profile tab of the iOS app at the very bottom you find “send protocols”
It only makes sense directly or max a few hours after the crash -
@alexej19 okay I need some help here then
-
@alexej19 after you send the logs (need internet connection to do that), send me a PM with the time and date you sent the logs, plus your username in Suunto App.
-
@isazi i have send it now. may name is alexander
-
@alexej19 it has to be immediately after the watch crashes to work.
-
@isazi ok it is a 3-4 hours ago.
but in any case thanks -
@isazi …the watch crashed again…
-
@alexej19 maybe it is a good idea if you contact support also.
-
-
I happen to have a similar problem to yours. My Suunto 9 Peak regularly ends activities on its own. This happened only in Alpine Skiing Modus so far, which I customized (changed Suunto Plus options to TrainingPeaks HR only, changed a few watchface things to my likings).
I‘ve also had the problem this week that my watch rolled back from v. 1.19.49 to v. 1.18.18. My watch is back updated to v. 1.19.49 by now, after support helped me out with a link that changed something on my iOS version of SA. Interestingly, my watch ending activities on its own started to happen after the rollback and persists even now that the watch is back on v. 1.19.49.
I‘ve also already contacted support this week and they told me to softreset the watch twice in a row, which obviously didn‘t solve the issue. I‘ve also already sent protocols via SA immediately after the activities were ended by the watch.Since it is Alpine Skiing I‘m doing currently, I pause the activity every time after a downhill, when I go back up the hill with the chairlift. I just don‘t want my watch tracking, when I‘m lazily sitting on the chairlift
Perhaps those frequent pauses and resumes have something to do with the issue? -
@team-keystroke-harmony It might be a problem as that mode does not record ascent data as it recognizes you are on a chair lift. Try it without pausing. The watch firmware should be 2.19.42.
-
@brad_olwin I see, I‘ll try it today without pausing. Thx for the advice!
-
@team-keystroke-harmony
plus: the watch might count uphills (does it really?), but it will be filtered in your annual statistics. -
Did use Alpine Skiing custom mode today again, with stops every time before taking the chair lift, but without having gps turned on. I decided against using gps, since I preferred more accurate TSS (not stoping the activity before chair lift would generate higher TSS due to seemingly longer activity duration).
Today, the watch never ended the activity by itself. So far so good, but still kind of sad, that the watch can obviously not handle frequent „distance skips“ as produced by stopping the activity before chairlift and resuming afterwards …
-
@team-keystroke-harmony
I imagine it difficult as it contains a division by 0 depending on the value we want so see (vertical speed: m/h, speed: km/h … etc) -
Besides, this is a bit off topic now, but the watch did measure distance and height, even if somewhat inaccurately.
Without gps enabled, did the watch calculate those values purely barometrically? -
@team-keystroke-harmony
but height of course by baro sensor.
disntance, not sure. for running activities there is an acceleration sensor that calculates distance, but this will not work reliably for skiing afair and afaik.I’m also not sure if your TSS is much influenced if you stop during chairlift rides. it is the intensity and time… time is there, but intensity is low on a chairlift.
I can just tell you what I do, but I am not crazy nitpicky on skis: I start an activity normally at the start of the first descent, pause when we go for lunch and restart when we hit the slopes again… no pauses inbetween whatsoever… not even when queueing before the lift.
I’m happy with how it works and what I see.
…I concentrate on enjoying the rides :hea -
@freeheeler I speculate that the watch does recognize when a downhill stopps through significantly increasing values for height. A new downhill measurement starts, when height values decrease once more.
Therefore I don‘t think there is a /0 problem underlying, since every time I begin to ski downhill a new measurement starts.
