How to stop iPhone from automatically calling missed calls

[C DM]

There is no point in sliding open a missed call on a locked screen if it doesn't give you the option to do other things beside automatically dialing the caller.

Is there a way to disable the feature of my phone showing me missed calls on a locked screen? This false convenience beckons one to open it. It's counterintuitive when compared with opening up a contact in the contact list and having all of those options to its one auto-dial option. Silly, really.

I use it all the time to call back a missed call right away when I notice it. What's the point of me unlocking the phone (with my password on top of that) going to the phone app and then the recents list there and calling back at that point when I can do it in one quick action from the lock screen?

Even if you don't use it for that for some reason, why get rid of it and not even know you missed a call (at least not until you unlock), rather than just leaving it and simply using the regular slide to unlock method to unlock the phone at that point?

----------

I agree that it's a bad design... and has been for years. I find myself accidentally tapping things all over iOS. Accidental calls, unknowingly tapping a notification banner instead of the top toolbar b/c the notification comes in mid-tap, etc.

I wouldn't hope for any immediate fixes.

You can disable notification banners, unless you are looking for something differnt from them...not sure what exactly though.

 

[texasmccoy]

Me too

Bumping this thread.

I too have had this problem for several YEARS now and it's getting quite annoying I'm not at all a newbie to Apple or iPhone, and I still do it! I think many answerers to this thread are misunderstanding the question. The problem is not that we are trying to see the contact details (aka "tapping the blue arrow on the right") and accidentally call someone. The problem is that we are simply innocently scrolling through a list and an unintended finger movement interpreted by iPhone as a "tap" will call someone we don't want to call! I have noticed it does this not only in the "recent calls" area but also in certain situations in messages and/or viewing contact details, this accidental-dial problem happens too.

Contrary to what has been posted by others here, just because the accidental call doesn't start ringing on your end doesn't mean it doesn't start doing something on the unintended recipient's end. Once I accidentally dialed a guy I had dated in the past and was now completely uninterested in. He was one of those annoying "clingy" people whom I kept his phone number in my contacts list only so that I'd know it was him calling/messaging and hence not accidentally answer because I didn't recognize his phone number. I hit the button to cancel the call literally just fractions of a second after I accidentally called him with the accidental "tap". Apparently the unintended call still started going through (damn fabulous digital signal!) After that accidental dial I got calls and messages from him for many weeks afterward! UGH!!!

I would REALLY like to know if there is an app out there that will work with iOS and ask something like "Are you sure you want to call so-and-so?", similar to the well known "Are you sure you want to close (whatever)?". It would be AWESOME if Apple would make an *optional* feature in the phone settings for the user to turn this sort of double-check system on, but I'm not holding my breath for that come around. If anyone out there with some wisdom on this problem has any suggestions on how to prevent this stupid unintentional user-error-dialing, please share thoughts! I'm very open to ideas... thanks for your time!

 

[laudern]

You're scrolling wrong.

 

[Ann P]

Bumping this thread.



I would REALLY like to know if there is an app out there that will work with iOS and ask something like...

As far as I'm concerned, no App Store app has the permissions to do that. There's a jailbreak tweak called 'AskToCall' that confirms before dialing. One of my favorite tweaks and the first one I install on all my phones over the years. You may want to look into that.

 

[jmulho]

user error?

Those of you who say this is user error don't understand interface design.

Take the famous example of the door handle. A door that opens one way typically has a rectangular (push-able) plate on one side and a U-shaped (pull-able) handle on the other side. If a designer decides to put a U-shaped handle on both sides, because for example they think it looks better, many users will approach the door from the push side and first try pulling the U-shaped handle. When that doesn't work they will try pushing it. When that works they will look around to see if anyone witnessed their "user error".

If I click a button that says "call", I expect my phone to make a phone call. If I click a person's name and my phone calls them against my wishes, this is design error.

 

[jaymc]

I agree that it's a bad design... and has been for years. I find myself accidentally tapping things all over iOS. Accidental calls, unknowingly tapping a notification banner instead of the top toolbar b/c the notification comes in mid-tap, etc.

