4 ms·
It's worth noting that a phone bouncing around in a pocket can experience substantially more acceleration than the person carrying it.
by jstanley 3y ago
It's worth noting that a phone bouncing around in a pocket can experience substantially more acceleration than the person carrying it.
- ImPostingOnHN 3y agohow much more? are we sure it's enough to excuse the failed crash detection described in the article (IE do we know the bouncing around generates multiple tens of Gs like an accident)? without such a confirmation, the error is still inexcused with it, the error seems like the feature is just poorly implemented or perhaps even poorly thought out
- yifanl 3y agoShould this not have been accounted for when designing the feature?
- jstanley 3y agoYes, but it explains why the problem is not as easy as the g-force comparison makes it sound.
- Swizec 3y agoI had one of these alerts go off once from my watch. After a really hard fall from tripping during a trail run. I still have the scars. The alert said: “You had a hard fall and stopped moving. Press this button or we call help” The “stopped moving” part seems like the perfect proxy here. People in a car crash experience a huge spike in G-force once. Then it stops. Or maybe it goes for a few seconds if you’re rolling down the highway. Car crashes don’t go on for minutes upon minutes. This seems like something a machine learning algorithm could handle. At the cost of calling 911 3min after a crash instead of 3sec. That’s still much faster than how long it takes people to call for help.