BUG - auto pause when stopped not working

Hi,

During a run or bike ride the auto pause does not seem to work as intended. I use a normal gps setting and auto pause 'when stopped'. Most of the time the activity is not stopped in 30-60s of no movement (waiting for traffic light to change). Previous Instinct did pause much more reliably hence I think it's a bug

0 Dr Phil over 3 years ago

Just because you've stopped doesn't mean the watch knows you've stopped. Satellites move around and can cause the watch to believe you are still moving.Check this by starting a GPS activity with the watch outdoors and not moving. You'll see there can still be a lot of 'movement' detected. My guess is that the improved GPS on the IS2 sees more movement when stopped therefore might not realise you've stopped moving.

The auto pause has a choice of setting - When Stopped, or Custom where you can set a pace. The default for the Custom is 60:00/km (1km/hr). Perhaps try that and see if it makes a difference.

0 kidney_thief over 3 years ago in reply to Dr Phil

Thanks for your input. I'm aware that movement detection relies on several factors - some of them are fixed satellites other is the interval determined by smart mode etc. In comparision to older Instinct 1 it looked like a bug, due to very low reliability. I'll give the pace based pause option a try.

0 kidney_thief over 3 years ago in reply to kidney_thief

Using pace-based pause solved the issue. Works fast and reliable now

0 amylynn829 over 2 years ago in reply to kidney_thief

I'm having the same issue with my 920xt. Auto pause when stopped used to work reliably but lately I'm missing huge sections of data during my run activities (it seems to work better for cycling but I'm not 100% positive since I mostly use my 520 for cycling.) Anyway, what pace-base pause did you set yours to that worked well for you? Is it still working okay using that fix?