(I posted this on the Lenovo site as well.)
Just wanted to report this happening on my xt1644 (US Retail version) G4+. I've had the device for roughly 6 months without this happening on 6.0.1.
When I double flip and occasionally when I use the icon to activate the stock camera, the display screen darkens to a point where the subject of what I'm shooting can't be seen.
I'll point the camera to a bright light source (like a light bulb or sky) and the screen brightens up. Also, if I close the camera app and restart it, it sometimes "fixes" itself.
Anyone else experiencing this? Perhaps this problem/issue has to do with the light sensor(s) on the phone? Just wondering.
Asking the wisdom of the forum and admin.
Thank you.
have you tried with different camera app ??
try and state results
Sent from my Moto G (4) using Tapatalk
dhyamato said:
When I double flip and occasionally when I use the icon to activate the stock camera, the display screen darkens to a point where the subject of what I'm shooting can't be seen.
Click to expand...
Click to collapse
If this happens with other apps, it could point directly to a problem with the ambient light sensor.
If this happens with only this app, it could still point to an issue with the sensor, or the app.
Check if this issue persists with adaptive display disabled. If so, then the problem is with the app. If not, chances are that the light sensor has issues.
zeomal said:
If this happens with other apps, it could point directly to a problem with the ambient light sensor.
If this happens with only this app, it could still point to an issue with the sensor, or the app.
Check if this issue persists with adaptive display disabled. If so, then the problem is with the app. If not, chances are that the light sensor has issues.
Click to expand...
Click to collapse
I haven't seen this happen while in other apps. It just occurs once in a while when I double wrist flip the phone to activate the stock camera. It doesn't happen all the time.
I'll try to isolate other elements that I may be overlooking.
Related
Just as the title says-
I am not able to locate the light ambient sensor on my A500 tab- My previous A500 got replaced by acer because the speakers were defective in some way-
I have read that the light sensor is located below the volume rocker and rotation switch on the black glass and can be seen under bright light- i tried every way to find it no success.
I tried "proximityscreenoff" and "sensorlist" from the market. Both of the freewares listed an ambient light sensor on my device as -"Lite-on al3000a Ambient Light sensor"-
BOTH THE APPS COULD NOT GET ANY DATA FROM THE SENSORS :O-
DO we even have a sensor? or is it just me without it?
Can someone please use the apps and tell me if any data is being collected from the sensors?
Highly appreciated- thanks you
I tried with Sensor List and it does indeed show up the sensor, but doesn't seem to be getting any data from it. So it's not just your tablet.
Same thing with "AndroSensor", it shows it but no data change in it either. Hopefully we can figure out what the issues is? Are both of you using the factory install rom? Or a rooted one with a tweaked kernel?
sda.171 said:
Just as the title says-
I am not able to locate the light ambient sensor on my A500 tab- My previous A500 got replaced by acer because the speakers were defective in some way-
I have read that the light sensor is located below the volume rocker and rotation switch on the black glass and can be seen under bright light- i tried every way to find it no success.
I tried "proximityscreenoff" and "sensorlist" from the market. Both of the freewares listed an ambient light sensor on my device as -"Lite-on al3000a Ambient Light sensor"-
BOTH THE APPS COULD NOT GET ANY DATA FROM THE SENSORS :O-
DO we even have a sensor? or is it just me without it?
Can someone please use the apps and tell me if any data is being collected from the sensors?
Highly appreciated- thanks you
Click to expand...
Click to collapse
I got Sensorlist and tried it and I do get data from it.
xhz/xxxx or xxxxxms and a red line. The upper limit is 227 and lower limit is -227 and the red checked number changes. It's nowhere as quickscrolling as the other sensors but I get a jagged red line moving across.
okay guyz i think i figured this whole thing out most probably-
I just came back from this electronic store, i closely examined the iconia on display- a500 - noticed the black glass under the volume rocker and rotation lock and THE LIGHT SENSOR WAS THERE! :O - looking like just any ordinary light sensor-
This made me come up to the following conclusions- since i have had another iconia before i returned it for warranty- i was able to identify the following differences-
1st variant-model
Light sensor present
Mic volume low
Volume locker button hard to push
Power button sorta pushed inside
2nd variant model -( the one i currently have)
Light sensor absent? Or hidden under black glass? (Manufacturing defect?)
Loose rotation lock (hardware) toggle
Mic volume high (as in proper)
-(i faced these additional problems)-> glass over the camera came off and the glossy label on the side slipped out.
So if u have the first variant, the one i previously had and the one i examined in the shop today- that should give u data from the light sensor, and the 2nd variant with hidden/absent light sensor won`t.
These are my findings. Feel free to point out and discuss-
What should we do? I m considering a second replacement now -_____-
With AndroSensor app open, try to put some direct light above the sensor and see if it shows some readings. I noticed that the sensor is in a sort of sleep status until it sees some light; after then it kinda wakes up and works properly.
I appear to have what you call the second variant model. I just checked with Androsensor, and the light sensor does appear to be present beneath the black glass, just under the volume up rocker. I agree it does appear to sleep until it senses a light source.
cm0901 said:
With AndroSensor app open, try to put some direct light above the sensor and see if it shows some readings. I noticed that the sensor is in a sort of sleep status until it sees some light; after then it kinda wakes up and works properly.
Click to expand...
Click to collapse
I just downloaded andro sensor-
Under light sensor it sed-waiting for event-
I took my hd2, turned on the flash! Pointed it right above the sensor and no response, it just kept saying waiting for event- so does this mean i have a defective sensor?
Can this be a kernel/rom related issue?
Pls someone try this and let us all noe.
Thanks
It's a long shot but you might attempt flipping the check mark a few times under the brightness setting and "auto adjust" as that probably toggles the sensor as well, though these apps are supposed to do it. Or close and start the app a few times and then check the sensor. I don't know what activates it but I can confirm that it has some kind of threshold where it sleeps or isn't active and another where it is, so you might want to try various things to, as others have mentioned, wake it up.
Are you using any ROMS by any chance or are you on stock? Have you done any sort of modification of the system - rooted and removed things or replaced kernels, etc?
If you are on a ROM or have done any modifications, you may want to try going back to full stock 3.2 or 3.1 and seeing if that helps before you decide it's actually defective.
Just double checked mine running a 3.2 rooted with thor's kernel. The sensor is working fine. But i did have to uncheck the box for the auto screen brightness to wake it up. Then i used a led maglight on the senor.
Readings from Androsensor:
Light (0.5mA)
55.0 lux
With the maglight cut on it.
65790.0 lux.
Please note with the maglight cut on you can see the light sensor hole then.
KILLER_K said:
Just double checked mine running a 3.2 rooted with thor's kernel. The sensor is working fine. But i did have to uncheck the box for the auto screen brightness to wake it up. Then i used a led maglight on the senor.
Readings from Androsensor:
Light (0.5mA)
55.0 lux
With the maglight cut on it.
65790.0 lux.
Please note with the maglight cut on you can see the light sensor hole then.
Click to expand...
Click to collapse
Same as Killer, seems to be working, rooted 3.2, couldnt see until bright light on it.
Anyone have any idea where the mic(s) are, not really important just wanna know which end to scream into when doing voice search
Mic is located directly in the top center of the front face, in the space between the glass and the bezel. You should be able to see it with just a small amount of light shining on it.
FINALLY!
after various non stop auto brightness toggle on and offs - waiting for event went and 1 lux came xD - i shone light the reading increased - and stopped working agen :|
I dunnu maybe the apps are not fully compatible.
I can say it is working because i changed my brightness to full manually and then turned auto on and the brightness level set itself automatically.
So will we have to wake up the sensor from a state of sleep all the time or is it just for the apps xP - last confusion.
Thanks every1 for ur responses, the mystery is finally coming to an end xD!
The N10 auto-brightness feature doesn't work right, as everyone knows. It randomly dims and brightens in an annoying way. I'd read it was a software issue - something to do with JB 4.2 - so I tried two different auto-brightness apps from Google Play, both of which get good ratings, and to my surprise I had the same problem with both of them. When the brightness depends on my N10's light sensor, the screen keeps dimming and brightening randomly. The app I have installed (but disabled) now is "Custom Auto Brightness". I wish I could use it because it looks very good.
The fact that the problem appears regardless of the software suggests to me that the problem is in the hardware - there's something wrong with the data put out by the light sensor. Does anyone have any info or insight about this? A workaround would be so nice.
Hello to all,
I have a strange behavior with my auto brightness. It sometimes will slightly increase then decrease again quite quickly. This happens not all of the time but regularly. It even happens in dark conditions without any varying lighting conditions that could cause this.
My phone has already been reset a number of times so am wondering if it is software related or hardware related.
Anyone else notice this?
It's a known issue (known by us, not ZTE, apparently). I believe the light sensor reads the light from the screen itself, bouncing on you, then corrects for that, the light changes accordingly and it starts over again
0Kajuna0 said:
It's a known issue (known by us, not ZTE, apparently). I believe the light sensor reads the light from the screen itself, bouncing on you, then corrects for that, the light changes accordingly and it starts over again
Click to expand...
Click to collapse
Thanks for that. It could indeed explain it.
0Kajuna0 said:
It's a known issue (known by us, not ZTE, apparently). I believe the light sensor reads the light from the screen itself, bouncing on you, then corrects for that, the light changes accordingly and it starts over again
Click to expand...
Click to collapse
I picked an Axon 7 up today and I too notice strange behaviour by the light sensor.
I've tried searching the forums and Google for this issue and I could only find this thread.
Is the issue hardware related? Do you think it could get worse over time? I'd love to read more about these issues but am having trouble finding anything about it.
Edit: symptom is an aggressively jumping auto brightness bar. The brightness is occasionally lowered and raised in rapid succession, even in stable lighting conditions.
EditEdit: I've not updated the phone since I received it. It's on 6.x.x. Could there be a recent update that tackles these issues, or makes them more bearable?
Maybe it's solved by turning off assertive display in settings. I haven't noticed this issue before on mine but a lot of other issues e.g. fingerprint sensor acting weird and giving continuous "finger moved too fast" or "partial fingerprint detected,please try again" errors (but when it works, it works really fast) that most of them were related to software. The stock ROM is quite buggy though. (Mine is Chinese A2017)
Hi guys, i have a big problem on my phone Mi A1, is the always active proximity sensor.... Drain battery, does anyone find my same problem? Take a test with a camera, you can not see with the naked eye! Thanks
I have attached the video!!
BUG OR FAULTY?
my video, search on youtube: Proximity Sensor always on Xiaomi Mi A1 BUG?
THANKS
https://www.youtube.com/watch?v=zdONFH0B6xg
UPDATE VIDEO: https://www.youtube.com/watch?v=H09kbi4-DCM
Mr.Oscar said:
Hi guys, i have a big problem on my phone Mi A1, is the always active proximity sensor.... Drain battery, does anyone find my same problem? Take a test with a camera, you can not see with the naked eye! Thanks
I have attached the video!!
BUG OR FAULTY?
my video, search on youtube: Proximity Sensor always on Xiaomi Mi A1 BUG?
THANKS
https://www.youtube.com/watch?v=zdONFH0B6xg
Click to expand...
Click to collapse
Unfortunately it looks like a bug in newest February stable stock ROM.....
This is how it looks like on my phone:
https://www.youtube.com/watch?v=0SO34GCD8Pg
ves626 said:
Unfortunately it looks like a bug in newest February stable stock ROM.....
This is how it looks like on my phone:
https://www.youtube.com/watch?v=0SO34GCD8Pg
Click to expand...
Click to collapse
Thanks, i have oreo patch january and on my xiaomi, when the screen is off, stops flashing
Yep! It is blinking when the screen is on. (I'm on February Patch.)
I'm on February patch and not facing this behaviour. Maybe you have an app making phone work like this? Hope you solve it.
carmeloamg said:
I'm on February patch and not facing this behaviour. Maybe you have an app making phone work like this? Hope you solve it.
Click to expand...
Click to collapse
No, I don't have any application which does this. Check it by a camera ( I think it is infrared) and when the screen is ON.
My proximity sensor test
Same here also
Mr.Oscar said:
Hi guys, i have a big problem on my phone Mi A1, is the always active proximity sensor.... Drain battery, does anyone find my same problem? Take a test with a camera, you can not see with the naked eye! Thanks
I have attached the video!!
BUG OR FAULTY?
Click to expand...
Click to collapse
I think it's a bug in new February Patch Stable Update
First of all, I can't reproduce it (used my work iPhone's camera, and yes iPhone sucks but it's for my job, no choice here ).
Second, are you sure it's a bug? Did you do similar check before Feb update?
I'm not a pro of phone hardware, but it seems normal to me that the sensor will be always working. I'm even using an app to wake the phone with the sensor (https://play.google.com/store/apps/details?id=com.jarsilio.android.waveup) so the sensor is working all the time, even with screen off.
It's not a bug, it's the same for a lot of phones, don't worry
N1ck474 said:
It's not a bug, it's the same for a lot of phones, don't worry
Click to expand...
Click to collapse
thanks, many mi1 owners do not have this bug
BtB said:
First of all, I can't reproduce it (used my work iPhone's camera, and yes iPhone sucks but it's for my job, no choice here ).
Second, are you sure it's a bug? Did you do similar check before Feb update?
I'm not a pro of phone hardware, but it seems normal to me that the sensor will be always working. I'm even using an app to wake the phone with the sensor (https://play.google.com/store/apps/details?id=com.jarsilio.android.waveup) so the sensor is working all the time, even with screen off.
Click to expand...
Click to collapse
thanks bro, I'm not sure it's a bug, however the sensor should only be activated for calls
It's not a bug. The proximity sensor is also used for auto brightness control.
When the proximity sensor is tripped, values from the light sensor is ignored, which means that screen brightness won't change even when the light sensor detects changes in ambient light.
This is useful for e.g. when you play a game or watching a movie in landscape and your hand covers the light sensor. The screen won't go dark, but stays at the same brightness. Without the proximity sensor activated, your screen would go dark every time you accidentally cover the light sensor with your hand.
Try turning off adaptive brightness and see if it's still on. It shouldn't be necessary to have the proximity sensor on all the time if you set the screen to a fixed brightness.
quetzalcoatl2435 said:
It's not a bug. The proximity sensor is also used for auto brightness control.
When the proximity sensor is tripped, values from the light sensor is ignored, which means that screen brightness won't change even when the light sensor detects changes in ambient light.
This is useful for e.g. when you play a game or watching a movie in landscape and your hand covers the light sensor. The screen won't go dark, but stays at the same brightness. Without the proximity sensor activated, your screen would go dark every time you accidentally cover the light sensor with your hand.
Try turning off adaptive brightness and see if it's still on. It shouldn't be necessary to have the proximity sensor on all the time if you set the screen to a fixed brightness.
Click to expand...
Click to collapse
Thanks for reply, I deactivated ambient display, and automatic brightness.
But it still does!
If can help someone I mock value with sensor disable xposed module.
My set is 2.5 (half of total value)
But my phone is a redmi 4a
#EDIT
Did one more test, my Mi A2 don't even use the proximity sensor, it uses only the front camera/light sensor to turn off the screen.
#EDIT
Hello, friends, everyone is well know about the problem supposedly about the proximity sensor, that is inaccurate when playing whatsapp sounds, in calls, messenger and etc. But, after several tests, calibrations and apps, today I figured out the REAL problem.
Today I tried to hear a whatsapp audio outside, with sun, and everytime I tried, the screen went off. So, I tried to calibrate the proximity sensor with the app, and the sensor was activated always, covering it or not.
Then I went to *#*#8464#*#* and instead of calibrate the proximity sensor, I calibrated the LIGHT sensor. For my surprise, it worked. The light sensor comes from the front camera, so, for some reason, on Oreo and Pie, don't know if it's Xiaomi software problem, or Google problem, but the Android is using the light sensor together with proximity sensor to turn screen off, or not. And because of this, bad programming or not, there is this problem. Even in other Xiaomi phones I heard about this problem, like Redmi 7.
Also, that's justify my other point, about Adaptive Brightness, if it's on, almost solving this problem.
Don't post here go to the Q&A section!
fir1996 said:
Don't post here go to the Q&A section!
Click to expand...
Click to collapse
Oh, sorry, tought that would be a discussion.
If any mod could move for me, I appreciate that.