Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I had the opposite experience while snowboarding. I crashed heels over head going 20+ mph while wearing my Watch Ultra with my iPhone in my pocket. Neither crash nor fall detection was triggered. I was kind of disappointed since I’ve “successfully” triggered crash detection when I was hit by a car while riding my bike, and triggered fall detection when I jumped down from the 2nd rung of a ladder.

I’d rather my phone call for help and me be ok enough to cancel it, than need help and not be able to call for it.

Did you send details to Apple about your unreported crash so that they can improve their algorithm?
 
  • Like
Reactions: I7guy
This is going to result in regulation, I'm willing to bet big money on that.

Apple better get this **** under control. A good start would be to only do the 911 calling if the phone is paired to a car's bluetooth.
…and for cars that do not have Bluetooth?
 
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.
I have no idea what you’re talking about. I pointed-out that Apple’s “secrecy above all” approach is contributing to the problem. Apple has publicly stated that this is their approach, including saying they are “doubling down on secrecy.” Apple’s documented support approach of erase and reinstall, RTA to engineering to be told to keep your device up to date is not a “wish,” it is what Apple does. Apple has refused to respond to a safety issue and saying so isn’t a “wish.” I understand you don’t like people pointing-out that Apple’s approach is failing, but there is nothing “wishful” about discussing the effects of the standard Apple publicly set. As I said earlier, if Apple focused on real-world testing, especially of public safety features that should not be secret, they would be better off.
 
Last edited:
  • Like
Reactions: TechNutt
That is the number of extra calls being received per day in a single small mountain county with four ski resorts. Your number is for the entire Unites States I assume. 20 extra calls for the entire country is nothing. For a small community, it's a lot.
That makes more sense. apparently according to their website Pitkin got 72,000 calls in 2017 around 1,384 a week still a lot, but I'm sure even 1 extra can be a problem.
 
No it's not. Apple doesn't tell users to disable it while skiing or on rollercoasters. They have no way of knowing of this issue unless they heard about it externally.
I’m not being facetious here, but is it Apple’s fault for failure to turn their phones on silent when in a business meeting? At some point, PEOPLE have to be held accountable rather than passing blame onto tech companies.

It’s really easy. Am I going skiing? Am I at an amusement park? *toggle crash detection off*
 
Whilst I agree with all of your other statements and from a person who has arrested people for false calls, I cannot disagree with this statement more.

Yeah, it was one I wavered on, so I suppose a crime is too harsh. I wish there was a way to filter unintentional 911 calls. If someone is frequently butt-dialing 911, is it Apple or the user’s fault. Maybe both.

I know some posters said something similar, but can’t they just have it detect when you are in proximity of a ski resort or amusement park and a notification can pop up asking you if you’d like to temporarily disable the feature? Then put it on the user to disable it, instead of automatically turning it off.

Sorry if someone said this exact thing already!

Crash detection trigger. Delay 60 seconds. Is victim moving? If yes, cancel crash detection 911 trigger.

Apple never warned about this and called the feature Car Crash Detection. They never said turn it off if you ski or go to rollercoasters. They said ‘this is gonna call 911 if you get into a serious enough to knock you out car accident’. So I don’t get how you’re trying to shift it as a user fault. Especially when the feature is turned on by default, the user is never in the wrong. After all, it’s an iPhone that does a bunch of other stuff, not a car crash detection device that the users failed to familiarize themselves with.

I expect an update in the user TOS, if it’s already not in there. The “why won’t it read!?” South Park meme comes to mind.

I honesty wonder if this technology had been in more hands.. How many people in Buffalo, NY could have been saved.

How so? People died while stationary buried in snow.

The EU will be fining Apple heavily for this in a few years. Still loving my 13 Mini on 15.7.

EU seemingly does things right in the tech world. Privacy law transparency and universal USB-C ring loud & true. Without EU common sense, we would still have Lightning cables on iPhone 20 Pro Ultras 😆
 
Last edited:
I’m not being facetious here, but is it Apple’s fault for failure to turn their phones on silent when in a business meeting? At some point, PEOPLE have to be held accountable rather than passing blame onto tech companies.

It’s really easy. Am I going skiing? Am I at an amusement park? *toggle crash detection off*
That would be not using the silent switch as intended. Like I said before, "Disable it while riding rollercoasters" is not intended usage. This is equivalent to saying the user is at fault if they plug in the phone and it catches fire. "You should've known batteries are flammable, you could've prevented this by just not charging the phone" isn't really a good argument. The user isn't at fault for using it as designed.

Really easy for who? It's on by default. The average user that doesn't follow tech news is not going to go on a rollercoaster and think "I better turn off crash detection because it has trouble with amusement park rides", many of them won't even know it exists. For those that do know and remember it's still supposed to be a set-it-and-forget-it feature.
 
