Issue with Proximity Sensor during calls - Continued v2

dbk9999 wrote:
The problem is, we know there are at least a few older phones out there that never had a problem with my test, so when we hear about new ones working, it's hard to tell if they improved the hardware or if we are just seeing some random chance.

Thus I'm hoping a LOT more people will report in telling us they work and what week it is - especially if they don't have 4.2.1 on it yet since that update has helped a good number.

The testing now just changes focus somewhat - what date phones will consistently pass it (if any are really consistent). For that we either need LOTS of positive reports or reports from one or two who test multiple phones.

Something else I need to do and didn't think about it when at the store is to try the phone that passed my test on my shoulder. *On my phone, unless I really make a special effort to press firmly to keep it against my ear, it will always come on. While I can live with that, it would be much better if it worked then too.*

wait a minute... when you say "your phone" does it have 4.2 installed? if it does and you are still having ps issue when its on your shoulder then its still broken man.

just go and exchange... this is hardware... maybe apple figured out a clever way to manipulate the IOS firmware to further minimize the issue but if even a small portion of users remain affected then its a hardware issue that can probably never be completely fixed via updating.

if people still have issues after 4.2 then i think its safe to say this is a hardware issue plain and simple. doesn't matter how few there are its still a percentage. a few people on a forum with 10 or 15 posters is actually a very substantial number percentage wise.

No, I'll not exchange it at this point - not until I have a lot more evidence that newer phones don't have the problem. Remember, every phone I've tested, except for ONE from week 46 (not enough to show a trend) have the same problem.

Meanwhile, the one I have now works pretty well - especially since I know how to avoid the problem or reset it if necessary.

So, why take a chance on possibly getting one that is worse? Don't want to go through the constant exchange process. Besides, at this point any unit replacement will probably be refurbished. That's fine, but what if it is refurbished from week 22 to 40? If they did make hardware changes later, those may not have it so another reason to sit tight for now.

Finally, it is possible when the next model comes out, I may look at what price I can sell this one for. If it is enough to bring the net cost for a non-subsidized one down to "normal", I may do that. We are only about 6 months away from when a new model may be coming.

4.1 fixed my fourth iP4's PS issue greatly. Now, slowly, I can say with certainty that 4.2.1 has made it considerably worse... the PS problem is back for me. I guess it's back to the store for a 5th phone and I will not accept anything other than a brand new, in the box model... just like #4.
Just insane, this thing.

chotty1 wrote:
4.1 fixed my fourth iP4's PS issue greatly. Now, slowly, I can say with certainty that 4.2.1 has made it considerably worse... the PS problem is back for me. I guess it's back to the store for a 5th phone and I will not accept anything other than a brand new, in the box model... just like #4.
Just insane, this thing.

Excellent Post! thats exactly what happened to me on 4.1

this post really illustrates why this is a hardware issue and can probably never be fixed 100% for every phone via software updates.

i am sorry to hear you are having problems though... really stinks but there is some lament. We have found that Apple is fixing the Hardware at the factory and that you CAN exchange and get a working phone. Many of us now have working phones and are completely satisfied including myself.

good luck Chotty... and i hope you get a working phone!

Issue: Customer claims the phone mutes calls and ends calls because their cheek presses the buttons
Steps To Reproduce: Visually verified. I explained to the customer that it was a user error and that a unit replacement would not solve the issue. Customer insist on phone replacement.
Proposed Resolution: Unit replacement.

Guy was a jerk about it at the store.

I've been gone for a long time from this thread... namely because 4.1 fixed the problem!
Without rehashing newer posts, what is the bottom line? Demand a week 42 or newer model?
Is that the consensus?
I'm not going to bother going near an apple store this time of year, thank you... I've had enough "fun" with this horse hockey.

How do you determine the week of manufacture?

Don't know if there is any consensus. Near as I can tell, before 4.1 LOTS of people had trouble and only a few said they didn't (who also did my tests). Plenty of others said they had no problems, but when I tested them, the same problem existed.

Some got worse with 4.1, some got better. I'd say the trend was positive though. And more got better after 4.2.1 and, as usual, some got worse or stayed the same. There is VERY LITTLE data to go on with that change so I'm mostly left with the fact that relatively few are complaining now.

