Terrible unlock delay since latest Android version - Google Pixel 4a Questions & Answers

I purchased my 4a to hold me over while sending my 4xl to get fixed(faulty battery connector, along with other bugs). One of the issues my 4xl had was a terrible lock screen delay after putting in my password or using face unlock. I chalked it up to slow facial recognition interfering with the unlock.
HOWEVER, I know now that the problem was not the facial recognition, as my 4a has had the same problem since I pulled it out the box and updated it. After using my pin/fingerprint to unlock the phone, I'm often met with this half transparent lock screen (see screenshot) that last anywhere from 5 to 10 seconds. This persist randomly in safe mode, and even after factory resets with minimal apps installed.
Is there a current bug tracker on this that I can't find? Link it if there is. Is there a workaround you guys are using? I can't imagine both of my devices having the same problem and it not occuring to anyone else.

Two different device similar issue ?
Could be the software you are running ?
Is it 100% stock ? When the device came out of the box did it not unlock right away ?
No delays on my device, touch the finger print scanner the phone immediately unlocks.

No delays here. Confidently can extend that to the overwhelming majority of 4a users who would be raising a torrid fuss if sign-in delays were the norm. Given it happened to you on two different devices/models you only need to look to the mirror to find root cause.

I found the cause and can replicate it across devices. It only happens when you're using pin + pixel print lock combo. Changing pin to pattern or password completely fixed my issues.
I cant believe I had this problem since the 4xl and it's my the pin option the whole time.

noidea24 said:
I found the cause and can replicate it across devices. It only happens when you're using pin + pixel print lock combo. Changing pin to pattern or password completely fixed my issues.
I cant believe I had this problem since the 4xl and it's my the pin option the whole time.
Click to expand...
Click to collapse
Strange, I use pin + pixel print lock combo (as I imagine is extremely common) and i don't have any issues. Maybe it's something deeper. At least you found a work around for now though.

noidea24 said:
I found the cause and can replicate it across devices. It only happens when you're using pin + pixel print lock combo. Changing pin to pattern or password completely fixed my issues.
I cant believe I had this problem since the 4xl and it's my the pin option the whole time.
Click to expand...
Click to collapse
tCizler said:
Strange, I use pin + pixel print lock combo (as I imagine is extremely common) and i don't have any issues. Maybe it's something deeper. At least you found a work around for now though.
Click to expand...
Click to collapse
"pin + pixel print lock combo" here as well; no delays. Try booting in safe mode to rule out personal app. All bets are off if rooted/unlocked.

DB126 said:
"pin + pixel print lock combo" here as well; no delays. Try booting in safe mode to rule out personal app. All bets are off if rooted/unlocked.
Click to expand...
Click to collapse
Completely stock. Latest updates. As mentioned in my original post, it even happened after factory resets and in safe mode. I can grab a screen recording, as I still have this problem after performing a factory flash. I setup pin and print in the initial setup, and soon after I have the problem stated. Only way to resolve is to disable/change pin option.
I remember pin unlock being a problem in the past, but it was a while ago.

noidea24 said:
Completely stock. Latest updates. As mentioned in my original post, it even happened after factory resets and in safe mode. I can grab a screen recording, as I still have this problem after performing a factory flash. I setup pin and print in the initial setup, and soon after I have the problem stated. Only way to resolve is to disable/change pin option.
I remember pin unlock being a problem in the past, but it was a while ago.
Click to expand...
Click to collapse
Hum - same weird problem on two different "stock" devices that isn't widely reported. Perhaps something related to your Google profile. Probably should reach out to them for further assistance or just stick with your workaround.

So I have this exact same problem with a Pixel 5. When I touch my fingerprint to the scanner, the screen stays black for 10+ seconds and then finally turns on. I tried the workaround (i.e. I switched from a PIN to a pattern), and so far I definitely see improvement. No issues so far. So I'll give it more time, but I think I may have replicated the problem and workaround. (on a Pixel 5)
Under Settings / Security / Device Admin Apps, do you all have an admin app configured? My employer has a special app for a VPN-like alternative and it has special admin privileges to validate the device security posture. I'm curious if it's related to having an admin app and security PIN enabled. It's probably an infrequently-used feature (relatively speaking), which makes it prone to weird unknown bugs.

