I'm having some weird things happen with the iris scanner. The phone will be sitting on my desk and randomly the screen lights up and goes to the iris screen with the red light on. Anyone else seeing this? Happens 1-2x a day. I'm thinking if this is something to do with some sort of movement sensor, it could be causing my battery drain since I see very high sensor usage in BBS.
Try disabling the iris scanner and see if your screen still randomly turns on. You may just have some other issue causing your screen to turn on, thus causing your iris scanner to start running since it's on the lock screen.
Outbreak444 said:
Try disabling the iris scanner and see if your screen still randomly turns on. You may just have some other issue causing your screen to turn on, thus causing your iris scanner to start running since it's on the lock screen.
Click to expand...
Click to collapse
This. Because my phone had same issue and was a defect in the home button. Exchanged the phone and its gone now. Does it also vibrate like pressing the homebutton?
Related
Hi All,
Not sure if this a bug or not, but if you are touching the screen (While off) and turn it on, the touch is broken. its like the calibration is completely messed up and the touch is unusable/uncontrollable. I can easily fix by Turning the screen off and on again not touch but it is a bit annoying.
Is this the way that android works, does it calibrate the screen touch every time you turn it on?
Does anyone know if i can fix this is any way?
I get this issue 2-3 times a day, it's not always from touching the screen though, for me it just seems to happen randomly. I wasn't able to reproduce it by touching the screen beforehand.
Hi All
My new 6P arrived and my favourite feature is the Imprint sensor to turn on screen and simultaneously lock it. Having my phone be alive when i pick it up and screen off when I don't is a real feature - what I was wondering is could we use the Imprint sensor to get around the problem where you're browsing and your screen turns off due to display time out. If it were possible to have the imprint act as a "keep the screen on, I'm using it" button it would be fantastic.
Anyone know if this is possible?
Ric
That's exactly how mine works. Finger on the Imprint and the phone comes on and unlocks. If the screen times out and goes off, putting finger back on the imprint switches it back on unlocked where it was.
400ixl said:
That's exactly how mine works. Finger on the Imprint and the phone comes on and unlocks. If the screen times out and goes off, putting finger back on the imprint switches it back on unlocked where it was.
Click to expand...
Click to collapse
It does wake up when you touch the Imprint sensor, but it I'm reading a doc and don't want the screen to time out whilst I'm doing it, keeping my finger on the sensor doesn't keep the screen on, which is what I'm after...
Maybe "Stay Alive" or a similar app from the play store might help? I haven't used it for a while but if I remember correctly, you can select apps that when active, will keep the screen from turning off.
Stay Alive Link: https://play.google.com/store/apps/details?id=com.synetics.stay.alive
When I make phone calls the screen stays on when I put it to my ear. This results in touch presses ranging from muting the call, typing digits or really doing anything through the phones interface. Bloody infuriating.
It's very annoying and it shouldn't be doing it. I say shouldn't because it doesn't always; some times a reboot will seem to fix the problem but that seems to depend on how soon after the reboot a call is made/answered.
I have used AndroSensor to test the sensors (accelerometer, light, proximity etc) and they all seem to be registering values. For proximity, putting my finger over the sensor can result in a drop in value to 0.4in or 1.2in. This could be the cause of the issue as 1.2in is far to high a reading to correctly disable the screen afaik.
Possibly related; when the screen stays on, and the call is long I believe the normal screen timeout will kick in and the screen goes blank, meaning to hangup I have to wake the phone and unlock etc.
My questions are;
Has anyone else experience this?
Is it a setting, bug or faulty hardware?
Can someone else perform the same tests with AndroSensor to see if their results are the same as mine?
Moto X Play XT1562
Android 6.0.1
Build MPD24.107-52
Do you have screen protector applied?
Sent from my XT1562 using XDA-Developers mobile app
pijes said:
Do you have screen protector applied?
Sent from my XT1562 using XDA-Developers mobile app
Click to expand...
Click to collapse
Nope.
Did you ever get this sorted out? I'm having the same issue, but the proximity sensor numbers don't change at all. No screen protector, stock unrooted device on Marshmallow.
Same Problem
Actually even i have been having the same problem. It is not smethin that has been there forever it has started in the past few weeks.
I had this problem once, but a simple restart had solved it.
I bought a used V20 with a defective screen. I change it, everything work for fine, but i notice a strange behaviour with the second screen.
The second screen is always on and i can unlock it by only touching the finger print sensor. BUT at night (or in the dark), the second screen turn off and i need to press 2 times on the power button to wake the phone.
The Knock On feature doesn't work too in the dark.
The light sensor seems to work correctly.
I would love to post a video but i can't......
This is an issue or it is normal ??
Thanks for your help !
Sounds like Doze.
I don't find anything related to Doze or "standby" about this screen.
check "daily timeout" on Show when main screen off. Seem u turn this function on at night
David_26 said:
I bought a used V20 with a defective screen. I change it, everything work for fine, but i notice a strange behaviour with the second screen.
The second screen is always on and i can unlock it by only touching the finger print sensor. BUT at night (or in the dark), the second screen turn off and i need to press 2 times on the power button to wake the phone.
The Knock On feature doesn't work too in the dark.
The light sensor seems to work correctly.
I would love to post a video but i can't......
This is an issue or it is normal ??
Thanks for your help !
Click to expand...
Click to collapse
thophan1975 said:
check "daily timeout" on Show when main screen off. Seem u turn this function on at night
Click to expand...
Click to collapse
Don't seems to change anything
Could it me the last security update ??
I reset the phone today and same "issue"
David_26 said:
Don't seems to change anything
Could it me the last security update ??
I reset the phone today and same "issue"
Click to expand...
Click to collapse
Sounds like there is an issue with the proximity sensor (not light sensor).
It's setup to turn the second screen off as well as disable knock on if the phone is in your pocket. Even during daylight hours if you put your finger within an inch of the sensor when the main screen is off, it should trigger it.
It seems your sensor may just be messed up.
David_26 said:
Don't seems to change anything
Could it me the last security update ??
I reset the phone today and same "issue"
Click to expand...
Click to collapse
There are a few apps on the play store you can try to fix it if you are rooted. You could also try a sensor app to see if the proximity sensor is showing feedback properly although you might need to be rooted for the apps to show the proximity sensor properly (not sure). My note 4 had a hardware test in the service menu not sure how to do it on V20 though.
Same Issue
Edit: Resolved the issue. Please read this post. There is a small rubber gasket-type thing that sits in the hole of the phone's frame where the proximity sensor is positioned. That rubber gasket was not included with my replacement screen. I pulled the rubber piece out of my original, broken screen, and installed it into my replacement screen. I am no longer having issues with the phone in the dark.
I am experiencing the same issue. I have a T-Mobile LG v20 (H918) and I cracked the screen last week. I ordered a replacement LCD assembly and installed it myself. Everything works fine during the day or in a well lit room, but at night, in a dark room, I experience all of the issues you are reporting. I am finding other posts online with our same issue, but as of yet, no resolution.
Even though the second screen is set to always be on, at night, in a dark room, it turns off almost immediately after locking the phone. It is almost as if the phone is in a "deep sleep" or something, because the following also occurs:
Knock On will not wake the phone
Fingerprint sensor will not wake the phone
Even connecting to the phone via AirDroid / AirMirror the phone doesn't wake
Need to press the power button multiple times to wake phone
Providing a light source immediately turns on second screen and resolves all issues
I picked up this phone on my local craigslist late last week (at $15, I could not resist), unlocked it, and have been using it. When compared to my moto Z play, I have to hold the fingerprint scanner longer to turn the phone on or off which for some reason is very frustrating. I do not believe this is a hardware limitation as the fingerprint response is instant if I turn the device on to my lock screen and then touch the fingerprint scanner.
Does anyone know if it is possible to correct this? At the moment, I have to touch the scanner for ~1 second before it will turn on/off my phone. If it were possible to change this to ~0.5 seconds, I would be a happy camper.
skotseno said:
I picked up this phone on my local craigslist late last week (at $15, I could not resist), unlocked it, and have been using it. When compared to my moto Z play, I have to hold the fingerprint scanner longer to turn the phone on or off which for some reason is very frustrating. I do not believe this is a hardware limitation as the fingerprint response is instant if I turn the device on to my lock screen and then touch the fingerprint scanner.
Does anyone know if it is possible to correct this? At the moment, I have to touch the scanner for ~1 second before it will turn on/off my phone. If it were possible to change this to ~0.5 seconds, I would be a happy camper.
Click to expand...
Click to collapse
Are you running stock software? If so, I'd try erasing and re learning your finger prints. I got an E4 for my daughter to use on WiFi - FP sensor is snappier and more accurate than my MZP. If that doesn't do it, I'd be inclined to think hardware issue.
dandrumheller said:
Are you running stock software? If so, I'd try erasing and re learning your finger prints. I got an E4 for my daughter to use on WiFi - FP sensor is snappier and more accurate than my MZP. If that doesn't do it, I'd be inclined to think hardware issue.
Click to expand...
Click to collapse
Well here is the thing: when the phone is on the lock screen (screen turned on and asking for fingerprint or pattern/pin) the fingerprint sensor is instant and always accurate. The only time I am seeing lag is when I hold to turn the screen on (the screen is off but holding the fingerprint sensor turns it on) or off (phone is on and unlocked but holding the fingerprint sensor turns off the screen).
Can you confirm that your daughters phone has a faster response when turning on/off the screen?
i've read from a handful of reviews that the scanner is just simply not as fast as the MZP or even g5+. could be a limitation of the processor? i moved from a MZP to the e4, definitely a noticeable difference in speed.
skotseno said:
Well here is the thing: when the phone is on the lock screen (screen turned on and asking for fingerprint or pattern/pin) the fingerprint sensor is instant and always accurate. The only time I am seeing lag is when I hold to turn the screen on (the screen is off but holding the fingerprint sensor turns it on) or off (phone is on and unlocked but holding the fingerprint sensor turns off the screen).
Can you confirm that your daughters phone has a faster response when turning on/off the screen?
Click to expand...
Click to collapse
Yep, the times I use it, it's normally from screen off condition, or from in use to lock/turn off screen.
I'll try to do a side by side tonight with my MZP
dandrumheller said:
Yep, the times I use it, it's normally from screen off condition, or from in use to lock/turn off screen.
I'll try to do a side by side tonight with my MZP
Click to expand...
Click to collapse
here's a link to a quick head-to-head video. What is apparent is that the other poster is indeed correct - MZP is slightly faster from touch to screen on, and touch to screen off. The difference is slightly more pronounced when waking than going to sleep. What isn't apparent from the video is the timing of the haptic feedback. On the MZP the vibration is triggered almost instantly at touch, with the bulk of the delay from touch to screen on happening after the vibration triggers. On the E4, the vibration occurs around the middle of the span from touch contact to screen on. This gives the impression in use, at least to me, of slightly more laggy sensor (on the E4) but slightly faster unlock times (on the E4).
Guess I don't have to be jealous of my kid's phone anymore. Was a cool experiment.