Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I’m not exactly sure what these dispatchers can possibly tell Apple…..
Exactly. It just seems like a further waste of their time. I'm not sure Apple can fix this. I'm sure in time they can make it more accurate, but it seems like there will always be situations where it will be nearly impossible to distinguish between an actual crash and an activity.
 
If it works with an iPhone without an Apple Watch, I wonder if it is also triggered if the phone detects a crash without the owner being close to it.
 
Sure thing, but it should be released when it’s reliable and not get in the way of saving other life’s.

The dark figure of delayed emergency call answers because of busy lines with fake iPhone emergency calls is probably much higher. This crap is surely leading to a lot of delayed e.g. stroke or heart attack treatments where every second matters, where every second decides between life, death, wheelchair or bedridden for life.

My take is that Apple has tested this feature behind closed doors as much as they reasonably could. Now that the feature is out in the real world, they will get more data, and continue to iterate and improve on said feature. That’s simply the nature of tech.

Come to think of it, Google likes to boast about android sporting a similar feature, yet we have never seen reports of false reports coming from android handsets. Is Google’s implementation simply that much better, or are android users simply not using it due to a lack of awareness?

Either way, I see this as a happy problem. Apple will go on to refine said feature, while articles like this raise further awareness that their iOS devices sport it. Google can only resort to taking pot shots at Apple in order to fight for what limited mindshare is left.
 
Crash detection sounds good in theory but this is just an embarrassing disaster for Apple. Hopefully they can get this figured out and they don’t have to disable it.

I don’t remember seeing stories like this for fall detection on the Apple Watch. Seems like that should be easier to accidentally set off. Still I’m paranoid about false alerts so I have fall detection turned off.
I’ve had fall detection go off while I was skiing. Arguably I actually fell over, so it wasn’t exactly a “false detection”, but I didn’t know about it until my emergency contact called me back when I was at the café, because the watch was under clothing so I didn’t hear anything from it at the time.
 
  • Like
Reactions: _Spinn_
Simple fix, skiing/snowboarding/rollercoasters are all very distinct profiles of motion that can be detected and could have separate ways to respond for those modes. They could also have a thing that says 'if they get up and keep moving at a normal pace, don't do anything'. They could also allow you a larger grace period, it seems like 30-60 seconds would be 3-6x more time to respond and wouldn't be that detrimental to response time.

It seems this is just a matter of not testing enough as others have noted.
 
Maybe. Previous articles claimed that most of the calls have no response (the skier/biker/roller coaster rider/etc doesn't even know the phone that is zipped up in their coat/pants/bag/etc is calling anyone). And my guess is that if the skier/etc does answer, they will just say "oh sorry my iPhone auto-called you". I don't think they are going to tell a long story to the 911 operator about what turn they were doing or where they were carrying their phone etc.
The location information is sent to the dispatchers and the number it’s from.
 
My take is that Apple has tested this feature behind closed doors as much as they reasonably could. Now that the feature is out in the real world, they will get more data, and continue to iterate and improve on said feature. That’s simply the nature of tech.

Come to think of it, Google likes to boast about android sporting a similar feature, yet we have never seen reports of false reports coming from android handsets. Is Google’s implementation simply that much better, or are android users simply not using it due to a lack of awareness?

Either way, I see this as a happy problem. Apple will go on to refine said feature, while articles like this raise further awareness that their iOS devices sport it. Google can only resort to taking pot shots at Apple in order to fight for what limited mindshare is left.
Apple loves to save money by using their user base as beta testers. No reason to have this feature on by default.
 
But Apple doesn’t market that very well. They emphasize on it too much. Not many people out there know you can disable it unless you really look into it.

Also, why am I disabling a feature that’s not going to work properly in the first place?

Skiing is an edge case. The crashes are usually okay, but not always. It’s very difficult to know if a crash is severe. Face smashing a tree and falling on to a snow bank is exactly the same. Don’t throw away the baby with bath water.

Just like Apple Watch may send you a high heart rate notification when you see a crush or getting really turned on while someone is going down on you. How would Apple know that’s actually safe? That’s challenging from the engineering stand point.
 
To be fair, many WFH employees don’t have a lab set up in their basement to test such features. Should have waited until everyone is back in the office to get this feature right
 
  • Like
Reactions: gusmula
[…].

Come to think of it, Google likes to boast about android sporting a similar feature, yet we have never seen reports of false reports coming from android handsets. Is Google’s implementation simply that much better, or are android users simply not using it due to a lack of awareness?
Nor do I recall it’s been reported that googles feature saved a life or resulted in a rescue either.
 
I wonder how this is going to work as more and more people have devices with this feature. Say there are five people in one vehicle and they crash into another vehicle carrying four people, and they all have phones or watches with Crash Detection. Is that going to be nine calls to the dispatch center, plus more from witnesses?
Probably like usual they must have a system to know if calls are in the same area for the same thing. There were people fighting in the street once. We called 911, but they said they already got calls.
 
If one of the worlds biggest and smartest and safest tech companies release a feature, but don't actually test it irl before releasing it, then they are not the biggest and smartest and safest tech company, they are a joke. And anyone here willing Apple to hurry up and fix it have jumped a step.
 
  • Disagree
Reactions: I7guy
There is 100% no way Apple would not have known about this kind of issue because of something in the design process called 'Brainstorming'. It is a practice used by all design engineers/design teams during the design process of a product whereby the design team all get together in one meeting and throw out ideas/suggestions/thoughts as to what could go wrong with the product. Every and all is considered regardless of how ridculous the idea/suggestion/thought is and then one by one each idea/suggestion/thought is discussed at length to determine if it's valid or not. I've been involved in design process and thus seen it in action first hand.

The ONLY way skiing and rollercoasters would have not featured in crash detection is if someone senior in the decision making removed them from the results of 'Brainstorming'.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.