Hello guys!
I've just got my repaired HTC Desire 500 from the service center after having yellow line along the screen and usb sync. failure. They said they replaced the entire motherboard and the screen.
Everything worked just fine until I experienced some weird proximity sensor issues. As an HTC user, I use the Gravity Screen app in order to wake the screen through the proximity and gravity sensor to save the power button from prolonged use.
I realized the proximity sensor is not working with the app. And the sensor works 8 out of 10 times when having a phone call, the other 2 times the screen doesn't wake when moving the phone away from my ear.
I tried testing the sensor via the built-in function test, it "most of the time" fails the test. On the other hand, it works okay with phone calls!
The sensor sometimes work, sometimes hang and sometimes never works!
I tried factory reset and wiping cache partition and sensor works okay at the beginning then starts acting weird.
Please help me with your useful feedback because it's truly frustrating!
Hi,
does anybody know an app or a tweak (build.prop or xposed framework) which doesn't wake up the display during a call? (mobile is rooted)
My mother in law has a Cynus T2.
Everytime she makes a call, she doesn't hold it properly and the display turns on, and with her ear and cheeks she triggers accidentely several buttons.
So sometimes bluetooh or wireless is on, or the call ends abruptly.
She holds the phone with her left hand and the proximity sensor is on the right, so there is enough space, it does not shade correctly and the proximity sensor turns the display on.
I searched for proximity sensor fixes, but they all do the opposite. They fix the proximity sensor to turn the display on for e.g. to open the phonebook or the dialer.
I would be very happy for every suggestion.
Hi,
does anybody know an app or a tweak (build.prop or xposed framework) which doesn't wake up the display during a call? (mobile is rooted)
My mother in law has a Cynus T2.
Everytime she makes a call, she doesn't hold it properly and the display turns on, and with her ear and cheeks she triggers accidentely several buttons.
So sometimes bluetooh or wireless is on, or the call ends abruptly.
She holds the phone with her left hand and the proximity sensor is on the right, so there is enough space, it does not shade correctly and the proximity sensor turns the display on.
I searched for proximity sensor fixes, but they all do the opposite. They fix the proximity sensor to turn the display on for e.g. to open the phonebook or the dialer.
I would be very happy for every suggestion.
Hi,
I've got some problems with my XZ, during a call i've got the proximity sensor that doesn't work correctly i need to put my hand on the phone near it to force it to activate, it doesn't work at all if i put the phone on my ears, the screen just goes black that's really annoying.
I've tested the sensor in the diagnostic mode and it is always on and it's hard to disable it, same in the test mode with *#*#7378423#*#* the proximity sensor is amlway on and doesn't detect my ear, i don't know what to do...
Second problem each time i activate the plane mode or the localization that automatically activate the bluetooth and if i disable it's the bluetooth stay enabled i need to shut it down manually.
If you have any solution that would be helpfull, thanks in advance.
Solution on 2nd post.
Hi.
Lately I'm having problems with proximity sensor.
1. During phone calls, after getting phone to my ear, screen turns off and that's fine, but after ending the call screen never wakes up. I have to press the Power button to wake up the screen.
2. After pressing the power button, screen turns off and AOD screen shows up, that's ok, but after putting it to pocket or after covering the proximity sensor with hand and taking it off the AOD screen doesn't show up. It's black screen always. I have to wake up the phone and off for AOD screen to show up.
I was testing the proximity sensor with different testing apps and it is recognizing near proximity but it never recognize that there is nothing near anymore. Ex.: during testing I cover the proximity with hand and it is recognizing it, but when I take my hand off, proximity sensor is still saying there is something near.
Problems started some time ago occasionally but since yesterday it always like that. It started on Android 10. Downgraded to 9 (ver 1.9 from zte de site) and it was ok for 2 weeks like. Yet it started to get stuck for good, even upgrading back to Android 10 (v 2.4) didn't help.
I looked where the sensor is, left side from earpiece and I swear I could see some dust under the glass, but since the phone is waterproof (IP68) how there could be any dust inside? I was shaking the phone to get rid of the dust from the proximity sensor to no avail, sensor is still stuck.
No glass protector applied, no any cover.
What do you guys think? Should I get RMA for it? Or s there anything can be done? Anyone else having these problems?
FIX for proximity sensor getting stuck/not working properly
Found fix by myself.
Proximity sensor in my case got some dust in it or it de-calibrated itself. If proximity sensor is broken on hardware level, probably this solution won't work. Yet, you are free to try it anyway.
If your proximity sensor de-calibrated somehow or got dust on it and it is misbehaving, do the following:
1. Go to Phone app, enter:
Code:
*983*673636#
to enable EMODE (self-testing app), toast info about enabling EMODE will be shown,
2. In the Phone app enter:
Code:
*983*0#
to start the EMODE, menu for various test will be shown,
3. Go to SENSOR TEST
4. Cover the proximity sensor with your hand ? (upper side of the phone ), test will say something like PASS in green color),
5. Swipe to the bottom of the menu, place your phone flat on the table in not so bright environment and hit CALIBRATE.
6. Your sensors are now re-calibrated and proximity sensor will work like new, even if it is dusted.
7. If you want to disable EMODE, go back to Phone app and enter
Code:
*983*2567336#
but refrain from doing so, if you want to run EMODE again in case of any of sensors misbehaving again and wanting to recalibrate later.
That's it, my proximity sensor is working again like new.
Sidenote: if there is dust inside the phone, phone is not so waterproof (IP68) after all. Just be careful with water with it
mancom said:
FIX for proximity sensor getting stuck/not working properly
Found fix by myself.
Proximity sensor in my case got some dust in it or it de-calibrated itself. If proximity sensor is broken on hardware level, probably this solution won't work. Yet, you are free to try it anyway.
If your proximity sensor de-calibrated somehow or got dust on it and it is misbehaving, do the following:
1. Go to Phone app, enter:
Code:
*983*673636#
to enable EMODE (self-testing app), toast info about enabling EMODE will be shown,
2. In the Phone app enter:
Code:
*983*0#
to start the EMODE, menu for various test will be shown,
3. Go to SENSOR TEST
4. Cover the proximity sensor with your hand ? (upper side of the phone ), test will say something like PASS in green color),
5. Swipe to the bottom of the menu, place your phone flat on the table in not so bright environment and hit CALIBRATE.
6. Your sensors are now re-calibrated and proximity sensor will work like new, even if it is dusted.
7. If you want to disable EMODE, go back to Phone app and enter
Code:
*983*2567336#
but refrain from doing so, if you want to run EMODE again in case of any of sensors misbehaving again and wanting to recalibrate later.
That's it, my proximity sensor is working again like new.
Sidenote: if there is dust inside the phone, phone is not so waterproof (IP68) after all. Just be careful with water with it
Click to expand...
Click to collapse
Hey! I have the same problem with the proximity sensor and even though I did the same that you say, nothing changed.
Do you any other solution?
CharlyNews said:
Hey! I have the same problem with the proximity sensor and even though I did the same that you say, nothing changed.
Do you any other solution?
Click to expand...
Click to collapse
Sorry to hear that. I have no other solution. Take it to service center.