Is device unlock slow after January update? - Google Pixel 2 XL Questions & Answers

Is it just me or is the device unlock using power button or finger scanner got slow after January update? It was normal before the update and definitely got slower for me after the update...tried clean flash also...if we have always on enabled, unlock is faster...issue is with always on disabled only...

This is a known issue if you took the update by sideloading the OTA

ram4ufriends said:
Is it just me or is the device unlock using power button or finger scanner got slow after January update? It was normal before the update and definitely got slower for me after the update...tried clean flash also...if we have always on enabled, unlock is faster...issue is with always on disabled only...
Click to expand...
Click to collapse
Reboot your device once or twice and it should work normaly.

This has been an issue since 8.1. I've noticed it as well as on 8.0 my device woke up instantly.
Other users on reddit have seen the issue as well. Turning on ambient display to always on "fixes" it for me. Every user on this thread who says their device unlocks quickly has ambient display on. https://www.reddit.com/r/GooglePixe...el_2_xl_january_update_security_patch_jan_05/
Here's the official bug report on Google's tracker:
https://issuetracker.google.com/issues/69984153

I did factory reset, had no delay. As soon as I rooted. Had the delay.

ram4ufriends said:
Is it just me or is the device unlock using power button or finger scanner got slow after January update? It was normal before the update and definitely got slower for me after the update...tried clean flash also...if we have always on enabled, unlock is faster...issue is with always on disabled only...
Click to expand...
Click to collapse
One of the results of the Meltdown/Spectre malware "mitigation" security fixes is a slowdown. Because of the nature of the exploit block, lag is going to be experienced in most all operating systems.

DoctorB0NG said:
This has been an issue since 8.1. I've noticed it as well as on 8.0 my device woke up instantly.
Other users on reddit have seen the issue as well. Turning on ambient display to always on "fixes" it for me. Every user on this thread who says their device unlocks quickly has ambient display on. https://www.reddit.com/r/GooglePixe...el_2_xl_january_update_security_patch_jan_05/
Here's the official bug report on Google's tracker:
https://issuetracker.google.com/issues/69984153
Click to expand...
Click to collapse
Yes, turning always on seems to be the fix as of now

wtherrell said:
One of the results of the Meltdown/Spectre malware "mitigation" security fixes is a slowdown. Because of the nature of the exploit block, lag is going to be experienced in most all operating systems.
Click to expand...
Click to collapse
My OG XL doesn't have this problem at all on the January 5th patch and meltdown only affects Intel x86 CPUs. Spectre affects quite a few ARM, MIPS and x86 chips but I refuse to believe that would cause a device to take 2-3x longer to unlock. Spectre fixes would incur a performance penalty on CPU demanding loads which waking a device up does not qualify.

Supposedly this issue has been fixed with the fix to be released at a future date. They said this in mid December, so doesn't look like the fix made it to the January security update. Hopefully the February one will have the fix

Related

HTC 10 Android 7.0 Nougat Update Issues

