Hey guys,
After initial setup, iris scanner worked great. At least 90% success rate on use. Until recently, about 5 days after purchase. Just attempts for a split second and fails, says dirty lense or retry. The lense is not dirty. I have tried removing the saved iris and starting over. Same error. Attached screen shot. Any ideas? Return maybe to Best Buy?
I have had mine for 8 days now of solid use and it works well. If you are within return period I would and order anew. Doesn't hurt.
Sent from my SM-N930P using Tapatalk
Read a few issues. Like oil from your face or fingers. Um any screen protector on it?
Sent from my SM-N930V using Tapatalk
Did you install a screnn proctetor that covers the sensor?
Sent from my SM-N930V using Tapatalk
Same thing happened with mine. Had it for a few days then the screen wouldn't rotate. Tested the sensor for the screen to rotate and it failed. Then a few days later while waiting for my replacement phone the Iris scanner stopped working. I did not have a screen protector on and I did not disable or freeze any apps. I reset the phone a few times and nothing changed. Took it straight to Verizon and switched back to my Nexus 6p until I received mine new phone (which works as of right now with all the same apps and settings as before).
It could be dust or anything like oil residue inside the phone under the screen itself. Or even a faulty connector, but yeah as said above go back and exchange it if you're within the 14 days.
dadsterflip said:
Read a few issues. Like oil from your face or fingers. Um any screen protector on it?
Sent from my SM-N930V using Tapatalk
Click to expand...
Click to collapse
No screen protector. Just does not work now
Attached screenshot
Trying to get the screenshot to attach
I had the same issue and still haven't got the replacement phone maybe later today. Also happened after the last update. I went into application manager than show system apps and went into "camera iris user test" and then storage and cleared the cache and data and i did the same for "iris". Then I powered it off not restart then back on and started working again.
Related
Hallo
After I updated to 4.2.2 my screen stopped respond to the touch. but only to touch with the finger and that is allso the "hard buttons", like Back and Menu. if i use the S-pen there is no problem.
I didnt have this problem befor updating, only after.
I have try to "Factory data reset" but that has not help. But it is like there is a "do not respond to finger touch, only to Spen" setting on.
I hope i have explained well enough.
..
Paland49 said:
..
Click to expand...
Click to collapse
I'm having this same problem with factory image of 4.2.2 on GT-N5110
The touch screen stops responding to my finger, but it responds normally to the s-pen.
Anyone else have the problem and idea for resolution?
Update: its somehow related to the case I was using. There is some sort of a proximity sensor in the phone and its getting confused and thinking the case cover is closed.
Was able to recreate the problem several times when its IN or even sitting ON the case. But is has never happened when the tablet is OUT of the case.
bigtexan99 said:
Update: its somehow related to the case I was using. There is some sort of a proximity sensor in the phone and its getting confused and thinking the case cover is closed.
Was able to recreate the problem several times when its IN or even sitting ON the case. But is has never happened when the tablet is OUT of the case.
Click to expand...
Click to collapse
Does that case have a magnet in it?
There is a "magnetic" sensor on the left side of the Note, when you close the case it will then shut off the note, some cases will even do that when you completely flip the "book" cover.
Hoping this helps
Sent from my SPH-L900 using xda premium
Common problem when this device came out. Mine did it to. Installed flexbeam rom by civato and problem went away. Kitkat is coming very soon and should fix the problem unless you want to root and install flexbeam.
Sent from my SM-N900V using XDA Premium 4 mobile app
I just got the phone 3 days ago... Today, a glass screen protector came in and I installed it. Of course, I messed up the first time, so I had to clean the screen and the protector since there was dust. There wasn't anything unusual in the installation, I just installed it as I did to my one plus. There wasn't an excess of water or anything. After the installation, the sensitivity was awesome, everything was great and worked great. An hour later, when I needed to use the phone, the sensitivity was lacking and eventually the phone started tapping by itself. I'm not sure what the issue is, but I proceeded with a factory reset believing it was the hardware since my oneplus never had this issue. After I reset, it still keeps auto tapping, and here I am now.
Thanks in advanced!
latituded1 said:
I just got the phone 3 days ago... Today, a glass screen protector came in and I installed it. Of course, I messed up the first time, so I had to clean the screen and the protector since there was dust. There wasn't anything unusual in the installation, I just installed it as I did to my one plus. There wasn't an excess of water or anything. After the installation, the sensitivity was awesome, everything was great and worked great. An hour later, when I needed to use the phone, the sensitivity was lacking and eventually the phone started tapping by itself. I'm not sure what the issue is, but I proceeded with a factory reset believing it was the hardware since my oneplus never had this issue. After I reset, it still keeps auto tapping, and here I am now.
Thanks in advanced!
Click to expand...
Click to collapse
did you already tried to remove the glass screen protector?
Were you able to find a solution? It's happening with me too!
On my tmo g4 I noticed when I was using my phone at night I could see light coming from both the right and left edges of the screen where it meets the body of the phone so I looked closer and the screen is actually coming out of the phone where the phone has a slight curve and I can literally push the screen down and see it move. I'm curious if I'm the only one or is this a common thing. I can't take any pictures because I don't have any other camera right now
Bump
The new update that tmobile pushed out should take care of the issues retracting the glue along with the screen by setting 10 second timer of an overclock to heat the phone up just right to let the adhesive settling in... at the end the update should prompt when this technical procedure is acomplished after a quick reboot! ??
Sent from my SM-G920T using Tapatalk
Slicktune said:
The new update that tmobile pushed out should take care of the issues retracting the glue along with the screen by setting 10 second timer of an overclock to heat the phone up just right to let the adhesive settling in... at the end the update should prompt when this technical procedure is acomplished after a quick reboot! ??
Sent from my SM-G920T using Tapatalk
Click to expand...
Click to collapse
Hahahahaha
To OP, Idk why you bumped this? Clearly this is an issue that's only fixed with returning the phone.
Sent from my G4 using your mom
Because I'm curious if anyone is having this issue
You sat on it didn't you.... Lol
Sent from my LG-H811 using Tapatalk
Don't know why it would "pop up" , just dont mention you dropped it when you were cleaning the gutters on your two story house.
Actually, someone on Reddit had this same issue. They ended up exchanging it with AT&T
I have some doubts on the fingerprint sensor region. Are we supposed to press the finger on the whole region all the time or is it sufficient to press some part of it? In my case, consider the region below the diameter of the sensor. I can see a line.. Only visible when I hold it up against the light in a horizontal angle. And when I tap the region below the diameter ie., Covering only the bottom 30 to 35% of the sensor. There's no detection at all. Is it normal?
And sometimes when the phone is idle for a while on the desk and I lift it up to unlock, it doesn't unlock on the first try. I have to tap again. I asked the Google support team and they said they're not sure if it's expected. Can anyone confirm? I have 3 more days left for replacement in my seller.
Thanks.
I'd say mine works if I cover 40% of the sensor whether that would be at the top or bottom. Have your tried re-adding your prints, when you do try out what ever is most natural to you and it should work everytime. Mine is flawless apart from when my hands are wet.
Mdizzle1 said:
I'd say mine works if I cover 40% of the sensor whether that would be at the top or bottom. Have your tried re-adding your prints, when you do try out what ever is most natural to you and it should work everytime. Mine is flawless apart from when my hands are wet.
Click to expand...
Click to collapse
Yes I have done that multiple times. It's just that when the phone screen is off for a while, it won't unlock on first try. Have to tap again.
AnandMuralidhar said:
Yes I have done that multiple times. It's just that when the phone screen is off for a while, it won't unlock on first try. Have to tap again.
Click to expand...
Click to collapse
I'm assuming Doze is the cause. Which is a fair trade off.
Sent from my Pixel XL using Tapatalk
I did try to search this and couldn't find anything so if I missed it I'm sorry but here goes.... When I make a call on my new pixel 2 xl the screen goes black like it should when I get the phone to my face but when I'm done with the call and pull it away it does not wake back up. I have to toggle the power button and use the finger print sensor to wake the screen back up. Anyone run into this?
do you have a screen protector on it ?
Yes I have the Verizon branded tempered glass on it
yotehtr1 said:
Yes I have the Verizon branded tempered glass on it
Click to expand...
Click to collapse
A lot of times the early made screen protectors for new phones are made wrong and forget the cut out for proximity sensor. Remember, it's a proximity, not light so even though glass is see through a proximity sensor detects anything, even glass.
It could also be lined up wrong.
Sent from my Pixel 2 XL using Tapatalk
yotehtr1 said:
I did try to search this and couldn't find anything so if I missed it I'm sorry but here goes.... When I make a call on my new pixel 2 xl the screen goes black like it should when I get the phone to my face but when I'm done with the call and pull it away it does not wake back up. I have to toggle the power button and use the finger print sensor to wake the screen back up. Anyone run into this?
Click to expand...
Click to collapse
Yes. It's happened several random times so I'm not sure what's wrong yet. For me I noticed that the ambient display just randomly went out. I now think it's because the proximity sensor triggered it. Similarly, I have an app called Screebl which turns off when the proximity sensor is triggered. I noticed that app also turned off. I hope it's a software problem not a hardware issue. I'm running the pixel 2 xl on Oreo 8.1 beta.
No screen protector here.. noticed this earlier today. Running the 8.1 beta..
jbarcus81 said:
No screen protector here.. noticed this earlier today. Running the 8.1 beta..
Click to expand...
Click to collapse
Yeah, I'm not using a screen protector either. Hopefully it's just the beta. I seached the beta bug reports and haven't seen anything reported on this yet.
Sm1000 said:
Yeah, I'm not using a screen protector either. Hopefully it's just the beta. I seached the beta bug reports and haven't seen anything reported on this yet.
Click to expand...
Click to collapse
Another thing I noticed with the beta is it slowed the finger print sensor quite a bit... So maybe there's something in the beta that affects the sensors some. Going to have to report some bugs...
I am on stock 8.0.0 here and am having the same issue. I did some searching and tried the "fixes" that involved turning off ambient display, restarting, etc., nothing worked. I have a screen protector on, but I tried the troubleshooting steps both with and without it on. I even tried the "Proximity Sensor Reset/Repair" app with no success.
Having the problem as well. Thank God it's a software issue
I also have an amfilm screen protector v2 on, as well as a Spigen Herringbone Neo-hybrid case.
No fingerprint sensor errors.
Sent from my Pixel 2 XL using Tapatalk
Fixed. Wiped down the proximity sensor with a dry toothbrush.
Need to get in touch with amfilm tomorrow and tell them their prox widow is too small.
Sent from my Pixel 2 XL using Tapatalk
Unfortunately for me, it wasn't a software issue. I removed the screen protector and wiped the phone, still no luck. Replacement is coming tomorrow.
I heard Google announced they know of the issue and will fix it with a software update
Jcsc831 said:
I heard Google announced they know of the issue and will fix it with a software update
Click to expand...
Click to collapse
Source?
Sent from my Pixel 2 XL using Tapatalk
http://www.androidpolice.com/2017/11/11/pixel-2-xl-touchscreens-unresponsive-near-edges-fix-coming/
never mind was for the touch screen issues not the proximity sensor
Same problem here. Started immediately with my first phone call after the 8.1 OTA finished installing, so clearly a change was made in 8.1 to the prox sensor sensitivity. This is with Google's "official" (and pretty lousy) Power Support screen protector
Everything back to normal with protector removed. C'mon, Google, geez.
Best part is, their touch screen fix didn't mix anything and now I have proximity sensor issues
Fremnet said:
Best part is, their touch screen fix didn't mix anything and now I have proximity sensor issues
Click to expand...
Click to collapse
Same here. Proximity sensor is weird at times
Sent from my Pixel 2 XL
I'm having issues as well BUT making calls via my watch or when receiving calls. If I make the call manually from the phone the sensor works fine.
Sent from my Pixel 2 XL using Tapatalk
8.1 update has caused my proximity sensor to lag like crazy, takes 1.5seconds some times before it gives me the screen to hang up. I think the issue may be linked to the general issue of unlock screen slowness