Issue with Proximity Sensor during calls - Continued.

This thread is a continuation of Issue with Proximity Sensor during calls which was getting too long and causing some browsers to time out. The old thread has been locked and the last post links to this thread.

Thank you.

Apple Discussions Hosts

PM G5, iMac, iPods, Mac OS X (10.6.4), Mac OS 9.2.2

Posted on Jul 14, 2010 6:16 AM

Reply
1,684 replies

Jul 24, 2010 9:21 AM in response to mbassoc2003

mbassoc2003 wrote:
Apple staff must be so sick of people going in to their stores to complain about the phone. The whole **** world knows sensor issue some buyers have an issue with, and yet people go ahead and buy the phone and then have the nerve to go in and complain about it, even though they knew before hand exactly how the phone was performing.

Buyers like that are what's giving iPhone users a bad name in general and make forum users look like a bunch of whining whinging old women.

Yes there is an issue. Yes it's a difference in the design of the new hardware. Not it won't be fixed by a recall. Apple are trying to find out just how much of a fix they can engineer into the next software release. Yes, it will probably be a software button to allow you to manually disable/enable the screen becasue no they can't fix the hardware.

You all know it. You all have the right to return and pull out of the contract.

Stop all the @oddam whining and whinging and get a life!



I find posts like this to be offensive and counter-productive.
People here are just trying to gather information as to what to do about their recent purchase. I've got 2 weeks to decide weather to return in iPhone 4 and reactivate my 3GS. I'm waiting for "the Fix".

I'm mad too like everyone else that has this proximity sensor issue. We paid good money for a high-end product and it's not. If this is a hardware issue then there is no why a "button to allow you to manually disable/enable the screen" is going to be satisfactory, as you put it. I'd like to know where you're getting your information.

Jul 24, 2010 10:01 AM in response to mbassoc2003

mbassoc2003 wrote:
Apple staff must be so sick of people going in to their stores to complain about the phone. The whole **** world knows sensor issue some buyers have an issue with, and yet people go ahead and buy the phone and then have the nerve to go in and complain about it, even though they knew before hand exactly how the phone was performing.


Actually, the whole world doesn't know about the sensor issue...I certainly didn't. The media has been so focused on antenna-gate, I'd never heard of, nor did I even know what a proximity sensor was until yesterday! I wasn't trying to be an early adopter - my 3G just happened to break (water spill) and went into the store to replace my beloved phone with the new model.
I figured I could live with the antenna stuff since Apple (in the store and in Job's dog and pony show) said that the cases fixed that problem. Now I'm wondering how many people thought it was the antenna dropping calls, when actually it was their own cheek! And by the way, I'm also having Bluetooth issues...I have to re-establish the connection every time I get into my car. We're all Apple lovers here, what is weird to me is why someone would be wasting their time lurking here and assaulting people who are just trying to figure out what's going on with their phones?

Jul 24, 2010 11:12 AM in response to Steve Kornreich

@Steve Kornreich

I'm in the same boat as you - returned the iP4 a few days ago and was pretty psyched about picking up the Captivate and giving Android a try. The specs and the little I used it in the store were all good. Something made me hold back (probably fear of buying anything after the iP4 experience), got home and researched the Captivate a bit more. You should check out all the user forums on this phone - androidforums, xda-developers, etc. The Captivate has a ton of issues right now, including totally non-functional GPS, terrible battery life, WiFi issues, etc. Some issues seem constrained to certain phones (like battery life), others (like GPS) seem universal (and the GPS fix only works for some people, and usually temporarily). I think the number of issues are actually higher on the Captivate than the iP4, though at least you can make calls on the Captivate.

I'm not trying to slam either phone, but it goes to show that the iP4 isn't the only phone having serious issues right now. HTC Incredible and Droid X and Evo, all having their own issues. At this point I have no idea what to do, I think I'm going to hold off on anything, hope Apple fixes all the issues with the iP4 (or wait for some other manufacturer to release a solid smartphone, maybe Droid 2). Good luck.

Message was edited by: rsage

Jul 24, 2010 12:28 PM in response to dmorris01

dmorris01 wrote:
Hey friend, why not STHU? Or, if you don't like the nature of the SUPPORT FORUM, leave until your guys prepare a fix that allows their phone to function correctly.


There's a small group of users on here who, for whatever reasons, want this to be anything but a support forum. They're easy to spot and seem to be the most active people here. If they had their way, every thread would be sunshine and lollypops about how great the iPhone is.

Usually, their progression of "helping" follows:
1) deny that the OP has a problem and imply that they are lying.
2) insist that the OP simply not using the device correctly.
3) tell the OP that the problem is AT&T or will be fixed soon by Apple.
4) tell the OP that they should just take the device back and "shut up".