Related

Is Smart Lock (Lollipop) working for you consistently?

Upgraded my N5 to its Lollipop Factory Image, and setup Smart Lock to work with my Moto 360. I'm noticing that my N5 will still prompt me for a passcode half the time, even though my moto 360 shows it's still connected (I can even PROVE it's connected, by doing an "Ok Google" voice search). I even set up face unlock to give it another unlock method, and that didn't seem to increase the success rate for Smart Unlock. It seems that no matter what, smart unlock doesn't work for me a lot of the time. To be more specific, it seems like it doesn't work if I haven't used the phone in awhile. Once I put my passcode in, smart lock seems to work just fine for awhile, but eventually it will stop working again, forcing me to enter my passcode to jumpstart it again.
Anyone else experiencing this?
Yes, this seems to be what I'm experiencing as well.
Same here... really want this to work. I assumed it might be because I dirty flashed, are you running a clean install?
same here...
Same here with a nexus 9. Tried connecting it to a moto and to my nexus 5. The units ARE connected to the nexus9 but in smartlock they have status "not connected". After setting up it works until the units are out of reach for the first time....after that it is back to pincode
jt3 said:
Upgraded my N5 to its Lollipop Factory Image, and setup Smart Lock to work with my Moto 360. I'm noticing that my N5 will still prompt me for a passcode half the time, even though my moto 360 shows it's still connected (I can even PROVE it's connected, by doing an "Ok Google" voice search). I even set up face unlock to give it another unlock method, and that didn't seem to increase the success rate for Smart Unlock. It seems that no matter what, smart unlock doesn't work for me a lot of the time. To be more specific, it seems like it doesn't work if I haven't used the phone in awhile. Once I put my passcode in, smart lock seems to work just fine for awhile, but eventually it will stop working again, forcing me to enter my passcode to jumpstart it again.
Anyone else experiencing this?
Click to expand...
Click to collapse
got no problem at all since N5 is paired with my LG G watch.
Got problems making NFC tag work. I have a NFC sticker at home, i use it with this app https://play.google.com/store/apps/details?id=com.jwsoft.nfcactionlauncher&hl=en making toggle wifi when i enter home (wifi on) and when i walk out (wifi off). I tried to use the same tag for smart unlock, but it simply doesn't works. Tag writing seems to be ok but still have to enter the pin when i pass my phone over it. Should i use another tag?
Mine works but RARELY
Sent from my Nexus 5 using XDA Premium 4 mobile app
Well, I figured out my issue anyway. It seems it's Gravity Screen. I use it to turn off my screen when I put the phone in my pocket (and turn it back on when I take it out). Because of this, I rarely touch the power button anymore. Apparently, when Gravity Screen locks the device, it REALLY locks it, making it so that Smart Lock can't unlock it, and forcing you to enter a passcode. I've left a note in the dev's thread, asking for a fix, but for now, I had to disable that feature.
Now, Smart Lock is working almost all of the time. I still have the occasional need to enter a passcode (like after rebooting), but for the most part, this fixed my issue.
I guess the tl;dr of all this is to make sure you don't have any apps running that lock or power-off your screen. They may be interfering.
jt3 said:
Well, I figured out my issue anyway. It seems it's Gravity Screen. I use it to turn off my screen when I put the phone in my pocket (and turn it back on when I take it out). Because of this, I rarely touch the power button anymore. Apparently, when Gravity Screen locks the device, it REALLY locks it, making it so that Smart Lock can't unlock it, and forcing you to enter a passcode. I've left a note in the dev's thread, asking for a fix, but for now, I had to disable that feature.
Now, Smart Lock is working almost all of the time. I still have the occasional need to enter a passcode (like after rebooting), but for the most part, this fixed my issue.
I guess the tl;dr of all this is to make sure you don't have any apps running that lock or power-off your screen. They may be interfering.
Click to expand...
Click to collapse
I don't use Gravity Screen, but have it installed. Could that cause the problem? I'm currently on 5.1 Cataclysm on my Nexus 5.
I have added Moto 360 as a trusted device. The moment I add it i'm able to unlock without PIN. However, after a few minutes, although the watch is connected, smart lock doesn't seem to work. I had this issue on stock Android 5.0 (no root or bootloader unlock) also with a Sony bluetooth headphones!
My smart lock "trusted places" is not working. I am assuming it is associated with the recent update to the Google Play Services for the "on body detection."
My Google Play Services has been sucking up my battery usage when location services is on. Other users have been experiencing the same issues. Some fixes suggest turning the smart features off then back and another is reinstalling the Google play services (revert then update again.)
I side loaded my Google Play Services but it didn't fix the problem. I am still looking for a fix so trusted places will work.
Sent from my Nexus 5 using Tapatalk
chrisinsocalif said:
My smart lock "trusted places" is not working. I am assuming it is associated with the recent update to the Google Play Services for the "on body detection."
My Google Play Services has been sucking up my battery usage when location services is on. Other users have been experiencing the same issues. Some fixes suggest turning the smart features off then back and another is reinstalling the Google play services (revert then update again.)
I side loaded my Google Play Services but it didn't fix the problem. I am still looking for a fix so trusted places will work.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Having absolutely the same problem. The "on body detection" feature works perfectly, howeve, the "trusted places" - almost never. I find myself entering my PIN at home every time I want to unlock the device, except for the times I slide it out of my pocket. If Google fixes these problems, Smart Lock would be my favourite feature!
I've pretty much given up on Smart Location Unlock. It's been broken for weeks now. I'm on CM12 and made profiles to disable pin/password/pattern when connected to my home Wi-Fi.

problems with fingerprint scanner

Okay so this happened a few days ago and has still not been fixed. The problem is that when I go to unlock my phone with the fingerprint scanner witch is what I've been using since I got the phone. Scan my finger and it just keeps saying no match I do know the backup password and it unlocks the phone. But I have tryed to scan my fingerprint again through the scanner option in settings. It want me to scan my finger for verification as this does not work iv tried. I then go to enter the backup password to access the setting to change my lockscreen code swipe exc. When I enter the backup password it tells my the the wrong password has been entered. Now this same password opens my phone unlocks it just fine. But will not let my scan my fingerprint again or change my lock screen. Any ideas on how to fix this woth out a backup and restore? It's rooted so it's not big deal but I'd rather not have to.
Did a bit of research myself as i had the same problem, always remember to deactivate fingerprint scanner before making a backup (This didn't sound like your issue but just something to keep in mind). I found this post from another forum which fixes your issue.
You will be able to input new fingerprints into your phone from the settings menu once you have completed this guide:
Hahaha it's not a fix so much as a workaround. It removes your registered fingerprints without having to factory reset.
Ready? In recovery, navigate to /data/validity/ and delete "template.db"
This won't remove the lock screen setting so upon reboot the lock screen will still think you're using fingerprint... But your backup password will work.
I actually had to do a reset the only thing I can think of that happened was I had the finger print scanner as the lock on my phone before I rooted the phone. I'm not sure exactly but I believe that it deleted the "details" I guess that's the best way to put it. You know the way it makes you scan your finger in multiple times in different ways. I always used the same way every time thinking about it now I always had problems with unlocking my phone with the scanner I just thought it he scanner was total crap. But yeah I guess when I rooted the phone it did something or maybe I just didn't do it right the first time.
But the problem has been solved and the phone works fine the scanner is a lot better than I thought.
TM_Ethos said:
I actually had to do a reset the only thing I can think of that happened was I had the finger print scanner as the lock on my phone before I rooted the phone. I'm not sure exactly but I believe that it deleted the "details" I guess that's the best way to put it. You know the way it makes you scan your finger in multiple times in different ways. I always used the same way every time thinking about it now I always had problems with unlocking my phone with the scanner I just thought it he scanner was total crap. But yeah I guess when I rooted the phone it did something or maybe I just didn't do it right the first time.
But the problem has been solved and the phone works fine the scanner is a lot better than I thought.
Click to expand...
Click to collapse
Give this guide a try for the fingerprint scanner if you wish to use the scanner. Always had issues with it till i found this and it has helped out drastically.
http://forum.xda-developers.com/note-4/general/to-fingerprint-scanner-bad-inaccurate-t2919453
My issue is......while using the phone it jumps frpm what am doing then prompt me with the option to enter my backup password

S View case and smart lock issue, MM

I'm hoping someone else is having this same issue since the MM update.
When I first got the Note 5 on lollipop, I set up a smart lock with my home location so I didn't have to use my fingerprint when I was at home. I also set up the s view case to automatically unlock the phone when opened. On lollipop this worked pretty much flawlessly.
Since the update though, both are somewhat finicky. Sometimes it works just fine while other times it's smart lock that still wants my fingerprint. At other times, smart lock is fine, I only need to swipe to unlock, but the s view case doesn't unlock the screen when opened. I'm hoping it's just an overlooked bug in the first MM software and will be corrected with future updates.
I have factory reset the phone and done everything I can think of to fix it. It's not a big deal as it doesn't hurt functionality at all, it's just a bug I've noticed. Also, I think a good option under the smart lock settings would be "when connected to a certain Wi-Fi access point" but it's not an option.
Has anyone else noticed this and fixed the issue? Thanks
Same issue. Set up paired with my Zenwatch and it seems to be about 50/50 whether I can slide to unlock or have to use fingerprint.
Same thing here. Its def a bug. I have tried clearing out my google settings, location settings, location cache, everything other than a master reset for the most part.
Honestly it never works right since the mm update. Wouldnt even give it a 50/50..
BUT
What i have noticed is if i simply press the home screen twice, one to wake, then again but lightly pressing, it unlocks automatically. The finger print scanner reads the print so quick it gets you straight to the home screen.. shouldnt have to do this. but it works pretty well to unlock quickly. Plus, dont have to slide anymore and get prints/smudge on the screen.

Smart Lock - Lots of Issues

I tried to enable Smart Lock and have run into a couple issues which no amount of searching gave way to results. I'm on a stock unrooted device.
Is there a way to make this feature work based on location? Seems to not work in locations where I set it to. I tried uninstalling and reinstalling google play services to no avail. Rebooting does nothing to fix.
Sometimes when I try to view the Smart Lock settings, after entering the pin/pattern nothing appears in the menu at all. Very buggy. Does this feature just plain suck or something? I'd rather not use face unlock, but this might force me to.
SOCOM-HERO said:
I tried to enable Smart Lock and have run into a couple issues which no amount of searching gave way to results. I'm on a stock unrooted device.
Is there a way to make this feature work based on location? Seems to not work in locations where I set it to. I tried uninstalling and reinstalling google play services to no avail. Rebooting does nothing to fix.
Sometimes when I try to view the Smart Lock settings, after entering the pin/pattern nothing appears in the menu at all. Very buggy. Does this feature just plain suck or something? I'd rather not use face unlock, but this might force me to.
Click to expand...
Click to collapse
I have issues like this. Supposedly, smart Lock not working by location is a bug from Google not op. It is very hit or miss
thejase said:
I have issues like this. Supposedly, smart Lock not working by location is a bug from Google not op. It is very hit or miss
Click to expand...
Click to collapse
I wonder if this is an Oreo issue and if it will be fixed in P. Very annoying. I may just drop security all together. I didn't have it on my last phone for over 3 years. I like the idea of it, but not being able to unlock the phone while driving and at "trusted" places is pretty useless.
SOCOM-HERO said:
I wonder if this is an Oreo issue and if it will be fixed in P. Very annoying. I may just drop security all together. I didn't have it on my last phone for over 3 years. I like the idea of it, but not being able to unlock the phone while driving and at "trusted" places is pretty useless.
Click to expand...
Click to collapse
Agreed
And the fingerprint unlock not fast enough for you. I do it in one motion. Pick up phone and unlock just like that
nujackk said:
And the fingerprint unlock not fast enough for you. I do it in one motion. Pick up phone and unlock just like that
Click to expand...
Click to collapse
It has nothing to do with speed and everything to do with convenience. Let's not forget that GOOGLE is the one who added the feature. Oreo has been out, in general, for a while. It should just plain work. If I'm at home, why should there be a lock on my device? When I'm out however, it just makes sense to be locked down. Adding a feature that actually doesn't work or works some of the time, is something you'd think they'd have caught during Oreo testing at Google; particularly, as it's an issue with Android, not manufacturers. Even my wife's Galaxy S9+ has this issue.
@thejase
I get that but I don't use it as I'm the opposite phone should be locked when not in my hand never know what will happen,who may come over to visit I have lots of nieces and nephews. One who grabs any phone he can.
But I meant it to be fast enough that it's as if it's not locked.
If you want to stick with
Smart lock have you tried use the voice feature it may work.
Also look into Tasker I seem to remember someone using it to unlock the device based on location. I use it to turn on and off my Wi-Fi based on location. Auto start my music when in my truck.
thejase said:
It has nothing to do with speed and everything to do with convenience. Let's not forget that GOOGLE is the one who added the feature. Oreo has been out, in general, for a while. It should just plain work. If I'm at home, why should there be a lock on my device? When I'm out however, it just makes sense to be locked down. Adding a feature that actually doesn't work or works some of the time, is something you'd think they'd have caught during Oreo testing at Google; particularly, as it's an issue with Android, not manufacturers. Even my wife's Galaxy S9+ has this issue.
Click to expand...
Click to collapse
Seems to be working better today. Disabled the "smart lock" in trust agents setting under fingerprint and security, then booted to the stock recovery and wiped the cache only. (I'm not rooted yet, but TWRP would work for this as well). Seems to have led to a fix, but it could be temporary. As for usefulness of smart lock, I am not worried about others in my own home taking my device and combing through it for all I care. If you have kids or are concerned about content on your phone being messed with, just don't use the feature. For a lot of people, it is a useful feature to have.
This issue has returned and requires a cache wipe almost every day. Beyond annoyed. I am considering deleting my fingerprints or any security. Pretty stupid feature that makes the phone require a password every single time I want to use it, when this feature could have alleviated that in so many places where I know my phone is safe (home, work, car).
Oneplus 6 - Phone unlocks with smart lock off on Android P
I don't use smart lock option in my phone but after upgrading to Android P, even when the smart lock option is off, my phone screen opens when picked immediately as it is supposed to show the screen is locked. Any suggestions please

Is this the dreaded lag issue (necessitating an RMA)?

About three months ago my Pixel 2 (purchased new from Google) began having an issue where it becomes unresponsive or extraordinarily delayed on responding. It almost always happens when I'm waking the phone up from being locked. When it happens, the phone will eventually unlock but everything reacts several seconds after contact (power button, taps, swipes). A reboot or power down fixes the problem, but is always necessary.
I switched to Project Fi around that time and thought it had something to do with the switching between CDMA and GSM (Sprint/US Cellular vs T-Moble) towers, but I've switched to T-Mobile (a solely GSM provider) since and the problem persists.
I am running Android Pie (stock). My bootloader is unlocked and I do have Magisk installed. No TWRP. I don't have any obvious troublemakers installed (like Xposed, for example) and only a few apps that even use root (Cerberus, Adaway, and Nova Launcher).
I have heard about the Pixel 2 XL having a hardware issue that results in unresponsiveness and that ultimately requires sending in the device for a replacement. Is this the same thing?
Any advice would be much appreciated. If it would be helpful, I can produce logs, but I'll have to wait until it happens again to offer logs that might contain clear indications of what might be happening.
- Computerslayer
computerslayer said:
About three months ago my Pixel 2 (purchased new from Google) began having an issue where it becomes unresponsive or extraordinarily delayed on responding. It almost always happens when I'm waking the phone up from being locked. When it happens, the phone will eventually unlock but everything reacts several seconds after contact (power button, taps, swipes). A reboot or power down fixes the problem, but is always necessary.
I switched to Project Fi around that time and thought it had something to do with the switching between CDMA and GSM (Sprint/US Cellular vs T-Moble) towers, but I've switched to T-Mobile (a solely GSM provider) since and the problem persists.
I am running Android Pie (stock). My bootloader is unlocked and I do have Magisk installed. No TWRP. I don't have any obvious troublemakers installed (like Xposed, for example) and only a few apps that even use root (Cerberus, Adaway, and Nova Launcher).
I have heard about the Pixel 2 XL having a hardware issue that results in unresponsiveness and that ultimately requires sending in the device for a replacement. Is this the same thing?
Any advice would be much appreciated. If it would be helpful, I can produce logs, but I'll have to wait until it happens again to offer logs that might contain clear indications of what might be happening.
- Computerslayer
Click to expand...
Click to collapse
Do you have the navbar hidden by any chance
crixley said:
Do you have the navbar hidden by any chance
Click to expand...
Click to collapse
Well, I have Nova set up to hide the dock unless I swipe up (or down) on it. I can't seem to find a setting about hiding the navbar. Where should I be looking to check?
computerslayer said:
Well, I have Nova set up to hide the dock unless I swipe up (or down) on it. I can't seem to find a setting about hiding the navbar. Where should I be looking to check?
Click to expand...
Click to collapse
Did you install any apps to hide your navigation bar? Is it always visible? Immersive mode apps for example
crixley said:
Did you install any apps to hide your navigation bar? Is it always visible? Immersive mode apps for example
Click to expand...
Click to collapse
We're talking about the back button and the new pill gesture button, right? If so, then no I haven't installed anything to hide those: they are always visible.
Well, after 24 hours, I had the issue resurface. Unfortunately, the logging app I was using (matlog) froze up with the phone and produced a blank text file. While rebooting restored normal function of the phone, I can't produce a log as a result.
It occurs to me that while I am not disabling the navbar, I do use a function of the Cerberus anti-theft app to disable the notification bar while locked. Could this be the source of my issue? If so, is there any way to confirm this?
In the meantime, I've disabled that function and will see if the lock-up occurs again.
I'm curious where you were going with the question about the navbar. Could you tell me more about what you were thinking it might have been?
I went ahead and disabled the 'block status bar' function of the Cerberus app and the problem has not resurfaced in over two days (it was occurring several times daily). Although I can't definitively prove it, I think the culprit was the app.
Thanks for the time and assistance!
computerslayer said:
I went ahead and disabled the 'block status bar' function of the Cerberus app and the problem has not resurfaced in over two days (it was occurring several times daily). Although I can't definitively prove it, I think the culprit was the app.
Thanks for the time and assistance!
Click to expand...
Click to collapse
Sorry I didn't get back to you I read this a while back and totally thought I responded. Yeah anything that hides the status bar or navbar from the system UI at all times is known to cause wake issues. On my essential phone it would require me to restart it to actually get the screen to come back on. It's called the deep sleep of death or something haha
crixley said:
Sorry I didn't get back to you I read this a while back and totally thought I responded. Yeah anything that hides the status bar or navbar from the system UI at all times is known to cause wake issues. On my essential phone it would require me to restart it to actually get the screen to come back on. It's called the deep sleep of death or something haha
Click to expand...
Click to collapse
Hello Crixley,
No worries at all - I'm always grateful when anyone responds around here because I know that we're all balancing regular life and our hobby time!
I'm relieved to hear that it is a known issue, though I'm going to miss the functionality! I wish Google would build some kind of equivalent security measure so that the network state can't be changed while the phone is locked. I'm guessing that this issue is exactly why they haven't gotten to it (yet?).
Thanks for your time & support, both here with my issue and across the forums.
Peace,
Computerslayer
computerslayer said:
Hello Crixley,
No worries at all - I'm always grateful when anyone responds around here because I know that we're all balancing regular life and our hobby time!
I'm relieved to hear that it is a known issue, though I'm going to miss the functionality! I wish Google would build some kind of equivalent security measure so that the network state can't be changed while the phone is locked. I'm guessing that this issue is exactly why they haven't gotten to it (yet?).
Thanks for your time & support, both here with my issue and across the forums.
Peace,
Computerslayer
Click to expand...
Click to collapse
I'm glad to hear it's fixed for you!
I try to help as much possible, I remember how good it was to have people help me when I needed it and sometimes I need a hand as well.

Categories

Resources