[FIX] CM10 Black screen after call - HTC Amaze 4G

Did some research (or a search for that matter) for those like myself that had an issue with black screen immediately after a call is placed or received. Turns out my proximity sensor was not responding properly in CM10. The sensor detects whether your ear is close the screen during a call and turns off the screen to prevent inadvertent operation of the phone.
Fix: My proximity sensor needed "calibration". User FrikinImpossible has a post which fixed my issue. See HERE
There is a flashable zip to make the proximity change permanent.
Thanks FrikinImpossible.

---

vinniej said:
Did some research (or a search for that matter) for those like myself that had an issue with black screen immediately after a call is placed or received. Turns out my proximity sensor was not responding properly in CM10. The sensor detects whether your ear is close the screen during a call and turns off the screen to prevent inadvertent operation of the phone.
Fix: My proximity sensor needed "calibration". User FrikinImpossible has a post which fixed my issue. See HERE
There is a flashable zip to make the proximity change permanent.
Thanks FrikinImpossible.
Click to expand...
Click to collapse
I'll try. Thanks,

---

After some extensive testing, seems this is about 90% and not a complete fix. I've still had issues with the screen blacking out. One thing is for certain, this is not a battery, or phone specific issue.
Guess i'll keep looking for a solution.

---

Black screen on the Stock rom
Same issue on a T-Mobile non-root phone with a stock rom. I haven't tried the zip yet but I can say that the AndroSensor shows "( 0.5mA ) 3.5 in" value against the proximity sensor and won't change even when touching the area around the earpiece.
Another Amaze 4g owner with the same problem has advanced an idea that it might have been a firmware issue: thread link. He witnesses keep running the problem after disabling the sensor. What does happen when the phoning function is called? The screen behavior is subdued to the proximity sensor. When the proximity sensor is disabled the screen must be still checking its value. Let's presume that the value is stuck and doesn't change regardless the sensor measures (or lack of them).
In short: the sensor works fine; the rom responds correctly; but the figure which must be collected by the rom from the sensor when phoning tells it to turn off the screen. So either this figure is stuck or it is corrupted by another factor.
P.S. this is only what I think but I have a very slight idea how it works in reality.

---

Can anyone confirm their state of the proximity sensor in the AndroSensor app. Mine seems to be stuck on "3.5 in" and on "0.0 in" alternately and won't react when putting anything next to the earpiece.
I still doubt whether it is a hardware or a firmware problem. It is least possible that it is caused by rom. Here is a part of log from the AndroSensor.
Code:
D/AndroSensor Debug(11578): Orientation sensor started
D/AndroSensor Debug(11578): Pressure sensor not found
D/AndroSensor Debug(11578): Relative Humidity sensor not found
D/AndroSensor Debug(11578): Proximity sensor found
D/SensorManager(11578): [SensorManager] registerListener: delay = 66667
D/SensorService( 238): enable: get sensor name = CM3602 Proximity sensor
D/Sensors ( 238): sensors_pana_poll_context_t::activate_pana
D/Sensors ( 238): Enabling Proximity Sensor..., mEnabled = 0, new state = 1
D/Sensors ( 238): Reading Proximity Sensor..., count = 16
D/Sensors ( 238): Reading Proximity Sensor..., distance = 38654705664.000000
D/Sensors ( 238): Reading Proximity Sensor...mEnabled = 0
D/EWdaemon( 135): !!! PL_Init
D/Sensors ( 238): Reading Proximity Sensor..., count = 16
D/Sensors ( 238): Reading Proximity Sensor..., distance = 9.000000
D/Sensors ( 238): Reading Proximity Sensor...mEnabled = 0
D/Sensors ( 238): Enabling Proximity Sensor..., mEnabled = 1
D/Sensors ( 238): Setting initial state for Proximity Sensor
D/Sensors ( 238): sensors_pana_poll_context_t::set_Delay = 200000000
D/SensorService( 238): SensorDevice::activate--: handle = 0x7, enabled = 0x1
D/SensorService( 238): pid=11578, uid=10159
D/Sensors ( 238): Reading Proximity Sensor..., count = 16
D/Sensors ( 238): sensors_pana_poll_context_t::set_Delay = 66667000
D/AndroSensor Debug(11578): Proximity sensor started
D/Sensors ( 238): Reading Proximity Sensor..., count = 16
D/Sensors ( 238): Reading Proximity Sensor..., distance = 0.000000
D/Sensors ( 238): Reading Proximity Sensor...mEnabled = 1
D/AndroSensor Debug(11578): Temperature sensor not found
You can notice that the distance value changed from 9.00000 to 0.00000 but it happened by itself.

---

It will sound stupid but I have found a simple solution:
I have just wiped the screen in the upper left corner where the proximity sensor is located and it started behaving normally. Though I don't use any protection tape on the screen it seem to have become less sensitive because of mud or sweat.

---

zandgreen said:
It will sound stupid but I have found a simple solution:
I have just wiped the screen in the upper left corner where the proximity sensor is located and it started behaving normally. Though I don't use any protection tape on the screen it seem to have become less sensitive because of mud or sweat.
Click to expand...
Click to collapse
Yea I thought for the longest time that something around the sensor was causing the issue. I've cleaned the area around the sensor, removed my screen protector, and also removed the main case to verify the sensor was not being "fooled" into one state or another. With Sense based roms, the sensor seems to respond fine for me. With JB roms the sensor has issues. Although I must say that after my latest setup of CM10, I have not had any issues with the sensor (after applying the FrikinImpossible fix). Perhaps the stars aligned when I formatted, checked md5's over and over, and flashed the rom?