As the title implies, I can never get my phone to unlock via the fingerprint scanner. I have 2 fingerprints set up and everything in the settings is turned on and configured, but when I'm actually on the lock screen it tells me is unable to use fingerprints and to use my knock code.
Am I the only one having this issue?
Long live doodoo
djsbad said:
As the title implies, I can never get my phone to unlock via the fingerprint scanner. I have 2 fingerprints set up and everything in the settings is turned on and configured, but when I'm actually on the lock screen it tells me is unable to use fingerprints and to use my knock code.
Am I the only one having this issue?
Long live doodoo
Click to expand...
Click to collapse
Mine has worked great. One suggestion would be to setup another fingerprint but use one the same fingers you already did. For example, I use my left index finger to unlock so I added another fingerprint, but used that same finger and tried to completely use a different side of the finger while setting it up. This way the scanner has more of a surface area to read and unlock with.
I just tried that. I added 2 more fingerprints from the same fingers as you suggested. Unfortunately, it didn't work.
As soon as I press the power button to turn on the screen, the dialog pops up saying unable use fingerprints. Please try the knock code.
Long live doodoo
Try setting it up with a pattern lock instead of a knock code. That worked for someone else who had the same issue
djsbad said:
I just tried that. I added 2 more fingerprints from the same fingers as you suggested. Unfortunately, it didn't work.
As soon as I press the power button to turn on the screen, the dialog pops up saying unable use fingerprints. Please try the knock code.
Long live doodoo
Click to expand...
Click to collapse
Have you tried completely starting over with the fingerprints? The few times where it didnt read my print I got at least 3 or 4 attempts before it told me to use knock code, so thats weird.
MIKESTONY said:
Try setting it up with a pattern lock instead of a knock code. That worked for someone else who had the same issue
Click to expand...
Click to collapse
I didn't think of that. I'll give it a try and report back if it works or not.
Long live doodoo
Coycaine said:
Have you tried completely starting over with the fingerprints? The few times where it didnt read my print I got at least 3 or 4 attempts before it told me to use knock code, so thats weird.
Click to expand...
Click to collapse
Yeah I deleted the fingerprints several times and did the steps you mentioned in your first reply above. I still couldn't get anything to work.
Long live doodoo
djsbad said:
I didn't think of that. I'll give it a try and report back if it works or not.
Long live doodoo
Click to expand...
Click to collapse
This finally worked. It took a couple of times to get it to finally be able to use the fingerprints, but it worked.
Thank you.
Long live doodoo
Had this issue with nova launcher... Would work great stop, added prints again, work for a while... Nice little cycle ended up using lg 4.0 and no issues.
thunderbls said:
Had this issue with nova launcher... Would work great stop, added prints again, work for a while... Nice little cycle ended up using lg 4.0 and no issues.
Click to expand...
Click to collapse
I'm actually using nova launcher myself. After following the steps listed from a previous poster, i have had no issues at all. it took a few times, but then it started working and I haven't had any issues since.
Long live doodoo
I just had to delete my fingerprints once and it worked. I did it with the pattern lock
Sent from my VS987 using XDA-Developers mobile app
Related
Hello,
I set my phone up to use the screen lock pattern option but now I cant seem to get rid of it. I was having problems with NoLED and thought the screen lock was interfering with it so I disabled it but even now when I turn my screen off and on it asked for my pattern. I have to put it in but it no longer seems animated.
Obviously this would be a bug and what I need to do to disable the screen lock now?
Whew! You gave me a bit of a scare just now.
I hadn't set a lock pattern yet, so I did to test this for you. Sure enough, I got the same thing as you.
Set a lock pattern, then un-set it by selecting "none" in the Settings/Security/Screen Unlock section. I was still getting the unlock pattern even though it was supposedly non.
I managed to turn it off by going through the set a new pattern process, then setting it to none after confirming the new pattern. Give that a try.
The other thing you might try is to switch it to a pin and see if the pin can be turned off. (I haven't tried that.)
A 4 day NS user and I didn't even know about noled. What a cool idea to fix the annoying no led problem. Thanks for leading me to the app.
elusivepeanut said:
A 4 day NS user and I didn't even know about noled. What a cool idea to fix the annoying no led problem. Thanks for leading me to the app.
Click to expand...
Click to collapse
Yeah it is, worked well until I added a few more apps. So if you dont have many apps it works well. There must be a conflict somewhere but cant be bothered trying to figure out what other app is affecting it, still might be the phone lock as well. It could also be gingerbread, NoLED might not be updated for it.
distortedloop said:
Whew! You gave me a bit of a scare just now.
I hadn't set a lock pattern yet, so I did to test this for you. Sure enough, I got the same thing as you.
Set a lock pattern, then un-set it by selecting "none" in the Settings/Security/Screen Unlock section. I was still getting the unlock pattern even though it was supposedly non.
I managed to turn it off by going through the set a new pattern process, then setting it to none after confirming the new pattern. Give that a try.
The other thing you might try is to switch it to a pin and see if the pin can be turned off. (I haven't tried that.)
Click to expand...
Click to collapse
Thanks for that, did the same as you and turned it off. NoLED seems to work properly again. Looks like the lock affects NoLED.
Hi, I searched the forum but had no luck:
Completely new Nexus 5, White 16GB, and I have this issue:
When i receive and miss a call, as soon as the ringer stops the phone automatically shows the unlocked homescreen and it just stays there, instead of locking itself normally. This is really weird, and happens even if the phone is in my pocket (so it's not sensor-related like whatsapp pop-ups for example). Also not really safe i'd say. If I select another lockscreen method, it behaves normally (showing, for example, unlock pattern for a certain amount of time before turning the monitor off again.)
Anyone experiencing the same issue?
http://www.reddit.com/r/Nexus5/comments/1q04f7/nexus_5_unlocks_itself_after_a_missed_call/
This is the only other reporting I found on the web. Can anyone test this? It's really fast and easy, and I think this could be a pretty serious issue.
My phone (pin locked) doesn't do that. Phone stays locked. Is your phone kept unlocked?
jj14 said:
My phone (pin locked) doesn't do that. Phone stays locked. Is your phone kept unlocked?
Click to expand...
Click to collapse
Yes. I don't really like the pin/passcode unlock (also don't really need it). Classic slide is simple and fast enough, but it's crazy that it stays unlocked after a missed call.
Also, I noticed that it automatically enters the last application that was open the last time you locked it, creating even more concerns (last online on messaging applications, online status in facebook, ecc.)
Just imagine you boss calling you, with no luck, and founding out a second later you're online in Facebook. Just because you were ignoring your phone, while driving for example.
themcfly said:
Yes. I don't really like the pin/passcode unlock (also don't really need it). Classic slide is simple and fast enough, but it's crazy that it stays unlocked after a missed call.
Also, I noticed that it automatically enters the last application that was open the last time you locked it, creating even more concerns (last online on messaging applications, online status in facebook, ecc.)
Just imagine you boss calling you, with no luck, and founding out a second later you're online in Facebook. Just because you were ignoring your phone, while driving for example.
Click to expand...
Click to collapse
I agree - that should not be the expected behavior
nexus5 32gb here, exactly the same behavior.. I had to enable a pin/password unlock method because every missed call would unlock my phone, even in my pocket..
I have the same issue.
Maybe it is because of the app Light Flow Lite ?
mr_smith1 said:
I have the same issue.
Maybe it is because of the app Light Flow Lite ?
Click to expand...
Click to collapse
I thought this as well, but then I tried it on my friends N5 and had the same behavior, without light flow. I think many of us actually discovered this trying notifications in Light Flow (i bought the pro version) but it's not related to that.
kowloon12 said:
nexus5 32gb here, exactly the same behavior.. I had to enable a pin/password unlock method because every missed call would unlock my phone, even in my pocket..
Click to expand...
Click to collapse
Me too, but I hate it because I can't swipe down from the top to quickly see my notification without unlocking the device first.
Let me know if you guys have any advice on this issue, also report it in this thread to keep it bumped and see if anyone is reporting any solution.
themcfly said:
Me too, but I hate it because I can't swipe down from the top to quickly see my notification without unlocking the device first.
Click to expand...
Click to collapse
exactly this, it was so useful to just throw a glance to the notifications to decide if open them or simply clean them away
Yes same here, this looks to be a bug surely?
Sent from my Nexus 5 using xda app-developers app
OK thanks,
I reported the problem on google discussion (I copy/paste our first topic because you explained the problem very well ^^).
the URL:
"https://productforums.google.com/forum/#!category-topic/nexus/nexus-5/KML5nWW9q6o"
mr_smith1 said:
OK thanks,
I reported the problem on google discussion (I copy/paste our first topic because you explained the problem very well ^^).
the URL:
"https://productforums.google.com/forum/#!category-topic/nexus/nexus-5/KML5nWW9q6o"
Click to expand...
Click to collapse
Nice one, I have posted in that discussion as well. Hopefully we will get a response.
Others have the same problem, do you know how to report a problem to google ?
I just tried it on my phone, called from my desk number, missed call. It did open the phone all the way, but the screen turned back off in 5 seconds, per my settings.
My phones is currently stock, have not rooted or unlocked the bootloader yet. Only UI modification apps are Widgetzoid and Dashclock, I wanted to stay stock for a bit.
Sorry, that you are having issues. Unfortunately sometimes the easiest way to figure out what is causing the problems is to do a factory reset, and re-dowload your apps one by one, to see what is causing the problem.
Ok, but a several people have the same issue ...
Anyway, I think I will tri not to miss a call whenever the phone is in my pocket !
Zandeer said:
I just tried it on my phone, called from my desk number, missed call. It did open the phone all the way, but the screen turned back off in 5 seconds, per my settings.
Click to expand...
Click to collapse
I don't like setting the screen timeout so short, many thimes i just place the phone on my desk while messaging and I want the screen to stay on, for at least 2 minutes.
And when I lock my phone to keep it in my pocket, it's supposed to stay locked and ignore any unintended touches as soon as i slide to unlock, which was originally introduced to prevent an unlock by accident. Yes, I could lower my screen timeout to 5 seconds, but that does not solve the problem because still unintended touches can occur in that time frame.
themcfly said:
I don't like setting the screen timeout so short, many thimes i just place the phone on my desk while messaging and I want the screen to stay on, for at least 2 minutes.
And when I lock my phone to keep it in my pocket, it's supposed to stay locked and ignore any unintended touches as soon as i slide to unlock, which was originally introduced to prevent an unlock by accident. Yes, I could lower my screen timeout to 5 seconds, but that does not solve the problem because still unintended touches can occur in that time frame.
Click to expand...
Click to collapse
I wasn't sing o set your screen lock time to what I have it set at, I was just saying that it did re-lock. However, you are right, IMO it should not completely unlock the screen when the phone is ringing.
Though I have never not had a passcode on my phone, so not sure if that is how it always behaves. Was just trying to test and be helpful.
I sent a message to the google team, let's wait and see.
here is a link to see the bug :"http://www.youtube.com/watch?v=SSTq8Xhe6Kc&"
Zandeer said:
I wasn't sing o set your screen lock time to what I have it set at, I was just saying that it did re-lock. However, you are right, IMO it should not completely unlock the screen when the phone is ringing.
Though I have never not had a passcode on my phone, so not sure if that is how it always behaves. Was just trying to test and be helpful.
Click to expand...
Click to collapse
Thanks for testing, I was wondering if this could have been related to root / unlocked bootloader somehow but you have confirmed this is not the case as it happens on a totally stock phone.
good catch there. same issue here.
at least a Google employee has responded to the topic created HERE. Maybe that will expedite then pushing out an update ASAP.
Hi, it seems like my screen has gone haywire and the fix is to reboot the phone. I experienced twice within the last months so I did a factory reset and experienced it again today.
Here is a youtube video of what I am talking about. I didn't bother focusing on the screen for there was no need to show what was on it.
http://youtu.be/WBREioPgBkM
yeah mine did that twice the other day (for the first time), Hasn't done since. I havent updated to the latest update.
Crazy. I do have the latest updates so I guess it isn't that.
Pretty sure it only wanted to party all by itself, haha.
I've had the screen glitch out from the lock screen when I get a text notification. Sometimes when I double tap to open the text from the lock screen the screen will glitch out badly.
totalrecarl said:
I've had the screen glitch out from the lock screen when I get a text notification. Sometimes when I double tap to open the text from the lock screen the screen will glitch out badly.
Click to expand...
Click to collapse
Dude, you may be on to something! That's when it freaks out for me too. I get a text and then go to unlock and it then flakes out.
Which SMS app are you using? I am using Textra and have the screen locked with the pattern lock.
Something similar happened to me when I first got my HP Touchpad few years back. Usually this is an indicator of a malfunctioning screen. I would recommend that you get it replaced while it is still under warranty. You can simply tell them that it is intermittent and cannot be reproduced easily.
TallTommy said:
Dude, you may be on to something! That's when it freaks out for me too. I get a text and then go to unlock and it then flakes out.
Which SMS app are you using? I am using Textra and have the screen locked with the pattern lock.
Click to expand...
Click to collapse
Thats exactly when I saw it happen. I'm using Textra but don't have any pins or whatever on the lock screen.
mk3 said:
Thats exactly when I saw it happen. I'm using Textra but don't have any pins or whatever on the lock screen.
Click to expand...
Click to collapse
Same. I'm also using Textra. Good to know I'm not the only one with this bug.
totalrecarl said:
Same. I'm also using Textra. Good to know I'm not the only one with this bug.
Click to expand...
Click to collapse
so the solution so far is to not using textra .-D
App conflict for sure, delete offending app.
Based on this thread:
http://forum.xda-developers.com/lg-v10/help/knock-to-wake-t3239674
So far it's only a confirmed suspicion, but it's already happened to several people including myself. Accessing the hidden menu may break the knock on feature, even without doing any modification in it.
Possible Solutions:
-Hard Reset (100% working)
-Deleting Finger Prints (I've only seen this working on 1 person in another thread)
Please report if this has happened to you and if you've done something else to solve the issue. Thanks!
I go in the hidden menu a couple times a day to change RAT selection and have only had one issue. So I wouldn't say it's a 100% the hidden menu
Sent from my LG-H901 using Tapatalk
Nope, doesn't break it. Been in the hidden menu to access Engineering Mode a bunch of times already and knock-on works fine.
Went in there to unlock the APN fields. Knock-on works fine.
Sent from my LG-H901 using XDA Free mobile app
Guys, it only breaks, as I stated in another thread, if you open the IMS Settings (which causes a crash) in the hidden settings menu. It is 100% reproducible, but *ONLY* that setting causes the issue.
toastido said:
Guys, it only breaks, as I stated in another thread, if you open the IMS Settings (which causes a crash) in the hidden settings menu. It is 100% reproducible, but *ONLY* that setting causes the issue.
Click to expand...
Click to collapse
Nope that didn't break it either
@baymon - Funny how everyone notices this until you post a PSA about it then everyone has to try to rebuke it.
If it "breaks" (turns knock on, off) you can use the anycut type app from the play store and make a shortcut to the hidden menu knock on option to toggle it back on or off if you so chose (I turned mine off so it would stop turning on in my pocket).
toastido said:
@baymon - Funny how everyone notices this until you post a PSA about it then everyone has to try to rebuke it.
Click to expand...
Click to collapse
Obviously we need more data on this issue, there could be other variables in play as well but that's why we're raising the awareness of the knock on issue.
@toastido haha it's all good.
LancerV said:
I go in the hidden menu a couple times a day to change RAT selection and have only had one issue. So I wouldn't say it's a 100% the hidden menu
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
How do you get into the hidden menu? Tried quickshortcutcreator but can't find it.
sentry07 said:
How do you get into the hidden menu? Tried quickshortcutcreator but can't find it.
Click to expand...
Click to collapse
Dial 277634#*#
I'm anxiously awaiting everyone now saying their knock on is broken ?
Didnt break mine! Thanks for the info to get into hidden menu though
nope mine still works but i do have issues with the screen in calls but thats it. but but was that way when i got it.
i think your hidden menu theory is good but my knock doesnt work but it stopped after i did a rest because the apn got messed up and it wouldnt let me add a new one. so i found this out this problem seams random as hell and if i turn knock pattern on to unlock the phone the knock works to turn the screen on but not off. i also noticed my second screen doesnt have the flash light on it when off anymore. so i will be doing a reset tomorrow unless anyone knows how to get the secound screen apps back when the screen is off. i think those apps are related to the tap on
It did break mine. Went to menu and hit apn unlock. No crash or anything. I noticed it not working immediatly. Knock code does still work.
I had the issue also, then did a reset. But I want to add to the issue that it didn't only effect knock on, but the touchscreen didn't register anything altogether when screen off. Meaning, the second screen can swipe when screen off to show the quick toggles, it did not work during that time.
joachim123 said:
I had the issue also, then did a reset. But I want to add to the issue that it didn't only effect knock on, but the touchscreen didn't register anything altogether when screen off. Meaning, the second screen can swipe when screen off to show the quick toggles, it did not work during that time.
Click to expand...
Click to collapse
mines the same no quick toggles
Mines the same no quick toggles but i found the answer with out rest on another post. i figured it out that its just something crashing the hidden menu doesnt matter what even force closing causes this problem. which is what i did seeing that the first time i used it nothing happened but the second time when the problem happened i cleared all apps and it stopped working. i'm guessing they disable it if something crashes it.
the knock on actually just gets turned off. Here's the quote for the answer make sure both knock on settings are on and it works instantly so no reboot needed.
-LBT- said:
Get yourself Quick Shortcut Maker, launch it, change the search type to 'Normal', search for 'Knock On', click on 'Settings', then on 'Try'. On the next screen, switch Knock On back and forth and see if that works.
Click to expand...
Click to collapse
clockcycle said:
If it "breaks" (turns knock on, off) you can use the anycut type app from the play store and make a shortcut to the hidden menu knock on option to toggle it back on or off if you so chose (I turned mine off so it would stop turning on in my pocket).
Click to expand...
Click to collapse
you are a genius and life saver!!! thank you.
hidden menu did break it, confirmed.
Hey guys,
I never tried on Pie so I'm not sure if the problem happened there as well but after adding my fingerprints when I go to unlock, my fingerprints don't do anything. No errors or anything either.
The sensor detects them perfectly however when setting them up. I still have to use my pin. I'm on Android 10 international btw and T-mobile variant.
It started to work when I was outside so I'm guessing it's a brightness issue?
Anyone? It randomly works then doesn't. However it works perfectly everytime in apps. Just not to unlock my phone.
That is strange. Personally I would try to change my pin to a pattern to unlock and see if the fingerprints work for unlocking the phone. Try to delete and redo all the fingerprints. I know it is a pain because you will have to reset up all your apps that use fingerprints but I would try random various configurations until it works the way it should. Last resort is a factory reset. UGH.
jaseman said:
That is strange. Personally I would try to change my pin to a pattern to unlock and see if the fingerprints work for unlocking the phone. Try to delete and redo all the fingerprints. I know it is a pain because you will have to reset up all your apps that use fingerprints but I would try random various configurations until it works the way it should. Last resort is a factory reset. UGH.
Click to expand...
Click to collapse
Thanks I appreciate the reply! I'll give all of those a shot even if I have to factory reset which would suck.
*edit* tried all that besides factory reset and still not luck. Really weird. As this only happens in Ambient display and lock screen. Apps that use it work everytime.
If data reset does not cange anything, try unbrick tool. It seems like the problem with soft. Unbrick tool return your phone to factory state.
I got it working now after switching from Nova back to Oneplus launcher. I read a comment on a forum saying to disable double tap to lock screen in Nova or other things that mess with the lock screen. I need double tap so I just went back to Oneplus launcher. Working so far!
The_Keeper86 said:
I got it working now after switching from Nova back to Oneplus launcher. I read a comment on a forum saying to disable double tap to lock screen in Nova or other things that mess with the lock screen. I need double tap so I just went back to Oneplus launcher. Working so far!
Click to expand...
Click to collapse
Ummmm, I may be mistaken but did you mention that you were using Nova? No wonder you were having such a strange issue! LOL
jaseman said:
Ummmm, I may be mistaken but did you mention that you were using Nova? No wonder you were having such a strange issue! LOL
Click to expand...
Click to collapse
Nah that was my bad. I honestly didn't think that would be my issue lol. I appreciate the help though. I should've searched more.
The_Keeper86 said:
I got it working now after switching from Nova back to Oneplus launcher. I read a comment on a forum saying to disable double tap to lock screen in Nova or other things that mess with the lock screen. I need double tap so I just went back to Oneplus launcher. Working so far!
Click to expand...
Click to collapse
Thanks keeper. I had the same problem, and this solved it.
Yet, Nova is so much better then OP launcher, so I really like to find solution that will halp me to keep it.
eyalsa said:
Thanks keeper. I had the same problem, and this solved it.
Yet, Nova is so much better then OP launcher, so I really like to find solution that will halp me to keep it.
Click to expand...
Click to collapse
No problem glad to help for once and I would as well but so far I've haven't been able to find one. I never tried turning off double tap to lock screen in Nova maybe that would work? I needed that feature though.
I disabeled the sleep by double tap or home button in Nova, and I'm using Xposed Edge gesture to sleep. It seem to work fine now.