I wouldn't hope for any immediate fixes.

Hope this is fixed in iOS 8 ... anyone confirm?

 

[C DM]

Those of you who say this is user error don't understand interface design.

Take the famous example of the door handle. A door that opens one way typically has a rectangular (push-able) plate on one side and a U-shaped (pull-able) handle on the other side. If a designer decides to put a U-shaped handle on both sides, because for example they think it looks better, many users will approach the door from the push side and first try pulling the U-shaped handle. When that doesn't work they will try pushing it. When that works they will look around to see if anyone witnessed their "user error".

If I click a button that says "call", I expect my phone to make a phone call. If I click a person's name and my phone calls them against my wishes, this is design error.

But that is the design of it. There isn't a set design in place that everyone follows, there is a design of a particular phone/OS that a person learns to use when they get that phone/OS.

 

[jmulho]

But that is the design of it. There isn't a set design in place that everyone follows, there is a design of a particular phone/OS that a person learns to use when they get that phone/OS.

If a significant fraction of users "can't learn" to stop making accidental phone calls, perhaps the design is confusing, or too hard to learn (i.e. a bad design). If users don't have to learn anything in order to avoid making accidental phone calls, that is known as a better design.

Given the potential serious consequences of accidentally calling certain people (losing your job, for example) an option to confirm before calling (or confirm before calling specific contacts) seems like a valuable missing feature.

 

[C DM]

If a significant fraction of users "can't learn" to stop making accidental phone calls, perhaps the design is confusing, or too hard to learn (i.e. a bad design). If users don't have to learn anything in order to avoid making accidental phone calls, that is known as a better design.

Given the potential serious consequences of accidentally calling certain people (losing your job, for example) an option to confirm before calling (or confirm before calling specific contacts) seems like a valuable missing feature.

Doesn't seem like there is a "significant fraction of users" that "can't learn how to make accidental phone calls".

That said, it wouldn't be a bad idea for there to be an option to allow enabling or disabling something like that (as is the case for a number of other options that aren't offered in iOS).

 

[jmulho]

Doesn't seem like there is a "significant fraction of users" ...

Let' find out.

I want a confirm before calling feature:
Yes: 1
No: 0

 

[westoncp]

It really is a terrible design flaw. It drives me bananas on a daily basis mainly because I work with my hands and have to quickly click on options without dropping what I'm working on. I can't imagine why they would think the majority of the world would prefer to have an IMMEDIATE call back function without verifying that was the intent. A function you can't change in the settings even though... going out on a limb here... nobody immediately calls anyone back anymore. The studies showing the massive decline in actual phone calls should be understood by the worlds leading multi communicative device manufacturer. Umm maybe a text to respond option would've hit closer to the mark with their demographic.

And please go easy on people questioning apple's design choices. Yes they make an amazing product but they make mistakes like every other company in the world. Blaming the consumer for not retraining themselves away from an intuitive response on a machine that is touted as having one of the most intuitive operating systems available is a very weak argument.

Apple, just make it changeable in settings. Stop forcing us to "jailbreak" our devices to keep from throwing them through a window.

 

[bobr1952]

It really is a terrible design flaw. It drives me bananas on a daily basis mainly because I work with my hands and have to quickly click on options without dropping what I'm working on. I can't imagine why they would think the majority of the world would prefer to have an IMMEDIATE call back function without verifying that was the intent. A function you can't change in the settings even though... going out on a limb here... nobody immediately calls anyone back anymore. The studies showing the massive decline in actual phone calls should be understood by the worlds leading multi communicative device manufacturer. Umm maybe a text to respond option would've hit closer to the mark with their demographic.

And please go easy on people questioning apple's design choices. Yes they make an amazing product but they make mistakes like every other company in the world. Blaming the consumer for not retraining themselves away from an intuitive response on a machine that is touted as having one of the most intuitive operating systems available is a very weak argument.

Apple, just make it changeable in settings. Stop forcing us to "jailbreak" our devices to keep from throwing them through a window.

