Hello,
i have a problem with my proximity sensor... it simply doesn't work with CM 7 (neither the RCs nor the final 7.0.0), on HTC stock it worked properly (switched display off when i took the phone to my face while calling someone).
When i install Sensor List it shows constantly the Value 9 not regarding if i touch the sensor or hold the phone to my face.
I did a lot of research... but nothing helps.
Many people say that i should change the ro.lge.proximity.delay in build.prop.
But i dont have this value in build.prop. Tried adding it with recommended value 200 but no change.
Also tried the Proximity calibrator from this forum and Sensor Doctor from Marked. Both Apps crash (i think because it doesn't find the ro.lge.proximity.delay value in build.prop).
Also have the always force proximity sensor option in CM setting set.
What can i try? Someone else this issue?
And why isn't there a ro.lge.proximity.delay option in /system/build.prop?
Thanks a lot
to finish this post: i found out that it's a hardware issue, my proximity sensor seems to be defect
and now your warranty is void! xD
time to unroot?
Will unroot if other Hardware defects should appear...
Only this defect is to small to give My Vision away for some weeks
Same her my proximity sensor seems to be defect but i think it's maby dust on it.
Related
Hi,
I've searched high and wide for a solution (other than sending it back to Motofailure repair) and am failing at finding one so far. So I'm hoping I can get some help from here.
So, this is the situation: I make a call, screen instantly turns dark and will only light up again when I press on the area where the light (&) proximity sensor is.
I've already tried the following.
1.) Done a factory reset (3x) - with mem card, with reformatted mem card, w/o mem card.
2.) Clearing the dust on the earpiece hole using an air duster.
3.) There were times that I worked properly after I've uninstalled apps but the issue came about again after a couple of tries.
So, now I'm thinking that I might want to root my Defy to set things right. I'm quite familiar with RSD Lite as I've used it before on my RAZR2 V8.
A bit of background: I bought my Defy on pre-order so this is one of the earlier models. I had the earpiece problem and sent it to Motofailure repair and the whole process took a month (32 days to be exact - long story. I'm avoiding having to send this PoS back. They updated the software when I got it back.
As far as I can recall, I didn't had this problem before the earpiece problem. And I'm thinking it might be a software problem hence I'm now looking at a solution by rooting and flashing the ROM with an original one.
I have no way of finding out (as far as I know) whether this is a hardware problem (hence hesitating to have it sent back to Motofailure repair).
What I've also observed is that when there is direct bright light, it works normally but when its dim, then the problem appears.
I don't have any screen protectors, just so you know.
Can anyone advise me on what to do?
During a call proximity sensor is activated to turn off the screen at the moment it detects proximity and asumes you are using the phone against your hear, so it turns off screen to save energy.
I think you might have some app installed in your phone, using and reversing the sensor status so it detects proximity when there isnt, and viceversa
You might want to try removing apps using that sensor and see if problem gets solved, there is also an app in the masket called sanity; which makes extensive use of proximity sensor for vaqrious things, and have an option to reverse proximity sensor, you might want to try it and see if problem gets fixed.
You might try this things: remove apps using proximity sensor, test phone. Deactivate in pocket detection; test phone, and install sainity, test phone, install a new rom?
If speaker is bigger than original one, or there was an assembly error, light/proximity sensor won't fit into right place.
I've seen such reports and you can't do anything unless you open up thing and check the problem, but you haven't seen the right assembly so you may not know the right place.
Are you using any screen protector? I know some screen protectors cause this problem.
Edit: Nevermind, I see that you're not using any.
how to calibrate the proximity sensor?
My new defy 's proximity sensor seems cannot work correctly,when i making a call ,the screen shut off immediately，and the screen could not light on by any key,but when i touch the proximity sensor with my finger,the screen may be light on!
so i download a app to test the proximity sensor which name's"Android sensor data",this app fingue out the state of proximity sensor,"near" or "far",sometimes I just passing my finger over the proximity sensor, the reading will show 'near' and then remain 'near' even when my finger is moved away!
Can anyone else help me to calibrate the proximity sensor?google told me some android phone can do this ,such as htc, zte etc.
goole tell me android phone have some standard testcode,such as *#*#4636#*#* can show the phone statue,it works correstly in Defy,*#*#0588#*#* test the proximity sensor ,but it doesn't work in defy!!!
I don't think this issue could be solved trough software tweaks. Chances are this is a hardware problem. Maybe you should contact the Motorola support.
try disabling in-pocket detection
have the same problem. it started 2 days ago. Im using CM7. It just turns dark and wont wake up unless someone else is calling me. Just got it tested, and when i cover the sensor with my finger it says 0cm distance for long time.
I've tried data wipe and similar, but nothing helped so far.
EDIT: I've just tried wiping the place where proximity sensor is with some soft cloth and alcohol and for the time being, it works. O.O
Could Wipe Dalvik help?
Soo.. it started a while ago, i switch roms alot and i am very cautious when it comes to kernels and i try to flash the right one every time but with the S-ON limitations it has been some kind of confusing
to be exact, i flashed the pokemon rom with the kernel impeded through fastboot
and the proximity sensor is not working (not turning the screen off during calls)
and i flashed bricked, faux and franco's kernels and still its not working
and no its not physically damage because i had IC rom before it and it was working fine
does any one know what is going on, what i might be missing or something i could try
anything will be helpfull
Cheers
i installed an app called AndroSensor and it said for the proximity sensor check "faliur to start" and then after a while "waiting for event"
if that might help
and the light sensor is "waiting for event" too
well i solved it.. i dont know what actually happend but here is what i did
first i tried to flash the new franco kernel along with its modules and it didnt work (didnt boot)
so i thought to try not just the stock boot image (as it is provided in the pokemon flasher) but also the stock modules (as i dont own a widnows i cant just run the script file)
i unzipped the franco modules, replaced it with the stock modules and repacked it, flashed the stock boot.img in fastboot, flashed the repacked modules from the recovery and i got the proximity and the light sensor working again
could you please help me, my proximity sensor is not working at all...and i dont know why, i changed the kernel and the modules and it havent come back..., the light sensor is working well
I have the same Problem. Light Sensor is working. Proximity Sensor suddenly stopped working. There is no reaction when i use z-device test. The weird thing is, it passes the HTC function test and the red light turns on when i try to get a reaction of it in z-device test. It seems to work somehow but is not reacting to movement. I hope there is a fix for that. I don't want to send it in for the 6th time.
So it seems that my proximity sensor is not broken. It just needs very high brightness values to work. So in a dark room it won't work. Is there a way to calibrate the proximity sensor?
Even I have the problem of non-operation of the proximity sensor and light sensor lenses. After various tests and seen several videos, I realized that the problem is in contact with the sensor to the motherboard. Pressing close to sensors, close to the camera (back) everything returns to normal ...
Sorry for my English ...
I know this is an old thread, but I'm having the same problem as guistanca. Thought it was broken, but squeezing the phone made it burst back to life... dodgy?
Same problem like giustanca and peedub, any ideas,? It is hardware issue or it can be fixed by some software modification?
Ik have the same problem sinds a month, pressing the screen on the upside wil help to get the sensor to work again.
For me it's a hardware faillure i think.
Exactly my situation but when I press screen on the upside it help but just for I whine, few second and sensor didnt work again. I will wait for new official Jelly update 4.2. and if problem will be still remain, probably I will send my One X to service.
So this is strange. Using stock Samsung ROM and dial *#0*# the proximity sensor works off the light sensor values. Proximity will be 1 until held right in bright light which at that point will be 0. WTF! I've been having a problem where the phone app uses the proximity sensor to turn off the screen and I can't turn the screen on unless the other end hangs up(big problem when it goes to voice mail) or i run to a bright light so the screen comes back on.
light sensor goes below 60 lux phone will start vibrate.
light sensor goes above 110 lux phone will stop vibrating.
I've tried many ROMs and kernels with no success and have Odined back to a stock Samsung firmware to start over. As of right now nothing should be different from when I got the device. Anyone know whats going on? I'm about to call Samsung for a replacement but wanted to see what people here say first. also I've been flashing ROMs for many years and have never seen this.
My understanding is that proximity sensor in note 2 is set for 8 cm and values are either 0 or 1 above or below 8cm
Sent from my SGH-T889 using xda app-developers app
cforlife said:
So this is strange. Using stock Samsung ROM and dial *#0*# the proximity sensor works off the light sensor values. Proximity will be 1 until held right in bright light which at that point will be 0. WTF! I've been having a problem where the phone app uses the proximity sensor to turn off the screen and I can't turn the screen on unless the other end hangs up(big problem when it goes to voice mail) or i run to a bright light so the screen comes back on.
light sensor goes below 60 lux phone will start vibrate.
light sensor goes above 110 lux phone will stop vibrating.
I've tried many ROMs and kernels with no success and have Odined back to a stock Samsung firmware to start over. As of right now nothing should be different from when I got the device. Anyone know whats going on? I'm about to call Samsung for a replacement but wanted to see what people here say first. also I've been flashing ROMs for many years and have never seen this.
Click to expand...
Click to collapse
I have this exact problem here was my thread a few months ago:
http://forum.xda-developers.com/showthread.php?t=2099898
and the only response was to factory reset (which I haven't done yet and from what you're saying that won't fix the problem either...)
Quick question, I only see 1 light coming out of the two holes at the top of the phone, are there supposed to be 2 lights? (you can check using another camera since it uses infrared)
-- edit --
just found this thread on sprint forums:
http://community.sprint.com/baw/message/544084
apparently the person had a tech open it up and air out the sensor
Easy FIX!!!!!
I took a can of compressed air and blew it through the top earpiece grill a few times and Voila, it works great now!!
I actually used a Old perfume can wich purfume was over and it was only pressing Gas OFF!!
same issue
cforlife said:
So this is strange. Using stock Samsung ROM and dial *#0*# the proximity sensor works off the light sensor values. Proximity will be 1 until held right in bright light which at that point will be 0. WTF! I've been having a problem where the phone app uses the proximity sensor to turn off the screen and I can't turn the screen on unless the other end hangs up(big problem when it goes to voice mail) or i run to a bright light so the screen comes back on.
light sensor goes below 60 lux phone will start vibrate.
light sensor goes above 110 lux phone will stop vibrating.
I've tried many ROMs and kernels with no success and have Odined back to a stock Samsung firmware to start over. As of right now nothing should be different from when I got the device. Anyone know whats going on? I'm about to call Samsung for a replacement but wanted to see what people here say first. also I've been flashing ROMs for many years and have never seen this.
Click to expand...
Click to collapse
I had the exact same problem with the proximity sensor and other weird sensor issues. I had never rooted or anything. T-mobile exchanged my phone for a new one.
vaghotstuff said:
Easy FIX!!!!!
I took a can of compressed air and blew it through the top earpiece grill a few times and Voila, it works great now!!
I actually used a Old perfume can wich purfume was over and it was only pressing Gas OFF!!
Click to expand...
Click to collapse
This fixed for me too. But the sensors start acting up like every couple weeks and I'd have to blow air into the ear piece.
i9100 proximity sensor doesn't work
Hi to all!
I have the issue with proximity sensor and didn't manage to find a solution in other similar threads!
The matter is that it is always stay as Released.
In the same time in test screen (*#0*#) there are changing reading for PROXIMITY parameter from 2 up to 240 with no ADC parameter at all. Please look for screenshots. PROXIMITY parameter changes its value when I move my finger in front of the sensor, but as I can understand Android doesn't recognize it because of ADC absence.
Moreover I tried to change proximity sensor for working one (from another phone), but it shows the same as mine (with no ADC readings).
After all I think it is software problem, but I don't know how to solve it. I flashed different firmwares (now it is XWMSE NeatROM v.6.4), but nothing helped.
Please assist! Thanks!
TRY THIS
Sensor fix installed through a custom recovery I use when flashing aosp ROMs might work but I only use it on my Liquid Smooth updates might work for you. Just have a backup in case
BRANDENDEUCE said:
Sensor fix installed through a custom recovery I use when flashing aosp ROMs might work but I only use it on my Liquid Smooth updates might work for you. Just have a backup in case
Click to expand...
Click to collapse
Thanks for advise! I'll try it and revert!
BRANDENDEUCE said:
Sensor fix installed through a custom recovery I use when flashing aosp ROMs might work but I only use it on my Liquid Smooth updates might work for you. Just have a backup in case
Click to expand...
Click to collapse
It didn't help! After the fix is installed the sensor works at the same manner... Is it possible to try something else?
Hi all i have a DHD with a screwed failed Proximity sensor and was wondering if it can be replaced.
I have looked at all the videos of tear downs, done the calibration the works and Sensor doesn't work at all not even it its factory stock rom.
So how does one go about replacing that part if its possible.
I very much doubt it will be as simple as replacing the casing.
Please help.
hacktrix2006 said:
Hi all i have a DHD with a screwed failed Proximity sensor and was wondering if it can be replaced.
I have looked at all the videos of tear downs, done the calibration the works and Sensor doesn't work at all not even it its factory stock rom.
So how does one go about replacing that part if its possible.
I very much doubt it will be as simple as replacing the casing.
Please help.
Click to expand...
Click to collapse
I have the exact same problem, phone has been flawless for 2+ years. Was away on holiday recently and used the night clock mode, power attached with the phone in landscape mode - following morning, no more rotation, calibration tool doesn't register anything, other market proximity tools show a sensor present but don't function.
Cleaned the sensor with a fine brush, no change, re-flashed a couple of roms with full factory reset, no change.
I can only assume the sensor has failed - shame this phone has been excellent - especially with the dedicated ROM community behind it.
I am now facing a full tear down next to try and clean the sensor fully, although suspect this will make no difference.
Can the proximity sensor be sourced as a part, or does anyone have any other suggestions/ things to try?
UPDATE: Following the guide on this thread fixed it for me!
I first noticed it when the screen didn't black out during a call. Then I downloaded an app which checks if there is a proximity sensor and the distance it reports. According to the app, the last distance reported is 5 centimeters and it doesn't change at all when I obstruct the sensor. That makes me pretty sure that it stopped working. What can I do now?
Oliie23 said:
I first noticed it when the screen didn't black out during a call. Then I downloaded an app which checks if there is a proximity sensor and the distance it reports. According to the app, the last distance reported is 5 centimeters and it doesn't change at all when I obstruct the sensor. That makes me pretty sure that it stopped working. What can I do now?
Click to expand...
Click to collapse
If its anything like mine, you'll start getting some even weirder behavior. When I would answer a phone call (or place one), the proximity sensor wouldn't work and the phone would reboot itself within 5-10 seconds.
I downloaded an app called "Hardware Disabler" which allows you to disable the proximity sensor on the Gnex (its the one labeled 4-0044). It works for me...only annoyance is having to turn my screen off/on during phone calls manually. But, its better than having no phone (i.e. soft reboots).
Anyway, to answer your question, i'm not sure there's much you can do (other than disable). I've read that the proximity sensors on these GNex's are a little buggy.
My Nexus Reboot During Call once in day too !
maybe my reboot problem is Proximity sensor ?
change my simcard and factory reset not solve my problem .
I have had this issue. Do you use a ROM with the active display feature? A lot of ROMs have been including this lately. I feel like my issue started when they added that. It has a "Pocket Mode" option that uses the proximity sensor and I've always felt like it messed up my proximity sensor during calls. I never had reboots but the screen would flicker on and off during a call. Sometimes just staying on. I have turned Active display off all together and sometimes it will work right and sometimes it will flicker. But for me, it seems to have started when ROMs started including that feature.
I'm just gonna go ahead an suggest the obvious, flash another ROM. Even stock if you aren't running it just to get collective results, this way you can eliminate the ROM factor.
amir-kia said:
My Nexus Reboot During Call once in day too !
maybe my reboot problem is Proximity sensor ?
change my simcard and factory reset not solve my problem .
Click to expand...
Click to collapse
It sometimes does it for me too, but it's very very rare. Sometimes the phone just freezes during a call (when swipe to take the call).
iLeopard said:
I'm just gonna go ahead an suggest the obvious, flash another ROM. Even stock if you aren't running it just to get collective results, this way you can eliminate the ROM factor.
Click to expand...
Click to collapse
Can't speak for others, but I tried everything that could be tried. Flashed different Roms, kernels, and even went back to stock using the images provided by Google. Nothing fixed it until I realized it was a hardware issue. I haven't had a single problem since disabling that sensor.
EDIT: also, to clarify, it wasn't an intermittent problem for me. I could NEVER make/receive calls until I disabled that sensor.
Sent from my Galaxy Nexus using xda app-developers app
Flash Catalism rom and disable Proximity sensor solve my reboot incall problem !