I upgraded to Nougat yesterday, currently facing many stability issues. Any help would be appreciated on the below problems.
* Sound is unstable, screen lock does not produce any sound
* Incoming calls are often silent, no sound comes out for some reason
* HTC Live Wallpapers disappeared, I cannot locate them
* Double tap to wake problem persists, I had this problem on 6 and still cannot fix it despite many attempts including sensors, wipe clean and 3 hard reset attempts // I had this issue when I purchased my phone back in September. After many trial and errors it somehow worked on its own. Then I got a problem on my screen and took it to the HTC Service. They told me they replaced the screen and did a software update and my DT2W no longer worked
Also missing the live wallpapers over here.
NFc is working for you? Reading any NFC tag?
sloaxleak said:
NFc is working for you? Reading any NFC tag?
Click to expand...
Click to collapse
Nfc is not working either
No live wallpapers either from UK Nougat update but not encountered stability issues yet.
My Xperia keyboard was playing up but reinstalled and seems to be OK now.
Are you guys on the latest 2.41.xxx update?
comstockload said:
Are you guys on the latest 2.41.xxx update?
Click to expand...
Click to collapse
Yes, the update has brought many challenges though
cengizbey said:
Yes, the update has brought many challenges though
Click to expand...
Click to collapse
I guess that's why there's a new firmware 2.41.401.4 leaked. Would explain why they halted the Roll-Out of 2.41.401.3, and seems they already working on a fix.
Sent from my htc_pmeuhl using XDA Labs
I guess so, in any case I am very disappointed by lack of stability of many features in #HTC10
cengizbey said:
I guess so, in any case I am very disappointed by lack of stability of many features in #HTC10
Click to expand...
Click to collapse
My HTC 10 is an unlocked US version and it seems pretty stable. After initial roll out of Android 7 on Nov 25th, we then got 2 updates(Dec and Jan) which contained bug fixes and security patches.
I guess my #htc10 has hardware issues out of the box
After the UK Nougat update my Sandisk SD card is not being recognised as external storage. Was ok before the update. I've removed & reinserted a couple of times, still no joy. Anyone experienced this?
Sent from my HTC 10 using Tapatalk
I had the same problem. I had to remove it and reinsert into the phone.
Hey guys,
None of the issues above I ran into....Has OP tried a factory reset? Always recommended to Android devices after a big version upgrade.
Speaking of factory reset, well, I did it, and I have some other issues :
1. Camera in Pro mode, under long exposure duration, the image quality drops significantly...I am an photography amateur, so I know what I am talking about.
2. Sometimes the phone app does not recognize saved contacts. (It seems that this would be solved with 2.41.401.4)
3. Battery drains...much quicker than 1.95...before I can get 5h or + screen on time, now barely passes 4h.
I've also noticed a batterydrain. Although I've done a fresh install. Yesterday I did a complete wipe again without backup recovery. Battery seems stable now.
Since the OTA Nougat update i've had issues with instagram videos not playing whilst pictures work fine (on both 4g and wifi).
Also gmail no longer syncs automatically and i have to manually refresh to get mail.
Wiping cache partition and wiping app cache/ reinstalling the apps didn't work. I do feel like the update has somehow caused this as it was fine before.
Anyone else having these issues?
To comment on issues others have been having, my battery drain feels normal. And I have always has issues with gestures and double tap to wake not working
Unlocked USA 2.41.617.3 is stable here
Unlocked USA 2.41.617.3 is stable here. It brought the January security patch and also fixed all of my battery drain issues I had since the September, 2016 Android 6.1 update. I lost 2-day battery life in September, 2016.
I am finally back to 2-day battery with doze acting normally since January, 2017 update.
No extra updates or fixes yet for us in the UK. Also noticing apps will won't auto update correctly now. Getting a google play is not responding message. HTC need to sort this out asap
cengizbey said:
Nfc is not working either
Click to expand...
Click to collapse
Got it... is it a known issue?
Same, no nfc either

reasons to upgrade 8.1?

