Autopause too aggressive for slow or climbing activities

[Fenr1r]

Have you seen this?

[Brad_Olwin]

@renius82 Don’t use auto pause. Not made for this and that is true for any brand.

[Stefano M64]

@Brad_Olwin said in Autopause too aggressive for slow or climbing activities:

Don’t use auto pause. Not made for this and that is true for any brand.

what it is made for?

[BRogers80]

Polar allows you to define a threshold speed per Activity.
IMHO the best solution

[Brad_Olwin]

@Stefano-M64 Works well for cycling.

[fondueaufromage]

@Brad_Olwin Sorry but I don’t agree with you because autopause worked well at low speed until first update Q1/2024.

[Luis Andés Olmedo]

@Brad_Olwin said in Autopause too aggressive for slow or climbing activities:

@Stefano-M64 Works well for cycling.

I use it for cycling and I like how it works.

[Tieutieu]

I used to have autopause enabled by time on my first Garmin bike gps 20years ago, but I quickly abandoned it as it wasn’t working well…and also because when having a journey, pause are part of the activity.
Never been using it since then.

[maszop]

@Brad_Olwin said in Autopause too aggressive for slow or climbing activities:

@renius82 Don’t use auto pause. Not made for this and that is true for any brand.

Instead of expecting improvement, you propose not to use something because it is uselessly designed, instead of the option to improve it?

[Łukasz Szmigiel]

Why not have different thresholds for auto pause per workout type (slow / fast moving) in the same way the “abnormal speed detected” notification works? The notification is awesome when, for example, one jumps into the car after a walk and the workout is still running.

Why not have auto pause engage on walks or hikes only when speed drops below 2 kmh for 15 seconds or longer and then unpause only after exceeding a distance of 25 - 50 meters?

[Stefano M64]

@Łukasz-Szmigiel said in Autopause too aggressive for slow or climbing activities:

Why not have auto pause engage on walks or hikes only when speed drops below 2 kmh for 15 seconds or longer and then unpause only after exceeding a distance of 25 - 50 meters?

I think something like this could be a good approach, the actual implementations just work for fast activities, while in the manual nothing is written about that, it is supposed to work for any kind of activity.

[Brad_Olwin]

@fondueaufromage Not for me:) Hills are too steep and I am too slow.

[Elipsus]

@Brad_Olwin Mouarf that’s not a great answer… “Autopause is not working correctly” -> “Don’t use Autopause”

Not really, his remark is relevant, if Suunto can’t make a functionnal autopause for hiking, Suunto should either make it work, or remove it, its not supposed to be up to the customer to find “which feature included,advertised, displayed and available in my 500€ smartwatch is working correctly”

making an autopause that work for hiking, or any sport really isn’t hard, make it position dependent instead of speed dependant, and boom, you have something that works, especially since nowaday GPS tracking is so much better than before

[t-Dox]

@Tieutieu Hi, I agree with you that the pause is part of a journey. In fact, if I go on a long trek with my girlfriend or friends, I also turn off the autopause. However, last year, I used it a lot to monitor the progress of a workout. This way, if I meet a friend on the street, I can stop to talk and say hello calmly, without compromising the training measurements. Otherwise, you can’t stop to talk to anyone without compromising the time recording…

[Tieutieu]

@t-Dox yep agree ; I still use manual pause in such case. Moreover the « resume reminder » when pause is on and a mouvement detected is perfect not to forget to restart recording

[fondueaufromage]

@Brad_Olwin Could the problem be in the calculation method for determining the speed of movement?
By that I mean, are only longitude and latitude taken into account or also elevation is include for determining the speed? Be careful, I’m not talking about vertical speed!
Because I was careful to move flat at the same speed as when going up a steep slope (using step cadence as reference) and the speed indicated by the watch is very different. On a slope, this gives the impression that the watch only takes into account horizontal movement, without taking into account vertical movement. Obviously, the steeper the slope, the bigger the error… thanks Pythagoras.

And therefore, this could be a reason for the sensitivity of autopause… ?

[Tomas5]

Most funny for me was on MTB. I have bike sensor. It measured speed less than 2km/h on big climb and put me on autopause even my pedaling rpm was around 30 rpm.

[Brad_Olwin]

@t-Dox said in Autopause too aggressive for slow or climbing activities:

@Tieutieu Hi, I agree with you that the pause is part of a journey. In fact, if I go on a long trek with my girlfriend or friends, I also turn off the autopause. However, last year, I used it a lot to monitor the progress of a workout. This way, if I meet a friend on the street, I can stop to talk and say hello calmly, without compromising the training measurements. Otherwise, you can’t stop to talk to anyone without compromising the time recording…

Or since this is training and you stopped it is recorded. I do not pause or use auto pause when running. If I stop an talk with a friend that is reflected in my workout as the stop reduced my effort and HR changing my workout. I want that recorded.

The only time I use auto pause is road cycling for stop lights.

[matteo_000]

@Tomas5 I agree with you. In MTB sport mode, when you are on a big climb, sometimes the watch goes in auto-pause status. Maybe it will be good adjust the watch setting for some sport mode.

M

[maszop]

The solution is simple, yet complicated.
Instead of 100 kinds of fake sports modes, just fewer but real ones.
Autopause, distance when navigation messages are displayed, elevation gain, button function and many other things should be tailored to the given activity.
Now there are 100 activities that only have slightly different configured information screens.
Everything else is rigidly set mainly for running.

The problem is that Suunto doesn’t know what user options are. Everything has to be hard coded with no option to change it - unfortunately often completely pointless for a given activity.