Database Info

[Q] Sensation 4g proximity sensor problem

Hey guys. Im having a problem with the proximity sensor on my sensation 4g. It was working fine when i bought it. It shut the screen off while calling, but now it does not. I thought that maybe rooting it would fix the problem by getting a custom rom, but i would like some input before i go rom exploring on this phone. I assume its a software issue because i havnt dropped the phone or anything along that line. Any Help would be highly appreciated. I also am looking for the dialer codes that would lead you into a test mode to test the functions on the device. If anyone knows of a code, I would appreciate to learn what it is. thank you for your help.

Make sure Proximity sensor is enabled in Settings > Call Settings > Additional Settings.

thank for your reply. I checked the settings and the only thing that shows up is Caller Id settings and Call waiting. Oh and i downloaded a market app that would show me all the sensors that work on my phone, and the light and proximity sensors both come up with an unknown error. Could it be something from the gingerbread update?

Did anyone figure this out? I have the same problem and its getting pretty annoying.

Me too...:-(

Hello,
I am having the same problem. Earlier, I thought that it was a ROM issue, however, after changing multiple ROMs, it seems to be firmware issue.
On my sensation, I found out that it is related to the back light for the soft keys (home, menu, back and search).
I can get it to work if I turn on pocket mode in Settings > Sound and then restart (once or twice). It will work until next restart.
I have installed AndroSensor from market and it shows one of the 3 messages
Proximity Sensor: Waiting for Event
Proximity Sensor: Unknown Error.
Proximity Sensor: 3.5in
Also, I am getting exceptional battery life which makes me wonder whether phone uses both the cores or if anything else is wrong with the phone.
I am using Energy ROM (3rd Oct).
Any feedback?
Thanks,
Baiju

baijunagori said:
Hello,
I am having the same problem. Earlier, I thought that it was a ROM issue, however, after changing multiple ROMs, it seems to be firmware issue.
On my sensation, I found out that it is related to the back light for the soft keys (home, menu, back and search).
I can get it to work if I turn on pocket mode in Settings > Sound and then restart (once or twice). It will work until next restart.
I have installed AndroSensor from market and it shows one of the 3 messages
Proximity Sensor: Waiting for Event
Proximity Sensor: Unknown Error.
Proximity Sensor: 3.5in
Also, I am getting exceptional battery life which makes me wonder whether phone uses both the cores or if anything else is wrong with the phone.
I am using Energy ROM (3rd Oct).
Any feedback?
Thanks,
Baiju
Click to expand...
Click to collapse
This is interesting b/c I just noticed I have the same problem, too. I do not check the pocket mode because I want to save some battery life. I did get the proximity sensor working during calls "sometimes". And it's really hard to define this "sometimes" b/c I cannot identify the pattern or reproduce the scenario.
My solution to this issue is that If it's not working, I recharge the battery until full, do a reboot, maybe reboot twice, and it is "sometimes" "fixed" by itself. In my case, after doing that, the proximity will work for a while (again, it's hard to determine how long), and just stopping working all the sudden.
I hope there is a easier fix, maybe a app, that would reset the proximity so we can apply it when the sensor does not work.

Hi I just realized the cause, it's because the battery % mod from UOT kitchen. I removed it and everything is fine now. Apparently the UOT kitchen's setting has problem.

I have 2 sensation 4g. One doesn't have any problem with Energy ROM. For the other phone, I went back to Factory settings and reinstalled original TMobile ROM. I still have problem with that one. I have contacted t-mobile and asked for a replacement. It is something with the hardware I suppose.
Baiju

hello
I got the exact same problem and i do many rom/kernel change to figure out this problem but i just can't .
Yungyeh could you explain more how do you solve it ? thks

