Related
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!
My nexus s' proximity sensors have stopped working. I am rooted and running aokpcb rom, I'm wondering if this is a hardware problem or something with the rom? The screen won't turn off when answering / making a call when the phone is brought up to my ear. I also tried using the app prox pro, and that wouldn't work either. If anyone knows a fix or what the problem is, that would be great.
Backup your current ROM , wipe and install a Stock ROM.
Issue solved --> Rom Issue
Issue unsolved --> hardware issue
Thank you for your response. I tried your suggestion, and the problem wasnt fixed with wiping and installing a stock rom. But, with experimentation, I installed the app "Prox Pro" and whenever I would turn it on, it would execute the command that was specified for when the phone was "flat". So, when realising this, I am assuming that my phone developed some sort of calibration problem with the sensors. All in all, I am wondering if there is a way that I can re-calibrate my proximity sensor so that they work properly. Thank you.
Could that just be the default for the phone if it's not getting a reading?
I don't think its the default. The sensors always worked fine up until sometime last week.
I meant a default if there is no signal or an error, which is what it currently looks like.
Oh, okay, ya that could be it. Do you have any idea how to change it? I also realised that the light sensor isn't working either, when on auto brightness, the screen will always be dim, no matter how bright it is outside. If you, or anyone else has a solution, I will open up my phone and check to see if there are any connection issues or something like that .
Hi all, I just noticed that my auto rotate isn't working anymore. I was using a custom rom, but reverted back to stock just to make sure everything would be alright, but it still isn't working on my stock rom. I downloaded "Phone Tester" from the app store, and when I check to see if it's working, it says that my device has no accelerator, compass, light sensor, etc...
What's going on here? It was working fine a couple of days ago.
Edit, when I go to the Phone Tester app, it says that I don't have:
- Accelerometer
- Compass
- Magnetic Field Sensor
- Proximity Sensor
- Light Sensor
- Gyroscope
- Pressure Sensor
- Humidity Sensor
bump
Having your same issue. It worked once when I flashed a new rom but then I rebooted and it stopped working. I went back to stock but that didn't help either.
neriamarillo said:
Having your same issue. It worked once when I flashed a new rom but then I rebooted and it stopped working. I went back to stock but that didn't help either.
Click to expand...
Click to collapse
If you flashed the factory image and it's still not working then it's most likely a hardware issue.
I remember soon after the N5 was launched there was a barometer app that was crashing all of the sensors. Maybe this is still an issue?
El Daddy said:
I remember soon after the N5 was launched there was a barometer app that was crashing all of the sensors. Maybe this is still an issue?
Click to expand...
Click to collapse
I have barometer installed and working since day 1 I bought the phone.. I would assume the OP problem is an isolated issue that somehow crashed all the sensors.
Most possibility is factory hardware defect.. or .. somehow the phone was at affected by strong magnatic/radiation field area that caused those sensors broken.
Having the same issue.
So I figured something out today. I flashed the stock image for 4.4, (not 4.4.2 like i had previously), and everything works perfectly fine! Now if I take the OTA for 4.4.2 it stops working once again. So now I have no idea what to do lol since I know its not necessarily a hardware issue but more of a software issue. Another thing is while on 4.4.2 if I open GPS Status & Toolbox app to check the GPS or sensors the phone soft reboots but the app never opens.
This is definitively a software issue somewhere. Its been working perfectly fine all day on stock 4.4
I will try and see if I can find what's changing or getting updated when you do the update to 4.4.2.
So, I have stumbled across this weird issue since January wherein if the proximity sensor is covered during an incoming call, the screen will remain off. What's weird is that this only happens on CM based ROMs and not on AOSP based ROMs. Of course, all full wipes and clean flashes. I have also tried flashing all the Marshmallow compatible modems available but none solved my issue. I'm using TWRP 2.8.6.0 to flash the zips.
CM based ROMs that I have tried so far;
1. Resurrection Remix M
2. Bliss ROM (both official and unofficial)
3. Marsh CM13
The older builds (December and early January) did not have this problem but of late, every CM based ROM activates the proximity sensor for an incoming call. The reason I'm posting this here is because no one else seems to have this problem and it's not specific to any one ROM.
On AOSP ROMs, everything works fine (no matter what modem I use). I have tried Darkobas ROM and I'm currently on CandySix where I don't have any issues with the proximity sensor.
Any idea why this could be happening? I miss all the customization on CM ROMs and I'm not a huge fan of Layers, so help would be appreciated.
Cheers!
This is the exact bug description:
1. when on a call, cover the proximity sensor >> screen turns off
2. while covering the sensor doubletap the screen (this is the reason for this issue!)
3. uncover the sensor >> screen stays off
The problem is that the doubletap is registered as a power button press and therefore the screen stays off.
It only happens if you accidentally touch the screen with your face, which is likely to occur on a phonecall.
I've already mentioned this in a commit and they said they know about this issue.
The needed commit needs to be ported from cm12.1.
So I guess we can only wait...
Thanks for your response, mate. But CM seems to have fixed this issue because I just flashed the 02/03 CM13 nightly and the proximity sensor works just as it should during an incoming call; no issues there.
I'm going to try flashing another ROM on top of this.
AcmE85 said:
This is the exact bug description:
1. when on a call, cover the proximity sensor >> screen turns off
2. while covering the sensor doubletap the screen (this is the reason for this issue!)
3. uncover the sensor >> screen stays off
The problem is that the doubletap is registered as a power button press and therefore the screen stays off.
It only happens if you accidentally touch the screen with your face, which is likely to occur on a phonecall.
I've already mentioned this in a commit and they said they know about this issue.
The needed commit needs to be ported from cm12.1.
So I guess we can only wait...
Click to expand...
Click to collapse
I just went through your post again and it seems that you misunderstood my issue.
Apart from the issue that you mentioned, the proximity sensor is turning off the screen even before I have answered an incoming call. So, for example, I get a call when the phone is in my pocket. When I take it out, it takes a while for the screen to turn on which is frustrating. If I don't answer the call, the screen should remain on for as long as the phone rings, irrespective of whether the proximity sensor is covered or not. But, in my case, if the proximity sensor is covered when the phone is ringing, the screen turns off. Am I being clear now?
So, after a few intense sessions of flashing different ROMs, it seems that the official CM13 nightly and CandySix are the only ROMs where the proximity sensor is not broken for incoming calls. I guess I'll be sticking with CandySix for the foreseeable future.
But I'd really appreciate if someone can identify why this is happening with all other ROMs and not with official CM13 and CandySix.
girishb said:
I just went through your post again and it seems that you misunderstood my issue.
Apart from the issue that you mentioned, the proximity sensor is turning off the screen even before I have answered an incoming call. So, for example, I get a call when the phone is in my pocket. When I take it out, it takes a while for the screen to turn on which is frustrating. If I don't answer the call, the screen should remain on for as long as the phone rings, irrespective of whether the proximity sensor is covered or not. But, in my case, if the proximity sensor is covered when the phone is ringing, the screen turns off. Am I being clear now?
So, after a few intense sessions of flashing different ROMs, it seems that the official CM13 nightly and CandySix are the only ROMs where the proximity sensor is not broken for incoming calls. I guess I'll be sticking with CandySix for the foreseeable future.
But I'd really appreciate if someone can identify why this is happening with all other ROMs and not with official CM13 and CandySix.
Click to expand...
Click to collapse
actually i think u messed up a bit mate dont mention calling ! something like screen OFF when i recieve a call from someone even when not answered or something like this ! and now getting back to your query i flash RR and CM13 by jgcaap right now just for checking ur issue and i dont have this i kept the phone on the table , called from my other phone and covered the proximity sensor with my hand ! screen was still ON .. and i should mention my RR build is a bit old ! i have been using jgcaap cm 13 from many days ! so
Well, there was only so much I could put in the title. I think my OP explains the issue clearly.
Also, can you try the latest version of RR or Bliss ROM? Because as I said, I wasn't having this issue on the older builds. I also don't have this issue on the official CM13 nightly or CandySix. I just want to find out what's causing this issue on my phone with other ROMs.
@girishb
Ok I see. The way you put it, I thought cm based roms includes stock cm13.
Regardless. The commit which fixed the proximity sensor with screen off has been merged on 02/20.
When did the other cm based roms get their last update?
AcmE85 said:
@girishb
Ok I see. The way you put it, I thought cm based roms includes stock cm13.
Regardless. The commit which fixed the proximity sensor with screen off has been merged on 02/20.
When did the other cm based roms get their last update?
Click to expand...
Click to collapse
but still that issue of phone getting locked furing call persists right ? i mean during call i get this lock sounds sometimes and i need to double tap agn to disconnect the call ! anyways im sure there is a more recent build after 20/2 for rr ! anyawys i should check and get back on taht
thepico said:
but still that issue of phone getting locked furing call persists right ? i mean during call i get this lock sounds sometimes and i need to double tap agn to disconnect the call ! anyways im sure there is a more recent build after 20/2 for rr ! anyawys i should check and get back on taht
Click to expand...
Click to collapse
Im on RR 24 and i can still see this issue. Lets see wht RR Mod comments on that.
Uh, I'm pretty sure that's a different issue. What you guys are facing is basically the screen getting locked when a call is going on, which should not happen. This issue is consistent across all ROMs that I have tried, even AOSP ones. So I don't think that's a CM issue.
My original issue is slightly different. During an incoming call, the screen should remain on for as long as the phone rings, right? If I choose to answer the call, that's when the proximity sensor should kick in and turn off the screen as I move the phone to my ear. However, in my case, if the proximity sensor is covered during an incoming call, it keeps the screen off so I can't see who's calling unless the sensor is uncovered. This should not happen. I hope this explains the issue properly.
girishb said:
Uh, I'm pretty sure that's a different issue. What you guys are facing is basically the screen getting locked when a call is going on, which should not happen. This issue is consistent across all ROMs that I have tried, even AOSP ones. So I don't think that's a CM issue.
My original issue is slightly different. During an incoming call, the screen should remain on for as long as the phone rings, right? If I choose to answer the call, that's when the proximity sensor should kick in and turn off the screen as I move the phone to my ear. However, in my case, if the proximity sensor is covered during an incoming call, it keeps the screen off so I can't see who's calling unless the sensor is uncovered. This should not happen. I hope this explains the issue properly.
Click to expand...
Click to collapse
What firmware are you on? Most proximity sensor issues are due to incompatible/old firmware.
YoshiShaPow said:
What firmware are you on? Most proximity sensor issues are due to incompatible/old firmware.
Click to expand...
Click to collapse
I have tried all modems from this topic (other than the h2os and oxygen one). I have also tried clean flashing the latest CM13 nightly before clean flashing any ROM. I also tried dirty flashing a ROM over the CM13 nightly with no luck. I used TWRP 2.8.6.0 for all of this.
What I can't seem to figure out is why I don't have these issues on the official CM13 nightly build or on CandySix ROM. All other ROMs that I have tried have this issue. If it's a firmware related issue, then shouldn't I be having this problem on all ROMs?
Any solution for this problem coz its really annoying.
I'm having the exact same problem with my phone running CyanogenOS 13.1.2-ZNH2KAS3P0-bacon. The screen doesn't turn on automatically if the proximity sensor is blocked in the beginning of the incoming call or alarm.
If someone finds a solution, please reply to my post
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