Continued Proximity Sensor Issue After 4.1 Upgrade

I was told by Apple Care and the Genius Bar that the proximity sensor issue was going to be resolved with the new 4.1 update. "This was after I exchanged the new IPhone 4 two times prior to the update. When the update arrived, it stated the items that would be resolved with the update which included the proximity sensor software fix. This update did not fix the issue and I exchanged my IPhone 4 for the third time with the same issue but slightly worse. Same issue exists with my cheek placing calls on hold, pressing numbers or even worst, placing them on speaker while having a private conversation. I have restored this phone and re-did everything from scratch and yet have the same issue. Is any one else having the same problems that I am facing, or have I just got four bad phones in a row? HELP.

Since I know for fact, it's possible to have a phone without PS issues, I would go to the Apple store, and get a replacement, but I wouldn't leave the store until you're sure the new phone doesn't have the same PS problems. Maybe the Apple Gods were smiling on me, but both my phones were bought on launch day and neither have suffered. 4.1 didn't have a negative effect. And I know people who did have the problem, which 4.1 resolved. You should have a phone that works too.......

Similar Messages

  • Those Who Got 'Reset All Settings' to Fix the Proximity Sensor Issue...

    I thought I would start a thread dedicated only to the steps that people took to get their proximity sensor issues resolved. So far, there are only scant posts lost deep in huge threads.
    For example, did you do a hard or soft reboot after you reset all of the settings? Did you make calls right away? Did you change all of your settings back first before making a call? Did you only change some settings before a call and then others after? Did you set up your visual voicemail right away? The reason why I am asking is perhaps there is a problem with a particular setting that we can narrow it down to...or maybe a certain combo of settings since resetting just the network settings seemed to work for some and not for others.
    Also, if it worked, was it only a temporary fix?
    Please post constructively. I have been following the threads for days, and I am well aware that this may be a hardware issue.

    labeck wrote:
    On my fifth phone and am currently working with an apple engineer to help investigate the issue. The best thing I've done to help temporarily is to reset all settings. That seems to hold for 24 hours or so but the issue always returns.
    Hope you get something to work, but I'm fairly certain apple won't be able to do a firmware update to fix this or they would of already done so or at least mentioned it.
    Thanks! That's what I was beginning to think as well...and it's also what I was most afraid of...
    Message was edited by: labeck
    Message was edited by: LorangeJuice

  • Proximity Sensor Issue, But It's Not The Proximity Sensor...

    So, has anyone had issues with apps that use the proximity sensor (like this one, for example: http://appshopper.com/utilities/touch-lcd-designer-speaking-clock)?
    I noticed, the bright light of the sun seems to be messing it up, and was wondering if anyone else was having proximity sensor issues, without it actually being the proximity sensor (where it seems to think something is in front of it, when it is not).
    When you watch the videos, please put your volume on mute, as there are outside, natural sounds and white noise, that will make you go deaf, if you have the volume on loud. The first video needs the sound on, but low.
    Video of the App With Proximity Sensor Glitch
    http://www.youtube.com/watch?v=Eugw2cVdWbo
    Video of the Proximity Sensor Glitch, Caused By The Sun
    http://www.youtube.com/watch?v=V_zEApUdc5M

    its not that noone cares its that anything related to the proximity sensor has been beaten to death and frankly there is issues with it that may or may not be software related could be hardware related apple said they fixed it and they didnt fix it

  • Otterbox Defender Case causing Proximity Sensor issues

    I think the otter box defender case offers the best protection for my Iphone4 but I also think it is causing my proximity sensor issue. I cant make a call without the screen becoming active. I have surgically removed the built-in screen protector (and the associated glue) but I think I need to remove the small plastic pieces that cover the front facing camera and the sensor. Or I will try another case that doesn't cover the sensor. Has anyone else noticed this issue with the Otterbox case?

    I notice this issue using the case however I didnt notice it until 4.1 and I removed all plastic on the front facing camera and the plastic over the proximity sensor I also removed the plastic covering the screen didn't fix the problem at all

  • Has 4.1 fixed the Proximity Sensor issue for you?

    At work, can't download 4.1 yet, but I'm eager to see if the Proximity Sensor issue will be fixed. This is my last straw, if 4.1 doesn't do it, I'm afraid I can't wait any longer. I need a phone..

    crh24 wrote:
    Pooleman0 wrote:
    For those who are slow on the uptake what is the issue with the proximity sensor? I have noticed no issues with mine.
    We have three iP4s in our family and none are experiencing the Prox issue, but for those that do it is extremely frustrating. Proximity sensor system seems to fail and activate the keyboard at odd times allowing your face/ear to randomly press 'buttons' resulting in all sorts of weird behavior.
    Got it. Mine is fine so I guess I should be grateful. Apart from the signal issues my phone works perfectly. I hope this update doesn't screw my phone up.

  • [Solved] Overheating/fan/sensors issues after kernel updates

    Hi all,
    I realise there has been a bit of correspondence on this already.  I'm after some advice for my specific situation:
    1. My laptop is an acer aspire 5315.  I has well understood overheating issues that arrise due to BIOS problems
    2. Fan control and temperature reporting worked perfectly with kernel 2.6.30, stopped working with 2.6.31 - I assume due to the well documented changes made in that release.  The temperature only seems to be read once - at boot.  sensors never reports a change after that; if the temperature is cold at boot the fan never get switched on.  Unfortunately this happens most often.
    3. I tried setting the recommended kernel option (can't relocate the post now).  It didn't help :-?
    4. I have tried upgrading the BIOS but the distribution from acer is a windows executable (won't run under freeDOS) and I do not have windows installed on this PC (not game to try under wine).
    5. I re-installed the old kernel from my pacman cache only to find that my wireless no longer works (fan works just fine though).
    I'm now totally stumped :-/
    I'd like to update my bios and go with the latest kernel but can't see a way without installing windows.
    This might be fixed in an ubuntu kernel release (https://bugs.launchpad.net/ubuntu/+sour … bug/453700) but I'd prefer not to do that switch... perhaps the same fix is coming to arch?
    I'd accept having to pin the kernel to an earlier version but neet to get the wireless working.
    help...
    edit: 
    I've now managed to get the kernel backdated correctly (so that wireless works as well as the fan) by re-installing the kernel and firmware together.
    Have configured pacman to igmore future kernel updates
    If anyone has any suggestions on howto update my bios I'd be very greatful.
    Last edited by drandre (2009-11-06 13:26:46)

    Hi,
    Got exactly the same issue, after running for a while laptop justs goes off... going to try to regress kernel until issue is resolved
    BIOS update does sound a bit extreme
    MrG

  • Proximity Sensor Issue - Replacement Phone Still doesn't work - Now What?!

    My face continues to press keypad buttons, mute, and End. I got a replacement yesterday and am still having the problem. This is disrupting my business calls and I'm getting very annoyed by the problem.
    How has Apple not considered this a known issue? There was a post about this problem that had over 180,000 views and it has somehow disappeared.
    I'm not really sure what else to do except return the phone and wait till they completely address all issues.
    *****

    Ok-- Im hoping I can help you in some way...
    I got my first iphone and knew of the proximity sensor problem because my sister was having the same issue-- i had issues right away and called the next morning (I called apple support)-- they set me up to get a new phone.... I got my new phone and synched it right away-- OF COURSE IT HAD THE SAME ISSUE.... I called apple support AGAIN and this time I got someone with common sense-- he got me to a senior advisor right away.... and this person suggested I try restoring the phone to "new" and isntead of backing it up from 3GS back up-- to do it as a "new" phone-- this made EVERY app i EVER downloaded in 2 years go back on the phone and took about 3 hours to get back to how I like it... and of course-- its still having the issue-- I am now on the phone with Apple Care AGAIN--- they are in the process of getting me in contact with an apple senior advisor---
    I know that I can return it-- but id hate to return it and find out that fridays press confrence is going to address ALLLL of this and that there is a fix....
    soooo as soon as I am off of here this time I will let you know what they say....

  • Proximity sensor issue resolved :)

    Big daddy resolved it You have to sacrifice resetting the phone using the Sony PC software 1st. Avoid data backup from old accounts. Then, after the reboot is done and Android is reinstalled with update x.x.x.534 goto the dialer & type *#*#7378423#*#* then press dial In the menu that will come go to calibration and then choose proximity sensor. (If you run the test it might give error = -1) Then, set settings to default and it may ask to reboot the device.After reboot type *#*#7378423#*#* then press dial. In the menu that will come go to calibration and then choose proximity sensor do the test and it will show success. VIOLAAAaaaa!!!! Check the phone...it works Have tested this and the issue is resolved on my phone finally ....yippieeeeeee!!! 

    Hi can I restore using phone settings and complete the remaining steps please tell me. phantomrocks wrote:
    looks more like a software glitch to me. gets resolved after these steps as confirmed. Plz dnt 4gt to give kudos
    This is not a hardware problem right??:seismology's:

  • Proximity Sensor problem after update. Lumia 710

    Hi,
    Yesterday i received the update notification to Tango through Zune. After perform the update, I noticed that when making or receiving calls, the screen immediately turned off and is not turned on again until the other person hung up.
    I did the tests in the diagnostic menu, and the proximity sensor always shows "detected".
    The problem is the same as in this post -> http://discussions.nokia.com/t5/Nokia-with-Windows​-Phone/Proximity-Sensor-stuck-in-quot-Detected-quo​...
    I did a rollback to the previous version and the problem was solved, but went update to Tango again, the problem reappears. I notice that problem appears just after the firmware update from Nokia.
    My current versions:
    SO: 7.10.8773.98
    Fw: 1600.3031.8773.12121
    Hw: 112.1402.2.1
    Prod Cod: 059N356

    can anybody help me.......i m facing issue with my proxomity sensor aa when i make or recive the call my phone (Nokia Lumia 710) screen gets disappear ant it comes only when other person disconnect the call. This happens only when i did update my phone with new updates. Can any one tell me hoe to roll back to previous version.
    Help me plz as it is really irritating as i am not able to disconnect the call or can not dial a number after call has been made. HELP ME PLEASEEEEEEEEEEEE........I don't have screen gard on my phone......
    OS version- 7.10.8779.8
    firmware num-  1600.3031.8779.12180
    hardware no- 112.1402.2.1
    bootloader version- 7.33.0.0

  • E-Case iSeries iPhone case - proximity sensor issue

    Hello,
    I have the E-Case iSeries iPhone case for my iPhone 5 ... it's basically a very durable Ziploc bag ... it's great for keeping out dirt, dust, sand, water, etc. (it's nature proof) but I'm having a hard time using Siri with it.
    Basically, every time I try to use Siri while the iPhone is in the iSeries case, the screen goes out and my iPhone acts as if I'm putting it up to my ear; it goes into "headset mode" or whatever it's called when you bring an iPhone up to your ear while using Siri or other services.
    This is very frustraing, especially when it happens while you're in midsentence.
    This happens because the case itself is interferring with the proximity sensor - the same behavior occurs when I take the case off and attempt to use Siri while putting my finger over the proximity sensor.
    Is there a way of disabling this automatic "headset mode" feature while using Siri?

    Yeah, I just saw that in an iFixit.com video.  I slid my phone down a little bit in its slot, so that the sensor was a little further into the handset speaker opening and it seems to help.  Otherwise, I could always cut a little notch there around it.
    I was a little surprsied that three of four AppleCare technicians were unaware of this issue.  I upgraded from a 3GS to the 4S last week and began noticing the problem, thinking it was one of my apps interacting/conflicting with Siri.  I even did a hardware exchange at an Apple store (under warranty) - nobody there seemed to have an awareness of this issue.  I'm surprised.

  • Proximity Sensor issues iOS 5.1

    Since upgrading to iOS 5.1 my proximity sensor has stopped working when a call is taking place. Knowing full well that correlation does not imply causation I need to ask...is anyone else having similar issues?

    I did the same thing...wasted a well-applied screen protector for no reason. 
    Anyway, I went to the Genius Bar today and they tried installing a fresh version of 5.1, saying the version I'd installed could be corrupted.  No help (no surprise).  I was told its probably a hardware issue and I'm out of warranty and for $149 they'll replace it.  I said I thought 5.1 caused it, and that I wasn't inclined to stick with a product when the company's own update is what is causing the problem.  (imo) 
    So now my options seem limited to jailbreaking and using CallLock.  Been researching how to revert to 5.0.1 to prove my point but can't figure out how without shsh blobs previously saved.

  • Major Proximity Sensor Issues on 4.1

    Holy crap. I had few issues with the proximity sensor on 4.0... but since upgrading to 4.1 I am constantly hitting speaker phone and facetime with my cheek.
    What the heck Apple? Are others experiencing the same problems? This is horrible!!
    Josh

    My iphone4 has a proximity sensor fault. The phone comes on when I'm talking and won't come back on (whilst in a leather pouch) when I attempt to terminate calls. I have had five call drop-outs since obtaining the phone five weeks ago. No sounds can be heard when connected to the car device. I tested some test model phones whilst in the Apple store at Bondi Junction, Sydney, Australia and they too showed proximity sensor faults. I checked the internet and there are many reports of the same problems. There is even a youtube demonstration of the same things I've described, but when I rang the Apple service number and visited the Apple store, I felt like an idiot as I was shown that my phone is fine and when I was told not to use the leather pouch (which makes no difference by the way. To date, I have restored the phone to factory settings, obtained a new sim card, downloaded the most recent upgrade (on 11/9/10) and visited the Apple store, yet the problems prevail. Occasionally, the phone does one-off unusual things (like scroll through my pictures at super speed or activate various apps without being requested). Can someone please accept there is a problem and help me out!!!!!!!!!!!

  • Lenovo S660 proximity sensor issue

    Just bought S660 last week. Overall its a nice phone but the proximity sensor is rather buggy. During a phone call ive noticed that initially the sensor works fine but after a minute or so the sensor becomes weak/unresponsive resulting in screen illumination and unwanted touch due to contact with cheek etc. I've noticed that the sensor becomes erratic especially if i receive a call waiting during an ongoing call. 
    The details of my phone are as under:
    Android Version: 4.4.2
    Build Number: S660_ROW_S058_140919
    Would really appreciate if this issue can be resolved.
    Thanks,
    AB

    Hi
    Did you try to factory reset the phone?
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as ''ACCEPT AS SOLUTION"! 
    Unsolicited PM's will not be answered! ....Please post your question/s in the appropriate forum board.
    English Community   Deutsche Community   Comunidad en Español   Русскоязычное Сообщество

  • Has any seen collection issues after 11g database upgrade?

    We do have an SR open.
    Just wondering if anyone else has experienced collection issues after upgrading the db to 11g? Our technical folks are hoping it is something else but for the past few weeks we have seen random issues stemming from collections. We run a full collections 5 nights a week. There are material transactions occurring during the two plus hours of collections. This seems to be randomly skewing on hand snapshots in collections as well as missing supply i.e. work orders. Only impacts a fraction of the records in material transactions and they are different every night.
    Reason I believe it has to do with transactions during collections is one collection run out of the five is generally pretty good...Sunday evening for there is very limited transactions taking place on this evening.
    Thanks in advance

    Answer to above question not required now as:
    Having read the 24th December update of note 761570.1 - 'Database Preparation Guidelines for an Oracle E-Business Suite Release 12.1.1 Upgrade' I have decided to upgrade the database to 11.2.0.x by following the Path C option.
    Unfortunately as the 11.2.0.x upgrade isn't covered by MWIZ yet I will have to follow the manual steps.

  • Proximity Sensor Issue?-Send Feedback

    Yes there is an illusive issue with the Proximity Sensor. We can complain. Or we can help.
    I know Apple does not want people thinking they produce junk.
    Send Feedback!
    http://www.apple.com/feedback/iphone.html
    Describe the conditions when your iPhone 4 malfunctions.
    If we fill the feedback channel with useful data they will have what they need to fix the issue.
    Lets be proactive. Lets be part of the solution.

    I don't think Apple can fix the proximity sensor in the current model. iPhone 4 has been out for 2 months. If the problem was fixable, they would have done it by now. The last iPhone 3Gs has 3 small proximity sensors on the left side of the speaker. To make space for the front camera, Apple moved the proximity sensor above the speaker. In other words, proximity sensor is a Hardware problem that can not be fixed with a software update. IP 4 is almost useless to make phone calls (unless you use it with bluetooth headset or with speaker). But don't expect any fixes until the next model. If you don't like it, return it.
    Read the following horror story from a reporter of PCWorld
    http://www.pcworld.com/article/201232/iphone4_**_a_personal_tale_of_iphone_4woes.html

Maybe you are looking for