That would be not using the silent switch as intended. Like I said before, "Disable it while riding rollercoasters" is not intended usage. This is equivalent to saying the user is at fault if they plug in the phone and it catches fire. "You should've known batteries are flammable, you could've prevented this by just not charging the phone" isn't really a good argument. The user isn't at fault for using it as designed.

Really easy for who? It's on by default. The average user that doesn't follow tech news is not going to go on a rollercoaster and think "I better turn off crash detection because it has trouble with amusement park rides", many of them won't even know it exists. For those that do know and remember it's still supposed to be a set-it-and-forget-it feature.

This is why it’s good to have these kind of cordial discussions rather than get enraged which gets society nowhere. You have valid points, which I thought about if my mom went coaster-riding. The main problem is the detection is on by default. It should be an opt-in toggle only after reading a guideline of precautionary activities for when to avoid using it. But I also fully understand people won’t read that, either. However, then that’s not on Apple or any tech company.

And this brings me into a brief segue about Apple options being on default instead of the user toggling them on. That does annoy me somewhat.
 
  • Like
Reactions: Paddle1
This is going to result in regulation, I'm willing to bet big money on that.

Apple better get this **** under control. A good start would be to only do the 911 calling if the phone is paired to a car's bluetooth.
Would not work for older cars. I don’t understand why Apple can’t pair data from location and speed of travel etc to elminate false positives.
 
Would not work for older cars. I don’t understand why Apple can’t pair data from location and speed of travel etc to elminate false positives.
What speed should you be limited to for the notification to be disabled? It would be a brave person who eliminates certain people from a safety feature based on where there are or how slow they’re going.
 
Really sad that this would’ve resulted in a major scandal a couple of years ago and now it’s just another of Apple’s seemingly never-ending **** ups. How you don’t think to test with such activities before launching such a feature with millions of people throughout the world is something that only the Apple of today can do despite charging more and more ✌️


You could. But I think this doesn’t apply when the device itself is responsible because this is totally a **** up by Apple, not the customer.
Major scandal? Give us a break.

Love how quick some people are to rip Apple for anything less than their imagined perfection.
 
Major scandal? Give us a break.

Love how quick some people are to rip Apple for anything less than their imagined perfection.
exactly. Every slight thing that wasn’t in the original script book means it’s the end of the world for Apple apparently.
For me, if it saves a life… There is no indication at all that increased false positives have actually caused the life of anyone. Purely subjective potential whinging from the anti-Apple camp.

At least Apple are trying. Can you imagine if these same people who whine such much had a loved one who died in a car crash because there was no way they could let emergency services know?
 
As an engineer, the algorithm change should be very simple... not sure why it's not implemented yet.

Crash detected -> Verify GPS location (exclusions for amusement parks and ski slopes) -> Call or not call 911
Maybe it’s not that simple. What if GPS location could not be verified because the phone is hidden or unintentionally shielded in such a way that GPS location is either inaccurate or not accessible?

Perhaps, though, Apple could make the device more conservative and caution users too that IF GPS location cannot be verified, that the phone will not dial 911.
 
As an engineer, the algorithm change should be very simple... not sure why it's not implemented yet.

Crash detected -> Verify GPS location (exclusions for amusement parks and ski slopes) -> Call or not call 911
And if we find it does the same thing when people jump off a jetty? Or someone falls off a mountain bike or skateboard? I’m not sure what simple means, but it seems more complicated than that.
 
And if we find it does the same thing when people jump off a jetty? Or someone falls off a mountain bike or skateboard? I’m not sure what simple means, but it seems more complicated than that.
These 50000 feet answers are always good...on paper only. Maybe the box labeled "crash detected" could be expounded upon in great detail and the results sent to Apple.
 
  • Like
Reactions: steve09090
As an engineer, the algorithm change should be very simple... not sure why it's not implemented yet.

Crash detected -> Verify GPS location (exclusions for amusement parks and ski slopes) -> Call or not call 911

I don’t know. With all the inner working of today’s phones, this honestly seems to me like a good solution would be to use the gyroscopes and gps location in tandem. Heck, yesterday I was briskly-walking to catch transit while noticing my phone was vibrating inside (I assume from the gyroscope). Looking down, my app started to snow. Last week, a friend of mine challenged me how high up we were from our starting point, and our phones could tell us without needing an extra app.

If a phone remains at point A for an extended amount of time after a crash detection, then that’s when it should dial out. However, every effort should be made to see if the user is still active using the phone’s internal components. The tech is already there.
 
  • Like
Reactions: steve09090
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.