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!
I have tried searching for some time and have encountered several different opinions on how to resolve the issue however, none so far work.
When taking a call or when placing a call after connecting to the call the screen goes blank in what seems to be 2 seconds even though I still have the unit in my hand and not up to my face and I am not touching/blocking the proximity sensors.
What is the definitive answer on what I can do to make a change to the settings to prevent the keypad/screen from blanking out while in a call?
I have the display settings set to keep the screen on when not in a call to 10 minutes and always on when connected to a power source. For the life of me I cannot find a resolution to this problem.
Exhibit II 4G with Stock ROM and now Cyanogen Mod9
have you got a proximiti sensor? Meaby you screen film blocked it
I think your proximity sensor is broken.. try to search in play store for "proximity sensor" i've heard of an app that can turn off your proximity sensor when calling but i don't know for rooted devices or non rooted
Sent from my GT-I9000 using xda premium
Nope, I do have a screen film installed however, it clears and does not block the 2 proximity sensors on the top front of the phone.
I installed a Proximity Sensor APP from the market and it registers the device as working and activates the sensor at about 2 inches away.
I did notice today that when using the phone to call T-Mobile voice mail the dial pad does NOT blank during the call.
Does Android have a config file anywhere for this or is the screen blank setting built in to the system or perhaps the dialing app itself?
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.
Hello there!
I have the problem since I put matte screen protector on my phone. Everytime I call/answering call screen goes black. Maybe it needs calibrating proximity sensor or something like, but I don't know how.
I would be very grateful if you could suggest me some way to fix this problem.
Thanks
Some screen protectors just mess with the proximity sensor, remove them and verify the sensors operation... If it fixes the problem, contact the manufacturer/retailer and request a refund, a screen protector designed for the device should not interfere with any sensor's operations.
There is no way to calibrate the sensor I am aware of.
Sensors Test app by Ettore Zaffaroni is a handy tool to check proximity sensor and others. It detects 3 levels of proximity, less than 1 cm, between 1 and 3 cm, beyond 3 cm on Moto G 3th. The proximity sensor on this model is right between the ear speaker and the front facing camera.
Thank you both for the answer.
The protector I'm using currently is custom cut (cause there was no other option for my phone in my region). It covers sensor and hence the problem comes. When putting on I didn't think there would form this kind of obstacle. The Clear one that I had purchased from amazon and used before was cut nicely and didn't cover sensor.
Lately I was searching some tools for calibrating and came up with an app named Proximity sensor restore/repair by Mobile Direction. As it says it only repairs the software problem not hardware. I gave it a try and for now sensor works. Though, I don't know if it will be permanent solution.
Alternative is to cut there too where proximity sensor is located, cause I don't want to remove the protector yet.
Oh no ! here it comes again! I had a long standing issue on Moto G Osprey with screen going blank when making or receiving a call . WIth AospExtended ROM 26/09 version it was resolved . In mean time I spent 1 year tried to resolve teh issue by installing stock motoroal firmwayre, proximity sensor disabling via exposed module, proximity sensor caliberation etc and nothing worked . But with 26/09 build thsi was resolved and my screen was working on 90% of calls and on 10 % dialler or call accepting option was not apearing but status bar was visible where on Andropid Nougat roms and Marshmellow Roms it was 90% of calls were made received with blank screen and then rubbing over sensor to wake up screen .
After the Alpha build 30/09 this has came back again . I have checked again on 26/09 build and issue is not there . Can anyone suggest why I am having this issue with new build or what changes been made into new build which can cause this issue ? I understand only few people have this issue and even on Lenovo forums there is no solution to it
Proximity sensor Complete solution 101%
I have also same problem and All osprey custom ROM last update has this problem.
But guys u can use cypheros 4.1.2 there is no problem with proximity sensor it's same stable as AEX 4.6
get.cypheros.co