More iPhone4 Issues: Proximity Sensor


Recommended Posts

Increasing numbers of iPhone 4 users are reporting the touchscreen becoming active during phone calls when the proximity sensor would normally shut it off, leading to inadvertent button-presses. The reports are coming in with enough frequency and consistency to suspect a hardware or calibration issue with at least a particular subset of iPhones. No word from Apple yet.

The iPhone's proximity sensor uses a small infrared LED and uses the reflection from nearby objects to deactivate the touchscreen when it's close to your head. If you hold it up to an iSight or other camera that can read near infrared light, you can usually just see the glow. The problem may be in how sensitive the detector is set to be on some phones or an actual problem with the detector. So far I haven't noticed it with my own phone, if I make a call and hold a finger in front of the sensor with my finger the screen deactivates out to about an inch away.

An email from a MMi member this morning reported hearing keypress tones during calls, and in one instance his phone tried to initiate a FaceTime call while he had the iPhone to his head. There's an Apple Support thread with forty-one posts as of the time of this writing, most with similar reports. One user saysthe display activates when he rocks it from side to side.

Anyone out there seeing this?

Source

Lots of reports of this now. Anyone here having this problem?

Link to comment
https://www.neowin.net/forum/topic/914742-more-iphone4-issues-proximity-sensor/
Share on other sites

I just had this happen when it was up to my face. I looked at the discussion on Apple's Discussion Boards. The contributors there have come to the conclusion that it's a software calibration issue that arises when you restore a backup from an earlier iPhone (2G, 3G, or 3GS) since the iPhone 4 has a different style of proximity sensor.

If you have the problem, try going to Settings > General > Reset > Reset All Settings (this doesn't delete any media). It fixed the problem for me.

You know we are hearing a lot more problems with the 4 than I can recall with any other version of the iPhone. Am I correct in saying that?

That is most likely because they redesigned the whole phone, while the previous 3 models had a similar design with very minor modifications.

The contributors there have come to the conclusion that it's a software calibration issue that arises when you restore a backup from an earlier iPhone (2G, 3G, or 3GS) since the iPhone 4 has a different style of proximity sensor.

Unfortunately I am experiencing this problem very frequently - it's rather annoying. I did not restore my phone from a previous back-up, so there is more to this issue than that I'm afraid.

You know, I wouldn't be surprised if this was the official response.

HAHA Same.. I was just thinking we will see an email screenshot in the next day or 2 from Steve Jobs saying, stop holding your phone completely. We are now selling a Bluetooth headset so you never touch your phone ever!!

I'm just glad I decided to get a new guitar amp with my money and wait a bit for the iPhone 4. I'd be so ****ed if I spent that much money (I'd buy it without a contract) and it had all these issues. Hopefully by the time I'm ready to buy, all the issues will be worked out.

Unfortunately I am experiencing this problem very frequently - it's rather annoying. I did not restore my phone from a previous back-up, so there is more to this issue than that I'm afraid.

That's odd. I did it and it completely fixed the problem for me. I haven't had it since I reset my settings.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The problem isn't with Epic, it's with the platform holders like Steam and Nintendo, they should be a lot more strict in their review process.
    • Hello, Installed here without issue. Regards, Aryeh Goretsky
    • Microsoft updates Visual Studio Code with easier language model discovery and in-app search by Paul Hill Microsoft has released Visual Studio Code 1.125, its latest weekly release. This week, the company has focused on discovering and installing extra language models via the Marketplace; searching the web and securely browsing over remote connections without leaving VS Code; choosing how long VS Code waits before installing extension updates; and delivering managed Copilot settings through existing device management tooling. In older versions of VS Code, extensions could contribute their own model providers, but to find these extensions, you needed the right tags to search for in the Extension view. Now, the Language Models editor gives you an Install Model Providers button that opens the Extensions view, which is filtered to extensions that contribute model providers, making it easier to find and install them. Once you install a provider, its model will appear in the model picker. If you use the integrated browser much, you can now look up information without leaving VS Code by typing a query into the integrated browser’s address bar. It will use your configured search engine, the same way a standalone browser does. You can use workbench.browser.searchEngine to pick a search engine. When the browser is opened in a remote workspace, it's now possible to proxy HTTP(S) traffic via the remote connection. This allows you to connect to any ports or services that can only be accessed from the remote machine. If you read our coverage from two weeks ago about VS Code 1.123, you might have seen that extension updates have a two-hour delay as a safety measure. In this update, Microsoft is giving you the ability to configure the time of the delay. You can find it under extensions.autoUpdateDelay. Finally, with this update, admins can deliver managed GitHub Copilot settings through native device management (MDM) channels on Windows and macOS, in addition to account-based enterprise settings files. Settings delivered via MDM appear as policy-enforced in VS Code and can’t be overridden locally. Future updates will extend the supported policy keys across Copilot surfaces. You can download the update from the Visual Studio Code website now.
    • "it opens up new doors for people who prefer using Edge, but cannot be bothered to configure a Microsoft account" You already have a Microsoft account if you are using Windows 11, because you can't set it up without one.
  • Recent Achievements

    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
    • Week One Done
      With What earned a badge
      Week One Done
    • Week One Done
      Harris Gilbert earned a badge
      Week One Done
    • One Month Later
      Vincian earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      543
    2. 2
      +Edouard
      171
    3. 3
      PsYcHoKiLLa
      84
    4. 4
      ATLien_0
      64
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!