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!

[Q] question on disabling front sensor, screen blanking ...

Hello all ... I'm sure this is a simple question ...
My wife has a stock d2vzw with 4.3 installed. The proximity sensor next to the front-facing camera seems extra sensitive; anytime a stray object/finger crosses it's path the screen turns off. My guess is this is a power-saving feature whenever the phone is turned over or placed in pocket, etc. However in my case, it is just super annoying and I would like to disable it. (in contrast, my CM10.2 d2vzw doesn't seem do this by default)
Can someone point me to the option needed (in stock 4.3) to disable this, or perhaps extend the time so that it doesn't black the screen instantly? I've poked through most of the menus and can't seem to find it ....
Thanks

vax1170 said:
Hello all ... I'm sure this is a simple question ...
My wife has a stock d2vzw with 4.3 installed. The proximity sensor next to the front-facing camera seems extra sensitive; anytime a stray object/finger crosses it's path the screen turns off. My guess is this is a power-saving feature whenever the phone is turned over or placed in pocket, etc. However in my case, it is just super annoying and I would like to disable it. (in contrast, my CM10.2 d2vzw doesn't seem do this by default)
Can someone point me to the option needed (in stock 4.3) to disable this, or perhaps extend the time so that it doesn't black the screen instantly? I've poked through most of the menus and can't seem to find it ....
Thanks
Click to expand...
Click to collapse
You can't disable the sensor with stock rom. The sensor is either on (value 5) or off (value 0) so there's no time setting for this. You have to be rooted in order to disable the sensor. Some technical people reported that they have take the phone apart and clean it, but if the sensor is defective, you either replace it or disable it. Also you can download an app called proximity sensor finder and test your sensor, open the app and wave your hand over it, you should see the value changes from 5 (not cover) to 0 (covered).

Thanks, I'll try it out.
However, is there a setting somewhere that will simply disable the feature of blanking the screen based on the proximity sensor?
With this same phone, I don't think I ever observed the annoyance with 4.1.2 .... it looks like the sensor/blanking is either something new in 4.3 or perhaps some default value/option was reset when the phone was upgraded.
Thanks!

vax1170 said:
Thanks, I'll try it out.
However, is there a setting somewhere that will simply disable the feature of blanking the screen based on the proximity sensor?
With this same phone, I don't think I ever observed the annoyance with 4.1.2 .... it looks like the sensor/blanking is either something new in 4.3 or perhaps some default value/option was reset when the phone was upgraded.
Thanks!
Click to expand...
Click to collapse
Do a factory reset. The ota has a lot of side effects if you do not reset.

Why Edge Sense doesn't work when screen is off ?

Hi. Does your Edge Sense feature work when the screen is off but the phone is on ?
For some reason mine doesn't work even though I don't have any PIN code setup or pattern or whatever. I don't use the fingerprint sensor either. So no security feautures set up as of right now. I've also checked the checkmark in the Edge Sense settings that says "enable Edge Sense when sreen is off".
What the...

lebigmac said:
Hi. Does your Edge Sense feature work when the screen is off but the phone is on ?
For some reason mine doesn't work even though I don't have any PIN code setup or pattern or whatever. I don't use the fingerprint sensor either. So no security feautures set up as of right now. I've also checked the checkmark in the Edge Sense settings that says "enable Edge Sense when sreen is off".
What the...
Click to expand...
Click to collapse
My U11 plus Edge Sense works when screen is off, I use it for the camera when I see something I want to snap and long squeeze for the Edge launcher shortcut.

lebigmac said:
Hi. Does your Edge Sense feature work when the screen is off but the phone is on ?
For some reason mine doesn't work even though I don't have any PIN code setup or pattern or whatever. I don't use the fingerprint sensor either. So no security feautures set up as of right now. I've also checked the checkmark in the Edge Sense settings that says "enable Edge Sense when sreen is off".
What the...
Click to expand...
Click to collapse
Is your proximity sensor is block by anyway (like screen protection) ? Mine doesn't work if proximity sensor is blocked

Kidy973 said:
Is your proximity sensor is block by anyway (like screen protection) ? Mine doesn't work if proximity sensor is blocked
Click to expand...
Click to collapse
Yes you are right. That's probably the reason why. I still use that screen protection layer that came with the phone. I will remove it ASAP.
Thanks again.

Proximity Sensor Issue OP7P

Guys!
Do you experience proximity sensor issues while answering calls on OP7P?
For me while I'm on calls. The display comes on and gets disturbed and get pressed by my ears all the time.
Also any idea of where the proximity sensor is located on OP7P?
Thanks ?

Yes, I'm having the same issues. While I'm on calls I often activate the notifications pulldown. It would be nice to know how to fix this.

