Garmin incident detection

[GeekEcosse]

Garmin has pulled incident detection from the MTB and eMTB activities.

Be aware if you think you have this protection in place when riding alone.

If this impacts you could I ask that you follow this thread and send an email as per the note on page 1.

No crash(Incident Detection) detection in mountainbike activities on v.21.00. On my Fenix 6 Pro - fēnix 6 Series - Wearables - Garmin Forums

A dedicated community for Garmin users to ask questions, provide answers, and share feedback.

forums.garmin.com

 

[Mteam]

I guess its because it was too easy to trigger it without there being an actual incident when riding rocky/steep stuff.

There is one rocky descent I ride where the incident detection is always triggered incorrectly and I have 30 seconds to cancel it before it sends an SMS to my contacts.

 

[Tim1023]

Thanks for the tip! I've raised a couple of issues around incident detection with them:
- Whenever it goes off - and whether you cancel it in time or not - it kills the trip recording.
- There is no control over vibrations on the watch (I have a Venu), which means that every time you stop or finish a "lap", the watch vibrates. This means that I only ever noticed that the incident detection had activated was when my wife called me in the middle of the next decent!

Pretty crappy of them to just delete this function rather than fixing it.

In any case, there is no bloody MTB activity on my Venu, let alone eMTB, just Bike. So I guess I still have the function

 

[Alexbn921]

It was terrible. I'm glad it's gone.

 

[GeekEcosse]

I’d still like the ability to configure the activity and decide myself rather than pull it.

 

[Marksou]

It went off a couple of times on the Downs Link last week on my Edge 530. Perhaps it thought I was in danger of drowning?

 

[Kingerz]

Yeah good, it was stupid and too easily triggered with usual MTB activity.