Currently Being ModeratedOct 3, 2013 5:13 PM (in response to NN2RL)
Power off three times,
rebooting three times,
turn Siri off,
Turn, raise to speak to Siri off,
reset all settings.
Nothing worked. iPhone 5 16GB, proximity worked fine for a year until upgrade to ios7.
Upgraded to ios7.02, repeat the list, still no joy.
I look like an idiot using my phone tilting it away from my face so I do not press any buttons. I still find a way to hit one.
Currently Being ModeratedOct 4, 2013 7:00 AM (in response to Markbp)
Same here no problem before ios7 now lots of "face dialing" muting and speaker dailed by cheek. This is very frustrating as it worked perfectly before and they mucked it up! Please fix this issue apple.
Currently Being ModeratedOct 6, 2013 9:43 AM (in response to Markbp)
iPhone 5 16GB when updated to iOS7 the proximity sensor failed. Tried all sorts of resets, reboots, turning Siri off, nothing worked.
Genius Bar identified several apple apps that were crashing behind the scenes. But a complete restore to manufactures specs, still no sensor.
One hour replace screen and sensor, sensor stil not working.
New phone, same make, model, upgrade to 7.02 everything works including the Siri raise to speak which I am already sold on.
take home message: If one million people upgrade a iPhone 5 to iOS7 and there is a one out of a thousand glitch that means one thousand people have the glitch and most of them are smart enough to go searching for a solution.
Currently Being ModeratedOct 6, 2013 11:01 AM (in response to Markbp)
Turning Siri off and reset all settings a couple of weeks ago has solved the issue for my iPhone 5, iOS 7.0.2.
I have been diligent to pat attention to screen "light-ups" during calls and the problem hasn't come back... once or twice (briefly) the screen lit-up but nothing major. Absolutely is a bug intro'ed by iOS 7 though.
Currently Being ModeratedOct 6, 2013 1:46 PM (in response to doby48)
Same problem for me, Apple Chat Support suggest me to do an Hard reset, reinstalling entirely all IOS 7.02, but no results.
Now I wrote to several OnLine magazine to spread this bug with all Internet communities, hoping that Apple will fix it.
It is not very common but is very annoying....
Currently Being ModeratedOct 6, 2013 11:23 PM (in response to Markbp)
Same problem here, with iPhone 4S and iOS 7.0.2.
I've been turning on speaker or facetime with my cheeks but I guess it only happens with the incoming calls. No such problem with iOS 7.
It is really annoying.
Currently Being ModeratedOct 7, 2013 11:21 AM (in response to Markbp)
I've had the same problem ever since updating to iOS7. I'm on an iPhone 5. Updating to 7.02 didn't fix it. I'm hesitant to "reset all settings" as I don't want to have to change all my settings again. A reboot did nothing. The thing is, it only happens with incoming calls and not on every call. From what I can tell, what's happening is that the sensor activates too late, so my ear is already on the phone and pressing things before it has a chance to activate. After I deactivate whatever it's pressed and put my ear back up to the phone, it's fine.
Currently Being ModeratedOct 7, 2013 11:34 AM (in response to SenorDD)
I've been thinking about this and thought I'd offer up a theory. Not sure what other "background" apps anyone else is running but I do have Good Enterprise messaging (MS Exchange integration). It never gave me this problem before in IOS6, but I know it's busy checking for my corporate email in the background pretty much all the time and I'm wondering if there's a priority issue or lack of available cycles for the proximity sensor to react properly all the time in IOS7 with whatever Apple added or changed. I can't easily remove Good without causing my IT department some work, but I was wondering if there's a common thread where others might have this App installed or some other heavy background app sucking up CPU cycles that might be occasionally interfering with the proximity sensor software from reacting quickly and consistently all the time.
Just a thought. Has anyone been engaged by Apple yet on this, does Apple even consider this a bug or do they need more people/time to confirm this?