iPhone 4S - Outgoing call no audio

Encouraging news! What does one have to do via "restore"? May it's my lack of knowledge but it sounds like going back to some previous settings - don't wish to lose my customised settings?

Make a copy of Your iPhone in iCloud before. After that in iTunes chose "Restore my iPhone" and later "Restore from iCloud" (I'm not using English OS, but something like that) - all Your settings and data and everything will come back, and the iOS version will be uppgraded to 5.0.1 (9A406).

I still have doubts whether it was really as simple as it was and would like to here whether it helped.

Hello Romelanda

yes I have 5.0.1 9A405 but how can I install the mini one?

Regards Ralf

Hi postings at the same time :-)

Ok but exactly this i had done on Sunday ?

I've had 9A406 installed since it was released and it DOES NOT solve OCNA.

Well, than I don't know... I will know more after a day or two and more placed calls. I forgot to ask him when 9A406 was released.

Got the 4S just 10 days back and have the same issue. It is so random that it is difficult to figure out as to what is triggering this issue. Hoping that 5.1 will fix this issue. Else, I am taking the phone back to Apple for a replacement.

Do You have iOS 5.0.1 (9A406) on Your iPhone?

Yes.

APPLE PLEASE SHOW US SOME COURTESY AND ACKNOWLEDGE THIS PROBLEM PUBLICLY.

I have exactly the same problem with my 32gb iPhone 4S. Intermittent OCNA worse after using headphones and often happening in clusters in general one out of four calls ever since I bought the phone in October. Almost always resolves after putting into speaker phone mode and back out but recurs soon after.

I called apple telephone support and they pretended they had never heard of such a fault. Told me to erase and restore my phone.... Several hours later the problem was still there. Called them back and they decided it must be a hardware fault so made me an appointment with a "genius" at an apple store for a phone replacement.

Apple store "genius" had also apparently not heard of the problem. Checked the diagnostics on my phone to no avail. Agreed that if erase hadn't worked then it must be hardware. Swapped my phone for a new one and restored from iCloud.... However the problem returned.

Then erased phone and set up as new phone- seeded to work. They concluded it was a problem with my backup, probably as it came from an old 3GS. Their advice: start afresh with a new setup but no way to restore text messages or app data. I'm not keen to do this as I'd miss all my text messages. This is very much a work around rather than a fix. I hope it is addressed in IOS 5.1

Whether it is or not I think I would like to reiterate the sentiments of many of the previous 2380 comments and the thoughts of many of the 273842 views of this discussion by saying, as above:

APPLE PLEASE SHOW US SOME COURTESY AND ACKNOWLEDGE THIS PROBLEM PUBLICLY.

It would be nice to know that it is being addressed and that you care about your customers problems with your otherwise good but very expensive product.

Thank you.

I have 9A406 and the problem exist there too. I have had it on the phone since I got it. Called Apple support but they wanted to charge me to diagnose the problem, that it may or may not be hardware. Trying to get a replacement phone from where I purchased it. Negative apple support, I may end up just returning the phone with this issue and battery performance.

After several succesfull calls with upgradet iOS 5.0.1 (9A406) the problem returned...

Apple knows about this problem. It is a hardware problem. If they manage to make a software fix, it is a software patch to initialize the hardware in a different order to circumvent this hardware problem from occuring. My guess, given the lack of addressing this, is that it can't be done. After emailing Tim Cook I was contacted by an Executive Relations liason. She spoke in round about codified legalise, but she did indicate that apple does monitor these forums but does not reply in them. She also indicated that 'everybody's problem could be different, therefore we want individual customers to contact us directly'. This is corporate speak for 'we don't want a mass product recall, we want to wait for consumers to come to us demanding replacements before we take action.' This is a cost savings measure, plain and simple. Apple is banking on the fact that you'll sit with your crappy defective phone and just take it.

I replaced my phone twice in a row. It now works fine. I only monitor this thread to see how crazy it gets.

Also, when you think you've found the magic software patch, please, in god's name, wait a few days before declaring that you've "found the fix!" It's happened 4 dozen times already throughout this thread and it never works out. Please, save us the frustration of being strung along and just wait 3 days before posting here. It's like lemmings.

I'm not disputing your info, but there is a fix for the problem in 5.1. There are many that have posted on this forum, including me, that have installed 5.1 beta 3 and the problems are now gone. I have been using the 5.1 beta 3 software for weeks with zero issues. Did Apple tell you exactly what part of the hardware is defective? Because of the behavior of this problem, I find it hard to believe that it is hardware. There have also been claims from folks that have the iPhone4 that have had the problem as well and a software restore fixes the issue for them. I still think it is software related and Siri has someting to do with the issue. After all, Siri is beta software at this stage. Word is that the offical release of 5.1 is March 9, Ill wait to see what that does before I exchange my phone if it needs to be done.

I'm glad to hear something is working for you. I've heard others who have this same update who it did not fix the problem for.

Here's the thing, and this has been explained by several people eariler in this thread. Just because a software patch fixes something does not mean that it is not a hardware problem. Hardware is often initialized in different ways and configurations depending on software control. If apple finds some way to initialize the audio receiver hardware in a different order that may ciurcumvent the faulty hardware exhibiting its behavior, then a software patch will hide the hardware problem. Sometimes this solution is elegant, sometimes it is not. It sounds like, and I've been following this thread since 30 pages or so, Apple is aware that it's a faulty audio reciever switching component that controls switching from ear to jack to speaker. This piece is under software control, so Apple might find some workaround. I do believe if they have found it they would announce it and address this issue, as it has been a thorn in their side. They are very aware of this, they are just not making any public statements about it.

Anyhow, I'm glad you have found your problem fixed!