Jul 24, 2010 12:46 PM in response to rsage

rsage wrote:
I think the number of issues are actually higher on the Captivate than the iP4, though at least you can make calls on the Captivate.


Hmm.. interesting to hear as I was looking at the Captivate, as well. Will be interesting to see how Motorola handles the issues and if they have learned anything from observing the iPhone 4 issues.

I really [edit]agree with those who say[/edit] the way Apple handled/is handling everything is a large part of why people are so upset. They're even continuing to add videos to their "other phones are as bad as ours" page(s).

Message was edited by: Denethor1977

Jul 24, 2010 12:44 PM in response to bobditch

Was having issues with sensor, but went beyond that. After answering and talking for 15 minues - somehow the phone managed to drill down to the ringtone mene and started playing ringtones in my ear while I was on the phone. Went to Apple store today, they suggested either reinstalling 4.01, which I had already done, or giving me a new phone. I chose the latter. Looking forward to see how this one works.

Jul 24, 2010 12:53 PM in response to Denethor1977

Denethor1977 wrote:
Hmm.. interesting to hear as I was looking at the Captivate, as well. Will be interesting to see how Motorola handles the issues and if they have learned anything from observing the iPhone 4 issues.


Captivate is Samsung, not Motorola (i.e. it runs on Android, but it's not a "Droid"). If it was Motorola, I'd be a little more optimistic the Captivate would see fixes sooner rather than later.

Jul 24, 2010 12:55 PM in response to wgaller

You may get lucky and not have any further problems, but most people on here who have obtained replacements have reported that the problem persists with the new device.

Also, depending on how you interpret Steve Jobs's mention of it in the press conference, the argument could be (and has been) made that it is a software issue. He said that they would try (not the best word choice) to address it in the next update.

wgaller wrote:
Was having issues with sensor, but went beyond that. After answering and talking for 15 minues - somehow the phone managed to drill down to the ringtone mene and started playing ringtones in my ear while I was on the phone. Went to Apple store today, they suggested either reinstalling 4.01, which I had already done, or giving me a new phone. I chose the latter. Looking forward to see how this one works.

Jul 24, 2010 12:58 PM in response to rsage

DOH! Have been reading too many articles about too many different phones. 🙂

Have heard that Samsung isn't the most responsive when it comes to updates and such.

rsage wrote:
Denethor1977 wrote:
Hmm.. interesting to hear as I was looking at the Captivate, as well. Will be interesting to see how Motorola handles the issues and if they have learned anything from observing the iPhone 4 issues.


Captivate is Samsung, not Motorola (i.e. it runs on Android, but it's not a "Droid"). If it was Motorola, I'd be a little more optimistic the Captivate would see fixes sooner rather than later.

Jul 24, 2010 2:42 PM in response to Denethor1977

Well I bought an IP4 within it's first week as an early upgrade from O2. Love the phone to bits and strangely, not had many antenna issues, but boy did I have this problem, pretty much every single call.

However, good story here is that I took it back to the O2 shop on market st, manchester and they were brilliant and swapped it within 5 minutes no questions asked for a brand new, boxed and sealed IP4 - only had one or two sensor problems since and I have restored from the backup, so am tracking this one carefully - will be making lots more calls on it this week so am going to log the issue as I really don't want to go back to the 3GS as i LOVE FaceTime and HD video recording and the screen quality.

For all the people who are getting angry at others on here, c'mon, grow up, grow a pair and realise that people are quite rightly wanting to find answers for a device that many of us are paying a lot of money for and that's only fair. You wouldn't buy a kettle that wouldn't boil would you???

Jul 24, 2010 2:59 PM in response to babybearbarker

babybearbarker wrote:
You wouldn't buy a kettle that wouldn't boil would you???


They would if it had an Apple logo on it. 😉

There's a lot of confusion about what to do with the proximity sensor. Some people have had success getting replacements. Others say they've had five phones and had the same problem with all. If it's a software issue (as was implied by Steve Jobs's comments), then it wouldn't seem like swapping would matter. If some handsets are affected while others aren't, then it seems questionable that a software change could fix it.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Issue with Proximity Sensor during calls - Continued.

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.