Hi all,
do you know if the Mate 10 Pro will be compatible with Google Assistant?
Will the "ok google" work on display off?
Thanks!
It defi works, but i'll need to check tomorrow if it also listens to 'ok google' if screen is off (i'm in bed and don't wanne wake the misses)
Hi,
Do we have to change something to get the google assistant in Belgium ? The langage ? Set as developper ? I thought that the google assisant was bot enable in Belgium ...
Chris
christophevdb said:
Hi,
Do we have to change something to get the google assistant in Belgium ? The langage ? Set as developper ? I thought that the google assisant was bot enable in Belgium ...
Chris
Click to expand...
Click to collapse
You need to set the language to English United States
Same for every other phone, no dutch assistant yet
Google Assistant cannot be awoken with "OK Google" when screen is off.
Any ideas how to make it working?
It stopped working for my Mate 10 Pro after rebranding to AT&T version using Funkyhuawei.
My bootloader is unlocked.
It did work with the screen off after updating to BLA-L29 8.0.0.127(C432), but I reinstalled the google app because the cards in google now wouldn't show up.
After that it didn't work anymore.
Any updates to make it work ?( i have smart unlock enabled in trusted agent and in GA i have enabled unlock with voce ) maybe a workaround ?
I just got this yesterday.
amonrei said:
I just got this yesterday.
Click to expand...
Click to collapse
Yes, it works if the screen is on but with screen locked it works now after u trained it ?
Sarjux said:
Yes, it works if the screen is on but with screen locked it works now after u trained it ?
Click to expand...
Click to collapse
Nope.
Any news on unlocking Huawei Mate 10 Pro with "ok Google" when locked?
DKWien said:
Any news on unlocking Huawei Mate 10 Pro with "ok Google" when locked?
Click to expand...
Click to collapse
I would be interested too
DKWien said:
Any news on unlocking Huawei Mate 10 Pro with "ok Google" when locked?
Click to expand...
Click to collapse
Mihalys said:
I would be interested too
Click to expand...
Click to collapse
There seems to be a feature built into the mate 10 which would lead me to believe Huawei wants to retain their own unique unlocking.
Future updates, not sure but for now.
Settings / Smart access / voice control
Latest Google upadte crash assistant in mate pro 10
since 29 april 2018 ...what a shame for google ...
how do you get "OK Google" or "Hey Google" to work on the phone? Any idea where is the setting that I need to enable it? I was previously running on 8.0.0.132 (ALP-L29C636B132) and it worked when I first setup the phone.
When I updated it to build 135, it stopped working. I reset my phone and gone thru the steps of the initial setup however, the phone is still not responding when i say "Ok Google" or "Hey Google".
donetus said:
how do you get "OK Google" or "Hey Google" to work on the phone? Any idea where is the setting that I need to enable it? I was previously running on 8.0.0.132 (ALP-L29C636B132) and it worked when I first setup the phone.
When I updated it to build 135, it stopped working. I reset my phone and gone thru the steps of the initial setup however, the phone is still not responding when i say "Ok Google" or "Hey Google".
Click to expand...
Click to collapse
Same with me... There is no setting to see and edit voice module or ok google detection
donetus said:
how do you get "OK Google" or "Hey Google" to work on the phone? Any idea where is the setting that I need to enable it? I was previously running on 8.0.0.132 (ALP-L29C636B132) and it worked when I first setup the phone.
When I updated it to build 135, it stopped working. I reset my phone and gone thru the steps of the initial setup however, the phone is still not responding when i say "Ok Google" or "Hey Google".
Click to expand...
Click to collapse
I was in the same boat as you. It was working fine on 132 and then I updated to 135 last week and that was it. Stopped working. I think it broke in the update. I factory reset the phone and still nothing. I read something about it here http://piunikaweb.com/2018/05/16/ok-google-access-broken-on-mate-10-pro-huawei-working-on-fix/
I noticed mine are greyed out too. So as of now, I'm hoping it will get fixed.
Related
I went into google now search settings and performed the voice training and enabled the option for hot word detection from lock screen and power off but it doesn't work. the only time it works is when i'm at the home screen UNlocked OR at the google now search area. Screen off or from lock screen detection simply does not work.
does anyone else notice this?
I don't have the nexus 9 but I did install the latest google now search and launcher from apkmirror .com and there was an always listening option in 'hotword detection' in voice settings of the google now. There was also the screen off detection option but it was greyed out. I had the always listening in all apps option enabled and it was working greatly but the next day I woke up and the feature wasn't working so I went into settings and discovered that both of those options had disappeared (not greyed out but freaking disappeared), its some kind of google restriction, they are remotely restricting users from using these features for some unexplained reason.
Maybe its the same for u or it might be something else.
Same here, bit worked arter reboot
It works for a while after a reboot, but eventually stops working after a couple hours.
Looks like a common bug, I've seen some threads about this same issue (and I'm experiencing the same problem, too)
Ok, let's hope Google is on it
borchgrevink said:
Ok, let's hope Google is on it
Click to expand...
Click to collapse
OK Google... get on it RIGHT NOW! same issue on the Nexus 4 AOSP build too...
mackendw said:
OK Google... get on it RIGHT NOW! same issue on the Nexus 4 AOSP build too...
Click to expand...
Click to collapse
Is it supposed to work on the N4? (I mean when screen off).
borchgrevink said:
Is it supposed to work on the N4? (I mean when screen off).
Click to expand...
Click to collapse
think about it...you're in your car, the screen times out and you want to make a call using voice recognition....so you have to unlock the screen and then use the voice recognition... sounds like a dangerous bug to me....serious liability IMHO
mackendw said:
think about it...you're in your car, the screen times out and you want to make a call using voice recognition....so you have to unlock the screen and then use the voice recognition... sounds like a dangerous bug to me....serious liability IMHO
Click to expand...
Click to collapse
I know, but the N4 doesn't support the neccessary hardware for this feature. Only the N6 and N9 does.
borchgrevink said:
I know, but the N4 doesn't support the neccessary hardware for this feature. Only the N6 and N9 does.
Click to expand...
Click to collapse
when I initially set it up, IT DID WORK....but then after a few hours, days (dunno for sure) it stopped. voice recognition works from google now screen, or the home page fine. something not right somewhere...
Hmm. From locked screen? Strange. Absolutely sure?
borchgrevink said:
Hmm. From locked screen? Strange. Absolutely sure?
Click to expand...
Click to collapse
there is an option in Google Now -> Settings -> Voice -> OK google detection ....a check box exists here stating:
When Locked
Allow "OK Google" to start a voice search or action from a secure lock screen
so, it would seem that this is what was intended. perhaps what they meant here was that the screen has to be on and not timed out. dunno.
Yes, but screen has to be on. Only nexus 6 and 9 support GN with screen locked and off
Google search from locked screen works for a while and then stops. It's done this on my s4 and note 3. It is defenetly supposed to work from secure lock screen. In Google now settings there is a 3rd check box and you even get a warning stating anyone may be able to unlock your phone.
Google needs to fix this issue. I'm not sure what's up with these companies making screwed up software. Where are the devs, and why are they getting paid if they can't make flawless software. When I crash My car into a tree trying to unlock my phone and I press a law suit against google I'll bet they will fix it. Always takes a law suit to fix ****.
Oh. Anyone notice every app you've ever paid for or downloaded is under my apps "all" what's up with "all" I'll file my documents in my office under the "all" folder and see how quickly I get fired...Thanks for allowing me to rant.
Happy new year!
https://productforums.google.com/forum/#!topic/websearch/xGiV6D4PMS8/discussion[1-25]
Major issue
Just wondering if anyone has Google Everywhere enabled and could speak to how well it can be implemented on the XU.
I realize it won't be as good as phone with a dedicated mic and chip but is it usable on your phone?
Asking to help me decide in purchasing this phone.
Thank you for your time.
It works quite well for for me. Since my system language is German I had to set the default language to English (U.S.) and German as secondary. But now "OK Google" works everywhere, even on the lockscreen and with commands in both languages. Only when the device is in standby, it doesn't react. Listening to music while the display is off? It works...
The phone itself is a steal here in Germany. Compared to a Samsung Galaxy S5, the specs aren't so much different (the size is rather a personal preference than a pro or con). Nevertheless the Z Ultra costs half (222€).
unidentifier said:
Just wondering if anyone has Google Everywhere enabled and could speak to how well it can be implemented on the XU.
I realize it won't be as good as phone with a dedicated mic and chip but is it usable on your phone?
Asking to help me decide in purchasing this phone.
Thank you for your time.
Click to expand...
Click to collapse
For me it's not sensitive enough. My voice could be in a whisper and the Nexus 5 could still pick it up, but for the Xperia Z Ultra I have to raise my voice a bit or hold it closer to my face.
OK Google works from everywhere except for when the screen is off. You can enable it in Google Now under Settings > Voice > "OK Google" Detection > From Any Screen
Works great for me
It seems to work everywhere, my only bicker is I wish I could hold a conversation with it only because it gets compared to siri. So I chose to go with my assistant from the play store best app ever.
H. E. Pennypacker said:
OK Google works from everywhere except for when the screen is off. You can enable it in Google Now under Settings > Voice > "OK Google" Detection > From Any Screen
Click to expand...
Click to collapse
haven't been on stock rom for a while, but in slimroms, "OK GOOGLE" can be setup to work when the device is sleeping while charging
ShadowVlican said:
haven't been on stock rom for a while, but in slimroms, "OK GOOGLE" can be setup to work when the device is sleeping while charging
Click to expand...
Click to collapse
Yeah, that's probably some kernel tweak or something. I don't know :silly:
ShadowVlican said:
haven't been on stock rom for a while, but in slimroms, "OK GOOGLE" can be setup to work when the device is sleeping while charging
Click to expand...
Click to collapse
H. E. Pennypacker said:
Yeah, that's probably some kernel tweak or something. I don't know :silly:
Click to expand...
Click to collapse
No, that's a feature of Google Search for all KitKat and up phones. It will always listen while charging if you have "Ok Google" detection from lock screen checked.
ApertureAndroid said:
No, that's a feature of Google Search for all KitKat and up phones. It will always listen while charging if you have "Ok Google" detection from lock screen checked.
Click to expand...
Click to collapse
Ohh, yes of course. That's a stock feature. I just haven't used it.
My clock only responds to "Ok Google" maybe 2 out of 10 times. When it works (or when I swipe to "Speak now" manually) the voice control is almost flawless (I'd say 95% success rate), so it obviously understands me.
What could be wrong and is there something I could do about it?
djr83 said:
My clock only responds to "Ok Google" maybe 2 out of 10 times. When it works (or when I swipe to "Speak now" manually) the voice control is almost flawless (I'd say 95% success rate), so it obviously understands me.
What could be wrong and is there something I could do about it?
Click to expand...
Click to collapse
I have exactly the same problem but with the 360 sport. If I delete and retrain the voice model on my phone it seems to temporarily fix the issue. Have tried factory reset, removing the wear app and reinstalling all to no avail. Have you had any luck? Im going to try pairing to a different phone to see if it's my phone or the watch. If that doesn't work I'm returning thE watch.
Mars104 said:
I have exactly the same problem but with the 360 sport. If I delete and retrain the voice model on my phone it seems to temporarily fix the issue. Have tried factory reset, removing the wear app and reinstalling all to no avail. Have you had any luck? Im going to try pairing to a different phone to see if it's my phone or the watch. If that doesn't work I'm returning thE watch.
Click to expand...
Click to collapse
That won't do any difference. I've tried another Moto 360 with another phone and it works as bad on the "Ok Google" part.
Retrain the command doesn't work when using another language than English so I haven't tried that.
I don't have scientific proof, but I believe different watch face apps provide different results. When I have had the "OK Google" problem, changing the watch face solved it.
kat3k said:
I don't have scientific proof, but I believe different watch face apps provide different results. When I have had the "OK Google" problem, changing the watch face solved it.
Click to expand...
Click to collapse
I haven't noticed any difference and most watch faces have been the stock ones that comes with Moto 360.
in my opinion, the stock watch faces respond faster than custom watch faces
I've had the same problem from Day One, the response to the keyword is far more haphazard than it was with my LG G Watch, but the speech recognition once past that is about the same; changing how I say "Okay Google" seems to be the only thing that makes any difference.
djr83 said:
My clock only responds to "Ok Google" maybe 2 out of 10 times. When it works (or when I swipe to "Speak now" manually) the voice control is almost flawless (I'd say 95% success rate), so it obviously understands me.
What could be wrong and is there something I could do about it?
Click to expand...
Click to collapse
Same for me. I had the LG Watch R before (a year ago) and it was working flawless. Thinking about buying the Fossil Q Founder. But new watches will be out soon when Google releases Wear 2.0, I guess.
Just to update. I recieved my replacement moto 360 sport. The 'ok google' command still only works about 20% of the time. It seems apparent this is a software issue as the mic and voice recognition seem to work fine. I hope this is fixed in wear 2.0 or another update.
In the meantime my workaround was to create a floating icon in AutoWear that launches GoogleNow on my watch. Now I just press the icon on my watch whenever I need to launch GoogleNow to set an alarm/reminder etc.
Mars104 said:
Just to update. I recieved my replacement moto 360 sport. The 'ok google' command still only works about 20% of the time. It seems apparent this is a software issue as the mic and voice recognition seem to work fine. I hope this is fixed in wear 2.0 or another update.
In the meantime my workaround was to create a floating icon in AutoWear that launches GoogleNow on my watch. Now I just press the icon on my watch whenever I need to launch GoogleNow to set an alarm/reminder etc.
Click to expand...
Click to collapse
How do you launch Google Now? It's not available under system apps.
So for me it shows an an available system app in autowear 'mange app actions' section (see attachment). If it's not in your version maybe it is a beta feature. I signed up for the beta test release :
http://joaoapps.com/beta-testing/
Mars104 said:
So for me it shows an an available system app in autowear 'mange app actions' section (see attachment). If it's not in your version maybe it is a beta feature. I signed up for the beta test release :
http://joaoapps.com/beta-testing/
Click to expand...
Click to collapse
What version do you have?
1.0.26
Mars104 said:
1.0.26
Click to expand...
Click to collapse
Same as me, but I still don't have Google Now in system apps. What could be wrong? Running Android 7 DP5.
Not sure. I'm running Google 6. The new update (M1D63G) seems to have improved 'ok google' detection. Not done much testing yet, but so far so good.
Mars104 said:
Not sure. I'm running Google 6. The new update (M1D63G) seems to have improved 'ok google' detection. Not done much testing yet, but so far so good.
Click to expand...
Click to collapse
I've done some testing and it worked all of the times except one. But that time I just said "Ok, Google" again and it worked. Before it has never worked after a fail without letting the watch be for a long while.
I'll test it more the coming days.
Hey,
So i was trying to get google assistant to get triggered when voicewakeup "ok Emy" is triggered, using tasker.
But, the google assistant is not responding to any question.... it just shows 3 dots (as typing) but does not give results. is there a way to get it to work ?
Thank you !!
Shady282 said:
Hey,
So i was trying to get google assistant to get triggered when voicewakeup "ok Emy" is triggered, using tasker.
But, the google assistant is not responding to any question.... it just shows 3 dots (as typing) but does not give results. is there a way to get it to work ?
Thank you !!
Click to expand...
Click to collapse
I used smart unlock with my pebble to make my phone always unlocked. And then I use tasker to swap ok emy to ok google.
I set a quick "go to home" action and then launch google assistant. It works everytime when I wake up my phone with ok emy, but Huawei is **** at detecting ok emy (needs to shout 4-5 times before it could wake up....)
tiantianisfox said:
I used smart unlock with my pebble to make my phone always unlocked. And then I use tasker to swap ok emy to ok google.
I set a quick "go to home" action and then launch google assistant. It works everytime when I wake up my phone with ok emy, but Huawei is **** at detecting ok emy (needs to shout 4-5 times before it could wake up....)
Click to expand...
Click to collapse
oh but my phone is still locked. i guess it is working with you because your phone gets unlocked on bluetooth pairing
Shady282 said:
oh but my phone is still locked. i guess it is working with you because your phone gets unlocked on bluetooth pairing
Click to expand...
Click to collapse
The trusted voice so far did not work for me.. this is the only nice workaround i found.
tiantianisfox said:
I used smart unlock with my pebble to make my phone always unlocked. And then I use tasker to swap ok emy to ok google.
I set a quick "go to home" action and then launch google assistant. It works everytime when I wake up my phone with ok emy, but Huawei is **** at detecting ok emy (needs to shout 4-5 times before it could wake up....)
Click to expand...
Click to collapse
How do you detect Ok Emy? It used to be detecting the title of the window which is "Sound Trigger" but it doesn't seem to work with Mate 10?
AlphaKimori said:
How do you detect Ok Emy? It used to be detecting the title of the window which is "Sound Trigger" but it doesn't seem to work with Mate 10?
Click to expand...
Click to collapse
Make sure it is written "sound trigger" not Sound Trigger. and enable accessibility and admin for tasker app
Shady282 said:
Make sure it is written "sound trigger" not Sound Trigger. and enable accessibility and admin for tasker app
Click to expand...
Click to collapse
Thanks, Shady282! I am actually using the free Automate app but it should work the same. It isn't detecting the "sound trigger" in the title of the window.
Seems like I need to detect "Place*" instead according to this thread in the Automate forum: https://groups.google.com/forum/#!s...t:date/automate-user/QD1LX2px33I/UFaq398BBAAJ
AlphaKimori said:
Thanks, Shady282! I am actually using the free Automate app but it should work the same. It isn't detecting the "sound trigger" in the title of the window.
Seems like I need to detect "Place*" instead according to this thread in the Automate forum: https://groups.google.com/forum/#!s...t:date/automate-user/QD1LX2px33I/UFaq398BBAAJ
Click to expand...
Click to collapse
if it works with you tell me.... i made assistant to launch but it is not responding to queries when screen is off.
ok updating the google app... added an options in the gogle app settings -> voice to unlock the phone permission !!!!! but seems mate 10 does not support smart voice unlock Useless AI chip
AlphaKimori said:
Thanks, Shady282! I am actually using the free Automate app but it should work the same. It isn't detecting the "sound trigger" in the title of the window.
Seems like I need to detect "Place*" instead according to this thread in the Automate forum: https://groups.google.com/forum/#!s...t:date/automate-user/QD1LX2px33I/UFaq398BBAAJ
Click to expand...
Click to collapse
The automate is able to detect text on the screen. For the keywords, you can use "*Place a call or find your phone“
I initially used the automate but later on turned to Tasker because it is faster and potentially consume less battery.
Hi, I had this issue with my note 4 stock rom (6.0.1), so installed a custom rom that worked fine for about 2 days. Then, suddenly, the problem appears again. I say "ok Google" and the command. Works fine. If I need to say a second command, it does not work. I need to wait for about a minute, then "OK Google" works again. And wait another minute for a third command.
Reinstalled the apps , cleared cache, battery is not on economy mode, retrained my voice model and nothing seems to work. Anyone had this problem? Need help. Thanks.
same issue
i have the exact same issue on my pixel 2
why is it happening?
Anandu48 said:
i have the exact same issue on my pixel 2
why is it happening?
Click to expand...
Click to collapse
Guess I found a temporary solution my friend. Went to apkmirror.com and downloaded Google App 8.55.3 beta by Google LLC, the most recent. Mine was 8.44 but could not upgrade even on playstore. Disabled automatic updates on playstore too. As my phone is rooted, I was able uninstall my old version and installed this 8.55 beta. Now works like a charm. Try it!