I don't think it is anyone questioning if this is a design flaw or not--rather--it is based on personal experience with the recent call screen. For me, I don't seem to have a problem with the way it is currently set up--meaning I don't hit the missed call number by mistake and cause the number to be dialed--rather I hit the info button if I want to know more about the call. So for me, it is not a design flaw since it doesn't cause me any problems.

 

[Mohli]

Yes I admit I've done this too and hang up straight away. But now I've got used to pressing the little blue arrow.

I have an iPhone 4 it's happened numerous times being a smaller phone! I noticed I'm charged for this even if the phone only rings once. If you don't give any feedback nothing gets changed !

 

[cbreze]

Bumping an old thread to add my annoyance to this ludicrous feature. Scrolling thru my recents list I frequently call someone by mistake. i don't understand why they can't have a simple pop up with the call option. It's far to easy to make an accidental call. This thread is years old yet Apple still insists this is the way it should be. SMH

 

[nieks]

Not to be rude, but it really is your own fault. I have never accidentally called someone while scrolling through the missed calls list. Be more careful when scrolling. Scroll. Don't tap. How hard can it be?

 

[cbreze]

Not to be rude, but it really is your own fault. I have never accidentally called someone while scrolling through the missed calls list. Be more careful when scrolling. Scroll. Don't tap. How hard can it be?

At least your a nice person, not rude. Not tapping, scrolling, but apparently lingering a millisecond to long at times. Problem is when one rarely goes into this log file one can easily forget when one is used to other call log files that don't have this issue. As others above had said it is a not so great option and would be better if this feature wasn't the way it is.

 

[C DM]

At least your a nice person, not rude. Not tapping, scrolling, but apparently lingering a millisecond to long at times. Problem is when one rarely goes into this log file one can easily forget when one is used to other call log files that don't have this issue. As others above had said it is a not so great option and would be better if this feature wasn't the way it is.

To be fair, there would likely be another similar type of thread with some people complaining why they have to spend time confirming placing a call yet again afer they already tapped on it to place it.

 

[cbreze]

To be fair, there would likely be another similar type of thread with some people complaining why they have to spend time confirming placing a call yet again afer they already tapped on it to place it.

That would probably be true. However , I didn't start this thread which is over 4 years old, just adding my disdain for this non(IMO)feature and surprised it is still the same 4+ years later. Apparently the majority is fine with it. I use Android as well as iOS and sometimes the devil is in the details and I forget the little nuances of each as I switch back and forth.
If you've ever declined to accept a call because it was an ex or someone else you don't ever want to talk to then go to delete the number and it rings them back, then, well, oops. It only need happen once to be seriously annoying. Guess I'll be more careful.

 

[potentmf]

I've had this happen to me. Possibly because I'm used to Android giving me the details when I click the number. I do think that there should be confirmation box when you are scrolling through recents call log. I don't even want to get into trying to copy the number to check if it's spam.

While I understand this site is pro Apple, why belittle members that have a particular gripe about a feature?

 

[cbreze]

I've had this happen to me. Possibly because I'm used to Android giving me the details when I click the number. I do think that there should be confirmation box when you are scrolling through recents call log. I don't even want to get into trying to copy the number to check if it's spam.

While I understand this site is pro Apple, why belittle members that have a particular gripe about a feature?

Yup, agree with this^
I like switching between the two OS's and certain aspects of one can trip you up when on the other one. But nothing annoys me more than this simply because accidental presses are to easy. I also like to check numbers for spam and frequently call it back by mistake. I find using true caller helps a lot with the spam calls but it's not perfect. So the idea that Apple has it this way to prevent that extra screen press is pretty lame since it's less than a second of extra time. This thread being started a few years ago obviously means the "feature" has been annoying some people a long time.

 

[jagooch]

The same thing happens to me. I make the right to left swiping gesture as I clear the call log. It goes like this for me.
swipe - cleared
swipe - cleared
swipe - dialing number .. what? That was the same swipe as the previous two! Why is it calling this time? Hurry and press cancel to stop the call!

The same thing happens when I click "edit" first.

The only solution I can think of without a jail break is the to put the phone in airplane mode before clearing the recent call log.

 

[C DM]