just curious if its worth updating to 8.1 with the January update going around?
Yes, always better to move forward than go backwards...
galaxys said:
Yes, always better to move forward than go backwards...
Click to expand...
Click to collapse
i was asking as the 8.1 december update had caused issues for some people and i was checking to see of they had fixed those issues
No issues here. Actually the screen is much more responsive. Plus latest Security patches, etc...
galaxys said:
No issues here. Actually the screen is much more responsive. Plus latest Security patches, etc...
Click to expand...
Click to collapse
awesome i was worried since the december update caused some issues but its good to see they fixed the responsiveness issue.
8.1 was necessary to get bluetooth to work with my car; I think they did a lot of bluetooth enhancements there.
I have had one unexpected shutdown since 8.1 (I'm on beta so that's over 2 months or so), that's the only downside (and no idea if that was really 8.1 specific).
The December 8.1 update has been great for me. I originally had huge issues using my fingerprint reader in apps, it now works flawlessly every time on 8.1. I have seen some multitouch issues playing Rules Of Survival, but I don't play that much so it's not a huge deal breaker for me.
Lol. I've been holding off updating to 8.1 because
a) I really like the current set up of my phone (rooted, workaround to carrier blocking mobile hotspot, stable OS)
b) I know i'll run into a bunch of hiccups trying to replicate this state mentioned above on 8.1
I do want to try the AR stickers and the supposed camera improvements, so will end up upgrading.... eventually.
8.1 was necessary to get bluetooth to work with my car; I think they did a lot of bluetooth enhancements there.
I have had one unexpected shutdown since 8.1 (I'm on beta so that's over 2 months or so), that's the only downside (and no idea if that was really 8.1 specific).
Click to expand...
Click to collapse
cool ive had some trouble with bluetooth but not alot just somedays it wants to be annoying and the rest of the time its fine.
The December 8.1 update has been great for me. I originally had huge issues using my fingerprint reader in apps, it now works flawlessly every time on 8.1. I have seen some multitouch issues playing Rules Of Survival, but I don't play that much so it's not a huge deal breaker for me.
Click to expand...
Click to collapse
so the fingerprint reader issue went away after using it for a while? have you updated to the january ota?
Youngbloodx said:
Lol. I've been holding off updating to 8.1 because
a) I really like the current set up of my phone (rooted, workaround to carrier blocking mobile hotspot, stable OS)
b) I know i'll run into a bunch of hiccups trying to replicate this state mentioned above on 8.1
I do want to try the AR stickers and the supposed camera improvements, so will end up upgrading.... eventually.
Click to expand...
Click to collapse
lol couldn't agree more but i want the active edge remapping option that just came out and it requires 8.1 sadly
razgriz1234 said:
just curious if its worth updating to 8.1 with the January update going around?
Click to expand...
Click to collapse
Yes! Because all the Kool Kids have.
Only issue I'm having with January 8.1 is same as I was having with December 8.1 which is the screen does not show who's incoming calling for whatever reason I have no idea. I had thought maybe it was because I was unlocked, rooted, etc... but right now I'm not, am fully stock and locked in and it still doesn't show, ugh. Other than that though, the January 8.1 is snappy, the touch responses are definitely better and I swear it almost seems like the blue tint at angles is much less noticeable or better now, but placebo probably.
CJ-Wylde said:
Only issue I'm having with January 8.1 is same as I was having with December 8.1 which is the screen does not show who's incoming calling for whatever reason I have no idea. I had thought maybe it was because I was unlocked, rooted, etc... but right now I'm not, am fully stock and locked in and it still doesn't show, ugh. Other than that though, the January 8.1 is snappy, the touch responses are definitely better and I swear it almost seems like the blue tint at angles is much less noticeable or better now, but placebo probably.
Click to expand...
Click to collapse
That issue is very annoying. I was hoping it would have been fixed with the January update, too. Back in December, I ended up making a macro with Macrodroid to turn the screen on with an incoming call, and it's fixed the problem for now. I think the phone app needs to be updated. I've given feedback through the phone app, but there has been no update for weeks.
The Autofill API has some improvements, and apps like 1Password are reliably filling in most apps and webpages (tested the latter with Chrome). This has been one of the reasons (for me at least) to come back to Android after a fairly long hiatus.
AR stickers are also cool.
And who doesn't like bleeding edge?
It's also been pretty stable.
8.1 is ONLY good if you need HD voice other than that it's buggier, finger print scanner is worse, lock screen touch response issues are more apparent for A LOT of people. So much so Google is aware of the issues. Also 8.0 battery life is WAY better than 8.1.
Sent from my Pixel 2 XL using Tapatalk

new Firmware 47.1.A.12.179