toowave said:
hello
I got the exact same problem and i do many rom/kernel change to figure out this problem but i just can't .
Yungyeh could you explain more how do you solve it ? thks
Click to expand...
Click to collapse
I guess nothing fancy.
As I've known so far, there are several causes, which can be divided into two categories: Hardware and software .
If your device came with this issue, with a stock rom installed, maybe applied some updates, then you shouldn't wait to call the (HTC/T-mobile?) customer service. Have a exchange or replacement is the only way to correct the hardware issue.
If it's a software issue, i.e. it worked before with a stock rom, but now it fails sometimes after flashing a custom rom, you may go with the following solutions.
Situation One: If the custom rom is fresh installed, charge your device until battery full, stay in charge mode for another 1 - 2 hours, complete power off and on at least twice (three times maybe, make sure the "fastboot" in the power settings is off). Do not install any mod until your rom settles for a few hours. Sometimes the sensor does not work will simply because the cache goes wrong. If after waiting for a few hours and the problem still persists, you may want to check your custom rom's instruction and make sure you've followed every steps.
Situation Two: If the proximity sensor does not work all the sudden, especially after doing a reboot, you should first clear your data for phone app (or any other apps that use the proximity sensor), and then boot into recovery to clear all your cache. After wiping your cache, you have to do what situation 1 instructed because your device is just like a fresh installed one.
Situation Three: If your proximity sensor fails to work after applying a mod, especially some mods cooked from the UOT kitchen, revert back to your previous backup. DO NOT APPLY THAT MOD ANYMORE!!! Try some other mods that work for you and that is friendly to your proximity sensor. This situation also applies to if your flash an inappropriate kernel. Revert back to your previous backup is the only solution.
If none of the situations described above works for you, then I am out of clue. Changing to other custom rom or kernel usually does not work. You may try that but I doubt it will resolve this issue. It may be just your bad luck that the proximity sensor of your device goes to its end. I sincerely hope it not the case.

my sensors are not working!!
accelerometer
gyroscope
light
magnetic field
orientation
proximity
All not working...
Was using HyperSensation-CM7.1-v0.8, then decided to update the kernel, faux newer one, then lost the ability to rotate the phone..
So, did a manual wipe, then super wipe, restored my backup, and still no sensors,
wiped again and tried a diffrent rom nothing changed,
wiped again tried arhd 3.6.7 with stock kernel and faux kernel,
tried cm7 with the kernel it comes with or the newer one and still nothing...
at what level does the software talk to these sensors, is there a 100%way to wipe the phone and start over? i have never had any issue like this before!
Would reverting back to the original rom via fastboot help at all versus what i have done?
if someone has any ideas pm me, its a little bit easier then catching a response here since this is the most popular rom in the world lol, but ill still be reading

I'm having the same probpem. I don't really mess around with Roms or anything and I have 2 sensation 4g that do the same thing. And I believe is an htc problem.

having the same iseu with proximity and light sensor.
Do you have an solution yet ?

