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

VA4 incident detection (during MTB ride) seems a tad sensitive?

During a recent MTB ride I triggered an incident detection event during a downhill trail , I only noticed when it beeped an alert stating unable to send the alert (no Cell signal available at the location) I hadnt crashed and the trail was rutted and bumpy but not excessively and I didn't encounter any large drop offs. I also noticed that as the incident detection had triggered (though I missed the events alerts at the time) it had also stopped the in progress rides recording.  Seems the watches incident detection algorithm is a touch too sensitive for MTB rides and its a PITA that it stops the ride recording as I lost a a part before it was spotted and had to start a new ride .