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] Compass / attitude sensor problem, Evo3D CM 10.1 "Wild For the Night" (Jan 30)
Would have posted in the related thread but I guess I haven't been chatty enough yet.
I've been running either Gangnam Style or Wild For the Night for about as long as they have been available and generally loving them, much better than previous roms.
However, when I installed the January 30 release of 10.1 WFTN, I noticed my compass isn't working. It seems like the attitude sensor is also iffy.
When I run GPS Status, the compass always stays locked at 000 degrees regardless of what attitude I'm holding the phone in. I have tried the Tools > Calibrate Compass function in GPS status and that doesn't seem to do anything. No heading arrow appears on Maps, either.
The attitude sensor in GPS status does not seem to work either, but if I open up Bubble Level, that seems fine - so I'm not sure if the compass and attitude sensor actually have any trouble, or if it's simply that some apps can't communicate with them properly.
This all comes up because I was trying to use photosphere and it can't figure out what angle I'm holding the phone at so it never takes a picture. I used the photosphere zip from the E4GT Wild For The Night thread, as suggested by Dastin.
I tried various combinations of reflashing the ROM, wiping cache + dalvik and reflashing the rom, reflashing Gapps, and reflashing the camera. I also reverted to 10.0 Gangnam Style (Jan 30) to see if that made it work, and all that got me was a neverending cyanogenmod boot screen. Reverting to 10.1 got me booting again, but...
Basically, does anyone know of a way to get the compass/attitude sensors working? Is this likely just an issue in the ROM or can those sensors be separately configured/calibrated?
Anyone have any input or suggestions?
I'd really like to check out photosphere, but the inability to use sky map hurts too as I'm a wannabe stargazer...
omgallthenamesaretaken said:
Would have posted in the related thread but I guess I haven't been chatty enough yet.
I've been running either Gangnam Style or Wild For the Night for about as long as they have been available and generally loving them, much better than previous roms.
However, when I installed the January 30 release of 10.1 WFTN, I noticed my compass isn't working. It seems like the attitude sensor is also iffy.
When I run GPS Status, the compass always stays locked at 000 degrees regardless of what attitude I'm holding the phone in. I have tried the Tools > Calibrate Compass function in GPS status and that doesn't seem to do anything. No heading arrow appears on Maps, either.
The attitude sensor in GPS status does not seem to work either, but if I open up Bubble Level, that seems fine - so I'm not sure if the compass and attitude sensor actually have any trouble, or if it's simply that some apps can't communicate with them properly.
This all comes up because I was trying to use photosphere and it can't figure out what angle I'm holding the phone at so it never takes a picture. I used the photosphere zip from the E4GT Wild For The Night thread, as suggested by Dastin.
I tried various combinations of reflashing the ROM, wiping cache + dalvik and reflashing the rom, reflashing Gapps, and reflashing the camera. I also reverted to 10.0 Gangnam Style (Jan 30) to see if that made it work, and all that got me was a neverending cyanogenmod boot screen. Reverting to 10.1 got me booting again, but...
Basically, does anyone know of a way to get the compass/attitude sensors working? Is this likely just an issue in the ROM or can those sensors be separately configured/calibrated?
Click to expand...
Click to collapse
First of all I must give a big THANKS to Albinoman and all who supported him in producing this ROM.
Recently I found one BUG, I have no idea if it is known issue. I tried to search the same but couldn't find any answer.
What I did was pulling down notification bar and switched on Torch, after the time limit Torch goes OFF but in the notification bar it is shown as ON. So far so good. Now if I switched on Camera it gives Camera Error, Can't connect to Camera. This error comes even if the torch is ON.
Build Date
Thu May 9 17:58:04 PDT 2013.
On BADASS
I will try the May 17th version now and POST the error again. I
I just want you to know that this is what I got. Anyways the ROM is good except for the Battery issue. Someone said ROM has nothing to do with any Battery consumption, but I tried with a different ROM earlier and its Battery life was good.
Also tried upgrading to May 17th, I know change log says nothing about Camera, but still I tried first without upgrading to Camera Sphere 4.2 and than with Camera Sphere 4.2 same issue found.
BTW I am S-ON.
Thanks
Love and regards
Prasad
prasad_m said:
First of all I must give a big THANKS to Albinoman and all who supported him in producing this ROM.
Recently I found one BUG, I have no idea if it is known issue. I tried to search the same but couldn't find any answer.
What I did was pulling down notification bar and switched on Torch, after the time limit Torch goes OFF but in the notification bar it is shown as ON. So far so good. Now if I switched on Camera it gives Camera Error, Can't connect to Camera. This error comes even if the torch is ON.
Build Date
Thu May 9 17:58:04 PDT 2013.
On BADASS
I will try the May 17th version now and POST the error again. I
I just want you to know that this is what I got. Anyways the ROM is good except for the Battery issue. Someone said ROM has nothing to do with any Battery consumption, but I tried with a different ROM earlier and its Battery life was good.
Also tried upgrading to May 17th, I know change log says nothing about Camera, but still I tried first without upgrading to Camera Sphere 4.2 and than with Camera Sphere 4.2 same issue found.
BTW I am S-ON.
Thanks
Love and regards
Prasad
Click to expand...
Click to collapse
First off, just for future refference, there are 2 threads for Albino's rom already.
One is in the development section and one specifically for troubleshooting like this post is in teh Q and A Section. In the future please search for an existing thread rather than create a new one. This helps keep XDA a little more organized.
Now onto your problem...
I agree with everything you said. The torch and the camera don't work at the same time. The camera needs access to the LED to work, and obviously so does the torch. When the torch is already on the camera doesn't have access to it. It's like trying to put 2 keys into the same lock at once.
So since the camera app reads the device to see if the hardware it needs is available, when it finds the LED isn't available it shuts down. Even though the torch itself has timed out and has gone off, the torch app is still running and it controls the LED hardware until the app stops. so even though the light is off, the camera still can't control the LED hardware.
This is an overly simplified explanation, but this is what's going on.
We discussed in the dev thread that the camera app can run the led constantly during video so this isn't being done on purpose to prevent a reboot due to extreme battery drain. Its just a conflict for hardware resources. But since the camera can keep the led on there is no reason to have the torch app keep the led on, so there is no reason to really fix this bug.
Again though, the camera still fc's after the led times out because the torch app is still in control of the led hardware. So you have to remember to turn off the torch. That's also why the notification bar says the torch is on, even though the led is off. The torch app is still running in the background, which is what the notification bar is rally indicating.
Thanks I thought I should mention here if it is a Bug, BTW I was not aware how to start a thread within the Albino's ROM.
I can see only option Reply to someones thread. I found new thread here and hence the confusion.
Anyways thanks.
Love and regards
Prasad
Hey Guys!
I have been wandering around new roms lately, I am using 64gb Sandstone Black Oneplus ONE device and I am in europe region (Turkey).
I have this issue since I am using CM12.1 nightlies and custom roms, My screen was not auto rotating and I was wondered if its a hardware issue or not. I installed Sensors Kinetics application from google play store, There is bunch of sensors listed in that application but I almost only have 2 or 3 sensors which is lights sensor and a non working proximity that always has 0 cm value and never changes. Tested while talking with my friend from the phone, screen not goes off when I have the phone near my ear.
I lately installed a rom from @Sultanxda Unofficial cm12.1 with CAF kernel. in this firmware my every other sensors are working. Accelerometer showing some results, screen is rotating, proximity tells 1-5cm values, gyro is working etc.
But my sensors are broken in every other ROM I have tried until now. I am now using Slimsaber's rom and my sensors are not working.
I wiped cache & dalvik etc. evet formatted every part of my phone to get a clean install of some roms but still my sensors are not working.
And also I my cell is often get no signal, I have to reboot 2-3 times to get a reception.
Halp me please guys. What can I do to get my sensors back online in Slimsaber's or another roms?
Same here.
Worked fine with the stock ROM, with CM12.1 nightlies proximity and accelerometer do nothing (i.e. not effective).
Strange thing is, in some sensor testing apps the proximity sensor shows some data and seems to function, in others nothing happens. Same with the accelerometer.
Still there's no effect on the phones behaviour. the screen is not locked during calls, no screen rotation, ...
as for reception: unstable but restores quickly (I remember reading something about that...)
cheers!
~def
Look at this:
http://forum.xda-developers.com/showthread.php?t=3127401
Maybe that will help.
Gede said:
Look at this:
http://forum.xda-developers.com/showthread.php?t=3127401
Maybe that will help.
Click to expand...
Click to collapse
:highfive:
Solved it for me, thanks man!
So, if TWRP does not update/flash the modem, it will persist after nighty updates?
[OT: for my own learning process: how come sensors are controlled/defined/whatever in the modem thingy? is there any info or documentaion on "what is where"?]
:good:
~def
Must be something wrong with TWRP, or how they put the zip together..