yungyeh said:
Hi I just realized the cause, it's because the battery % mod from UOT kitchen. I removed it and everything is fine now. Apparently the UOT kitchen's setting has problem.
Click to expand...
Click to collapse
I`m having the same problem with both proximity and light sensors.They work occasionally but not for to long.Have you found a solution for this?

It's April of 2012 and I have found NO answers or fixes!!!!!!!!!!

Same sensor problem on my sensation.
If I reboot the phone in a dark room, booth sensors are working (I don't know if it's correct when the proximity sensor shows only 3,5 or 0 inches, but it works)
When I go to a lighted room, the proximity sensor stops to work and the light sensor needs more time to measure the illumination.
If I reboot the phone into lighted room, the sensors didn't work.
It is possible to simulate a "dark room" by covering the sensors with a finger ;-)
It is not easy to decide if the error is located into software or the sensors are "overloaded". For finding out a solution I have ordered new flex main board which should contain booth sensors. Hope it helps ^^

schand99 said:
Same sensor problem on my sensation.
If I reboot the phone in a dark room, booth sensors are working (I don't know if it's correct when the proximity sensor shows only 3,5 or 0 inches, but it works)
When I go to a lighted room, the proximity sensor stops to work and the light sensor needs more time to measure the illumination.
If I reboot the phone into lighted room, the sensors didn't work.
It is possible to simulate a "dark room" by covering the sensors with a finger ;-)
It is not easy to decide if the error is located into software or the sensors are "overloaded". For finding out a solution I have ordered new flex main board which should contain booth sensors. Hope it helps ^^
Click to expand...
Click to collapse
@schand99: The Flex/Main Board actually isn't the problem. It is an HTC software/hardware related problem. I have 2 Sensation's here now, one is rooted and unlocked entirely and the Proximity and Ambient Light Sensors and the Capacative Backlights on the touchpad DO NOT WORK. FYI, the touchpad lights work in cooperation of the Ambient Light Sensors: If there is any light under 90.0 Luxes (this is how the sensor measures light) the backlights will come on. If there is anything over 90.0 Luxes, the backlights will stay off. This is based on the fact that you need light in a totally dark environment, or you do not need light as you can see the touchpad and it is not that dark.
It is DEFINITELY not a hardware issue as there are some temporary fixes that will bring them back to life, but usually after a reboot, they are both dead again.
I am curious if your new flex/main cable would do the trick or not. I have tested the sensors chipsets independently and they work fine, there is just something that block their functionality on a software end.

mariosaraylian said:
It is DEFINITELY not a hardware issue as there are some temporary fixes that will bring them back to life, but usually after a reboot, they are both dead again.
I am curious if your new flex/main cable would do the trick or not. I have tested the sensors chipsets independently and they work fine, there is just something that block their functionality on a software end.
Click to expand...
Click to collapse
My report about main flex board changing:
After changing the board booth sensors are working fine. I have tested the functionality of the sensors also on different ROM's like stock rom, OrDroid and CoinDroid. No problem until now. It makes not a difference anymore if I power on the phone into dark room or on a sunny place.
BUT!
I don't recommend to do this by yourself. It is verry difficult to do this work !!
It is my profession to do this kind of work.
AND
to change the board was the right method for fixing the sensor-problem on my HTC Sensation. I had to unlock the hboot 1.27.xx by using the "beer drinking" method. So perhaps I have damaged the sensors by doing this...

schand99 said:
My report about main flex board changing:
After changing the board booth sensors are working fine. I have tested the functionality of the sensors also on different ROM's like stock rom, OrDroid and CoinDroid. No problem until now. It makes not a difference anymore if I power on the phone into dark room or on a sunny place.
BUT!
I don't recommend to do this by yourself. It is verry difficult to do this work !!
It is my profession to do this kind of work.
AND
to change the board was the right method for fixing the sensor-problem on my HTC Sensation. I had to unlock the hboot 1.27.xx by using the "beer drinking" method. So perhaps I have damaged the sensors by doing this...
Click to expand...
Click to collapse
@schand99: That's very strange that it could be the SAME hardware problem for all of these people that are complaining about this issue. I wonder if is some sort of production issue they have. The strange part is that it is not just for the lot of hardware issued for the USA only, it is also in other parts of the world also.
I did a hardware exchange with mine at the TMOUS store and the "new" one I have now is working fine thank God.
I told them that the TMOUS ICS RUU OTA upgrade broke the sensors LOL!
Thanks for your feedback!

Screen Goes off while call

Hi.
I have this wierd bug. When i call someone. Screen automatically goes off and wont come on until call is finished.
I know this isnt due to proximity. Even when the sensor is not covered up.
I am on stock mm rooted.
..
Does this mean my sensor isn't working or software issue?

gamingdarstark said:
Hi.
I have this wierd bug. When i call someone. Screen automatically goes off and wont come on until call is finished.
I know this isnt due to proximity. Even when the sensor is not covered up.
I am on stock mm rooted.
..
Does this mean my sensor isn't working or software issue?
Click to expand...
Click to collapse
Most likely your sensor is bad and always reporting NEAR, the symptoms you are describing are exactly what would happen in this condition... have you tried a sensor test app from the Play Store to see what the proximity sensor is doing?

Finally worked!!!! had to calibrate sensor
Well thanks i tested the sensor it was always showing 1cm reading.
Calibrated it using an app on playstore. >> Proximity Sensor Calibration <<
Now working fine.
Cheers!! :good::good:

Screen turns off immediately after dialing/answering a call

I have a common problem in all ROMs I'm installing . whenever I answer a call or dial a call my screen goes off as if proximity sensor is activated and doesn't turn on even when I take it away from my ear or press my power button. Screen doesn't turn on at all during call.
Phone remains fine for a day or two after I wipe cache etc from recovery but again the problem starts. This happens in all custom roms and also in rooted stock ROM. My device is XT 1055.
Kindly suggest any solution as it causes lot of inconvenience.

abhishekturumella said:
I have a common problem in all ROMs I'm installing . whenever I answer a call or dial a call my screen goes off as if proximity sensor is activated and doesn't turn on even when I take it away from my ear or press my power button. Screen doesn't turn on at all during call.
Phone remains fine for a day or two after I wipe cache etc from recovery but again the problem starts. This happens in all custom roms and also in rooted stock ROM. My device is XT 1055.
Kindly suggest any solution as it causes lot of inconvenience.
Click to expand...
Click to collapse
Your device is a Moto X (1st generation/2013 )? A quick Google search would tell you this is a Proximity Sensor issue, it is device specific whether anything can be done or not, so you might want to check your device's group.

acejavelin said:
Your device is a Moto X (1st generation/2013 )? A quick Google search would tell you this is a Proximity Sensor issue, it is device specific whether anything can be done or not, so you might want to check your device's group.
Click to expand...
Click to collapse
No bro. Mine is a moto g3 xt1550. Searched the forum later yday and found that it is calibrating proximity sensor issue. Will try doing that and check. Thank you for the response

abhishekturumella said:
No bro. Mine is a moto g3 xt1550. Searched the forum later yday and found that it is calibrating proximity sensor issue. Will try doing that and check. Thank you for the response
Click to expand...
Click to collapse
Sorry, you must have typo'd earlier, you clearly said XT1055 which is a valid Moto device. Anyway, sounds like you're on the right track.

acejavelin said:
Sorry, you must have typo'd earlier, you clearly said XT1055 which is a valid Moto device. Anyway, sounds like you're on the right track.
Click to expand...
Click to collapse
Oops. Sorry. It was a typo. Mine is motog3 xt 1550.

abhishekturumella said:
Oops. Sorry. It was a typo. Mine is motog3 xt 1550.
Click to expand...
Click to collapse
please let me know if you can some how fix this issue. I have same issue ands I did proximity caliberatiin as well and it did not resolve my issue

chungomungo1 said:
please let me know if you can some how fix this issue. I have same issue ands I did proximity caliberatiin as well and it did not resolve my issue
Click to expand...
Click to collapse
I too did proximity sensor calibration but it worked only for few times. But the only solution that's working is whenever screen goes blank I rub with my finger on proximity sensor area for 3-4 times as if like cleaning it. Immediately the screen lights up. This is the solution am doing since past few times and its working consistently.

abhishekturumella said:
I too did proximity sensor calibration but it worked only for few times. But the only solution that's working is whenever screen goes blank I rub with my finger on proximity sensor area for 3-4 times as if like cleaning it. Immediately the screen lights up. This is the solution am doing since past few times and its working consistently.
Click to expand...
Click to collapse
Thanks

Can we disable the proximity sensor ???

Mohammed Siamwala said:
Can we disable the proximity sensor ???
Click to expand...
Click to collapse
Yes u can disable the proximity sensor.....
Procedure:
1. The device need to be rooted
2. Install the xposed module
3. After installing search for sensor Disabler apk in xposed module
4. Install sensor Disabler and open the app and select the proximity sensor.
5. Select the value of proximity sensor to Maximum level and save it
6. Do the reboot
This whole procedure will disable ur proximity sensor ie ur screen will no go blank on any call.
Note : Xposed installer for nougat ROM is in development phase ...
Do it ur own risk I'm not responsible for any harm.
All the best :good::laugh:

abhi8939 said:
Yes u can disable the proximity sensor.....
Procedure:
1. The device need to be rooted
2. Install the xposed module
3. After installing search for sensor Disabler apk in xposed module
4. Install sensor Disabler and open the app and select the proximity sensor.
5. Select the value of proximity sensor to Maximum level and save it
6. Do the reboot
This whole procedure will disable ur proximity sensor ie ur screen will no go blank on any call.
Note : Xposed installer for nougat ROM is in development phase ...
Do it ur own risk I'm not responsible for any harm.
All the best :good::laugh:
Click to expand...
Click to collapse
Thanks for your help !!
But will need to wait as I'm using Nougat ROM :laugh:
Any disabling method for 7.1.1 ???

Mohammed Siamwala said:
Thanks for your help !!
But will need to wait as I'm using Nougat ROM :laugh:
Any disabling method for 7.1.1 ???
Click to expand...
Click to collapse
To my knowledge it is not there... U can Google it bro
As I'm also facing this problem...
Some info about xposed....
Xposed is not compatible with Nougat, the truth is it may never be a viable option again due to security changes in Android. The developers have said that Xposed is on it's last legs, the changes in Android and the security are becoming impossible to work around. Remember last year at this time, the developers of Xposed had mostly given up and thrown in the towel and said Xposed was dead with Marshmallow, but they got lucky and found a work around just before completely giving up. They have not as yet found such a exploit to make it work, and if they do it will only be temporary as the next version of Android will probably close it again. They may get it to work with Nougat, or maybe not, either way best bet is to learn to live without it, because it will be gone before too long.

abhishekturumella said:
I have a common problem in all ROMs I'm installing . whenever I answer a call or dial a call my screen goes off as if proximity sensor is activated and doesn't turn on even when I take it away from my ear or press my power button. Screen doesn't turn on at all during call.
Phone remains fine for a day or two after I wipe cache etc from recovery but again the problem starts. This happens in all custom roms and also in rooted stock ROM. My device is XT 1055.
Kindly suggest any solution as it causes lot of inconvenience.
Click to expand...
Click to collapse
hi buddy i have a solution for this hope this will be helpful............
i have flashed the cm 12.1 yesterday on my moto g3 and since yesterday i didn't faced the problem of screen going off on call .....
this conclude that rom is somewhere responsible for screen off during call on some phones( my opinion )
you can try this if u want:fingers-crossed:

This will help you mate
github.com/Alberto97/proprietary_vendor_motorola/blob/cm-14.1/osprey/proprietary/lib/hw/sensors.msm8916.so?raw=true
Paste this in system>lib>hw>
And change the permission to rw- r-- r--

9.5.7 - screen off in pocket and calibration not working

Hi
Basically the title says it all.
On 9.5.7 (I believe on 9.5.6 too) screen turns on a accidentally while being carried in pocket and keeps being activated.
When I had 9.5.6 I calibrated promixity sensor following a thread here in xda but I am unable to bring the sensor calibrarion app now.
*808*# doesn't work anymore for calibrarion of promixity sensor - is it the same for you?
Thanks

nickname_marco said:
Hi
Basically the title says it all.
On 9.5.7 (I believe on 9.5.6 too) screen turns on a accidentally while being carried in pocket and keeps being activated.
When I had 9.5.6 I calibrated promixity sensor following a thread here in xda but I am unable to bring the sensor calibrarion app now.
*808*# doesn't work anymore for calibrarion of promixity sensor - is it the same for you?
Thanks
Click to expand...
Click to collapse
I know maybe was an error but you do know that the correct code is "#*808*#" not "*808*#" as you write it.

alek889 said:
I know maybe was an error but you do know that the correct code is "#*808*#" not "*808*#" as you write it.
Click to expand...
Click to collapse
Thanks for your reply but no, the engineering mode is accessed by dialling *808*# - the other one doesn't do anything.

Actually the code working for me is *#808# but my phone also turns on in the pocket. Would be happy to get a pocket mode like with the Op5

nickname_marco said:
Hi
Basically the title says it all.
On 9.5.7 (I believe on 9.5.6 too) screen turns on a accidentally while being carried in pocket and keeps being activated.
When I had 9.5.6 I calibrated promixity sensor following a thread here in xda but I am unable to bring the sensor calibrarion app now.
*808*# doesn't work anymore for calibrarion of promixity sensor - is it the same for you?
Thanks
Click to expand...
Click to collapse
Can you please send me the link to the calibration instructions. I can't make it work either...

nickname_marco said:
Hi
Basically the title says it all.
On 9.5.7 (I believe on 9.5.6 too) screen turns on a accidentally while being carried in pocket and keeps being activated.
When I had 9.5.6 I calibrated promixity sensor following a thread here in xda but I am unable to bring the sensor calibrarion app now.
*808*# doesn't work anymore for calibrarion of promixity sensor - is it the same for you?
Thanks
Click to expand...
Click to collapse
Sorry to barge in here, and steal a bit of this thread, but..
I'm very picky about phone-on-pocket activation + unlocking.
I've had to return phones because of this, and I can't buy a OnePlus locally.. so, I'm a bit more concerned about returns/etc.
Is there a mode on the oneplus 7 pro, where:
- it NEVER EVER wakes up, unless you push the power button
OR
- if it is woke by an event, it can NEVER be unlocked by any means without a pass/numeric code/swipe code first?
EG, one phone I had.. I couldn't remove the camera app from the lockscreen. So, it'd stay locked, but I'd pocket click the camera app, and it'd stay on forever as I walked. I noticed this once as I took a picture of my pocket and the flash came on.
So does the lockscreen have a mode where no app can ever open, nothing can ever happen, unless the phone is actually unlocked? EG, no swipe up/down, icons, anything?
I'm guessing you guys like the proximity sensor because it prevents some of the above?
If so, any luck? How isn't it calibrating?

nickname_marco said:
Hi
Basically the title says it all.
On 9.5.7 (I believe on 9.5.6 too) screen turns on a accidentally while being carried in pocket and keeps being activated.
When I had 9.5.6 I calibrated promixity sensor following a thread here in xda but I am unable to bring the sensor calibrarion app now.
*808*# doesn't work anymore for calibrarion of promixity sensor - is it the same for you?
Thanks
Click to expand...
Click to collapse
If you aren't too attached to the option where one displays the ambient displays by picking up the phone, you can disable that option and I'll prevent this from happening. Personally, I use tap to display only

LoopDoGG79 said:
If you aren't too attached to the option where one displays the ambient displays by picking up the phone, you can disable that option and I'll prevent this from happening. Personally, I use tap to display only
Click to expand...
Click to collapse
OK, that helps re: my concerns above -- although I'd surely like to know about the rest of the lock screen.
With the proximity sensor 'acting up', pocket hitting of power button, volume keys, etc happens. And when it does, if the lockscreen has 'stuff' on it, stuff could still get activated.

psiLion said:
Actually the code working for me is *#808# but my phone also turns on in the pocket. Would be happy to get a pocket mode like with the Op5
Click to expand...
Click to collapse
Yes, my bad, I lost a symbols while typing

Proximity sensor and others not working properly after android 10 update

My Pixel 3's proximity sensor reads 0cm after android 10 update(using Sensors Multitool), and double tap to wake and lift to wake not working.
I've search on the internet and I read the post of "FIXED - Android 10 - Sensors Bug". and also tried using proximity sensor reset or calibrate app, but all seem not working.
In my case, all other sensors works perfectly(Active Edge,Ambient Light Sensor, Auto-brightness, Accelerometer, Auto-rotation), but proximity sensor have reading of 0cm all the time. Which make the screen black when having a phone call. And double tap/lift to wake is not working(although my accelerometer is working according to sensors multitool).
I don't have screen protector, and this problem happened just after i first updated it to android 10. so i think it might be just a software problem.
I had the october update already, but it is not fixed.
And this is a phone that never oem unlocked or rooted, no trwp installed ever, so it might be a different problem rather than that FIXED one.
I live in a country that I could not send the phone back for repairing or replacement, and i have to use adb sideload to install every ota
(and most of time when I switch my camera to frontfacing camera, it will buzz and vibrate, but when i switch back to rare and back to front, it can be fixed. this is another small issue, but it happened before this update already, maybe i just need to mention it)
Any idea what might cause this and how can I fix them?
Thanks.

https://forum.xda-developers.com/showthread.php?t=3967525&p=80233629

TonikJDK said:
https://forum.xda-developers.com/showthread.php?t=3967525&p=80233629
Click to expand...
Click to collapse
i read this already and my issue is not the same one as mentioned...
in that issue, all sensors are dead, but not in my case.
my device is never unlocked or rooted, no twrp installed, so maybe nothing has right to write the persist?
and if it is the same one, it should be fixed in october patch, but mine is not FIXED at all.

zhangcx93 said:
i read this already and my issue is not the same one as mentioned...
in that issue, all sensors are dead, but not in my case.
my device is never unlocked or rooted, no twrp installed, so maybe nothing has right to write the persist?
and if it is the same one, it should be fixed in october patch, but mine is not FIXED at all.
Click to expand...
Click to collapse
I factory reset my device yesterday and it fixed a lot of errors I was getting. Have you tried factory reset?
Be sure the phone has backed up to the google drive