If you pull down the notification shade, the sensor is located just above the fifth icon on the first row. IE behind the screen.
If you pull the shade all the way down it is above and between the third and fourth icons. Easiest way to describe it. Put your thumb over that area with auto brightness on to watch the slider move.
Annoying while on a call that the screen comes on.

I'm experiencing the exact same issue with the caller app.
I also tried to make a flip cover to turn screen on or off with a proximity sensor detection app and it didn't work either.
I search a little in engineer mode (*#808#) and found that there is multiple proximity sensor, the IR sensor work quite well but it doesn't seem to be the default one.
The default one seems to be the ultrasonic sensor which works really bad.
There is also a "TP" proximity sensor which seems to be a near field detection which seems to work if I move my hand near the screen.
The sad thing is that in dedicated app to use or test proximity sensor (and in antutu or else) only one proximity sensor is listed (The ultrasonic one I guess) so you cannot switch to use the one which is working well.

Isn't this in the wrong place? Shouldn't it be in the Questions and Answers section?
Mods?

Probably just here looking for a mod to improve the situation

Actually I was going to open a new thread in Q&A when I found this one with the same subject and problem.
Do you think I need to open a new thread?
Is any of you experiencing the same issue as I described in my answer?

did anyone calibrate the proximity sensor using *#808# first? That seems to fix double tap to wake for some people

I tried to with no luck but as I explain in my first message the IR sensor is only used when screen is off (that's why it could help with double tap to wake)
But when screen is on another or couple another sensors are used and you can't calibrate them.
I think ultrasonic sensor is used when screen is on.
Do someone tested proximity sensor with any app on the play store? (Like proximity sensor test)
Put it on a table and check if it's working, mine is absolutely not. If I hold it like I was about to phone it works a little but it's not impressive.
Since I got 9.5.7 (EU version) earlier this evening screen turn off when I make a call.

I'm having this issue since 9.5.8... It's very annoying and I'm really disappointed, I often turn on airplane mode during a call... I tried to calibrate but it doesn't work.
I'm very very frustrated

schmeggy929 said:
did anyone calibrate the proximity sensor using *#808# first? That seems to fix double tap to wake for some people
Click to expand...
Click to collapse
When I click on proximity test it says it needs calibration how do I do that cause otherwise I can not test my proximity sensor cause when I click on it nothing happens
I am on 9.5.8

dallasnights said:
When I click on proximity test it says it needs calibration how do I do that cause otherwise I can not test my proximity sensor cause when I click on it nothing happens
I am on 9.5.8
Click to expand...
Click to collapse
This...

I've been having issues with phone calls but more so with pocket issues.. When I had the 6t pocket mode kept the phone neutral but this phone doesn't seem to have an accurate prox sensor.. Is there a way to activate a pocket mode?
Sent from my [device_name] using XDA-Developers Legacy app

Happening to me too, approached oneplus via live chat about this issue and at one point they said to wipe and reset my phone even if I told them the sensor is working but seems badly calibrated. Will try the wipe & reset and if it's not working I am returning my phone.

Proximity sensor is working fine - there is a bug elsewhere on the firmware that does not lock the screen when it is blacked out

pinzarualex said:
Happening to me too, approached oneplus via live chat about this issue and at one point they said to wipe and reset my phone even if I told them the sensor is working but seems badly calibrated. Will try the wipe & reset and if it's not working I am returning my phone.
Click to expand...
Click to collapse
Let us know if it's going to fix the issue wiping and resetting everything please!!!

Jaco2k said:
Proximity sensor is working fine - there is a bug elsewhere on the firmware that does not lock the screen when it is blacked out
Click to expand...
Click to collapse
But I have had this issue since release.. Do you a link to this information? If that's the case maybe someone can look into the firmware and see if it's minor tweak that can fix it?
Sent from my [device_name] using XDA-Developers Legacy app

Jack_Sparrow_ said:
Let us know if it's going to fix the issue wiping and resetting everything please!!!
Click to expand...
Click to collapse
Of course it didn't fix anything...

Jaco2k said:
Proximity sensor is working fine - there is a bug elsewhere on the firmware that does not lock the screen when it is blacked out
Click to expand...
Click to collapse
This has been an issue since the release. Do you have a link to where you read this information? If it is the firmware maybe someone can look into the settings and see if needs a tweak..
Sent from my [device_name] using XDA-Developers Legacy app

j0hnee said:
This has been an issue since the release. Do you have a link to where you read this information? If it is the firmware maybe someone can look into the settings and see if needs a tweak..
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I have reported this to Funk wizard on the OOS support thread and he said he cannot reproduce it anymore on the latest test build, so... We have to wait for next firmware release and see if that is indeed the case

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