tastyratz

tastyratz t1_irss3l8 wrote

Most rides are absolutely under 5 minutes so detecting high speed and forces inside a geofence and then disabling for a 5 minute period every time should cover... most if not all rides.

If Apple is worried about liability then they could pop a temp notification that the feature is currently disabled for x reason (just like you might see with a wet charging port on android).

This allows for automatic crash and fall detection feature disablement without user interactivity in false detection scenarios.

The 5 minute timer could start every time they get on a ride and they can still have fall detection walking the park. They could even tie in heart rate / apple watch false readings.

This is also an EXTREMELY broad and short solution by a Redditor with very little investment. I am sure any implementation would get far more complex. Maybe it's... 4 minutes? 3? a weighted answer depending on forces?

Either way, it can easily be refined.

6

tastyratz t1_irsfjvi wrote

More obvious observation:

Geofence crash detection on rollercoasters in known amusement parks because people won't do that.

You could also disable crash detection for 5 minutes when G forces and speeds exceed a certain criterea (i.e. combination of speed, accel, force, and time) when in the entire confines of an amusement park and similar locations.

This is easily solved through software by design. It won't fix corner cases (like traveling carnival rides) but I bet it solves a significant number of fixed location issues.

Edited to improve clarity after some confusion

14