Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iPhone 14's Car Crash Detection Still Triggering False 911 Calls, Forcing Dispatchers to Reallocate Resources Away From Real Emergencies
- Thread starter MacRumors
- Start date
- Sort by reaction score
Apple CarPlay using existing vehicle crash detection sensors would suffice. Take it off the iPhone.
Unlikely, crash detection on Android is limited to models Pixel 3 and up, which are a small slice of overall Android sales. Samsung and the like have not licenced it or come with their own yet.
Also, the crash detection functionality is disabled by default (while it's enabled by default on capable iOS devices) - I actually had to google my way to it on my Pixel 4a, it's within the safety app rather than the device settings.
There have been some crash simulations to compare the two detection functionalities, Google's version does not do better than Apple's, but Apple decided to make it a strong point by having it on by default, so we're hearing about the false-positives due to the sheer volume rather than because it's worse than Google's (even though it sounds like all options are half-baked right now).
Last edited:
Maybe you can give feedback at feedback at apple dot com. Because obviously this feature was slapped in without testing. /s
Crash Detection offers an override as well. I think the delay is 10 seconds. Which seems short maybe? The issue with skiing is they often will have their phone buried deep in a backpack or under a bunch of layers of clothing and don’t get to it in time or don‘t even hear the warning sound.
The same thing that will happen if you have an older iPhone.
No, it’s not the same thing. It’s reasonable to NOT expect an iPhone 13 or earlier to not call 911 in the event of a crash. It’s not reasonable to expect an iphone 14 to not call 911 regardless of the electronics or lack thereof in a car.
Currently more probably die due to false calls :/
I was also not a fan of it, expected lots of false positive calls because it has been enabled by default and not alligned to car Bluetooth or at least any kind of maps driving
Apple’s obsession with secrecy over all else prevents them from properly testing their features in the real world. Additionally, bugs happen and no company can prevent them. However, because Apple has chosen to place secrecy above all else, when these bugs are reported, instead of making a reasonable response (we’re aware and are trying to track it down and we’ve made some optimizations in iOS 16.2), they rigidly follow their “keep everything secret,” approach to support: erase and reinstall then RTA to engineering to be told to keep your device up to date.
Last edited:
I see your view. I just get frustrated that more and more we can make some so sophisticated to hurt\kill people yet it appears we learned nothing and cannot help people at a high degree. We can hurt more people then help. Just ahhhh! lol..
But this goes back to the old adage that you have the most accidents in places you are familiar with, where you most likely wouldn't be using Maps
Even easier: if person continues to move then they’re not dead.
Post-crash behaviour is important too when determining if the crash was serious enough to warrant an emergency call. More easy to gauge that from a phone (which is likely to be on your person and which you interact with frequently) than a device like an AirTag which could be easily forgotten.
Also, cars themselves are in a pretty good position to detect accidents (Airbag deployment = serious accident), and future models probably will have an emergency notification feature like this.
gonna have to give a hard no on this one. I’m legally unable to drive for medical reasons—I rely on Uber & this feature may save a driver’s life one day (or—not “literally” more importantly, but, on a deeper personal level—the lives of family members I ride with, none of whom have Bluetooth in their car).
Honestly? I think Apple only got away with this like they have so far because it earned a lot of "good will" with other efforts focused on safety and medical responses. (EG. Lots of propaganda of all the lives saved with the Apple Watch's ability to warn of irregular heartbeats.)
Because the rest of their stuff worked properly and didn't overload emergency services with false alarms, people just trusted Apple to get this right. And now, they didn't!
I think it called or texted the first number on my contacts alphabetically because I had not set up the feature. Also, I am not complaining about the feature. I think it is awesome, I am just commenting on what happened to me accidentally triggering the feature.
So in other words, no concrete suggestions other than “more people” in the hopes that somehow replaces real world testing scenarios.
You don’t just throw people on to look at code.
If you had suggested something like a partnership (under NDA) with responders or a university program focused on safety testing I’d be happy to say you had a point.
Instead, you’re using “secrecy” as a hole to simply dump your gripes without any evidence of how secrecy has hampered development. I’m not a subscriber to wishcasting.
This scenario always makes me think what if some totally unscruplous person comes to the car wreck and steals the unconscious person's iPhone
I think that would be AES. Maybe they would save me so I can keep paying my student loans