Some reported week 42 or later is better. We've had that kind of report at least twice before which turned out to be bogus. All I can say is that I found one from week 46 that would not fail my test. It's just that one test isn't enough. We need at least a dozen or so from that period making reports. If you get almost all positive reports, that could represent a hardware adjustment.

I'm hoping the Apple stores will keep putting newer ones on display so I can check them. Until that week 46 phone, every one I ever tested failed the test. But the next newest was around week 35 or something (mine is 37).

The serial number gives this info:

The first two digits are the manufacturing plant ID.

The third digit is the last number of the year (so "0" so far). The forth and fifth digits are the week of manufacture since the start of the year.

My proximity sensor is completely malfunctioning to the point where I would never recommend any consumer purchase this phone. I don't even use the phone that much (I mostly use apps or just browse) but it is so frustrating when the calls to my family (who don't text or anything) will drop 5/6 times per call. Today when I was talking to my dad, my iPhone 4 put him on hold and called up my mom. They are divorced, from a while ago, and I am just thankful that the phone didn't decide to conference them together! The other times it just hung up and at towards the end of the call started dialing numbers.

It's at the point where I just want to get a different phone and would wish Apple would refund my purchase. I'm not sure if it happens on every call, but it does happen on nearly 100% of any longer calls. It's impossible to stay on hold for tech support or something like that. Those situations will drive you mad because you feel compelled to try the call again only for the same result after waiting twice so patiently.

It seems like something like this should void the warranty because the phone is inoperable. I'm taking mine back to the store tomorrow and seeing what happens. I kind of hope that by going there, somebody will tell me how to fix this problem because it is enough to drive me absolutely crazy.

Don't know how much of this huge thread you've read, but here are things you should check:

What version of the iOS are you using? If 4.0 or 4.0.1 you definitely need to upgrade because 4.1 made some worthy changes to the sensor operation. Didn't work for everyone, but you have nothing to lose.

4.2.1 was next and while Apple didn't say it did anything to the sensor, I can tell from my tests that it changed it some. Again, some people say it solved their problem and a smaller number say it didn't.

If you already have the latest version or upgrading doesn't solve it, I think you can get an exchange. Some people say newer phones work better (week 42 or later), but there haven't been enough reports to confirm that. But if they exchange your phone, it will probably be a refurbished unit. But hey, if you keep having problems, you have cause to insist they give you a new one - some have succeeded in that.

One other option in the meantime. Download the "Call Guard" app. You make your call and then launch the app. It gives a blank screen so you can't accidentally activate anything. It also registers every time you touch the screen, and where, so you can go back and see if you would have had problems without it.

If you want to end your call, you can press the top button, which disconnects the call. Or press the home button to quit Call Guard and then take the steps to reach the call screen.

man i would honestly wait till after the holidays and then just go return. I have heard people say they demanded a week 42 or newer but i dont know. I just kept waiting until i felt like the odds of getting a working model were high enough to justify another trip to the A store. i didnt ask for anything special but maybe i should have.

If you've read my previos posts you will know that my week 30 ip4 4.1 is majorly a pain in the ***! But for my 2 cents, i finally found a friend of mine with week 46 ip4 on 4.1 and during my tests of her phone noticed there was absolutely no problem.

Guess Apple pushed 4.1 to inadvertently cover up the flaw while then releasing more stable models without the ps issue.

For me, I was on the brink of going Android, but as i love my Apps will prob hold out till the ip5 comes out.. Even then, i wont be rushing out to get one until its confirmed that it works as a **** phone first!!

"The third digit is the last number of the year (so "0" so far). The forth and fifth digits are the week of manufacture since the start of the year."

In that case, there's a fly in the theory - my phone is from week 38. The good one, the one without the PS issue. Too bad I don't still have the S/N from the first (bad) one laying around, but I know it had newer software pre-loaded so I suspect it was built later.

There have been good phones from the start. The week of manufacture doesn't guarantee a good or bad one - the theory that phones after week 42 (or 46) are better because of some change would, if true, simply mean that you chances of a good phone are better.

So far, I haven't seen anyone report a week 46 or later phone that didn't work properly. I've only gotten to test one, but it passed both my two main tests. OTOH, no phone I've tested passed either test prior to 4.2.1 - yet others have had them pass, but it's only a handful that actually took the test and reported success.

After 4.2.1, I can only get the older phones to fail one test - unfortunately, the most important one.

But even phones that fail can work well enough for many users, depending on handling habits when on the phone or shape of their ear.