Related
Coming from Samsung here, so this feature is very new for me.
Does the knock to wake feature work if you're set on pattern lock? Or does it only work when you have knock code set as your security?
Reason I ask is because I initially had the knock code set as security, then changed to pattern after I set Android Pay. BUT, knock to wake has been working for me the past two days (even with the pattern lock ON)...until 2 hours ago.
Now the only way I can knock wake the device (or even access the second screen) is either to set the security as Knock Code, or press the power button.
Is this behavior normal? I found it weird that the second screen is untouchable with the pattern lock ON.
Knock On will work everytime regardless of your lock screen setting (double tap on the center of the screen to wake device up into lock screen).
Knock Code, however, need to be set to unlock your device, the pattern is of your choice.
Android Pay doesn't accept a knock code as a security measure. I was using it, then was forced to switch to pin after setting up Pay.
Ryu Kenshin said:
Knock On will work everytime regardless of your lock screen setting (double tap on the center of the screen to wake device up into lock screen).
Knock Code, however, need to be set to unlock your device, the pattern is of your choice.
Click to expand...
Click to collapse
ok so correct me if I'm wrong: regardless of your security settings, KNOCK ON will work to wake the device up. Yes?
In that case, something has gone wrong with mine as I can only do knock on when Knock Code is set. Even worse, the second screen shortcuts are only accessible in that mode as well.
I think I just encountered a similar if not the same problem but I'm not sure if it's an app or if it coincides with something I accidentally tapped in the hidden menu last night.
I had been using pattern unlock since I got the phone on friday and double tap to wake the screen was working fine along side fingerprint unlock, now double tapping doesn't work and the second screen does not respond when locked.
EDIT: I just tried knock pattern and it allowed me to wake the screen but the moment I switched back to pattern it stopped responding to screen wake tapping.
mastarpete said:
I think I just encountered a similar if not the same problem but I'm not sure if it's an app or if it coincides with something I accidentally tapped in the hidden menu last night.
I had been using pattern unlock since I got the phone on friday and double tap to wake the screen was working fine along side fingerprint unlock, now double tapping doesn't work and the second screen does not respond when locked.
EDIT: I just tried knock pattern and it allowed me to wake the screen but the moment I switched back to pattern it stopped responding to screen wake tapping.
Click to expand...
Click to collapse
sorry to hear about that, seems like you have exactly what I had. Knock on just stopped working out of nowhere.
Good news is, I did a factory reset and it fixed the issue. Albeit, without access to Titanium Backup, it's quite a chore right now to redo all of my setups. Trying LG Backup now just in case.
Give factory reset a try and hopefully it'll solve your issue as well.
baymon said:
sorry to hear about that, seems like you have exactly what I had. Knock on just stopped working out of nowhere.
Good news is, I did a factory reset and it fixed the issue. Albeit, without access to Titanium Backup, it's quite a chore right now to redo all of my setups. Trying LG Backup now just in case.
Give factory reset a try and hopefully it'll solve your issue as well.
Click to expand...
Click to collapse
Yeah I was kind of afraid I'd have to reset already, barely a week in, lol!
Thanks for letting me know a reset worked, hopefully it doesn't happen again.
I think @knifedroid had the answer. AndroidPay doesn't allow you to use knock. I have the same issue as well...well i guess it's not an issue...it's a feature.
Sent from my LG-H901 using Tapatalk
KwestJones said:
I think @knifedroid had the answer. AndroidPay doesn't allow you to use knock. I have the same issue as well...well i guess it's not an issue...it's a feature.
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Knock Code is a security method, Knock On is a feature that LG implemented at kernel level to wake up/turn off the device. The issue that we've been having is with the Knock On not functioning anymore.
Long story short the reset restored Knock On (wake).
Long version, I gave the LG Bridge software a shot to do a backup to the PC.
It let me backup just about everything including apps and data, including Humblebundle apps and stock homescreen layouts, so it's probably as close to tatanium as you ca get.
I Haven't gone through updates yet but so far Knock On is still working after a restore, I'll edit if that changes. *crossing fingers*
oh man I'm glad i came to peek this section for this, as i feel like i tapped something wrong in the hidden menu as well. i might wait a little bit to do a reset and see if someone finds out a way to keep the KnockON thing running when screen is off.
joachim123 said:
oh man I'm glad i came to peek this section for this, as i feel like i tapped something wrong in the hidden menu as well. i might wait a little bit to do a reset and see if someone finds out a way to keep the KnockON thing running when screen is off.
Click to expand...
Click to collapse
hey someone on another thread said that deleting all the fingerprints solved his Knock ON issues. Can you try this out?
baymon said:
hey someone on another thread said that deleting all the fingerprints solved his Knock ON issues. Can you try this out?
Click to expand...
Click to collapse
Just tried it, no luck. Both knock on and off are still not working.
The issue started for me last night after going to the hidden menu and enabling Fast Dormancy. Disabling it again doesn't help. I guess just avoid the hidden menu is the takeaway here.
Sent from my LG-H901 using XDA Free mobile app
pakraider said:
Just tried it, no luck. Both knock on and off are still not working.
The issue started for me last night after going to the hidden menu and enabling Fast Dormancy. Disabling it again doesn't help. I guess just avoid the hidden menu is the takeaway here.
Sent from my LG-H901 using XDA Free mobile app
Click to expand...
Click to collapse
ok, sorry bud. Hard reset did the trick for me, but it'll be good to know what caused this and what can we do to solve it.
Now that you mentioned it, I think my issue started after I was playing around with hidden menu as well. Although I didn't recall changing anything.
baymon said:
ok, sorry bud. Hard reset did the trick for me, but it'll be good to know what caused this and what can we do to solve it.
Now that you mentioned it, I think my issue started after I was playing around with hidden menu as well. Although I didn't recall changing anything.
Click to expand...
Click to collapse
Yeah, tbh it sounds like a software bug by LG. Just going to the hidden menu seems enough to break the knock on/off. Makes you wonder what else might be getting messed up too that we haven't noticed.
p.s. this thread is why XDA is awesome.. everyone thinking 'omg what happened?' only to see others in exactly the same boat.
This makes sense. I think my knock on stopped working after using the hidden menu to look at the dB on the LTE signal.
Sent from my SM-N900T using Tapatalk
So in this case of resetting, would I be able to just grab the system img and flash it without actually doing a hard reset? I don't want to have to set up everything, again.(i had forgotten it was going to reset when I unlocked the BL)
Just confirmed it. Knock on breaks when you try to enter the ims settings menu inside the hidden settings menu. It crashes, then knock on stops.
Sent from my SM-N900T using Tapatalk
I am having an issue where it is grayed out and stating something else has an administrator lock. Any idea on what's holding it up?
Sent from my LG-H901 using XDA Free mobile app
MacMitten said:
I am having an issue where it is grayed out and stating something else has an administrator lock. Any idea on what's holding it up?
Sent from my LG-H901 using XDA Free mobile app
Click to expand...
Click to collapse
That looks like you are in the android pay security options. If so, android doesn't think that knock is secure enough for androidpay. Don't think there is anything we can do about it yet.
If you decide to use android pay you cannot use KnockOn pattern unlock to open your phone.
Sent from my LG-H901 using Tapatalk
Is this possible. I've tried everything the fingerprint scanner doesn't work unless you have a secure lock screen. I have used knock code since I got the V10 along with fingerprint so I can use the fingerprint, but I don't want to have to put a knock code in if my fingerprint doesn't work or its on the table...
Anyone got a workaround? I'm still searching.
Matt
Does no one know how I can do this?
Matt
I'd like to know the same thing. I know LastPass just added fingerprint support (for marshmallow) and I'd love to be able to use my fingerprint to unlock that (when marshmallow comes) without having to have a secure lockscreen. I don't really care if someone can get into my phone. I just don't want to have to type in my password to use lastpass
I've searched around everywhere for this option .... I just don't think it exists.
So just don't use any lock to get into the phone now. I've got the stuff I want secure in locked files/apps section. Makes using and accessing the main functions of the phone much more accessible. Only doing this for a few days now as a test, but I think it'll be the way I keep it.
My Two Lock Screens Worth
I've addressed the issue another way. I added several more "trusted" places, devices, and connections as well as "trust while moving" which means as long as the phone senses it's on me, I'm at home, connected to Bluetooth devices I know, and more, there's no secure lock but fingerprint still unlocks it. Perfect. Still testing it
Matt
So i just updated to MM. Now, my fingerprint sensor/scanner(whatever you wanna call it) is acting up. There are times when it won't read my finger at all. Other times, i would have to try three or more times to get a good scan in. This usually happens when the phone has been on standby for at least 10mins. Unlocking the phone with the fingerprint sensor when you just(say 2-5mins) locked it is ok. It works as it should. Could it be a doze related bug? Is there anyone else experiencing this problem?
update: it does happen even if i just locked it. though not as often as when it had been on standby for a longer period. "/
My response got better with MM. Try a factory reset? How did you install MM?
eumanoid said:
So i just updated to MM. Now, my fingerprint sensor/scanner(whatever you wanna call it) is acting up. There are times when it won't read my finger at all. Other times, i would have to try three or more times to get a good scan in. This usually happens when the phone has been on standby for at least 10mins. Unlocking the phone with the fingerprint sensor when you just(say 2-5mins) locked it is ok. It works as it should. Could it be a doze related bug? Is there anyone else experiencing this problem?
update: it does happen even if i just locked it. though not as often as when it had been on standby for a longer period. "/
Click to expand...
Click to collapse
After scaning my fingerprint, sometimes I need to enter my password, it's not like this before I upgrade the device.
Yakkosmurf said:
My response got better with MM. Try a factory reset? How did you install MM?
Click to expand...
Click to collapse
dirty install with pcc. i'm reluctant to reset since i have 12gb worth of installation files. will it be ok if i backup-reset-restore?
iMaeGoo said:
After scaning my fingerprint, sometimes I need to enter my password, it's not like this before I upgrade the device.
Click to expand...
Click to collapse
right. at first i thought it wasn't reading my finger. but now that you mention it, it may have read my finger but asked for my key after since it didn't show an error. if it didn't read/recognize my finger, it should show an error saying so right? but it just vibrates and asks for my key. will clearing fingerprint data and re-adding them help? sure hope so.
eumanoid said:
right. at first i thought it wasn't reading my finger. but now that you mention it, it may have read my finger but asked for my key after since it didn't show an error. if it didn't read/recognize my finger, it should show an error saying so right? but it just vibrates and asks for my key. will clearing fingerprint data and re-adding them help? sure hope so.
Click to expand...
Click to collapse
If it vibrates and asks for a key, then you are probably using an app to lock the screen. On marshmallow, you have to lock the phone with the power button for the fingerprint sensor to work
eumanoid said:
right. at first i thought it wasn't reading my finger. but now that you mention it, it may have read my finger but asked for my key after since it didn't show an error. if it didn't read/recognize my finger, it should show an error saying so right? but it just vibrates and asks for my key. will clearing fingerprint data and re-adding them help? sure hope so.
Click to expand...
Click to collapse
I heard that Nexus based on MM has this problem, too.
Screen Lock Pro(Prahallad) on Play store may be useful.
---------- Post added at 10:12 AM ---------- Previous post was at 10:07 AM ----------
Sadman Khan said:
If it vibrates and asks for a key, then you are probably using an app to lock the screen. On marshmallow, you have to lock the phone with the power button for the fingerprint sensor to work
Click to expand...
Click to collapse
Thanks, when I use one-key lock, it'll always ask me for passwords.
iMaeGoo said:
I heard that Nexus based on MM has this problem, too.
Screen Lock Pro(Prahallad) on Play store may be useful.
---------- Post added at 10:12 AM ---------- Previous post was at 10:07 AM ----------
Thanks, when I use one-key lock, it'll always ask me for passwords.
Click to expand...
Click to collapse
Yep. I used to use the app "Soft Lock Screen" but now I can't anymore as I have to input pin if I use that to lock the phone hahaha
Sadman Khan said:
If it vibrates and asks for a key, then you are probably using an app to lock the screen. On marshmallow, you have to lock the phone with the power button for the fingerprint sensor to work
Click to expand...
Click to collapse
yes. i am using knock-off(double tap to turn off display) from smart launcher to lock my phone. i'll try disabling this and report back. thanks a bunch Khan.
Update: evrything is working fine now. Looks like it was a marshmallow issue as khan said. Too bad i can't use double tap to lock anymore.
Hi,
So I have this strange issue which I cannot figure out. I set up the knock code when I got the phone, as well as one fingerprint to unlock it. It works fine both ways in everyday use. But recently I wanted to add more fingerprints to my phone, and when I try to add them, I am prompted to input my knock code, which I do. The weird part is that the phone says that it's the wrong code. Now, I am sure that I am not inputting it wrong. It always unlocks my screen, just not the security options.
Is there an another code I am not aware of? Maybe a default one for the security options? Has anyone had an issue like mine, and can help me?
Thx in advance.
sbto said:
Hi,
So I have this strange issue which I cannot figure out. I set up the knock code when I got the phone, as well as one fingerprint to unlock it. It works fine both ways in everyday use. But recently I wanted to add more fingerprints to my phone, and when I try to add them, I am prompted to input my knock code, which I do. The weird part is that the phone says that it's the wrong code. Now, I am sure that I am not inputting it wrong. It always unlocks my screen, just not the security options.
Is there an another code I am not aware of? Maybe a default one for the security options? Has anyone had an issue like mine, and can help me?
Thx in advance.
Click to expand...
Click to collapse
Its definitely an issue with your device. I just checked and it works like it's supposed to. There is no other code for security options, it's the one and same, no matter PIN, PW or Knock Code.
So I got Ok Google to be detected even when the phone is turned off, but I can't seem to make it unlock the phone. I have the option turn on in the settings of the Google assistant ( Unlock with voice match) and when the device is turned off and I say Ok Google it asks me to input the pattern or finger print.
Is there some kind of permission I should give the assistant app so it's able to unlock the phone ?
Sent from my BLA-L29 using Tapatalk
No, you have to wait the next update .131, where huawei implements this function. I'm also waiting for it.
Elia934e said:
No, you have to wait the next update .131, where huawei implements this function. I'm also waiting for it.
Click to expand...
Click to collapse
As much as I'm enjoying the m10p emui still sucks but I hope they release Android P faster than others.
Sent from my BLA-L29 using Tapatalk
I'm sorry but why should it unlock the phone? That would be terrible for our security to be able to unlock one's phone completely by using just "ok google". The issue was the voice recognition to work on a locked screen and now it's fixed.
Aethergr said:
I'm sorry but why should it unlock the phone? That would be terrible for our security to be able to unlock one's phone completely by using just "ok google". The issue was the voice recognition to work on a locked screen and now it's fixed.
Click to expand...
Click to collapse
I have nothing to worry about when I'm at home and would like it to unlock my device with voice, plus it won't work as long as the device is locked like play music or something.
Sent from my BLA-L29 using Tapatalk
I still have to use a screen unlock method for google assistant. On 131
Wanted to ask the same question but I can't Poston XDA since I'm new. I was reading that this feature is implemented in the 132 version and they rolled it to Latin America. I am in the Europe zone and still on the 129, I'll wait a bit more.
As a digression, I come from stock android and when I switched to emui was really a pain, and still it is. There are many features that android stock implements beautifully that here are not present (vibration intensity control, screen lock notifications are not expandable in emui, wake up with ok Google and so on) and this is really a pity since the mate 10 pro is a really good piece of hardware. But yeah, hope never dies so I keep dreaming about a good emui version one day
nahlawy said:
So I got Ok Google to be detected even when the phone is turned off, but I can't seem to make it unlock the phone. I have the option turn on in the settings of the Google assistant ( Unlock with voice match) and when the device is turned off and I say Ok Google it asks me to input the pattern or finger print.
Is there some kind of permission I should give the assistant app so it's able to unlock the phone ?
Sent from my BLA-L29 using Tapatalk
Click to expand...
Click to collapse
How did you enable OK google with screen off? I can't seem to get this at all
kazprotos said:
How did you enable OK google with screen off? I can't seem to get this at all
Click to expand...
Click to collapse
Using Tasker https://forum.xda-developers.com/showthread.php?t=3713936
Sent from my BLA-L29
I'm on B137 C432, and it's the same, Google Assistant will wake up the phone with the keyword but won't unlock it.
Makes me think to ditch the mate 10 pro now
Sent from my BLA-L29
So, I've updated to the 137 version but even if the change log says so, I still cannot wake up my phone with voice. When in always on display nothing happens, when I do it in lockscreen it wakes but then it asks the combination for unlocking. Any hint here?
andre.nisti said:
So, I've updated to the 137 version but even if the change log says so, I still cannot wake up my phone with voice. When in always on display nothing happens, when I do it in lockscreen it wakes but then it asks the combination for unlocking. Any hint here?
Click to expand...
Click to collapse
Check in the assistant, settings > phone > unlock with voice match
Sent from my BLA-L29
nahlawy said:
Check in the assistant, settings > phone > unlock with voice match
Click to expand...
Click to collapse
It's enabled, but it works in lockscreen. The only problem is that after the lock combination appears
andre.nisti said:
It's enabled, but it works in lockscreen. The only problem is that after the lock combination appears
Click to expand...
Click to collapse
So I guess even updating won't solve this issue
Sent from my BLA-L29
So a quick update.
I went to Settings > Security > Lock screen > Smart lock
And I went to trusted voice, I disabled and re-enabled it, and now it unlocks my phone also when the screen is off.
Luinwethion said:
So a quick update.
I went to Settings > Security > Lock screen > Smart lock
And I went to trusted voice, I disabled and re-enabled it, and now it unlocks my phone also when the screen is off.
Click to expand...
Click to collapse
Gonna try that, thanks!
---------- Post added at 06:56 PM ---------- Previous post was at 06:33 PM ----------
nahlawy said:
So I guess even updating won't solve this issue
Click to expand...
Click to collapse
Luin method solves partially the problem, thanks! I can unlock the phone now from the unlock screen, from the always on display i still can't but it's still something
andre.nisti said:
Gonna try that, thanks!
---------- Post added at 06:56 PM ---------- Previous post was at 06:33 PM ----------
Luin method solves partially the problem, thanks! I can unlock the phone now from the unlock screen, from the always on display i still can't but it's still something
Click to expand...
Click to collapse
That's strange, I turned AOD on and okay Google will still unlock the pone.
Be aware that trusted voices will try to match much more points of your voice than when summing Google when the device is unlocked, try retraining voice model if needed.
Luinwethion said:
That's strange, I turned AOD on and okay Google will still unlock the pone.
Be aware that trusted voices will try to match much more points of your voice than when summing Google when the device is unlocked, try retraining voice model if needed.
Click to expand...
Click to collapse
Weird, it's not happening on my device. I retrained the voicebut no luck still
I used the work around here what helped with lock screen on. Now there was a Google app update and it's also working with Lockscreen turned off.