[sulla1965]

Just noticed that I have to tap and wake up the phone to use fingerprint. If phone is off and I touch fingerprint, nothing happenes. Is this a new security feature, or a bug? Thanks

[B. Diddy]

Do you mean if the screen is completely off?

[sulla1965]

Yes on the AOD it shows fingerprint scanner, but I have to tap to wake before it will activate.

[brosko]

Yes on the AOD it shows fingerprint scanner, but I have to tap to wake before it will activate.

That's a bug then I think. On the always on display you should be able to place your fingerprint on the icon and have it read your print to unlock the phone. With screen completely off it should not work.

[sulla1965]

That's a bug then I think. On the always on display you should be able to place your fingerprint on the icon and have it read your print to unlock the phone. With screen completely off it should not work.

Thanks that's what I thought.

[dookie.]

Has been mentioned by others as occurring intermittently. Is your situation always the case, or does it work properly sometimes?

[sulla1965]

Happens since the Jan update. Didn't notice it happening before. It shows fine on AOD but nothing happenes when I press it. I have to wake screen first by tapping the screen or via power button to wake, then it works fine.

[Blaize19]

Actually, it works for me with the screen off, fwiw. So I think it must be a bug.

[Rodawg71]

Just checked...locked the phone and unlocked with FPS just fine (on AOD, ten multiple times)

Edit: just did it again with notifications and no problem.

[Scott337]

For the OP: do you have any smart lock trust settings enabled (trusted device, trusted location, etc.)? I am seeing this periodically also since the January update. I have a smart watch set as a trusted device and once every few hours I see the fingerprint icon on the lock screen but it does nothing. When I swipe up to unlock the phone smart lock kicks in and the phone unlocks. I wonder if this is related to the smart lock fix that was part of the January update?

[dmxjago]

That's how I was always believed how it's supposed to work. You tap the screen to wake up the screen or hit the power button to wake up th screen and then tap the finger print to unlock. Same as if you didn't even have a password where you need to wake up the phone first then swipe up to unlock.

Am I missing something? Are you saying you used to be able to just put your finger where the sensor is without having to wake the phone or are you using always on display? I don't use always on display and for me I have to wake it then use my finger to unlock it.

[dmxjago]

I just tried it by enabling always on screen and i can unlock mine with on tap without waking it.

[sulla1965]

I did a factory reset and it fixed it for a while. But not working again. I works if I tap (wake) the screen. But it's supposed to work directly from AOD with the phone off. I shouldn't have to wake the screen first. I got used to that feature with the s21, but it's not working on P6 for some reason.

[StormnNJ]

Strange. I don't use AOD but turning it on I can NOT unlock. Might as well be a picture of a fingerprint. Does nothing until I wake screen.

VZ unlocked P6P

[sulla1965]

Strange. I don't use AOD but turning it on I can NOT unlock. Might as well be a picture of a fingerprint. Does nothing until I wake screen.

VZ unlocked P6P

That's exactly how it is with my P6. Its showing, but it does nothing when pressed.

[Morty2264]

Yes on the AOD it shows fingerprint scanner, but I have to tap to wake before it will activate.

I too think that's a bug. Does it happen in Safe Mode? Have you tried restarting your phone to see if a quick restart fixes anything?

[dookie.]

I have seen this intermittently as well. Of course when I try to replicate now, it works fine...

[sulla1965]

I too think that's a bug. Does it happen in Safe Mode? Have you tried restarting your phone to see if a quick restart fixes anything?

Yep happens in safe mode as well

[HighwayBob]

Interesting. Since I got my 6 there have been times when I see no fingerprint "target" on the screen so I couldn't unlock it. I would either have to repeatedly tap the screen or tap the power button.

However, since I installed the January update this problem seems to have disappeared.


Is there some way to file bug reports with Google, besides having to open an inquiry with support? I had a Bluetooth issue that I solved myself and support was difficult in diagnosing it - they just wanted me to do a factory reset.

[Scott337]

Interesting. Since I got my 6 there have been times when I see no fingerprint "target" on the screen so I couldn't unlock it. I would either have to repeatedly tap the screen or tap the power button.

However, since I installed the January update this problem seems to have disappeared.


Is there some way to file bug reports with Google, besides having to open an inquiry with support? I had a Bluetooth issue that I solved myself and support was difficult in diagnosing it - they just wanted me to do a factory reset.

I don't have the link in front of me, but it's called Google Buganizer. That's where we file our bug reports.

[YankInDaSouth]

Having this happen to me now too (6 Pro) ... Was flawless just a few days ago. Now with AOD on it appears as if the FPS is completely unresponsive until I tap to wake.

I'm also having to unlock my phone on the double press of the power button to open the camera ... Which totally defeats this shortcut LoL

Neither of these issues happen when I boot into safe mode and only appears to have surfaced a day or two ago Haven't installed any new apps so I can't help but wonder if one of my apps updated and borked something.

[Gdraft#WN]

I've had the same issue since day one. the January update made it better......but that's relative.

I've had pixels since day one. this POS is making me rethink this decision

[YankInDaSouth]

So weird ... After my post above I tried safe mode again and all was good. Rebooted (not safe mode) and now everything is working fine. Go figure

[mustang7757]

So weird ... After my post above I tried safe mode again and all was good. Rebooted (not safe mode) and now everything is working fine. Go figure

Sometimes going in and out of safe mode fixes small glitches

[HighwayBob]

I don't have the link in front of me, but it's called Google Buganizer. That's where we file our bug reports.

When I search for this I get Google Issue Tracker. Is that it? Says it's for internal Google use and for developers who work with Google teams.