This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Incident detected during a mountain run

I had an incident detected while running down a steep set of switchbacks during a mountain run today. I did not fall, yet the watch started vibrating and tried to connect to my phone to call for assistance. I was able to cancel prior to any calls being made. Strange that the watch would detect running down technical trails as a fall or something else. I guess Garmin needs to work on this particular algorithm.

0 CloggyAbroad over 6 years ago

For this feature to activate the watch needs to detect some kind of shock load followed by a period of not moving. Whatever you did during this run must have satisfied the criteria set by Garmin to trigger the alarm. Maybe Garmin could set the threshold higher for this feature to trigger, but that could mean that a genuine incident is not detected.

If I had a choice between occasionally having to cancel an alarm (you get 30 seconds to do this) and an incident going undetected I would always take the first option.

0 tchazzard over 6 years ago in reply to CloggyAbroad

Yes, I did stop abruptly to wait for my wife to catch up. But could they not determine I was stopped but upright?

0 Levon over 6 years ago in reply to tchazzard

If you had fallen, you'd be 'stopped' too (rather than stopped waiting for your wife), it would be hard for the Garmin to know at what level you had fallen, i.e., the elevation, so it can't tell if you are motionless upright or motionless face down. I bet the algorithm looks for some sort of shock followed by no movement like CloggyAbroad mentioned. Had you continued to move a bit afterwards, it probably wouldn't have triggered it. These are useful observations to share with the users and Garmin as we learn about the characteristics of these new watches and their features.

Glad you were able to cancel this alert.