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

False Incident Detection - too sensitive.

Today I was cycling along at around 8mph when I heard my phone in alarm then noticed the watch had started an incident. I've also had another false alarm when I sprint finished a parkrun and had to slow down for the finish token maybe a little quicker than usual, but had kept moving.

There seems to be no pre-incident warning where you can cancel it off before it happens either, it seems to go straight into full blown incident mode. Stopping the incident doesn't resume your activity which is also annoying.

It could be such a useful feature, but I'm going to end up turning it off as it's such a bad user experience and the more false alarms it creates the more chance there is my emergency contact will start ignoring them.

Are there any settings I can tweak to make it less sensitive? I think I have it set so I have to be stationary for 5mins before it goes off, so it's the impact detection that there seems to be an issue with.

Thanks.

  • Since the latest updates, my watch has been detecting incidents and attempting to contact even when there is no incident, yesterday i was stood still volunteering at junior parkrun when it just started vibrating and it also takes ages too to actually cancel. its too sensitive i have turned it off