I've got google assistant set up with trusted voice etc so that I can issue commands to my locked Note8 while driving etc, one thing I've noticed that I'm not a fan of is if I issue a simple command like 'what time is it' for example, google completes the request without ever leaving the AOD but after the request is complete my phone is still off but it stays unlocked. Is there a way to make my phone automatically re-lock after a voice command with Google assistant?
dicko101 said:
I've got google assistant set up with trusted voice etc so that I can issue commands to my locked Note8 while driving etc, one thing I've noticed that I'm not a fan of is if I issue a simple command like 'what time is it' for example, google completes the request without ever leaving the AOD but after the request is complete my phone is still off but it stays unlocked. Is there a way to make my phone automatically re-lock after a voice command with Google assistant?
Click to expand...
Click to collapse
Say "Hi Bixby, lock screen" when you're done.
harveydent said:
Say "Hi Bixby, lock screen" when you're done.
Click to expand...
Click to collapse
Yeah I know, it would just be better if it relocked itself.
dicko101 said:
Yeah I know, it would just be better if it relocked itself.
Click to expand...
Click to collapse
Why not just set your lock to 30 seconds or whatever. Assistant commands unlock your phone.
Sent from my SM-N950W using Tapatalk
milan187 said:
Why not just set your lock to 30 seconds or whatever. Assistant commands unlock your phone.
Sent from my SM-N950W using Tapatalk
Click to expand...
Click to collapse
My lock does time out, it's just annoying, it seems logical that your device should just re-lock after a voice command, a lot of voice commands don't need to unlock, like the example I gave, they don't even leave the AOD, it just seems like something that should have been obvious and would have been easy to implement.
dicko101 said:
My lock does time out, it's just annoying, it seems logical that your device should just re-lock after a voice command, a lot of voice commands don't need to unlock, like the example I gave, they don't even leave the AOD, it just seems like something that should have been obvious and would have been easy to implement.
Click to expand...
Click to collapse
Most commands require access to something therefore can't work in a locked encrypted system. Can google work around it? Probably. This is the first time I've seen a complaint about this.
Sent from my SM-N950W using Tapatalk
Related
Hi everyone
I have the phrase set to OK Google Now.
When the phone is locked, screen off or even on moto display, quite a lot of the time saying the launch phrase will do nothing. When I unlock the phone it works perfectly fine. Then when I lock it, it works for a while but then after a bit it stops working until I unlock it again.
Is this some kind of bug that any of you have experienced also?
it kinda happens for me too. Even when it does get it, some commands are almost unusable. it just redirects to google search. is your phone a US one?
Moto XT1097 for the win
No I bought mine from Moto Maker in the UK. Hopefully it should be fixed in the next update.
raze599 said:
Hi everyone
I have the phrase set to OK Google Now.
When the phone is locked, screen off or even on moto display, quite a lot of the time saying the launch phrase will do nothing. When I unlock the phone it works perfectly fine. Then when I lock it, it works for a while but then after a bit it stops working until I unlock it again.
Is this some kind of bug that any of you have experienced also?
Click to expand...
Click to collapse
The Moto X unlike the regular Ok Google which is available on all phones, is not only listening for the words to activate but also processes it to make sure its a close match to the voice used during the initial training setup. Try rerunning the voice training and record your voice without any accent, try speak casually the way you normally do trying to wake up your moto x. This should help
Google must think we are idiots. They force us to look at that stupid "Ok Google" banner every time the watch enters bright mode - as if we somehow forgot the magic words since the last 300 times we said them.
Is there a hack to turn this off? Thanks in advance.
Ok, just figured this out i think.
You can permanently disable the "Ok Google" banner by clicking the fob, saying "Ok Google", then clicking it again to dim. Repeat this 5 times and the "Ok Google" banner should permanently disable. I guess Google figures we have it figured out by then.
mitchellvii said:
Ok, just figured this out i think.
You can permanently disable the "Ok Google" banner by clicking the fob, saying "Ok Google", then clicking it again to dim. Repeat this 5 times and the "Ok Google" banner should permanently disable. I guess Google figures we have it figured out by then.
Click to expand...
Click to collapse
Change your watchface, and it appears again There is no way to get permanently rid of this blight!
RoosW said:
Change your watchface, and it appears again There is no way to get permanently rid of this blight!
Click to expand...
Click to collapse
Not correct. If you follow my method the banner will never come back. Changing watchfaces has no effect, at least under 5.01.
mitchellvii said:
Not correct. If you follow my method the banner will never come back. Changing watchfaces has no effect, at least under 5.01.
Click to expand...
Click to collapse
Thanks! Indeed it stays away now, lets hope i do not need another system reset any time soon
I was thinking after you "kill" it it stays gone till reboot.
mitchellvii said:
Not correct. If you follow my method the banner will never come back. Changing watchfaces has no effect, at least under 5.01.
Click to expand...
Click to collapse
Confirmed with 5.0.1 - the banner does not come back after a reboot or after changing faces.
-fg
If clicking it doesn't work just use the OK Google command for some random searches about 5-6 times and it will definitely not appear anymore after you've done so. Had the same issue initially but found it disappeared after a few uses.
I have had it reappear twice now (went away after one 'ok google') while i have followed the instructions, not a clue why it did, the last time it just was there when i pulled the watch from the charging cradle..
There are some external watchface apps where you can take it out if you're into those at all.
It is a cue for saying OK Google...
Do random searches 5 times by saying OK Google..(OK Google.. What's the weather..) Let it finish searching each time.. It will be gone... It will reappear if you reset your watch or after a new update... Do some Search 5 times again
Sent from my SM-N910C using Tapatalk 2
pakure said:
It is a cue for saying OK Google...
Do random searches 5 times by saying OK Google..(OK Google.. What's the weather..) Let it finish searching each time.. It will be gone... It will reappear if you reset your watch or after a new update... Do some Search 5 times again
Sent from my SM-N910C using Tapatalk 2
Click to expand...
Click to collapse
Yeah, did that, following the method described somewhere on the first page of this thread, i was assured it would be gone, over and done with, and would not even reappear after a reboot, but it does, kinda random, and always gone for a few days when i 'Ok Google' once.
But it should not happen as i have done the 5 times and such!
RoosW said:
I have had it reappear twice now (went away after one 'ok google') while i have followed the instructions, not a clue why it did, the last time it just was there when i pulled the watch from the charging cradle..
Click to expand...
Click to collapse
I've had it also reappear (and disappear on it's own) a few times the last 2 weeks. No idea what the trigger is it was gone after the last update for at least 3 weeks before it came back.
I switched from the Moto Voice app to the OK Google because the Moto X voice app is terrible. Everything was working great until a few days ago. OK Google only works from the home screen now. Does anyone else have this issue? Is there a work-around to fix it? Thanks!
I'm assuming that the "From any screen" option is checked in the Google app?
imaginaryenemy said:
I'm assuming that the "From any screen" option is checked in the Google app?
Click to expand...
Click to collapse
Correct, and I did the training. It works perfectly on my Moto G. My Moto X has been acting quirky so I am getting an advanced replacement from Motorola. They are now charging a $25 "Premium Fee" for advance replacement. I hate this company ever since Lenovo took over and this will be my last Motorola phone.
Having the same issue.
Starting to regret this phone deeply.
I just realized that I hadn't checked it since my update to 5.1, and it no longer works for me either. It is not a feature I use, but it is a shame that it is broken.
Me neither, which makes me think it's a server side error.
Broken on my Moto X running 5.1 stock or CM 12.1 and my Nexus 5 in the same scenarios, so I think it's a bug in the app not with our phone.
chrisrozon said:
Me neither, which makes me think it's a server side error.
Click to expand...
Click to collapse
raptir said:
Broken on my Moto X running 5.1 stock or CM 12.1 and my Nexus 5 in the same scenarios, so I think it's a bug in the app not with our phone.
Click to expand...
Click to collapse
These certainly sound like the most likely causes, however, is it strange that we are the only people talking about this? If it were a global problem, I would think more people would be complaining.
I had this exact issue and figured out quite a simple fix.
All you need to do is going to the "Moto" app and disable the "Moto Voice" function. The moto voice function apparently takes control of the mic at all times, stopping google now from doing so. Once I disabled the Moto Voice, I could enable Google Now / Ok Google from all screens and didn't get the "microphone is in use, please restart device" error message anymore.
Hope this helps
Yugnoswam said:
I had this exact issue and figured out quite a simple fix.
Click to expand...
Click to collapse
This is not the problem being discussed here. The problem is, after being setup properly, the "OK Google" command only works on the homescreens. Not on the lock screen, not when an app in is the foreground. Are you able to use "OK Google" in these instances?
imaginaryenemy said:
This is not the problem being discussed here. The problem is, after being setup properly, the "OK Google" command only works on the homescreens. Not on the lock screen, not when an app in is the foreground. Are you able to use "OK Google" in these instances?
Click to expand...
Click to collapse
It seems intermittent ever since the last Motorola OTA I received. I can't seem to do OK google from my homescreen anymore although it will occasionally wake from lock screens and in an app if I use it, it will pull me out of the app to the Google Now search screen. I think the whole thing is pretty much bugged to be honest :/
I've found just going into the google search and hitting the mic button much more reliable and thus faster.
So I got the upgrade but now I am unable to use the voice command Ok Google from watch face as before. I can only get it working by holding power button and even then it seems just laggy.
Anyone else having this issue activating it by voice?
Thanks!
Having that same issue. Not only does not "Ok Google" work, even after enabling it in the watch's settings, even when pressing down the crown, the whole thing is extremely slow. Furthermore, for sending a message, the "Ok" doesn't time out after a couple of seconds in order to send the message automatically. It requires me to tap the screen.
All in all, its looking more like a downgrade for me. The whole system feels sluggish and incoherent from a usability standpoint of view.
Edit: Didn't factory reset the watch after update
I have an another problem. Google Assistant isn't launched in Czechia yet and there isn't Google Now in Android Wear 2. So, I lost any speech control.
I've too had issues with "OK Google" after Android Wear 2.0 install. I did get it sort of working after a device reset and reconnect to my phone. (Samsung Note 5). Its slow!! and now for sending text messages you have to confirm with a tap. All in all the functionality went down....
Anyone know how to revert back to the old rom?
Mr.Caution said:
I've too had issues with "OK Google" after Android Wear 2.0 install. I did get it sort of working after a device reset and reconnect to my phone. (Samsung Note 5). Its slow!! and now for sending text messages you have to confirm with a tap. All in all the functionality went down....
Anyone know how to revert back to the old rom?
Click to expand...
Click to collapse
So another issue is that even after going to the stupid settings where you actually have to enable Ok Google from any screen on your watch, it STILL wont work. I can only get it to work by using the power button which has a huge delay and then only when I am connected on Wifi. For some reason it no longer works when on my normal cellphone connection.
The phone is super laggy, battery dies fast...its a MESS.
Basically my watch is useless now for all the things I need it to do daily
Mine only works if i go and disable Bluetooth and enable WiFi else it complains it can't contact Google. Play store is the same too. Slow lagging assistant is not good especially sending txts with no auto send
Sent from my Moto G (4) using Tapatalk
Same issue here. "OK Google" is the most important feature...
You need to give permissions for the OK Google to work. Didn't notice about it until I read this thread (I think most particularly Phone access)
shaolin95 said:
So I got the upgrade but now I am unable to use the voice command Ok Google from watch face as before. I can only get it working by holding power button and even then it seems just laggy.
Anyone else having this issue activating it by voice?
Thanks!
Click to expand...
Click to collapse
Yes , it is the same on my watch - it is laggy ! I am looking for a way to downgrade back to old android wear.
venzislav said:
Yes , it is the same on my watch - it is laggy ! I am looking for a way to downgrade back to old android wear.
Click to expand...
Click to collapse
I just got the ROM from this post and used the flash steps he listed and it worked fine.
https://forum.xda-developers.com/showpost.php?p=71823043&postcount=3
shaolin95 said:
I just got the ROM from this post and used the flash steps he listed and it worked fine.
https://forum.xda-developers.com/showpost.php?p=71823043&postcount=3
Click to expand...
Click to collapse
Is it possible after downgrade to stop watch from upgrading again to 2.0 ?
venzislav said:
Is it possible after downgrade to stop watch from upgrading again to 2.0 ?
Click to expand...
Click to collapse
I want to find out as its annoying to see the upgrade message over and over
shaolin95 said:
I want to find out as its annoying to see the upgrade message over and over
Click to expand...
Click to collapse
Pfff this 2.0 is a big s**t !!!
Doesn't lag on mine using the 2 core or 4 core kernel
almostthere said:
Doesn't lag on mine using the 2 core or 4 core kernel
Click to expand...
Click to collapse
Does OK Google work with voice commands and when not connected to Wifi???
shaolin95 said:
Does OK Google work with voice commands and when not connected to Wifi???
Click to expand...
Click to collapse
Yup mine works perfectly without wifi (have been testing it outdoors since 2 days ago). Fix is to go to apps, system apps, google, permissions, enable permission to phone (maybe others too since IDGAF and ticked all)
almostthere said:
Yup mine works perfectly without wifi (have been testing it outdoors since 2 days ago). Fix is to go to apps, system apps, google, permissions, enable permission to phone (maybe others too since IDGAF and ticked all)
Click to expand...
Click to collapse
Would you look at that! It works but WTH is google making it so complicated now for users? Most people dont hang around XDA to know these things. Like for instance apps now need to be downloaded on the phone as its not autmotically done, etc.
Really weird approach.
Thanks for the tip!
After a factory reset and being extremely patient, I was able to get Ok google to work. You have to go to the store on the app and update all of the apps and then enable, OK google in the settings. Problem is the response time is horrible. I'm going to stick with 2.0 and hope that they roll out updates to make it faster.
Isham.padron said:
After a factory reset and being extremely patient, I was able to get Ok google to work. You have to go to the store on the app and update all of the apps and then enable, OK google in the settings. Problem is the response time is horrible. I'm going to stick with 2.0 and hope that they roll out updates to make it faster.
Click to expand...
Click to collapse
Responses time is horrible on the initial due to it running on single core at lower clock speeds and on conservative core governor.
Therefore you'll have to give it sometime for it to settle down or if you can't deal with it, you'll have to unlock the bootloader and flash in the dual or quad core enabled kernel file
Running in quad core kernel, battery life seems decent and response real snappy
Well that's just stupid because it worked fine on the previous android wear build. This is dumb on LG's part.
I'm not sure when this changed. I used to be able to say "OK Google" and the assistant would interact with certain apps, like texting or calendar, when the phone was still locked. Now, as soon as I say the hot-phrase it goes straight to the pattern lock screen and won't go further until I unlock. Is this a function lost on devices without "Trusted Voice"?
I'm running the latest PN with the stock PN kernel. I'm not in beta for the Google app either.
I've tried retraining voice recognition, turning always listening off/on, updated Google app a couple times, tried different launchers (Action and Pixel)...
Any thoughts or recommendations on this?
The way I handle this is using tasker to set the screen lock delay to some thing silly like 10 days when the phone is in a "safe" location. Then the ok google works as expected with the screen off. The rest of the time I live with the fact that I have to unlock the phone to use ok google.
On reflection, smart lock should give the same effect of there is a trusted device connected.
I've considered something like what you've said. I do want the security to work though. I used to be able to do very basic things by voice without unlocking. I don't want to effectively turn off security.