Related
Anyone else notice or experience a slower fingerprint unlock after applying the 8.1 OTA update? A VERY noticeable difference in unlocking speed after the update.
1up1up said:
Anyone else notice or experience a slower fingerprint unlock after applying the 8.1 OTA update? A VERY noticeable difference in unlocking speed after the update.
Click to expand...
Click to collapse
No issue here mate, still as fast as it was before on 8.0.0. Might wanna try another reboot to see if it fixes your issue. You could then always try a factory reset as well.
I just downloaded and reinstalled the 8.1 factory image. Went through and setup phone from today's backup and added fingerprints. While the phone was finishing downloading apps from backup, the fingerprint unlock was fast and normal as usual. After apps updated and restore finished, I restarted the phone. Immediately, the slow fingerprint unlock returned. I have very few apps and this wasn't an issue until after I applied the 8.1 OTA side load before the initial posting of this thread. Additional testing of the speed by pressing the power button then unlocking with fingerprint reader yields inconsistent unlock speeds. At this point, I do not want to say that maybe it's because of a particular app that is installed on the phone, but rather it's possibly a problem with 8.1.
Any thoughts?
To put it into perspective, the fingerprint unlock under normal speed feels almost "too sensitive" because it's so fast. Now it registers my fingerprint touch right away but is followed by a slight pause/stutter before unlocking the screen.
1up1up said:
To put it into perspective, the fingerprint unlock under normal speed feels almost "too sensitive" because it's so fast. Now it registers my fingerprint touch right away but is followed by a slight pause/stutter before unlocking the screen.
Click to expand...
Click to collapse
I have this exactly
I too am facing similar problems. My phone on 8.1 takes about 1.5s to unlock while it only took <1s on 8.0. A workaround I took was to have always on display activated. And I ain't a fan of the always on display.
Yup. First thing I noticed was this delay between when the fingerprint is actually recognized (vibrate), until I actually get visual on the screen. Around a second or more
I actually had this issue on 8.1 DP2. But since doing a fresh install of the 8.1 official release, my finger print reader is just as fast as 8.0. Maybe try a new fresh install.
SOLIDFND said:
I too am facing similar problems. My phone on 8.1 takes about 1.5s to unlock while it only took <1s on 8.0. A workaround I took was to have always on display activated. And I ain't a fan of the always on display.
Click to expand...
Click to collapse
I too, am not a fan of the "Always On" display but can confirm that this does fix the problem. Thanks for sharing your finding.
sn0warmy said:
I actually had this issue on 8.1 DP2. But since doing a fresh install of the 8.1 official release, my finger print reader is just as fast as 8.0. Maybe try a new fresh install.
Click to expand...
Click to collapse
Sadly, I actually went through a fresh 8.1 install but fingerprint scanner is still slow with ambient display off. Off to reinstalling my apps...
I found hit super hit or miss. When I flashed my rma phone to dp2 it was slow to unlock. When I flashed 8.1 final it was fast again. I had to flash 8.1 final again but this time the phone was slow to unlock. I got my new device flashed 8.1 on and it is thankfully unlocking quickly. I wish you all luck
I submitted it to Google under DP2 and it has been deferred to a future build... maybe re-submit under the final 8.1 as well??
https://issuetracker.google.com/issues/69984153
Today I also noticed a random "static pop" noise coming from the phone while Chrome browser was open. It was quite distinct and loud and happened twice.
SOLIDFND said:
Sadly, I actually went through a fresh 8.1 install but fingerprint scanner is still slow with ambient display off. Off to reinstalling my apps...
Click to expand...
Click to collapse
Same problem, gets fixed with always on display but if the screen is not on in between the seconds of pressing the power button and ambient display kicks in then the problem is still there. Also tried deleting the fingerprints and redoing the fingerprint initiation, but it did not help. The sensor registers the fingerprint by vibrating but screen gets on only after a second or more. sometimes though it is instantaneous. another problem for Google to fix I guess in next month update.
1up1up said:
To put it into perspective, the fingerprint unlock under normal speed feels almost "too sensitive" because it's so fast. Now it registers my fingerprint touch right away but is followed by a slight pause/stutter before unlocking the screen.
Click to expand...
Click to collapse
Same issue here since updated to 8.1
The fingerprint is recognized quickly (you fell the short vibration) but the screen turns on with a delay of about a second.
I have the same issue when I just press the Powerbutton - it also takes about a second until screen turns on.
Guys, I'm so disappointed with my Pixel 2 XL. Never had so many issues with a stock firmware phone.
Been running 8.1 through the beta for awhile now and haven't had any of these issues. Not sure if I'm just lucky or what but it's been humming along just fine. Just installed the 8.1 official over the 8.1 beta and haven't noticed anything as of yet. Will pay attention to see if I notice anything being slower.
I am also seeing the issue after updating to 8.1. It takes about 2 seconds for the screen to appear. AOD does make it faster but I can deal with it and hopefully google fixes it soon
I searched he'd the issue on google- obviously because I HAVE IT TOO. This is infuriating. This is major functionality. after 8.1 the finger print reader is slow AF. It feel like my old galaxy s4 that i just came away from when i would swipe to unlock it. How many times do we unlock these things a day? We just went from the fastest unlocking phone to the slowest. Why is this effed up? I'm pissed.
We have ppl whining about the freaking hamburger emoji having the cheese on the bottom and the wrong foam in the beer mug, meanwhile it takes forever to get into the phone to do anything much less get to the Emojis. How does BASIC functionality go BACKWARDS with an update?
What's even more infuriating is I can't go back to 8.0!!! Google doesn't allow it do they? I am coming to this phone off a Galaxy s4. One of the big benefits of the pixel family is the "fast updates."I saw someone argue that this isn't necessarily a plus sometimes these new Android versions slow a phone down, and it's done. Sometimes, like in this case, bugs are introduced. The very first update I took on this phone largely argues his point.
Another thing I'm noticing is the battery life seems to be dropping much faster. I'm wondering if it's the flash kernel 2.0 I installed though.
I will be filing a complaint on the link someone so kindly posted above (thank you), and I will be going into the chat option through the help menu on my phone to file a complaint there.
EDIT: it also seems like Google assistant isn't working now either. "Ok Google" brings her up. The mic registers my talking, but no results are displayed.
EDIT 2: I also forgot to mention that along with the slow unlock the swipe function on the finger print reader has been altered. Smiling up and down to toggle the notification drawer is very inconsistent and buggy. I have the finger print quick action app installed. I had a single tap set up to lock the screen. I had my finger print reader un/locking the phone and toggling the notification drawer. While the notification drawer has always been a little buggy, it was VERY functional and very acceptable. Something has changed on the reader so it is having a harder time differentiating between the different movements. Now it usually registers a swipe as a tap and the screen locks. I expected this to happen when I first downloaded the app on 8.0, but I was pleasantly surprised when everything worked through the sensor. Now I am very disappointed. The issue is NOT constant. It comes and goes. Idk why it does that. I'll be seeing if I can figure out why. I will NOT be activating the always on screen as a means to circumvent this issue. I don't want burn in. I've been concerned with that issue associated with always on before the pixel showed up.
jbarcus81 said:
I submitted it to Google under DP2 and it has been deferred to a future build... maybe re-submit under the final 8.1 as well??
https://issuetracker.google.com/issues/69984153
Click to expand...
Click to collapse
I want to jump on board and file an issue too. What do I select the issue as?it's not a developer preview. Is it android system issue? Framework?
fearfighters said:
I have this exactly
Click to expand...
Click to collapse
-deleted
---------- Post added at 06:08 PM ---------- Previous post was at 06:02 PM ----------
1up1up said:
To put it into perspective, the fingerprint unlock under normal speed feels almost "too sensitive" because it's so fast. Now it registers my fingerprint touch right away but is followed by a slight pause/stutter before unlocking the screen.
Click to expand...
Click to collapse
Same here
im on the latest january patch (Thats when i noticed the issue more) and now my fingerprint rarely works. Ive tried cleaning the sensor with a mild soap and a good rinse and its good for half a day. I've tried deleting the prints and re doing them but most of the time it wont even read my finger period!
Anyone else with this issue? Should i go back to december?
I have a stutter with mine but it still works. I imagine Google will address in an upcoming release. Also, mine is not related to the Jan security patch.
Sent from my Pixel 2 using Tapatalk
still on december, works super inconsistently. half the time it doesnt recognize and i get locked out and gotta do the pattern unlock. the other day i tried to reset the finger prints and that UI would tell me the sensor is dirty...but its not. its kinda annoying.
Hi guys,
I recently upgraded my LG G7 thinq G710EAW to G710EAW10e_00_OPEN_HK_DS_OP_1005 through LG Bridge. Done that the usual way, all went fine.
Now I realize that my fingerprint sensor occasionally stops working. To be precise, after the phone has been idle for a few minutes in my pocket or charging. It takes a few seconds to a few minutes until it starts working again. I did a reset and the issue came back. When the phone is in use, the sensor does work. The LG diagnostic utility also detects the issue.
I have seen another user with an Indian FW has a similar problem. Any ideas?
Cheers,
Boono
Not a single issue with the same firmware.
I have the same issue, but with the Hong kong version (V10e-HKG-XX with October 2018 security patch installed). Seems to be more random for me, about 30% of the time it doesn't work, or only detects my finger after a few seconds, quite annoying. I've already reset my fingerprint but no change.
Just a heads up:
The function 'reset app preferences' in settings does the trick, at least temporarily. The downside is that after using this, you have to allow each app to use certain functions, such as location and VPN again.
Same issue with pie latest update in india. Doesnt work 30% times.
My LG G7 is a Verizon Wireless model that is not rooted. Over the last few weeks, the fingerprint sensor has been working only part of the time. Mostly, when I hit it with the phone locked, it will do nothing. Then I push the power button to get the screen to light up, and it leaves me at the knock code screen. 95% of the time, the fingerprint sensor will work at this time (yes I know I need to use the knock code when I boot the phone, before the sensor will work). A couple of days ago, the sensor would not work at all, so I went in and deleted some stored fingerprints. When I tried to enter new ones, I instantly got a message on the screen telling me the sensor was not working and to contact a customer center.
So, I did a factory reset and set the phone up as a new phone, figuring some setting was wrong, or an app messed with things. No luck. Still a partially working fingerprint sensor. Strange thing is, I then booted into safe mode and the sensor works 100% of the time. In regular mode though I may be able to wake the phone 5 times in a row, and then for the next 10 times nothing.
A short time after these issues started, I started getting a WiFi issue in that my phone will not connect to my work's "Public_Access" WiFi. It connects up to my home WiFi, and other WiFi, but not at work anymore. My tablet connects at work, and everyone else's phone connects, but not mine. I get a "Obtaining IP Address.." message, and every once in a while it will flash the word "Saved", but no luck in connecting. Signal strength is "good" to "excellent". Link speed is normally around 144 Mbps or higher, frequency is either 2.4 or 5Ghz, and security is "None". None for proxy, and I'm DHCP. If I go to static settings, the IP and gateway look like numbers from home.
Anyone else having these issues? anyone found any workarounds?
andygold said:
My LG G7 is a Verizon Wireless model that is not rooted. Over the last few weeks, the fingerprint sensor has been working only part of the time. Mostly, when I hit it with the phone locked, it will do nothing. Then I push the power button to get the screen to light up, and it leaves me at the knock code screen. 95% of the time, the fingerprint sensor will work at this time (yes I know I need to use the knock code when I boot the phone, before the sensor will work). A couple of days ago, the sensor would not work at all, so I went in and deleted some stored fingerprints. When I tried to enter new ones, I instantly got a message on the screen telling me the sensor was not working and to contact a customer center.
So, I did a factory reset and set the phone up as a new phone, figuring some setting was wrong, or an app messed with things. No luck. Still a partially working fingerprint sensor. Strange thing is, I then booted into safe mode and the sensor works 100% of the time. In regular mode though I may be able to wake the phone 5 times in a row, and then for the next 10 times nothing.
A short time after these issues started, I started getting a WiFi issue in that my phone will not connect to my work's "Public_Access" WiFi. It connects up to my home WiFi, and other WiFi, but not at work anymore. My tablet connects at work, and everyone else's phone connects, but not mine. I get a "Obtaining IP Address.." message, and every once in a while it will flash the word "Saved", but no luck in connecting. Signal strength is "good" to "excellent". Link speed is normally around 144 Mbps or higher, frequency is either 2.4 or 5Ghz, and security is "None". None for proxy, and I'm DHCP. If I go to static settings, the IP and gateway look like numbers from home.
Anyone else having these issues? anyone found any workarounds?
Click to expand...
Click to collapse
By any chance are you using VZW Messenger?
I'm having the same issue with the fingerprint sensor. The only workaround I've found is to reboot the phone, then it will start functioning again for a little awhile. Very bizarre.
I also recently started having issues with the fingerprint scanner. Since a lot of people have this issue I'm starting to think it is software related.
andygold said:
My LG G7 is a Verizon Wireless model that is not rooted. Over the last few weeks, the fingerprint sensor has been working only part of the time. Mostly, when I hit it with the phone locked, it will do nothing. Then I push the power button to get the screen to light up, and it leaves me at the knock code screen. 95% of the time, the fingerprint sensor will work at this time (yes I know I need to use the knock code when I boot the phone, before the sensor will work). A couple of days ago, the sensor would not work at all, so I went in and deleted some stored fingerprints. When I tried to enter new ones, I instantly got a message on the screen telling me the sensor was not working and to contact a customer center.
So, I did a factory reset and set the phone up as a new phone, figuring some setting was wrong, or an app messed with things. No luck. Still a partially working fingerprint sensor. Strange thing is, I then booted into safe mode and the sensor works 100% of the time. In regular mode though I may be able to wake the phone 5 times in a row, and then for the next 10 times nothing.
A short time after these issues started, I started getting a WiFi issue in that my phone will not connect to my work's "Public_Access" WiFi. It connects up to my home WiFi, and other WiFi, but not at work anymore. My tablet connects at work, and everyone else's phone connects, but not mine. I get a "Obtaining IP Address.." message, and every once in a while it will flash the word "Saved", but no luck in connecting. Signal strength is "good" to "excellent". Link speed is normally around 144 Mbps or higher, frequency is either 2.4 or 5Ghz, and security is "None". None for proxy, and I'm DHCP. If I go to static settings, the IP and gateway look like numbers from home.
Anyone else having these issues? anyone found any workarounds?
Click to expand...
Click to collapse
By any chance are you using VZW Messenger? It was an update to VZW Messenger that caused the issue for me. Next update resolved it.
OnceAMatrixMan said:
By any chance are you using VZW Messenger? It was an update to VZW Messenger that caused the issue for me. Next update resolved it.
Click to expand...
Click to collapse
I do have Messenger on the phone. It is NOT set as my default messaging app as I do not like it. Only reason I have it is because too many of my colleagues send me messages through it, which I can't open any way else that I know of. I'll look for an update and see if that helps. If not, I'll delete it and check again.
Thank,
Andy
Last update to Messenger I have is from April 9th. I looked for a more recent update but no luck.
Just deleted Messenger, and rebooted. After the initial need to enter the knock code, I slept the phone by tapping the power button (sorry if my terminology is off). 4 different fingers then and no joy (from the sleeping phone). If I hit the power button, the screen lights up and leaves me at what I guess is the lock screen showing recent email and calendar events. From there, I can successfully (still about 95% of the time) use the fingerprint sensor or the knock code to unlock the phone. But from a screen-off, sleeping mode, the fingerprint is still in a maybe it will work, maybe it won't situation.
If I have the same problem for about two weeks approximately install youtube vanced and yowhatsapp I do not know if it will be that but it is very annoying I hope lg update soon but I do not think I have the Indian version
Have same model and had same issues. I recently found out that I was missing 3 updates. December update started these issues. I'm now on the 10j version and so far haven't noticed the issue. But it's only been a day or so.
redbar0n11 said:
Have same model and had same issues. I recently found out that I was missing 3 updates. December update started these issues. I'm now on the 10j version and so far haven't noticed the issue. But it's only been a day or so.
Click to expand...
Click to collapse
I am also on 10j, and the issues are still there in regards to the fingerprint sensor....although for some unknown reason, after weeks of no WiFi at work, my phone finally decided to hook up to my work WiFi yesterday afternoon, and this morning when I got into work it instantly hooked up to it again. So, hopefully the WifI issue has been rectified. I guess I should somewhat count my blessings as WiFi is more important to me than fingerprint sensor, in the big scheme of things!
There has to be a software/firmware issue going on though as the sensor seems to be most troublesome when the phone is sleeping. Once the lockscreen is on, although there are still issues, it works 95% of the time. That makes me believe it's not a hardware issue.
I have Verizon also. It may help if all of you download the latest kdz for Verizon and reflash it vs factory reset. Using the lg up method by lamemonster. I do it all the time when I cross flash kdz as well as flashing back to Verizon. Hope this helps.
My G7 EAW is the same, fingerprints flicker. However, I removed the back cover and corrected the fingerprint, and it worked normally
netookska05 said:
I have Verizon also. It may help if all of you download the latest kdz for Verizon and reflash it vs factory reset. Using the lg up method by lamemonster. I do it all the time when I cross flash kdz as well as flashing back to Verizon. Hope this helps.
Click to expand...
Click to collapse
can you link to or specify that exact flashing method? nothing works for me, second piece of new hardware, no results.
Dear Friends
A50 current version A505FDDU1ASE3 / A505FOJM1ASE2 / A505FXXU1ASE2, Security patch level 1 May 2019
The issue: very slow FP reading plus Face reading is not good, it can open the device with eye closed face, even with the diagonal angle too, which is dangerous, it means anybody can unlock your phone while you sleep.
I have logged the call with Samsung support and they advised to upgrade to the latest version through the phone, which I did. and asked to delete the registered FP and Face, and re-register it.
I did, the problem remains the same... anybody found a similar issue?
FP reader posts are dime a dozen in this forum. To provide my opinion, the FP reader was extremely poor in March, significantly improved in April and now seems to be working at the level allowed by the hardware.
It takes less than a second to completely unlock using the FP reader, but for that you have to register your FP in the various positions you would normally unlock it and then make small adjustments. Don't follow any guide telling you to register using specific movements. This is what works best for me.
The Face Unlock is extremely insecure as it unlocks with photos and closed eyes. It is there only for convenience.
saifeesl said:
Dear Friends
A50 current version A505FDDU1ASE3 / A505FOJM1ASE2 / A505FXXU1ASE2, Security patch level 1 May 2019
The issue: very slow FP reading plus Face reading is not good, it can open the device with eye closed face, even with the diagonal angle too, which is dangerous, it means anybody can unlock your phone while you sleep.
I have logged the call with Samsung support and they advised to upgrade to the latest version through the phone, which I did. and asked to delete the registered FP and Face, and re-register it.
I did, the problem remains the same... anybody found a similar issue?
Click to expand...
Click to collapse
I have been facing the same issue. I got my phone on my birthday in March month; I was excited about the Samsung A50 device, but when I set the screen lock using fingerprint, it gives delay. Also, I have the latest version of Android 9. Still, it troubles me.