1. Bigfireq's Avatar
    I have a problem with my 4S where I'm talking on the phone, but the screen remains on, and I can trigger buttons (such as Mute or Hangup) with my cheek. And guess what? I trigger them a lot!

    I had the same problem with my first phone, and exchanged it, and the second one has the exact same problem.

    Also, I don't have a screen protector, so I don't think anything could be interfering with the sensor.

    If it wasn't for this problem, the phone would be great. Does anyone have any suggestions for dealing with this problem? I can't believe I've hit this with two phones, but I can't find anyone else talking about it.
    05-16-2017 03:11 PM
  2. ttsoldier's Avatar
    There are problems with the proximity sensor.

    I have issues where even though the phone is by my ears, it changes to speaker. They really need a firmware update for this phone.
    05-16-2017 07:39 PM
  3. Bigfireq's Avatar
    Nice to know I'm not crazy, but strange people aren't up in arms about this.
    05-17-2017 01:01 AM
  4. xandros9's Avatar
    I would exchange it again if you could (I've seen bad cases involving more than a few replacements of a phone several years ago) but if the issue is truly as widespread as these three phones have suggested, the pool of affected devices is likely quite small.

    Now if it affected all Android-variants including the DTEK60, it might be higher-profile but seeing how it took a lot of reports for the LG bootlooping issue to take flight, I can't see this going much of anywhere other than hoping for a firmware update or low-level warranty repairs.
    05-17-2017 06:50 AM
  5. miraidave's Avatar
    As I have mentioned in the thread about the Creator's Update, I've exchanged my phone through T-Mobile warranty exchange twice, and all three phones have the proximity sensor issue. I do not think it is a hardware failure, but a firmware incompatibility with Windows 10 Mobile.

    I have identified that the proximity sensor will become non-responsive if you receive an incoming call when the sensor is covered, i.e. the phone is in your pocket or faced down on a table. If you receive a call when the sensor is unobstructed, it will work fine. Therefore, I believe this is a firmware/software issue and not a hardware issue.

    I uncertain if what is described above matches your exact issue, therefore I would try calling the phone in both the face up and face down positions to see how your phone responds. If the proximity sensor does not work in both scenarios, or if you are sending an outgoing call, you might actually have a bad sensor. If your phone responds exactly as I described then getting a new phone through warranty probably will not resolve the issue.
    editguy likes this.
    05-17-2017 09:13 AM
  6. Nate W's Avatar
    I can attest to this (sensor issue), and have had this issue while the phone is locked and answering a call. If I hold the phone to my face when answered the backlight never shuts off hence the sensor is not enabled for some reason...Like posted just above, I am not certain if this only if the senor is covered or not activated or what.
    05-17-2017 12:29 PM
  7. Nate W's Avatar
    Can we update the title to this thread, it has a spelling mistake.. @RumoredNow or another mod.

    This way if there are more folks seeing this they can easily find it.
    RumoredNow likes this.
    05-18-2017 07:41 AM
  8. editguy's Avatar
    I'm convinced that it's related to the Creator's update/firmware related. I've tried what miraidave commented on about the phone being pocketed/unpocketed and I got the same results that he did. If it's laying face up on my desk when I answer, no sensor problem whatsoever.
    05-18-2017 09:52 PM
  9. Nate W's Avatar
    If bad or conflicting sw per the CU update then ask @fatclue_98

    He rolled back to the AU update. Maybe he would know if the T-Mobile model gets the same result.

    Also, I have had this issue since the updates on the last build, 14393.xxx before CU on the unlocked open market model.
    05-19-2017 02:37 AM
  10. fatclue_98's Avatar
    Mine was the T-Mobile variant but I never experienced the issue y'all have been discussing. That would've driven me insane if it happened to me. Quick show of hands, how many of you experiencing this have thrown your phones? We're family, speak freely.
    05-19-2017 05:23 PM
  11. editguy's Avatar
    Mine was the T-Mobile variant but I never experienced the issue y'all have been discussing. That would've driven me insane if it happened to me. Quick show of hands, how many of you experiencing this have thrown your phones? We're family, speak freely.
    I'm not throwing a glass-backed phone.
    fatclue_98 likes this.
    05-20-2017 12:56 AM
  12. Nate W's Avatar
    05-20-2017 02:43 AM
  13. fatclue_98's Avatar
    Unfortunately, Google Services has stopped working.
    05-20-2017 11:18 AM
  14. RumoredNow's Avatar
    05-20-2017 03:18 PM
  15. Nate W's Avatar
    Unfortunately, Google Services has stopped working.
    hahaha, that is because you are browsing a Windows forum...
    fatclue_98 likes this.
    05-20-2017 08:58 PM
  16. fatclue_98's Avatar
    hahaha, that is because you are browsing a Windows forum...
    Nah, even the most "flagship" Android drops that message every now and then and will drive you to pull a Nolan Ryan. I'm sure AC is littered with similar comments.
    Nate W and editguy like this.
    05-20-2017 10:01 PM
  17. Nate W's Avatar
    Yes. The life of "first world" problems.
    editguy and fatclue_98 like this.
    05-20-2017 10:19 PM
  18. Nate W's Avatar
    My freaking idol 4s keeps trying to call places and take photos in my pocket due to this issue. Every time I get a message or email it wakes up in my pocket now while locked. Frustrating.
    07-04-2017 11:03 PM

Similar Threads

  1. Why a dual-boot Coship Windows/Android phone is a bad idea
    By WindowsCentral.com in forum Windows Central News Discussion
    Replies: 4
    Last Post: 05-17-2017, 12:45 AM
  2. After CU, bad performance on L950
    By user4545 in forum Windows 10 Mobile
    Replies: 22
    Last Post: 05-15-2017, 01:02 PM
  3. Windows Central = Bad Place for Advice
    By MLXVI in forum General Windows Phone Discussion Lounge
    Replies: 23
    Last Post: 05-11-2017, 03:05 PM
  4. Microsoft Surface revenue fell 26% during third quarter, but that's not so bad
    By WindowsCentral.com in forum Windows Central News Discussion
    Replies: 0
    Last Post: 04-28-2017, 10:10 AM
  5. Do you have a bad boss story?
    By HeyCori in forum Ask Dan!
    Replies: 3
    Last Post: 04-25-2017, 01:45 PM
LINK TO POST COPIED TO CLIPBOARD