[Sprint HTC EVO 4G LTE] LiquidSolstice:
So this thread is for those of us who simply cannot get our proximity sensors to function properly in-call. I will attempt to explain what's going on, my ideas on possible explanations, and why this is actually a critical issue.

What's supposed to happen?

When you place a phone call, and audio goes through your earpiece, when you bring the phone up to your ear, the phone will utilize the proximity and light sensors to shut the screen off, so that you don't accidentally press any buttons with your cheek or face. It's incredibly useful.

What's actually happening in CMX?

In the CM10 previews that are being released in the IRC, for a smaller subset of users, when you make an outgoing call, moments after the call is connected, the screen will go black, regardless of whether or not you've put the phone up to your face. No button on the phone does anything. The call still goes through, and you can hear the other end and the other end can hear you. But you simply cannot get the screen to turn back on.

How do we get the screen turned on again?

There's several ways to get the screen back on, none of them are convenient.

You have to wait for the other person to end the call. This is extremely problematic if the other end does not pick up and you are forced to leave a voicemail message.

You have to take a very bright light source and put the phone directly up to the light source. The scren will turn on. You have to be very, very quick about this because if the phone moves just a tiny bit away from the light source, the screen shuts off and you're back to square one again.

You can take any IR-based TV remote and aim it directly at the speaker grille on the front of your phone and press a button.

You can press and hold the power button for 15 seconds until the capacitive buttons start blinking, and when they stop blinking, the phone reboots.

NEW! You can plug in any headphones into the 3.5mm jack, and the screen will turn on and stay on. Thanks yohaq from the IRC.

NEW! It is possible to bypass the issue altogether by using a bluetooth headset. Thanks to people in IRC for figuring this out.

As you can see, none of those are really realistic.

Why is this happening?

Let me get this out of the way right now; it's not a case of faulty proximity sensors/hardware. The call behavior functions exactly the way it should be in Sense ROMs and stock ROMs. I have a few ideas as to why it's going on.

The proximity sensor is simply just not being used at all, and only the light sensor is being used.

There might be slight variations in proximity sensor drivers among different phones, and for that reason, the "incorrect" driver might be causing the varied proximity sensors to malfunction.

The proximity sensor may not be sensitive enough.

arrogantbastard has a very thorough breakdown with his conclusions as to why. Check it out here: Post

What could be possible short-term fixes?

Now, I don't quite know how many of these (if any) are even possible, but here's a few ideas I have. Because my "if you don't have this issue please don't bother with this thread" forewarning is apparently rocket science to a few people, when I suggest that we try and remove files, I'm obviously referring to just us removing said files, not deck removing the functionality for everyone. Normally, I'd assume this was obvious, given the title of this part is "short-term fixes", but...

Completely disable the proximity and light sensors through the deletion of files (I highly doubt this would work)

Implement a Jewel-specific

option

(please note how it says "option" and not "setting that is forced upon everyone") to force the screen to stay on during calls (this seems like the most likely)

Implement a Jewel-specific control to tweak the sensitivity of the light/proximity sensors.

What steps do we need to take from here?

Honestly, we need AOSP developer exposure. So many people are shrugging it off as "bad hardware" when we know that's not the case. The following from you would be helpful:

Your experiences

If you've had issues before and now they are fixed, tell us how many days of testing you've done and how long your calls have been.

Your workarounds

Your ADB logcats (please attach them here)

Other Resources:

Proximity Issue in CM7 - Bugtracker

HTC EVO 4G LTE - Test Your Proximity Sensor

Arrogantbastard's extremely thorough dissection of the ROM/kernel in comparison with others:

As of now, anything you guys can do would be tremendously helpful. In my eyes there is nothing else stopping the CMX builds from being daily builds.