The same thing happens to me. I make the right to left swiping gesture as I clear the call log. It goes like this for me.
swipe - cleared
swipe - cleared
swipe - dialing number .. what? That was the same swipe as the previous two! Why is it calling this time? Hurry and press cancel to stop the call!

The same thing happens when I click "edit" first.

The only solution I can think of without a jail break is the to put the phone in airplane mode before clearing the recent call log.

You can clear the log completely with just a tap of the clear button when you are in edit mode. Also in that edit mode to delete individual entries you would tap on the red minus icon on the left first to reveal the delete button on the right which you can then tap to remove the entry. No swiping or accidental presses on the number involved.

 

[daflake]

I think this is totally legit... I do this a lot myself and it is actually annoying, it would be nice to have a little confirm button.

 

[ajxoxo]

Hi. It's me. The original poster from the year 2013. Thanks to those of you who revived this thread. It is now the year 2017, and this annoyance about the iPhone Recent Call list still exists It has been over 4 years and Apple has done nothing to update this poor functionality. I really want Apple to fix this thing I think is not a good User Interface design, but it's been 4 years and they haven't done anything about it, so I guess I shouldn't be holding my breath about it.

Here is the summary of my original complaint... I originally posted a message in Feb 2012 about an issue that I perceive to be poorly designed functionality of the iPhone Recent Call Screen. The problem is when you want to scroll through your All or Missed Call list. If you don't scroll perfectly, and accidentally tap the screen (instead of a scrolling motion), you can inadvertently call back someone who you actually didn't intend to call. Yeah, so instead of your iPhone giving you a pop-up screen that says, "Call" or "Cancel", your iPhone just immediately calls the person you accidentally tapped on. Gee. Thanks for nothing Apple! I just accidentally called back a Missed Call from someone who I wasn't ready to talk to just yet!

And here is the summary of the way this thread went down. After I initially posted the thread in 2012, alot of people criticized me saying that its my fault if I accidentally dial someone back that I didn't mean to. So, yes I am apparently the village idiot who doesn't know how to use my phone despite Android having some sort of call confirm feature to avoid accidental dials. Some people did, however, think that my complaint was valid. So thank you to those people.

 

[potentmf]

Hi. It's me. The original poster from the year 2013. Thanks to those of you who revived this thread. It is now the year 2017, and this annoyance about the iPhone Recent Call list still exists It has been over 4 years and Apple has done nothing to update this poor functionality. I really want Apple to fix this thing I think is not a good User Interface design, but it's been 4 years and they haven't done anything about it, so I guess I shouldn't be holding my breath about it.

Here is the summary of my original complaint... I originally posted a message in Feb 2012 about an issue that I perceive to be poorly designed functionality of the iPhone Recent Call Screen. The problem is when you want to scroll through your All or Missed Call list. If you don't scroll perfectly, and accidentally tap the screen (instead of a scrolling motion), you can inadvertently call back someone who you actually didn't intend to call. Yeah, so instead of your iPhone giving you a pop-up screen that says, "Call" or "Cancel", your iPhone just immediately calls the person you accidentally tapped on. Gee. Thanks for nothing Apple! I just accidentally called back a Missed Call from someone who I wasn't ready to talk to just yet!

And here is the summary of the way this thread went down. After I initially posted the thread in 2012, alot of people criticized me saying that its my fault if I accidentally dial someone back that I didn't mean to. So, yes I am apparently the village idiot who doesn't know how to use my phone despite Android having some sort of call confirm feature to avoid accidental dials. Some people did, however, think that my complaint was valid. So thank you to those people.

OP, pay the criticism no mind. Some people are just willing to overlook certain things in iOS because this is a pro Apple site and anytime someone mentions anything Android does that iOS doesn't it grinds people's gears. Just browse around and anytime Android comes up someone mentions lag or glitchyness, then I look at my 7+ that just froze because I switched out of a game . Bottom line iOS isn't perfect, we all know Android isn't either, but on this particular issue, I do wish and hope that Apple take a cue from Android and add a confirm button. Right now, I make sure to hit the info button, but sometimes if I don't hit it just right it will start dialing.