Ever since I rooted my Droid incredible and started changing roms, the sensor to automatically shut off the screen when the phone is up to my ear hasn't worked. Auto brightness and everything else works as far as I can tell but during a call the screen will stay on until it times out and locks. To get back to the call screen or anything I have to unlock the phone again, is there anything or any suggestions on what to do about this?
Sent from my ADR6300 using XDA App
so the issue is that the backlight doesn't go off?
try going back to stock and see if that happens, or change to a different rom, see if issue persists. if it doesn't, then its a rom issue.
also, try cleaning your screen. maybe the proximity sensor is dirty/covered in acne medicine?
Related
Has anybody had an issue where when they press the power button, the screen will turn off for a moment, then come right back on? And if so, does anyone know a solution? I've looked around on the forums a bit, and its a problem on other phones where the screen has to be at at least 40% brightness, but it happens to me no matter how high or low the brightness setting is. Running ACS 1.0.2, but it has happened on other ROMS before, so i doubt it is a ROM issue.
I have had this happen too, but only in CM 7. And just figured it was because that rom is in the alpha stage right now. I have not had it happen in any other rom so far. When it was happening it was only some of the time. Was never able to figure out what the differences were when it would and wouldn't happen. Seemed like it was just random.
Sent from my SPH-D700 using XDA App
I've since found this happens very often when the brightness is up all the way, and the lower the brightness, the less it happens. Could this be a software problem?
I had this happen a few months ago. I wasn't sure what was causing it. At first it was turning on the lock sound, and the sound would play after the screen shuts off. Then the sound would kick the screen back on. I believe I changed ROM later and it never happened again. If you are on a custom ROM, maybe try reflashing?
I have had the exact same thing happen on 2 different Roms. Just wipe and flash and it fixes the problem.
BloodThirstyEmu said:
I have had the exact same thing happen on 2 different Roms. Just wipe and flash and it fixes the problem.
Click to expand...
Click to collapse
Unfortunately that only lessened it, not fixed it. It still happens enough that I leave the brightness down. Tried multiple times. :/
This still happens on a fresh stock install of EC05. Could this be a hardware issue that I should get checked out?
Proximity sensor kine of stopped working..
If I make a call and place the phone to my ear, the screen will turn turn off, but when the phone is pulled away it won't torn the screen back on.
This makes me believe is not a hardware issue just a little software conflict with maybe some app that maybe be solved by resetting the phone off but I don't want to do that.
Does anyone know which app I can clear off data/cache that may make this thing work again?
Note: I have used AndroidSensor and some other apps to test proximity ans light sensor and they don't seem to work, according to the app.
Thanks.
Edit: Never mind guys, I deleted the last 10 apps, rebooted and it came back to life.
Delete thread ......
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?
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 !
I've had my g3 for a couple days now but twice I've noticed the vibration will stop working. Everything is turned on for vibration but still no go. A reboot fixes everything. Anyone else seen this?
Sent from my LG-D851 using XDA Premium 4 mobile app
polo79 said:
I've had my g3 for a couple days now but twice I've noticed the vibration will stop working. Everything is turned on for vibration but still no go. A reboot fixes everything. Anyone else seen this?
Sent from my LG-D851 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've had the same thing happened to me twice. The only work around I know of is to reboot the phone. After a few times, I haven't had it happen again (fingers crossed).
Hopefully it stops then but I have a feeling it will come back
Sent from my LG-D851 using XDA Premium 4 mobile app
This happened to me once about 5 days ago. Thought it was just a fluke, but it happened again earlier today. After restarting, it happened again about 45 minutes after the restart... I'm already on my second G3... I don't want to have to exchange it again
Mine did this too
Sent from my LGLS990 using XDA Premium 4 mobile app
t1m1t said:
This happened to me once about 5 days ago. Thought it was just a fluke, but it happened again earlier today. After restarting, it happened again about 45 minutes after the restart... I'm already on my second G3... I don't want to have to exchange it again
Click to expand...
Click to collapse
I think it's safe to assume it is software related. If a reboot didn't fix it then I would think hardware.
Sent from my LG-D851 using XDA Premium 4 mobile app
Keeps happening to me also every few days, no idea why.
Happened to my D852. Likely a software issue. I doubt exchanging will do anything.
I haven't had this issue on either of my two G3's, but I'm just tossing some steps out there to see if it might resolve it without rebooting.
Did you try the notification panel button to put it into Vibrate then back to Sound to see if it forces the Vibrate again? Also pushing it into Vibrate causes the phone to Vibrate as you do it. If vibrates doing that, you can assume it's a software issue and not a hardware issue.
Also, in the Settings menu under Sound, did you try checking the Vibrate Strength menu? Perhaps moving those slides might jolt it back or reset it via software without you having to reset your phone.
Just some ideas to see if perhaps using the UI might awake the software settings without rebooting everything to fix it. :silly:
JustLok said:
I haven't had this issue on either of my two G3's, but I'm just tossing some steps out there to see if it might resolve it without rebooting.
Did you try the notification panel button to put it into Vibrate then back to Sound to see if it forces the Vibrate again? Also pushing it into Vibrate causes the phone to Vibrate as you do it. If vibrates doing that, you can assume it's a software issue and not a hardware issue.
Also, in the Settings menu under Sound, did you try checking the Vibrate Strength menu? Perhaps moving those slides might jolt it back or reset it via software without you having to reset your phone.
Just some ideas to see if perhaps using the UI might awake the software settings without rebooting everything to fix it. :silly:
Click to expand...
Click to collapse
Yep, I tried switching sound modes to quiet, to vibrate, to sound again; and I still can't get vibration to work until a proper reboot.
I have the same issue happening randomly. Has to be software related. Wouldn't stress much on it. I'm sure it will be fixed in a future update. Seems to be a global issue.
And now it happened to me =( I thought it was from deleting bloatware (Stock F400S 10k) but after restarting all work.... I'm thinking about selling G3 for Meizu MX4
JustLok said:
I haven't had this issue on either of my two G3's, but I'm just tossing some steps out there to see if it might resolve it without rebooting.
Did you try the notification panel button to put it into Vibrate then back to Sound to see if it forces the Vibrate again? Also pushing it into Vibrate causes the phone to Vibrate as you do it. If vibrates doing that, you can assume it's a software issue and not a hardware issue.
Also, in the Settings menu under Sound, did you try checking the Vibrate Strength menu? Perhaps moving those slides might jolt it back or reset it via software without you having to reset your phone.
Just some ideas to see if perhaps using the UI might awake the software settings without rebooting everything to fix it. :silly:
Click to expand...
Click to collapse
I have had this happen once a day at least for the last few days.. A reboot does fix it.. But that doesn't seem to be a solution in the long term to me. I tried the messing with the sounds from the settings menu as well as trying different vibration patterns nothing works.. Its driving me nuts.