I have tested OK Google to respond to my commands , from sleep, for the past few days. with positive results.
Ok Google, responds when screen is off /sleep mode.
If your data is on, it will return a result eg Weather report, time eg.
I have tested it with lock screen.
Fingerprint, Pin working fine.
Also no lockscreen, working fine.
However it cannot turn screen on
As Google, is enabled in my Edge Lighting settings
when i say Ok Google, my Edge Lighting "lights up " and Ok Google will respond to my command.
( See screenshot.)
On my previous handsets Ok Google only worked
when screen was on.Never from sleep /screen off.
Any alternative info, results ?
but what ?
this is good news.
Ok Google works, but....
if screen can turn on, it would be 100 %
Best scenario will be to try youself and see what your results is.?
Same or otherwise?
As in past,
Xda members using Samsung devices
eg Note 5 or S8 etc could not get Ok to wake from
sleep /off. Samsung restricted ?
I posted OK Google results as there's
been a few threads on older to current devices
try to get Ok Google to wake/respond, from sleep.
Odd. My Note 8 screen will turn on and unlock when I say "OK Google". I've only tested this at home though, and I have Smart Lock keep my phone bypass fingerprint/PIN at home. Will try later somewhere else.
Wait, I just noticed on Smart Lock setting that there's a section for "OK Google detection". Maybe you have yours turned off? Say "Smart Lock" to Bixby or go to Settings>Lock Screen and Security>Smart Lock>Trusted Voice>OK Google detection and turn on the two options there ("say 'OK Google' at any time" and "Trusted Voice")
I've been using Bixby and everything seems to work OK and if she has a hiccup I help her with it (trying to build my pay points lol) but yeah try with Bixby and see if there is a difference
willcor said:
I have tested OK Google to respond to my commands , from sleep, for the past few days. with positive results.
Ok Google, responds when screen is off /sleep mode.
If your data is on, it will return a result eg Weather report, time eg.
I have tested it with lock screen.
Fingerprint, Pin working fine.
Also no lockscreen, working fine.
However it cannot turn screen on
As Google, is enabled in my Edge Lighting settings
when i say Ok Google, my Edge Lighting "lights up " and Ok Google will respond to my command.
( See screenshot.)
On my previous handsets Ok Google only worked
when screen was on.Never from sleep /screen off.
Any alternative info, results ?
Click to expand...
Click to collapse
is this with the stock launcher?
danon.brown said:
is this with the stock launcher?
Click to expand...
Click to collapse
I'm using Nova Prime.
However, i switched over to stock launcher, TouchWiz /Samsung Experience, and it was working fine.
As stated in previous threads (in past) you could not
wake device with Ok Google.
Yes with the Note 4 or previously you could.
With Note 5 etc it was suddenly not possible.
(Samsung ?)
harveydent said:
Odd. My Note 8 screen will turn on and unlock when I say "OK Google". I've only tested this at home though, and I have Smart Lock keep my phone bypass fingerprint/PIN at home. Will try later somewhere else.
Wait, I just noticed on Smart Lock setting that there's a section for "OK Google detection". Maybe you have yours turned off? Say "Smart Lock" to Bixby or go to Settings>Lock Screen and Security>Smart Lock>Trusted Voice>OK Google detection and turn on the two options there ("say 'OK Google' at any time" and "Trusted Voice")
Click to expand...
Click to collapse
Yes , when i tested it Smart Lock was off/not enabled ,but configured .
I don't use lockscreen ,
as phone is in a case .So Smart Lock won't work
OK Google wake up ,
works overall without lock screen or lock screen with Smart lock enable or not .
Point is ,
that you could not wake OK Google from sleep ( Samsung restricted ?)
Question is ,
what did Samsung do ,that Ok Google works .?
or did Samsung "slip up "/ bug ,that it works.?
and this( not turning screen on ) is the reason why it works fine , but does not/.cannot,turn screen on ?
Maybe later Samsung restricts it again .?
willcor said:
Yes , when i tested it Smart Lock was off/not enabled ,but configured .
I don't use lockscreen ,
as phone is in a case .So Smart Lock won't work
OK Google wake up ,
works overall without lock screen or lock screen with Smart lock enable or not .
Point is ,
that you could not wake OK Google from sleep ( Samsung restricted ?)
Question is ,
what did Samsung do ,that Ok Google works .?
or did Samsung "slip up "/ bug ,that it works.?
and this( not turning screen on ) is the reason why it works fine , but does not/.cannot,turn screen on ?
Maybe later Samsung restricts it again .?
Click to expand...
Click to collapse
there is an option in the Google settings "Say ok Google anytime"
danon.brown said:
there is an option in the Google settings "Say ok Google anytime"
Click to expand...
Click to collapse
Yes, all my settings are correct.
The option you refer to, I'm aware of, it's enable.
My take on Ok Google waking screen, (which
it had never over past years done) , is Samsung
restricted it in favour of S voice and now with Bixby.
However somewhere they let it "slip" and Ok Google
wakes up from sleep.
My take on this us if Samsung realizes
it, they will again restict Ok Google wake up.
Even though on other handset brands, Ok
Google wakeup works fine.
Just on Samsung phones i believe it's a issue.?
Otherwise my Ok Google and Google Assistant and Bixby is working 100 %.
No other issues with them.
I don't understand what your problem is. You're saying it is waking up but not waking up in some circumstances? Samsung hasn't restricted anything on this phone (Note 8) as far as I can tell. I'm able to get my screen to unlock from sleep by saying "Okay Google." The phone unlocks and the screen turns on and goes to the Assistant app as expected.
What exactly is wrong on your end?
This is also on my s7,s8. I don't think it's note 8 specific.
Sent from my SM-N950U using Tapatalk
When I say Ok Google...all I get is a buzz...then a buzz after my command...but no other results.
SiNJiN76 said:
When I say Ok Google...all I get is a buzz...then a buzz after my command...but no other results.
Click to expand...
Click to collapse
You may have to clear cache of the Google app and set it up again. I had to do that after I installed Nova and turned on the hotword button.
Sent from my SM-N950U using Tapatalk
danon.brown said:
You may have to clear cache of the Google app and set it up again. I had to do that after I installed Nova and turned on the hotword button.
Sent from my SM-N950U using Tapatalk
Click to expand...
Click to collapse
Nice! That worked. Prior to it...I guess if I unlocked the phone real quick, it would give me the answer. But now it just does it with the screen off. Thanks. :good: Now is there a way to get a chime instead of a buzz?
After setting up voice and resetting data. Google assistant was reset and setup. Now the Screen turns on when I say OK Google. Ok. Worked Once.
I just wish it would by pass my pin and or fingerprint but I understand anyone that may sound like me could say ok Google and get into my phone....but it would be dope if I say ok Google and it bypasses locks because it knows my voice specifically
peacey8 said:
I don't understand what your problem is. You're saying it is waking up but not waking up in some circumstances? Samsung hasn't restricted anything on this phone (Note 8) as far as I can tell. I'm able to get my screen to unlock from sleep by saying "Okay Google." The phone unlocks and the screen turns on and goes to the Assistant app as expected.
What exactly is wrong on your end?
Click to expand...
Click to collapse
I'm not just talking about Note 8.
The past few years, on on previous Samsung
devices, you could not wake Ok Google from
sleep.
There were quite a few threads (over the years) discussing this issue and how to "fix" issues.
It was obvious from previous thread discussions that Samsung had something to do with phone not able to wake from sleep. (Restricted?)
Otherwise Ok Google worked fine.
I can recall the last Samsung device, that could do this
eg. waking from sleep and responding to commands, was my Note 4.
In my case with Note 8, Ok Google works fine, waking from sleep and responding to commands..
However my screen lights up, but does not turn screen on.
Screen stays black, but Ok Google working fine.
I'm looking to see if other members have a similar
issue /experience, with Ok Google waking etc, but not turning screen on.?
On your side,
it seems like you got no issues with
Ok Google turning screen on.
danon.brown said:
This is also on my s7,s8. I don't think it's note 8 specific.
Click to expand...
Click to collapse
Yes i agree.
It's not just Note 8.
I had this issues since Note 5 days.
This is why i maintain Samsung
had something to do with it (over the years)
Maybe as result of Knox and security issues.,who knows?
But now on Note 8,
Ok Google is able to wake from sleep again.
willcor said:
I'm not just talking about Note 8.
The past few years, on on previous Samsung
devices, you could not wake Ok Google from
sleep.
There were quite a few threads (over the years) discussing this issue and how to "fix" issues.
It was obvious from previous thread discussions that Samsung had something to do with phone not able to wake from sleep. (Restricted?)
Otherwise Ok Google worked fine.
I can recall the last Samsung device, that could do this
eg. waking from sleep and responding to commands, was my Note 4.
In my case with Note 8, Ok Google works fine, waking from sleep and responding to commands..
However my screen lights up, but does not turn screen on.
Screen stays black, but Ok Google working fine.
I'm looking to see if other members have a similar
issue /experience, with Ok Google waking etc, but not turning screen on.?
On your side,
it seems like you got no issues with
Ok Google turning screen on.
Click to expand...
Click to collapse
Try clearing the cache of the Google app and setting it up again.
Sent from my SM-N950U using Tapatalk
Related
Got my Gear Live yesterday. The raise arm gesture was flaky compared to my Gear 1 but it was no big deal. Today the raise arm gesture doesn't work at all. My Gear Live does not have notifications disabled. I've reset the Gear multiple times, uninstalled and re-installed the android wear software multiple times (cleared cache and data too) and made sure it was unpaired and re-paired on my phone. If my screen is set to off, it will never come back on unless I press the button or touch my screen. If my screen is set to always be on, it will stay in the lower brightness mode until I touch the screen or press the button.
It seems like the motion sensing or the gesture itself is totally broken after only a day. Anyone else have issues with the gesture? (flakiness or otherwise)
novadaemon said:
Got my Gear Live yesterday. The raise arm gesture was flaky compared to my Gear 1 but it was no big deal. Today the raise arm gesture doesn't work at all. My Gear Live does not have notifications disabled. I've reset the Gear multiple times, uninstalled and re-installed the android wear software multiple times (cleared cache and data too) and made sure it was unpaired and re-paired on my phone. If my screen is set to off, it will never come back on unless I press the button or touch my screen. If my screen is set to always be on, it will stay in the lower brightness mode until I touch the screen or press the button.
It seems like the motion sensing or the gesture itself is totally broken after only a day. Anyone else have issues with the gesture? (flakiness or otherwise)
Click to expand...
Click to collapse
Mine works fine with always-on enabled. If anything it works too well. I wish I could turn the functionality off because my screen is always waking up when I don't want it to.
There were complaints that it was too sensitive, perhaps the latest update has toned it down a little too much.
You do now need a definite arm movement to make it come on.
Lift the arm and roll the wrist around towards you.
Rik
I've had mine since Monday and the gesture worked great. About half way through the day yesterday the gesture completely stopped working. I tried to reboot, factory reset but nothing worked. Eventually I held the power button down for about 10 seconds in order to bring up the power menu. Instead the watch just rebooted itself and after that, the gesture started working again. Weird.
czonin said:
I've had mine since Monday and the gesture worked great. About half way through the day yesterday the gesture completely stopped working. I tried to reboot, factory reset but nothing worked. Eventually I held the power button down for about 10 seconds in order to bring up the power menu. Instead the watch just rebooted itself and after that, the gesture started working again. Weird.
Click to expand...
Click to collapse
What the hell..... I've held down the power button before and the menu usually pops up. I just tried this and it worked! It also rebooted like you said, and now it works again. holy ****. thank you so much!
novadaemon said:
What the hell..... I've held down the power button before and the menu usually pops up. I just tried this and it worked! It also rebooted like you said, and now it works again. holy ****. thank you so much!
Click to expand...
Click to collapse
No problem, glad I was able to help!
i've also found that it responds to the rolling towards your face more than the raising of your arm. (for me at least)
adiliyo said:
i've also found that it responds to the rolling towards your face more than the raising of your arm. (for me at least)
Click to expand...
Click to collapse
+1
However, I thought the gesture worked better before the recent update. I don't KNOW that the update changed the gesture but it seems less reliable than it did when I first got the watch. Now I seem to get quite a few false activations and sometimes now have to repeat the gesture to make it switch on.
This is not a major issue, don't get me wrong.
czonin said:
I've had mine since Monday and the gesture worked great. About half way through the day yesterday the gesture completely stopped working. I tried to reboot, factory reset but nothing worked. Eventually I held the power button down for about 10 seconds in order to bring up the power menu. Instead the watch just rebooted itself and after that, the gesture started working again. Weird.
Click to expand...
Click to collapse
Same boat (reboot, factory reset, etc). Held down for 10 seconds, it rebooted, and fixed!
The gesture does NOT work when the watch is on silent. This is most likely your issue.
Held down for 10 seconds, it rebooted, and fixed!
seh6183 said:
The gesture does NOT work when the watch is on silent. This is most likely your issue.
Click to expand...
Click to collapse
This is correct - I just tested this with my Samsung Gear Live. If notifications are not muted, the 'lift arm and roll wrist' gesture will wake the watch.
This works even when the watch face is not set to 'Always On' in the Android Wear settings menu.
I come from the Gear Fit where you can switch off this automatic gesture completely. I hope this setting will show up within Android Wear soon. I drove with my car tonight and the watch was constantly waking up showing me the same card all over again and again while steering... Argh.
Is there some kind of patch or adb setting where I can change this?
TIA
Greetings
plant
plantagoo said:
I come from the Gear Fit where you can switch off this automatic gesture completely. I hope this setting will show up within Android Wear soon. I drove with my car tonight and the watch was constantly waking up showing me the same card all over again and again while steering... Argh.
Is there some kind of patch or adb setting where I can change this?
TIA
Greetings
plant
Click to expand...
Click to collapse
I guess for the time being, you could just mute notifications while driving. Unless of course you want them to come through while driving.
My problem is it is too sensitivity.
Scratch my nose the watch wakes and this drains the battery
Hi friends !
Just received mine today, and released it on 4.4w1....But no issue to this fu...g problem of automatic switch on gesture !!!
Please Google, lesson to us !!
No root, no need to download or install anything.
This work for other devices as well as the Note 4. This enables the Google now "Ok Google" Feature where you can active Google now while the screen is off. This is something like the Moto X feature.
How To:
1) Open Google Now
2) Go to Google Now Settings
3) Click on "Voice"
4) Enable "Audio History"
5) Click "Ok Google Detection"
6)Click "Always on" and follow the remaining directions.
You Can also watch this How To Video if you want:
If you device is unsupported or it just wont work, then there is an app called "Open Mic+ for Google Now" which does this for you.
This also works on the Lg G3, Nexus 5, and Galaxy S5, from what I know. Please feel free to try other devices and let me know if they work as well.
The question is, will this murder your battery and leave it on the side of the road? :laugh:
I am just going to use S Voice and program whatever saying I want to wake up the Note 4. Easy peasy.
EP2008 said:
The question is, will this murder your battery and leave it on the side of the road? :laugh:
Click to expand...
Click to collapse
I woke up today to find out my phone was still on with 1%. I went to sleep with it at 2%. I also had it on all day and it does nothing to the battery at all. Try it out let me know if you get the same results.
followed the instruction but when i turn the screen off and say "ok google" the beep sound come on but the screen doesn't turn on nor listen to my command but it rather stop listening and just show "say ok google, or tap mic button"
blackout720 said:
I woke up today to find out my phone was still on with 1%. I went to sleep with it at 2%. I also had it on all day and it does nothing to the battery at all. Try it out let me know if you get the same results.
Click to expand...
Click to collapse
Video says this will only work without a secure lockscreen, so I'll have to pass
i found that "ok google" works with a lock screen if you have the phone plugged in and charging. It doesn't work with a lock screen if the phone is unplugged. for me at least.
randpost said:
i found that "ok google" works with a lock screen if you have the phone plugged in and charging. It doesn't work with a lock screen if the phone is unplugged. for me at least.
Click to expand...
Click to collapse
I didn't try that, interesting. Now do you mean it by passes the lock screen or does it tell you while its still locked?
blackout720 said:
I didn't try that, interesting. Now do you mean it by passes the lock screen or does it tell you while its still locked?
Click to expand...
Click to collapse
It doesn't unlock the screen. Google now pops up while locked.
Noticed any battery drain? I still have no issues.
randpost said:
i found that "ok google" works with a lock screen if you have the phone plugged in and charging. It doesn't work with a lock screen if the phone is unplugged. for me at least.
Click to expand...
Click to collapse
There is a checkbox for wakeup with screen locked
I used this feature last night while sleeping. I tend to wake up a few times in the night affraid i am late for work.
"Ok Google, what time is it?"
Worked like a charm but the wife hated it. I did not notice any battery drain to be honest.
Would be nice to have your own phrase,
s.morris said:
Would be nice to have your own phrase,
Click to expand...
Click to collapse
s voice does the same with your own custom phrase:good:
ant78 said:
s voice does the same with your own custom phrase:good:
Click to expand...
Click to collapse
Ok google when screen is off, is a real hit or miss situation. I've tried saying the phrase 5 times over and nothing. If I'm on the screen app thats google with the microphone greyed out and say OK google it does it everytime but with the screen off, not that much, kind of a waste. I hope maybe with an update from google or samsung this gets better recognition.
abacus0101 said:
Ok google when screen is off, is a real hit or miss situation. I've tried saying the phrase 5 times over and nothing. If I'm on the screen app thats google with the microphone greyed out and say OK google it does it everytime but with the screen off, not that much, kind of a waste. I hope maybe with an update from google or samsung this gets better recognition.
Click to expand...
Click to collapse
I have experienced this as well but only when I haven't used it for a long period.
Works every time for me. I even have a noisy environment with a 2yr girl running about and the television on. Take about 2-3secs to turn screen on though. I was worried about security as I have screen lock with fingerprint and the fact that you can get to Internet search and ask Google to open an app on the phone but it seems to go back to lock screen if you try anything like that but I bet that this is a short hop to being able to gain access to part of a locked phone that you think is secure unless it just makes the G-Now features simply an overlay on the lockscreen. I will be turning this off for time being.
Hello. It's working only in english langage not in French.
Envoyé de mon SM-N910F en utilisant Tapatalk
Good. The french could use some more english in their diet .
There is no battery drain and it does work properly with screen off, but you should register your voice in the process (say ok google louder, quiters, faster, slower) and it will recognize it good.
Hi everyone,
I got a new Moto X (2014) recently (through the Motorola Cyber Monday deal). It's really a great phone.
I have one small question: The "OK Google" voice command doesn't seem to work from the lock screen (yes, the option is enabled in settings and yes, I've 'trained' it to recognize my voice). It works fine when the screen is unlocked. Initially I thought it was because Moto Voice was activated and I tried deactivating/turning off Moto Voice (both in accessibility as well as in the 'Moto' app settings). Still I can't get the phone to respond to the "OK Google" command when screen is locked. Am I missing something somewhere?
PS., I have tried using Moto Voice and it works too (I tried with one of the suggested phrase, "OK Moto X"). But for some reason, it doesn't recognize properly and if I say, for example, "Call Mom", it opens up a contact whose name has "Mohan" in it (Google opens my mom' contact details perfectly every time).
Thanks.
I can't test it right now, but if I remember correctly, the default command is "OK Google Now," not "OK Google."
Thanks,
It works with "OK Google" once the screen is unlocked and I'm on the home screen (or any of the home screens). and not when the screen is locked.
Edit: Funny (and weird). I tried with "OK Google Now" few times and then went back to repeating "OK Google" and it's now recognizing the command from the lock screen. As mentioned in the initial post, Moto Voice is inactivated (both under settings > accessibility and the Moto app).
Well, it's stopped working again this morning (after working for a while last night). The voice command "OK Google" doesn't do anything when the screen is locked (yes, the option "when locked" in 'voice settings' is turned on).
Though, the Moto Voice command that I set up works when the screen is locked. It's just the "OK Google" command which isn't working properly.
Any ideas on how to fix this? Thanks.
PS., I can use Moto Voice instead but as I said, for some reason it's not recognizing my voice / accent as well as Google does. Google voice gives an almost 100% perfect voice recognition.
I believe the "locked" is in reference to the "lock screen", not screen off "locked". Definitely diminishes its functionality, though...
Yeah, they mean the screen is on but locked, not that the phone is locked.
"Locked" meaning when the screen is locked or screen is turned off. There is an option in Google Now voice settings to enable the device respond to the "OK Google" command even when the screen is turned off or locked (precise wording - "Allow OK google to start a voice search or action from a secure lock screen").
Does that mean when the screen is 'locked' with either a PIN or pattern (and not just swipe)? I have tried "OK Google" both with just a 'swipe' setting or a 'PIN' lock setting. Doesn't work in either case (it did work for a short while though, last night, when I had the screen lock set to just 'swipe').
Edit: Thanks, @chrisrozon . So it doesn't work when the phone is 'locked'? Does the screen have to be turned on? Meaning, even if it's locked, does the lock screen have to show up before having it respond to the "OK Google" command?
When I tried (and when it worked intermittently) last night, I was able to see the device respond to "OK Google" from when the screen was locked and when the screen was turned off.
Alright. I checked again and it works when the screen is locked but the lock screen is on. Does it make sense? I mean, when the screen is locked and then I activate the display so that the lock screen shows up, then the "OK Google" command works.
This kind of defeats the purpose of 'works even when the screen is locked', isn't it? Or is this a known issue?
But I swear I could have the device respond to the "OK Google" command even when the screen/display was locked AND turned off. Or may be I was just trying too soon once the display turned off because I have the display to turn off after 15 sec of inactivity and the screen lock set to 15 sec after display turns off.
Well, I am just confused.
That's how it is supposed to work, the screen needs to be on.
fonduekid said:
But I swear I could have the device respond to the "OK Google" command even when the screen/display was locked AND turned off. Or may be I was just trying too soon once the display turned off because I have the display to turn off after 15 sec of inactivity and the screen lock set to 15 sec after display turns off.
Well, I am just confused.
Click to expand...
Click to collapse
You are not the only way cause I was able to get this to work yesterday with the screen turned off. I waited a good 5 mins with the screen off and said "OK Google" and it wake up the phone. it worked great for about 2 hours and then it just stop. Even since I cant get it to work again. I went ahead and did a factory reset last night and this moring trying to get it to work and and its still not working.
Were you plugged in? Because it always works when you are plugged in.
Well, looks like that's how it works - screen needs to be turned on. For sure I am not doing a factory reset for this!
bongostl said:
Were you plugged in? Because it always works when you are plugged in.
Click to expand...
Click to collapse
I haven't checked when it's plugged in. I'll do that later this evening and get back. Thanks.
dazz87 said:
You are not the only way cause I was able to get this to work yesterday with the screen turned off. I waited a good 5 mins with the screen off and said "OK Google" and it wake up the phone. it worked great for about 2 hours and then it just stop. Even since I cant get it to work again. I went ahead and did a factory reset last night and this moring trying to get it to work and and its still not working.
Click to expand...
Click to collapse
I see the ability to use the launch phrase when the screen is off, locked (use swipe) when connected to a trusted bluetooth device. Otherwise, the screen need to be on, but can still be locked. When no trusted bluetooth is connected, I'll wave, wake the screen, then say the launch phrase.
bongostl said:
Were you plugged in? Because it always works when you are plugged in.
Click to expand...
Click to collapse
Amazing. Yes, it works when plugged in. It also works when connected to a trusted bluetooth device as sailindawg mentioned.
Otherwise I have to wave to turn the screen on (still locked) and then use the "OK Google" command.
The feature should work even after screen is locked and without the need for any Bluetooth devices. I have noticed since the lollipop update that the feature stopped working reliably when locked. In fact, after successful setup, some time would pass and voice actions would stop responding. SOLUTION: after wiping all app data for Moto voice and then rebooting. I re-setup moto voice and now all is working as it should and it has continued to function reliably.
Sent from my XT1095 using XDA Free mobile app
stevetsimmons.com said:
The feature should work even after screen is locked and without the need for any Bluetooth devices. I have noticed since the lollipop update that the feature stopped working reliably when locked. In fact, after successful setup, some time would pass and voice actions would stop responding. SOLUTION: after wiping all app data for Moto voice and then rebooting. I re-setup moto voice and now all is working as it should and it has continued to function reliably.
Sent from my XT1095 using XDA Free mobile app
Click to expand...
Click to collapse
Tried this. Doesn't work for me.
stevetsimmons.com said:
The feature should work even after screen is locked and without the need for any Bluetooth devices. I have noticed since the lollipop update that the feature stopped working reliably when locked. In fact, after successful setup, some time would pass and voice actions would stop responding. SOLUTION: after wiping all app data for Moto voice and then rebooting. I re-setup moto voice and now all is working as it should and it has continued to function reliably.
Sent from my XT1095 using XDA Free mobile app
Click to expand...
Click to collapse
I think you're talking about the MOTO Implementation, NOT the pure Android "OK Google" that we are talking about in this thread.
This issue is troubling me, it's not too much of a hinderance but I don't understand why it's doing it. I've set a PIN on lock screen to unlock, but I've got smart lock trusted to my watch (Sony smartwatch 2). It's ok for the most part, but I'm finding that after half an hour or so of being left alone, the phone asks for the pin code. Cannot understand why? The watch isn't disconnecting or anything as far as i know.
spark001uk said:
This issue is troubling me, it's not too much of a hinderance but I don't understand why it's doing it. I've set a PIN on lock screen to unlock, but I've got smart lock trusted to my watch (Sony smartwatch 2). It's ok for the most part, but I'm finding that after half an hour or so of being left alone, the phone asks for the pin code. Cannot understand why? The watch isn't disconnecting or anything as far as i know.
Click to expand...
Click to collapse
It happens to me, not within 30 minutes, but if i leave it overnight while i sleep. I'm not sure if its a bug or a feature to deep-lock the phone after x-amount of time of not being unlocked.
Happens to me.
spark001uk said:
This issue is troubling me, it's not too much of a hinderance but I don't understand why it's doing it. I've set a PIN on lock screen to unlock, but I've got smart lock trusted to my watch (Sony smartwatch 2). It's ok for the most part, but I'm finding that after half an hour or so of being left alone, the phone asks for the pin code. Cannot understand why? The watch isn't disconnecting or anything as far as i know.
Click to expand...
Click to collapse
I've got home wifi set and car set to smartlock but even after logging on to them, the first time I use phone after log in I have to enter code, after that everything works. Also after sleeping during night, in morning have to enter code first time upon waking up. So I think it is a bug.
vvveith said:
I've got home wifi set and car set to smartlock but even after logging on to them, the first time I use phone after log in I have to enter code, after that everything works. Also after sleeping during night, in morning have to enter code first time upon waking up. So I think it is a bug.
Click to expand...
Click to collapse
Same here with a Nexus 5. Smart watch and home location set as smartlock but each morning a manual unlock is required. Maybe it is designed to work that way.
Sent from my Nexus 7 using Tapatalk
bug or not
did this get resolved ?
I've noticed that smart lock automatically locks after 4 hours of non-use.
Evolution_Tech said:
I've noticed that smart lock automatically locks after 4 hours of non-use.
Click to expand...
Click to collapse
Now it even puts a pull down notification saying that too.
Strange thing is happening recent to me...
Namely, while using headphones while talking on the phone, the unit gets unlocked while in pocket and problems arise with spontaneous keys getting activated.
If even cannot be explicitly locked by pressing the power button.
Have not found a solution to this problem, and it's strange why the proximity sensor does not work in pocket.
Cannot remember whether this was previously, or is it since last ROM upgrade.
Anyone having same problem?
tomsag said:
Strange thing is happening recent to me...
Namely, while using headphones while talking on the phone, the unit gets unlocked while in pocket and problems arise with spontaneous keys getting activated.
If even cannot be explicitly locked by pressing the power button.
Have not found a solution to this problem, and it's strange why the proximity sensor does not work in pocket.
Cannot remember whether this was previously, or is it since last ROM upgrade.
Anyone having same problem?
Click to expand...
Click to collapse
Yep I have the same thing... Today my pocket took 9599295 pictures and movies.. also when I'm a bit sweat my pocket dial random numbers. I've noticed that when screen is touched and disnt recognize fingerprint then whole lockscreen shows up and its easy way to random open dial or camera... Its rly anoying, because I dont want to hide phone screen outside of the skin. (Its easier to break screen if I hit something with my leg.)
Dunno why it doesnt use proximity sensor to recognize that phone is in the pocket like every other brand... :/
Do you have the double tap to wake up activated?
I had this problem a while ago and it was the double tap that played all kinds of tricks calling emergency and taking pictures in my pocket! Disable double tap to wake up screen and the problem goes away.
Disable the fingerprint icon on when the screen if off.
Gokh said:
Disable the fingerprint icon on when the screen if off.
Click to expand...
Click to collapse
Tried everything but the problem is eventually still there. Actually I've found a bug, namely the display will wake up once touched several times near the center of the fingerprint reader. Try it yourself.
Not nice - cannot avoid to happen it sometimes even if all options are disabled.
tomsag said:
Tried everything but the problem is eventually still there. Actually I've found a bug, namely the display will wake up once touched several times near the center of the fingerprint reader. Try it yourself.
Not nice - cannot avoid to happen it sometimes even if all options are disabled.
Click to expand...
Click to collapse
I didn't have this problem. If I try now and touch the part with the scanner, doesn’t have to be just the centre of the scanner, rapidly around ten times the lock screen will turn on, but nothing happens when I touch the shortcuts. Perhaps they are disabled, so the only thing that happens if the scanner is touched again is that the numpad to unlock with pin appears.
This is not good as it may severely affect battery life if it happens a lot. This clearly must be a bug!
gerhard_wa said:
I didn't have this problem. If I try now and touch the part with the scanner, doesn’t have to be just the centre of the scanner, rapidly around ten times the lock screen will turn on, but nothing happens when I touch the shortcuts. Perhaps they are disabled, so the only thing that happens if the scanner is touched again is that the numpad to unlock with pin appears.
This is not good as it may severely affect battery life if it happens a lot. This clearly must be a bug!
Click to expand...
Click to collapse
Even worse, since it is happening all the time while on a call via BT and my phone is in the pocket. I am now thinking about to switch over to my old MI8...
Cannot understand why the keyboard is not disabled in the pocket. Seems so easy to do it but it's as it seems on.
tomsag said:
Even worse, since it is happening all the time while on a call via BT and my phone is in the pocket. I am now thinking about to switch over to my old MI8...
Cannot understand why the keyboard is not disabled in the pocket. Seems so easy to do it but it's as it seems on.
Click to expand...
Click to collapse
My only solution was to buy a flip case. At first, I disabled the fingerprint reader by removing all fingerprints and setting up face recognition, but this didn’t fix the problem you are talking about. I don’t really like flip cases, but the Nillkin QIN Smartcase is rather good.
So now I ‘m eagerly awaiting a fix from Xiaomi so I can strip the Mi9 again!
Gokh said:
Disable the fingerprint icon on when the screen if off.
Click to expand...
Click to collapse
Where can the fingerprint icon be disabled? Thank's.
j4dotcc said:
Where can the fingerprint icon be disabled? Thank's.
Click to expand...
Click to collapse
Disabling the fingerprint icon has no effect on the problem we are talking about here. The only way to make the problem go away is to remove all the stored fingerprints thus disabling the use of fingerprints all together. This will shut off the fingerprint sensor doing away with this problem in a crude way.
If you really are looking for a setting, please use the search function at the top of the settings.
gerhard_wa said:
Disabling the fingerprint icon has no effect on the problem we are talking about here. The only way to make the problem go away is to remove all the stored fingerprints thus disabling the use of fingerprints all together. This will shut off the fingerprint sensor doing away with this problem in a crude way.
If you really are looking for a setting, please use the search function at the top of the settings.
Click to expand...
Click to collapse
Thanks for the prompt reply. I don't have the problem and just wanted to know where I can disable the fingerprint icon. Thanks again.
New uppdate out that include Pocket Mode. MIUI-V10.2.27.0PFAEUXM EEA version.