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!
Hi. I have noticed some problems with proximity sensor on my sensation. When I make phonecall my screen wont shut down at all, i have tried vipers jb and albinos and then android1234567 4.3 so I think problem is with hw, anyone what I should do?
I have the same issue with the roms u mentionned, and in my case dunno if it's HW related because with skype and viber the proximity sensor works fine!
This helped me....sensors seem to work again
Hi,
i also (and a lot of people in fact) have the dreaded proximity and lightsensor problem. And indeed there seems to be no solution... People have been reseting and reflashing the Sensation till it drove them mad, without the problem solved... The problem seem to start when the Sensation was upgraded to ICS, and seems software related...
In my quest to solve the problem I stumbled upon a solution on the htcsensationforum.... and gues what, it seems to work for me, that is, the sensors work more often now.
I quote the solution, since i cannot paste the link;
Hi Tim.
I had the same problem. Phone is now fine after 24 hrs. Here's what I changed:
1. Turned off 'Pocket Mode'. Settings -> Sound -> Pocket Mode. No obvious change by itself
2. Turned off 'Fas tboot'. Settings -> Power -> Fast boot.
3. Turned off, removed battery, waited 30 secs and powered back on.
Simple as that! The proximity sensor was glowing occassionally after the upgrade, and that has gone away too. On the bonus front my battery life has never been so good (using about 60% of what it used to)!!!
Cheers.
Click to expand...
Click to collapse
Don't know how long this solution will hold, but it seems that the pocket mode and / or quickboot option are causing the problems... What i use to check the sensors behavior is the free app android sensor box, found in the playstore.
Maybe one of the devs here can take a look at this solution, and can come up with a permanent solution to have the proximity and lightsensor working normal again...:good:
Just my 2 pence on an old pain in the *ss problem, thanks go to Maestro @ htcsensationforum for his solution...
Cheers:cyclops:
Hello guys. I have a problem with my orientation sensor on my Nexus 5. I think that is a hardware issue, because it didn't resolve after reboot or clean install.
The funny part is that it works in games, but not in apps like camera (i can't use panorama or 360 mode). Also, the auto rotate doesn't work. The phone has suffered from a drop on the floor, and i think that's the root of problems .
Anyway, i guess that i should take him to service. Do you guys have any ideea of the price? The orientation sensor can be replaced or it will be the motherboard?
So, recap. The phone has suffered 2 drops. The first one had shut down the auto rotate feature, the second one has maked the sensor to work better in games. I take care of my phone, but sometimes it happens.
P. S. I checked the auto rotate option.
P. P. S. I checked this forum http://forum.xda-developers.com/google-nexus-5/general/sensors-fix-nexus-5-t2704915
Ty for any sugestions.
My phone is a LG Optimus G (a F180 converted to E975, stock Euro firmware), but from googling this issue it seems to be a problem that can strike any phone with no readily apparent solution...
I first noticed it while playing Star Wars KOTOR, where it'd get stuck; flipping the phone (to better orient the charging lead) started leaving the picture upside down. Initially, I could fix it by long-pressing the home button to get at my notification bar and toggling auto-rotate off and on, before it crapped out entirely (necessitating an orientation-locking app), which led me to think it was a software issue...
But after googling the problem and seeing how widespread it is, I'm thinking maybe these sensors are just prone to failing? I saw all sorts of possible solutions offered, which apparently work for some, but it seems nothing solves it for many, including factory resets and flashing firmware... I uninstalled KOTOR when I was done with it, but to no avail. I don't fancy figuring out how to flash the firmware again, but if that's what it takes...
Does anyone know anything about this issue? Am I stuck with a slightly crippled phone now?