Hi,
since 2 months ago, i meet an issue which is kind of boring.
I have the ambiant display with the tap to wake mode ON and the fingerprint sensor activated.
At the begenning of my use, i have not met any issue : ambiant display was functional (i.e written informations on a black screen).
Now, when i wake up the screen with a double tap to wake gesture , informations are stile written but, this time, on a grey flickering/flashing screen (kind of stobe ligh effect). At the moment i touch the fingerprint sensor, it stops to be flashing grey and return to normal black.
Does someone have any idea of this issue? I am hesitating to proceed to a factory reset in order to see if it solves it.
Thanks in advance for your comments.
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!
One of the big issues I have found, mainly with CM based ROMS, is that the option to prevent accidental unlocking seems to be missing/unavailable.
I've been testing various apps and utilities that monitor the proximity sensor, but there is one big issue - they monitor for screen on, but it seems in CM12.1 that the monitoring app doesn't work or get a screen on signal when you're using a lockscreen.
So the solution is not to check for screen on, but check for screen unlock.
I have a TASKER profile set up as follows:
If screen unlocked and proximity sensor on, then turn the screen off.
Works really simply. cover the proximity sensor with a bit of cloth or something and test it - if you double-tap the screen on, or it wakes due to a notification, the screen still goes on. But any subsequent action, eg slide to unlock or click on a notification, triggers the screen unlock flag, and this then checks to see if the proximity sensor is covered, and if it does, it turns the screen off again.
I CAN POST SCREENSHOTS IF ANYONE WANTS FURTHER INFO - BUT I'D SUGGEST GIVING TASKER A GO AND A PLAY ANYWAY, IT'S A BRILLIANT APP.
I'm not sure if i'm posting this in the right place but couldn't find any other more appropriate location. I'm running Oxygen 9.0 build A6013_34_181001 and I've already noticed a few bugs.
I have my phone set to use fingerprint unlock and pattern unlock. Pattern lock is configured such that the pattern line is NOT displayed when I enter it. This works fine, except after a reboot. Upon rebooting the phone I'm prompted for my pattern unlock, and the pattern is displayed when I enter it. After this one instance, the pattern display is correct and consistent with my setting. Subsequent pattern inputs don't display the line, it's just the first one after boot.
I also noticed a strange issue with the fingerprint unlock. When the screen is off and I double tap to turn on the ambient display, normally I put my finger on the fingerprint sensor and the display brightness increases. I'm assuming this is to provide illumination for the fingerprint sensor to function and get a good image of the fingerprint. Sometimes when I put my finger over the sensor the screen doesn't brighten, and the sensor can't read my fingerprint. I know it's detecting my fingerprint and trying to read it since I get the animation on the display around the sensor, the screen just doesn't brighten and the sensor can't read my fingerprint.
There have also been some instances where the double tap on the screen doesn't turn the ambient display on. I can use the power button to wake the phone, and that works fine, but periodically the double tap just won't turn the ambient display on. I like this feature so I can quickly check if there are any pending notifications without having to press any buttons, most often when my phone is lying on my desk.
I haven't been on any of the OnePlus forums yet. Do they have a forum for bug submittals?
I would like to tell you that it often happens when I pull the S10+ out of my pocket, so the display is not in "stand by" mode, it is not always on display, but it is slightly backlit. Classically, the display is black and shines only AOD. But when I pull it out of my pocket, instead of the classic AOD it shines for hours and even seconds and after them you can see the wallpaper of the locked display and it is slightly backlit. The display itself is dark, but it is slightly backlit and you can see the wallpaper. With the classic AOD, the display is completely black and I have set only hours, minutes, date and battery, and of course, the notification, if any. Does anyone know what it is, whether it can be turned off so that the display does not illuminate the pocket?
I have accidental touch protection on.
As far as I know proximity sensor is only accessible when you are in call, that's why other apps can't access it.
Samsung should remedy this. Because I always change the Always On setting in my pocket. Specifically - Rotation and Brightness Always On.
EDIT: It happens most when I tap wake-up.
Does anyone else has a problem with ambient always on display not working? Most of the time it is there, but even if I turn off the Scheduler, sometimes off for hours, just the black screen. 10.3.10 MIUI
Yes, the same issue for me. Little annoying, but I hope it will be fixed in the next update. Maybe I will for now just turn off the always-on display.
You should read the description
Could you be more specific please?
"To reduce power consumption, items won't be displayed in the following situations:
1. When your device lies in dark for a long time.
2. When DND mode is on"
Haha, didn't saw that, but still, my room wasn't dark at all and it still went off. For now I have just disabled that option, and if that is only big bug I will be super happy.