The new Firmware 47.1.A.12.179 is out:
https://xpericheck.com/device/G8441
in Android-Hilfe.de Thread they write that the firmware includes Android Security Patch is 01. May 2018.
It is the May security patch. Couldn't find any other changes so far.
Good day.
I noticed that wifi now connects intantly.
Good news about wifi, although for me, the issues are so intermittent that it's tough to tell.
SmartLock settings are still blank.
I won't be able to test car bluetooth until tomorrow, so fingers crossed. Although I did discover last weekend that if I pause from the car's headset, it will display the currently paused song after 2, or so, seconds.
snowkeep said:
Good news about wifi, although for me, the issues are so intermittent that it's tough to tell.
SmartLock settings are still blank.
I won't be able to test car bluetooth until tomorrow, so fingers crossed. Although I did discover last weekend that if I pause from the car's headset, it will display the currently paused song after 2, or so, seconds.
Click to expand...
Click to collapse
To fix the smart lock, in your security settings find "Trusted Agents" and uncheck Smart Lock, then reboot and enable the agent for Smart Lock again. Worked for me.
Covalex said:
To fix the smart lock, in your security settings find "Trusted Agents" and uncheck Smart Lock, then reboot and enable the agent for Smart Lock again. Worked for me.
Click to expand...
Click to collapse
Doesn't work for very long, two or three days max, then it stops opening and trusted device fails to unlock
As long as it does come with 8.1 I'm not too interested. Whole reason with going with Sony was project treble for faster updates. Disappointing to say the least.
Sent from my G8441 using Tapatalk
ninjazin said:
Whole reason with going with Sony was project treble for faster updates. Disappointing to say the least.
Click to expand...
Click to collapse
You really can't see the benefit of Treble? We get security update each month! I'd never seen such quick updating before Treble, on non Google's phones.
To compare: my Motorola X Force is still on October 2017 security patch :/
Davka said:
You really can't see the benefit of Treble? We get security update each month! I'd never seen such quick updating before Treble, on non Google's phones.
To compare: my Motorola X Force is still on October 2017 security patch :/
Click to expand...
Click to collapse
As my wife's S7 from Samsung also gets monthly updates then it's not really impressing
Sent from my G8441 using Tapatalk
Covalex said:
To fix the smart lock, in your security settings find "Trusted Agents" and uncheck Smart Lock, then reboot and enable the agent for Smart Lock again. Worked for me.
Click to expand...
Click to collapse
I have to agree with Didgesteve. The only improvement is that the SmartLock screen stays visible - it still doesn't work, but you can see it. The wifi problems came back. And the bluetooth is the same, to possibly worse. Yay! for security updates, but from a user perspective, this update did nothing, as far as I can tell. At least there are workarounds for the problems. It's still a huge improvement over the Galaxy S5 it replaced.
Disappointing - WIFI is unable to stay connected for more than a 24 hours. Daily restarts are needed. No solution even after 4 months of this ridiculous behavior. SONY should admit this is a HW issue and offer replacements or solve it ASAP.
darklordtom said:
Disappointing - WIFI is unable to stay connected for more than a 24 hours. Daily restarts are needed. No solution even after 4 months of this ridiculous behavior. SONY should admit this is a HW issue and offer replacements or solve it ASAP.
Click to expand...
Click to collapse
Agreed
darklordtom said:
Disappointing - WIFI is unable to stay connected for more than a 24 hours. Daily restarts are needed. No solution even after 4 months of this ridiculous behavior. SONY should admit this is a HW issue and offer replacements or solve it ASAP.
Click to expand...
Click to collapse
I've never had this issue. I wonder if it's wifi ap/router dependent ?
Good day.
Because i have been having abnormal consumption with RCS Service, i tried this tutorial and it seems that the wifi problem that it sometimes takes long to connect has disappeared. (https://forum.xda-developers.com/sho...44&postcount=6)
And i now have a better battery life.
@Hansoliv
Hello
The link is wrong. :/
Burn02 said:
@Hansoliv
Hello
The link is wrong. :/
Click to expand...
Click to collapse
Oops, sorry
See this Thread the 6th post
https://forum.xda-developers.com/xperia-xz1-compact/help/how-to-deactivate-rcs-service-rich-t3730605
ninjazin said:
As my wife's S7 from Samsung also gets monthly updates then it's not really impressing
Sent from my G8441 using Tapatalk
Click to expand...
Click to collapse
And yesterday she not only for the may update but also Android 8.0. so now her one year older phone is more updated than mine, without treble :/
Sent from my G8441 using Tapatalk
I have problems with battery drain after this update. Before the update, the phone could be used for more than two days without recharging and now I have to recharge after 8 hours without much use. Consequently I have deleted almost all apps from my phone and did everything reasonable (yes, stamina mode is activated). No success. Sad.

General Accessibility Service Issue Fixed

https://www.reddit.com/r/GooglePixel/comments/sc7ken
Seems like Big G's dev team has fixed the accessibility services issue plaguing some of our devices to varying extremes. Hopefully the fix is implemented in the February patch!
I hope so as well, it's been killing the gaming and typing on this thing for me.
Once it's fixed I might finally have found love!
I just wish they confirmed it would be in our next update, instead of a "future build". They haven't inspired confidence in that particular model lately.
Indeed, it would be great if Google indicated the fix was coming in the Feb update. I do wonder if people are having varying levels of this issue since it locks up touch for some for just a few seconds. I wonder if it locks touch up completely for some and longer than the 2-3 seconds. I suppose anything is possible. Here's hoping it's sooner rather than later!
I already installed the February update and sadly the issue hasn't been fixed. But I am happy to report that the issue doesn't occur on Android 12L Beta 3. Staying on this for now.
zetsumeikuro said:
https://www.reddit.com/r/GooglePixel/comments/sc7ken
Seems like Big G's dev team has fixed the accessibility services issue plaguing some of our devices to varying extremes. Hopefully the fix is implemented in the February patch!
Click to expand...
Click to collapse
Unfortunately it wont be ever fixed completely. Just avoid using it if you can
"Working As Intended" - An Exploration into Android's Accessibility Lag
Android's Accessibility feature is known to cause UI lag. Is it a bug, or is it a feature? Why does it occur? We at XDA investigate the root cause.
www.xda-developers.com
Article from 2016
mdaka42 said:
Unfortunately it wont be ever fixed completely. Just avoid using it if you can
"Working As Intended" - An Exploration into Android's Accessibility Lag
Android's Accessibility feature is known to cause UI lag. Is it a bug, or is it a feature? Why does it occur? We at XDA investigate the root cause.
www.xda-developers.com
Article from 2016
Click to expand...
Click to collapse
I actually don't have this issue at all on my device. While some have a 2-3 second hang every time the battery drops 1%. Google has stated they have fixed the issue, also there are reports of individuals on 12L no longer having the problem while previously having it on 12.
zetsumeikuro said:
I actually don't have this issue at all on my device. While some have a 2-3 second hang every time the battery drops 1%. Google has stated they have fixed the issue, also there are reports of individuals on 12L no longer having the problem while previously having it on 12.
Click to expand...
Click to collapse
The article is not about this exact issue. You can read it if you are interested
Had this issue also, caused my "gesture plus".
Fun fact: this only happens when language is set to "German", switching to "English" solved it for me.
mdaka42 said:
The article is not about this exact issue. You can read it if you are interested
Click to expand...
Click to collapse
Gotcha, I'll give it a read. I'm always interested about learning more about how processes work in the backend.
god, i'll be so happy when this drops. i use a couple different things that use accessibility services, like third-party gestures, and i just kinda deal with my keyboard locking up now and then. will be great.

Question Issues afteratest update

S21fe updated to UI5.
Couple of issues.... Fingerprint reader sometimes doesn't work when phone hasn't been used for some time. When it happens I need to double tap the screen to wake it up and then scan my fingerprint again.
Also "back" gesture (where I swipe up from the right bottom of the screen) sometimes instead of going back brings up the list of background apps.
Both issues very annoying.
Anyone else experienced anything similar?
Try clearing the system cache. Double check all settings. If that flaws things get more complicated...
A factory reset may be needed, but hard to say if it will resolve the issues. Someone will need to try the latter if the former doesn't work. A global reset of settings is a less drastic option but it may not be enough and still take a lot of time.
This is one reason why I spurn upgrades on a platform that's fulfilling its mission. Lol, I'm still using UI 1.5, no glaring issues.
Unfortunately with latter versions an upgrade may resolve flaws in earlier post >1.5 variants. Tough choice once you are on Android 11 as there's no roll back on stock Samsung's for that. I wasn't locked into using 11 on my N10+'s and never will load it. 12 is even worse.
Roll back is an option for you if bootloader wasn't upgraded too. Eventually Samsung will fix it if it's a firmware/software glitch but don't hold your breath for that
blackhawk said:
Try clearing the system cache
Click to expand...
Click to collapse
With each major update, I always clean the system cache from the recovery !
jbs68 said:
With each major update, I always clean the system cache from the recovery !
Click to expand...
Click to collapse
That may not be enough if going from 11 to 12, etc.
Rule #1 - if the OS is fast, stable and fulfilling its mission let it be! You have little to gain and a lot to lose. Although there was a big security hole in 12, not sure if it was patched already or if the patch is in what you just install. Oddly that hole isn't in 9-11.
Gookill is a mess...
I have the same problem with fingerprint unlocking. It simply doesn't work (if I press the side button, it works). Some hours ago I wiped the system cache and after that, I didn't notice the described problem. I will see in the next few hours.
Now I changed "Fingerprints -> Show icon when screen is off" to "Tap to show" instead of "On always on display" which was the default after the upgrade to Android 13.
UPDATE: The phone still has the same problem. Sometimes it simply doesn't allow it to unlock with a fingerprint. The screen is locked as hell. Only the side button unlocks it.
If you go to Lock screen>Always On Display>Show always, does that solve your problem? Mine was set to "show for new notifications" only and the fingerprint icon would disapperar after locking it.
Mine was set to "Show for new notifications". As you suggested, I changed it to "Show always" and we will see, how it works. In my opinion, it is better to show display only when something happens. But something changed and problems occurred.
Report: it didn't help. I have found out that the issue appears if the phone is locked for a while and then a notification comes. This is the reason why this problem exists also while using Android Auto. It creates a notification when it connects ... and then the phone can be unlocked with a fingerprint until the side button is pressed. I'm sure this is a bug that didn't exist before the upgrade to Android 13.
no such issues here with the eu version. definitely an upgrade in every way.
After 3 days with Android 13 on snapdragon variant, only two minor issues found here : slow charging (2h20 from 0 to 100, less than 2h before) and an "unauthorized action due to modified device" screen when rebooting, disappearing by touching "OK" button. Don't know what is unauthorized but... well. I was rooted before, now stock unrooted and relocked bootloader. It doesn't seems to lock something, everything I use is working.
I have the same fingerprint issues after updating to UI5 (unlocking from turned off screen). Sometimes it works, sometimes it doesn't. It worked perfectly before I updated, didn't change any settings. Very annoying, hopefully it will be fixed in a future update.
d0j0m0j0 said:
I have the same fingerprint issues after updating to UI5 (unlocking from turned off screen). Sometimes it works, sometimes it doesn't. It worked perfectly before I updated, didn't change any settings. Very annoying, hopefully it will be fixed in a future update.
Click to expand...
Click to collapse
The recent update with the December security patch seens to have resolved this issue for me.
Edit: scratch that, still not fixed...
Edit2: turning off lock scrern mods in Galaxy MaxHz seems to help.
jbs68 said:
With each major update, I always clean the system cache from the recovery !
Click to expand...
Click to collapse
How does one do that?
xda-eh said:
How does one do that?
Click to expand...
Click to collapse
It's on the boot menu on Samsung's.
blackhawk said:
It's on the boot menu on Samsung's.
Click to expand...
Click to collapse
You're referring to accessing the recovery mode as explained here?
xda-eh said:
You're referring to accessing the recovery mode as explained here?
Click to expand...
Click to collapse
This. Some have said Android 12 needs to be plugged into the PC to access the boot menu, don't know as I run Pie and Q.
blackhawk said:
This. Some have said Android 12 needs to be plugged into the PC to access the boot menu, don't know as I run Pie and Q.
Click to expand...
Click to collapse
The link I provided and the one you did refer to the same thing. Only difference is my link also provides a way to do it via ADB. In any event, thanks for your response.

Categories

Resources