Related
Hi guys. I have a peculiar problem in my new Galaxy S3. Whenever I make a call, the screen remains on even though I have ticked the 'Auto screen off during calls' option in call settings. Also, whenever I input any numbers while in a call, the keypad does not hide. I mean I get the 'Hide' option but it doesn't do anything and the keypad stays on the display. Can anyone tell me if this is a known issue or am I the only one facing it? Is there any workaround this? I am on stock firmware (XXLF2) and haven't even rooted my phone yet. Please help me guys!
I have exactly the same problem. I know the proximity sensor works, because I tried the proximity sensor test app. But my phone does not turn off screen when in call.
i have same problem any one help us ?
I also have this problem.. and to make it worse, I can't seem to call out occasionally. I swipe to call, but nothing happens. I can't even dial out at times.. rebooting usually solves the issue, but the problem quickly comes back.
I'm not rooted, on stock rom. Anyone know what the issue is?
OK, it looks like for me, it was a conflict between Google Voice and the phone. Turning it off/disabling it fixes the problems I've been having. I'll have to see what exactly is causing the conflict, but at least everything works with it off.
BlueG2 said:
OK, it looks like for me, it was a conflict between Google Voice and the phone. Turning it off/disabling it fixes the problems I've been having. I'll have to see what exactly is causing the conflict, but at least everything works with it off.
Click to expand...
Click to collapse
Where exactly is the option for turning off Google Voice?
I looked in Applications All but couldn't find it.
Beards said:
Where exactly is the option for turning off Google Voice?
I looked in Applications All but couldn't find it.
Click to expand...
Click to collapse
Check under 'Voice', not Google voice. It's also an option on the Voice widget.
If that doesn't fix it, try rebooting and doing it again.
BlueG2 said:
Check under 'Voice', not Google voice. It's also an option on the Voice widget.
If that doesn't fix it, try rebooting and doing it again.
Click to expand...
Click to collapse
'Voice' was my search pattern. It's got to be there I'll find it.
Hi guys,
Did you find a solution to this problem yet? I have the same problem, and no matter what I do, I can not make it work. The screen is always on during a call. I am using the stock rom, without root, as it is.
------------
Nevermind. I fixed it by removing FSC ID, apparently it was interfering.
i had the same problem but it was fixed after i made a phone restart.
I have the same problem...
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
Hi guys,
I'm using moto g4 plus.
Because I've enabled greenify in accessibilty.
My phone asks for finger print or pin even when I'm at home. (I've set my home address as a trusted place)
Any help would be much appreciated.
thefallenangel19 said:
Hi guys,
I'm using moto g4 plus.
Because I've enabled greenify in accessibilty.
My phone asks for finger print or pin even when I'm at home. (I've set my home address as a trusted place)
Any help would be much appreciated.
Click to expand...
Click to collapse
In Greenify's Settings, enable Alternative Screen Off Mode. It is compatible with Smart Lock on most phones.
tnsmani said:
In Greenify's Settings, enable Alternative Screen Off Mode. It is compatible with Smart Lock on most phones.
Click to expand...
Click to collapse
Hello,
I have enabled Alternative Screen Off Mode.
But for some reason when i wake up my phone, the lock appears unlocked. When i swipe it up, it asks for PIN or Finger Print.
Further more, in accessibility i have enabled Norton & Greenify.
In device admin, i've enabled Norton & Greenify as well.
The issue is not with norton.
thefallenangel19 said:
Hello,
I have enabled Alternative Screen Off Mode.
But for some reason when i wake up my phone, the lock appears unlocked. When i swipe it up, it asks for PIN or Finger Print.
Further more, in accessibility i have enabled Norton & Greenify.
In device admin, i've enabled Norton & Greenify as well.
The issue is not with norton.
Click to expand...
Click to collapse
Please try deactivating the device-admin of Greenify. If you enabled the "Alternative screen-off", it's not needed any more.
Hi Oasisfeng,
Thanks!
Looks like my issue has been resolved
Hello,
The issue still persists.
Only if I remove greenify from accessibility, my smart lock works. I guess I'm left with no option but uninstall it.
oasisfeng said:
Please try deactivating the device-admin of Greenify. If you enabled the "Alternative screen-off", it's not needed any more.
Click to expand...
Click to collapse
I did this on my Oneplus 3. But still get a black screen after i use fingerprint unlock. When i uninstall greenify, it unlocks instantaneously. Could you please help me resolve this? All other features are working flawlessly.:angel:
grubber24 said:
I did this on my Oneplus 3. But still get a black screen after i use fingerprint unlock. When i uninstall greenify, it unlocks instantaneously. Could you please help me resolve this? All other features are working flawlessly.:angel:
Click to expand...
Click to collapse
The issue seems to be with your phone since Greenify works without issues on my OP3.
tnsmani said:
The issue seems to be with your phone since Greenify works without issues on my OP3.
Click to expand...
Click to collapse
Nope.. having the same problem on my friend's oneplus 3 too. It doesnt happen on each unlock but 60% of the time it does.
grubber24 said:
Nope.. having the same problem on my friend's oneplus 3 too. It doesnt happen on each unlock but 60% of the time it does.
Click to expand...
Click to collapse
hello. any update on this issue. seems to be interfering with smart lock on my OP3 as well...
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.
I have an issue guys. When both fingerprint and face unlock options are activated, there are times when using fingerprint to unlock, the screen remains locked with the message 'Slide to unlock after successful facial recognition'. In face recognition options, it is already set to 'Direct unlock'. I do not know why it does that. Any Mate users here who have the same issue? Is it sort of a software bug? Is it because I might have slightly missed the scanning point so that error kicks in?
Usually this happens when the screen is turned off, it scans it, then the display turns on but it pops the message 'Slide to unlock after successful facial recognition'.
Yep, I noticed that too. The phone unlocks directly if only face recognition is activated. When you add fingerprint you need to slide.
I had this issue until i reset now it unlocks perfectly with face unlock.
phil999 said:
I had this issue until i reset now it unlocks perfectly with face unlock.
Click to expand...
Click to collapse
What did you reset exactly? I tried removing and readding facial ID but that didnt fix anything
ch1lko said:
Yep, I noticed that too. The phone unlocks directly if only face recognition is activated. When you add fingerprint you need to slide.
Click to expand...
Click to collapse
I guess it only happens when you fail fingerprint tho, doesnt it? Still annoying
furiouszagreb said:
I guess it only happens when you fail fingerprint tho, doesnt it? Still annoying
Click to expand...
Click to collapse
Exactly, it is a software issue reported on Huawei's forum too.
When fingerprint fail (once or few times, not sure), Huawei decides that the phone requires an extra security step before unlocking, hence the annoying slide to unlock even with direct unlock.
I hope it gets resolved in a future update.
furiouszagreb said:
What did you reset exactly? I tried removing and readding facial ID but that didnt fix anything
Click to expand...
Click to collapse
I completely reset the phone
phil999 said:
I completely reset the phone
Click to expand...
Click to collapse
Sorry, in what way? Could you please instruct step by step so I dont fu*k sth up?