hi,
I somehow noticed how when I took the phone away from my ear near my face during a call the screen was still locked, so i ran the lightsensor test and it kept going from 0 to 3.xxxxxxx on and off reporting Dark, it is late night here but the lights are on, i then put it near my monitor, still "dark"
I then finally shone a torch on the sensor and it reported normal after a few seconds!!?
Is there a way to re calibrate it, i'm guessing it does sense light but not correctly?
Thanks so much
oops!
I ran a test again today morning, but i exposed the thing to the sun near at my Window and it shows bright. however, i still think the light sensor is a tad bit un sensitive, or is it acutally being super smart and sensing ambience around my room??
Related
I have been noticing that my auto brightness doesn't work like it did when I first got my phone a few months ago.
Back then it seemed like it changed brightness after a few seconds when it should.
Nowadays it doesn't seem to do that anymore.
Now if I hold my phone close to a bright light, hit the power button and unlock the phone, the screen is very bright, as it should. When I hold my phone in a dark place, it doesn't adjust the brightness. It keeps being very bright.
BUT, if I hold my phone in a dark place and hit the power button and unlock the phone, it's dark, but when I move my phone to a brighter location it does make the screen brighter.
I first thought this had to do with CM, but now on stock froyo it does the same thing.
Is this normal, and am I just mistaken? And should the phone adjust the brightness when I hold my thumb on the sensor thats just right under the power button on the front of the phone (I expect the screen to be less bright)? Because it doesn't do that.
Thanks in advance.
No it's not normal, mine reacts to changes in ambient light in a second or 2 (FRF50), just like yours used to.
When I cover the light sensor with my thumb, the screen dims right down.
Thanks for your reply.
Is there anything I can do to check why this doesn't happen on my phone?
Can I perform a check on the status of my sensor, on it's behavior?
And are there any known reasons why this could happen?
Thanks in advance.
This exact issue is happening with me ever since I updated to 2.2. It worked perfectly before but now I notice that once the screen adjusts to maximum brightness in a well lit area, it never dims....don't know what the problem is. But I hope there is a solution.
Good to hear I'm not the only one with problem, that gives me hope this might be a software issue rather than a non-working sensor.
Rusty! said:
No it's not normal, mine reacts to changes in ambient light in a second or 2 (FRF50), just like yours used to.
When I cover the light sensor with my thumb, the screen dims right down.
Click to expand...
Click to collapse
Actually I may have to take this back, in retrospect, the dimming actually could have been the screen timing out.
When covering the sensor with my thumb and not having the screen set to 15secs, it doesn't dim until I lock/unlock the screen.
Reading on another forum this is by design rather than a flaw, as people complained the screen would fade in and out in certain light conditions... now it can't.
Ah, okay. Good to hear.
Thanks again, Rusty.
froyo seems to fix the autobrightness for me, at least now i can see the screen brightness is changing according to lighting condition, previously i don't notice it (using cyan ROM prior to froyo).
You must have ROOT to complete this process. I have been having issues with my light and proxy sensor ever since I had gone S-Off on the phone.. well tonight i decided to do some research and see if I could figure it out. I love having S2W and DT2W but without the pocket protection, you tend to turn the screen on alot when you dont want to, well some how the calibration gets changed.
there are two apps on the Play Store to help get you set up
the first will be your testing app, its called - Android Sensor Box
and the second is called - Rezound Prox Sensor Calibration
when i used the Android Sensor Box, my light sensor would never go over 40 luxes and drop to 10 luxes when I covered the sensor. and my prox sensor always said "NEAR" and would never change
Now go to the Prox Sensor Calibration app, my stock settings were 16 low and 24 high (I think), after playing around with it, I found a great sweet spot set at 40 low and 60 high, but feel free to play and see how it works for you. when done, click on "Set on Boot" and reboot the phone.
When my phone rebooted, I went back to the Sensor Box app and just under normal light conditions my light sensor was at 160 luxes and as i slowly covered the sensor it gradually went down. then i checked my prox sensor and it worked perfectly and would change from "NEAR" to "FAR" after my hand moved farther then 2 inches away. and this fixed my S2W function with working pocket protection.
I hope my frustration will help someone else out with the same issues
My only real big issue with this phone is that the proximity sensor doesn't work unless I squeeze it between my fingers. In dark lighting it's the only way to turn on the screen. Also,it's the only way to get the screen to turn back on.
I downloaded an app to test the sensor ans it says it's near even if there's nothing in front of it. But after I squeeze it the test shows that it's far
I use my phone regularly for navigation with waze. One thing that is really annoys me is that when it's really sunny and bright outside, the phone display dims down to minimum brightness level. Brightness doesn't change even if I touched the screen. If I cover up the (brightness sensor?) on the top left part of the phone, the screen is bright again.. It seems like diffuse sunlight is causing some sort of weird thing with that sensor. I tried to point a flashlight directly on the sensor and the display brightens like it should. Only when there is diffuse sunlight, it does this weird behavior.
Anyone else seen this?
EDIT: I am on 5.1 leaked soak test. I am pretty sure I had the same thing happen when on stock 5.0
I've had that happen on other phones by different manufacturers as well. Very annoying, the only fix I had was to just disable auto brightness.
Such a good feature, but haphazardly implemented it seems.
Sent from my Moto X
this have been issue for Pixel devices, proximity sensor not working properly.
Mine's on same boat, proximity sensor always read something blocks (distance 0cm).
actually it does not hurt for most of time, but only 2 things.
AOD turned off, i prefer AOD is always on..
display off when calling.
There is workaround.. just press the screen, the proximity area, then it works normally for a while.
I kept doing that, and it fixed for couple of months in last winter.
It started happening again when I stayed in Desert area, 90F over night.
looks like proximity sensor should be stuck on some "right" place, but glue does not hold it tight?
I donno... anyways, it happened again when weather comes warmer.
so, I was looking for a solution, just disable the proximity sensor, or make it always 5cm reading.
nothing works so far!
first trial. use "disable sensors" in developer option.
I created a tasker command for toggle that function --> this works. but...
it disables mic as well, cannot use during phone call.
for AOD, that command does not work when screen is off. command does not go through for AOD.
second trial. use disable sensor addon for xposed (now LSPOSED with magisk)
not working on Android 13 and 12.
Looks like it worked on Android 8 or 9? not an option for pixel 5.
I gave up at this point.
Pixel 5 is great phone, light and small enough, easy to carry. performance is not great but ok for me. battery life is also ok.
easy to unlock bootloader, flip to other custom roms..
because of only for this small proximity sensor, this is hard to use for me..
Is there any way to disable it?
see this thread for a general idea of what to do.
[Q] Disable proximity sensor via terminal emulator
Hi @ all, I have that following problem: My phones display turns off automatically while im receiving or doing a call. My proximity sensor is broken and i would like disable it and i found a good solution here in this formus...
forum.xda-developers.com
that is for a HTC phone and is a 10 year old thread but I think if you can identify the correct device you can use root to effectively prevent it from changing state.
Maybe not. its been a while since I messed with Android Internals.
Worth a try.
I recently got a refurbished Pixel 5 and had this same issue, a few searches on the internet and I learned about the screen gap fiasco. If I'm not wrong isn't the reason behind the proximity issue this same screen gap on top left. As far as mine is concerned, I heated it up a little to loosen the adhesive, covered it in a soft cloth and then applied a plastic clip I had lying around on top left for compression. I left it overnight and voila the sensor works perfectly now. Also I have a relatively tight case on.