http://lifehacker.com/nova-launcher-adds-ok-google-support-no-root-requir-1586692372.
It works on my X but does not replace "Ok Google Now" with touchless controls. Hotword must be turned on in settings.
My Moto X hasn't had the actual google hot word working since November. The nova launcher hot word works great on my Nexus 10
Sent from my XT1060
rupterr said:
http://lifehacker.com/nova-launcher-adds-ok-google-support-no-root-requir-1586692372.
It works on my X but does not replace "Ok Google Now" with touchless controls. Hotword must be turned on in settings.
Click to expand...
Click to collapse
Action Launcher Pro also got same update.
I don't understand. How is this different from "OK Google Now" that is built-in to the Moto X? I am using Apex for several month without any issues with the hotword.
Or is the ingenuity here that you have to say one word less, Nexus 5 style?
cannondale0815 said:
I don't understand. How is this different from "OK Google Now" that is built-in to the Moto X? I am using Apex for several month without any issues with the hotword.
Or is the ingenuity here that you have to say one word less, Nexus 5 style?
Click to expand...
Click to collapse
It's for those who DON'T have a moto x and use Nova. But there are some advantages still.
Touchless controls doesn't recognize nicknames such as "call my wife, call my girlfriend, call "nickname associated with contact" So if you're just on your phone you can use the google hotword.
Unfortunately I my google hotword is disabled and turning off touchless control doesn't bring it back nor is the option available in google now settings to enable.
^^Basically yes, but also if you are on your unlocked homescreen with Nova Launcher you can say "Ok Google" without touching anything as well.
I was using Google search 3.2 after uninstalling version 3.4, which took hotword detection away, hotword works fine with 3,2. It all seems moot now though after installing Android 4.4.3 today. With the install it updated Google Search to 3.4 and there is no way that I see to uninstall updates to Google Search anymore in Android 4.4.3, the Android update took the option "uninstall updates" away from Google search.
So if anyone wants hotword to work on your X don't update to 4.4.3 and keep Google Search on version 3.2. That is until an update to search might fix the issue?
Related
[email protected],
I've CyanogenMod 11 M7 installed on my Samsung Galaxy Note 3 N9005 (international). I have installed the newest version of the Google Search App and the Google Now Launcher as well. Google Now and the hotword detection are activated. But the hotword detection 'OK Google' does not work.
Is there no support for this in CM11? If not in general, is it not supported in CM11 for the Galaxy Note 3?
I've tried different workarounds. Usually I use Nova Launcher. As of late it supports the hotword detection as well. I thought maybe the feature is buggy. So I tried it with Trebuchet and Google Now Launcher. Both didn't work. It also doesn't work in the Google App itself!
I've configured my system in german. Usually voice input and also the hotword detection should work in german as well. Again I thought maybe it's buggy and switched to english (US). It didn't work.
I also never saw the prompt for the hotword in the Google search bar.
I use Xposed Framework with a module called Xprivacy. With Xprivacy one can restrict permissions for Apps, including access to media, like the camera and microphone. I thought this could be a reason, but I haven't restricted media for the Google Search App, Google Now Launcher and Nova Launcher. Can Xprivacy be a problem anyway?
Does anyone have the same problem? Does anyone know how to fix this?
Greets
The matter has sorted itself out. I got an update of the Google Search App today, now it works! :victory: :fingers-crossed:
It seams that this was a bug. I still don't see the prompt for the hotword in the Google search bar, but maybe this is another tiny bug and doesn't bother me.
I've still configured my system in german. Hotword detection works in the Google Search App, Google Now Launcher and even Nova Launcher! It doesn't work in Trebuchet, but one could assume that.
Anyway, thanks to everyone who contemplated about the case.
I have some more interesting information.
Because hotword detection didn't work again, I dealt with the topic again.
It seems that it wasn't a bug. I used Titanium Backup to integrate updates of system apps into the system. I don't know why , but obviously this caused the problem.
So I completely uninstalled the app using Titanium Backup and installed it again via the Play Store. Now hotword detection works again.
So if you have the same problem, do not integrate the newest version of the app into the system, or if you don't have it installed, simply install it via the Play Store and you should be fine. :good:
Greets
Really don't like moto voice, any way to use Google Now in lieu of it? Root of otherwise? It's l literally the only thing that I want to return the pure for the 6p.
Don't you just turn off the voice assistant in the Moto app?
Isn't it literally the same thing though?? Moto voice uses Google search and I'm sure any ok Google command works with moto voice...just customize your launch phrase to "ok Google" and you should be fine...
rpudner said:
Don't you just turn off the voice assistant in the Moto app?
Click to expand...
Click to collapse
That doesn't make it work with the screen off.
therealrayzzor said:
Isn't it literally the same thing though?? Moto voice uses Google search and I'm sure any ok Google command works with moto voice...just customize your launch phrase to "ok Google" and you should be fine...
Click to expand...
Click to collapse
Most of the commands are just handed off to Google any way, so it's much slower than just Google from the get go. I have the Pure and the 6P and the 6p is way faster with voice commands.
Has anyone received the Google Assistant update yet? It was suppose to role out yesterday. Just wondering since the default for this phone is Moto assistant if we will get it or not.
Love the Nougat update
Gary
I installed the "Play Services Info" app by weberdo and used it to download Google Play Services version 10.2.99 (440-148249840) from APK Mirror. After a couple of reboots and disabling Moto Voice, Google Assistant became active. I had to touch the microphone icon, and after a couple of tries, it went into "configure" mode and learned my voice. Now working fine.
rhickers said:
I installed the "Play Services Info" app by weberdo and used it to download Google Play Services version 10.2.99 (440-148249840) from APK Mirror. After a couple of reboots and disabling Moto Voice, Google Assistant became active. I had to touch the microphone icon, and after a couple of tries, it went into "configure" mode and learned my voice. Now working fine.
Click to expand...
Click to collapse
Didn't work for me. Oh well, I guess I'll just have to wait.
Gary
Interestingly, for me, even while running on play services 10.2.98, I had all the assistant settings in the google app, and even paired it with my smartthings account, but alas, voice search is still going to the old style search. Updated to 10.2.99 and still seeing the same behavior. I didn't even know we were getting assistant, and was quite excited when I saw the settings, so when it didn't work, of course I got unreasonably upset. oh well
astephon88 said:
Interestingly, for me, even while running on play services 10.2.98, I had all the assistant settings in the google app, and even paired it with my smartthings account, but alas, voice search is still going to the old style search. Updated to 10.2.99 and still seeing the same behavior. I didn't even know we were getting assistant, and was quite excited when I saw the settings, so when it didn't work, of course I got unreasonably upset. oh well
Click to expand...
Click to collapse
Alright, I let it sit for a couple hours, and it's working now. Though, still can't launch it from the microphone button in the google app or the google search bars on the home screens. That still launches the old voice search. Have to long touch the home button or use the "ok google" launch phrase. It's a shame it can't use the always-on mic from moto voice though.
I'm seeing some similar things. Google Assistant came down to my phone automatically. Set up the OK Google voice command. Seems to work fine when launching from the mic button on the assistant, but will not respond to always on mic when the phone is idle.
You do have to disable Moto Voice, or change the voice phrase to something other than OK Google. Phone still responds to Moto Voice command on idle, but not OK Google.
Yea, so unless there's a software update for Moto Voice, we're likely not going to get the always-on mic to work with assistant. There's a dedicated processor on the SoC that handles the always-on mic, and it's tied directly to Moto Voice. Moto voice really doesn't do a whole lot other than listen for the launch phrase. Everything after that point is basically handed off to Google Voice search. It really should be quite a easy fix (pass the requests onto assistant instead of voice search), but I doubt that will happen.
smiley4017 said:
Has anyone received the Google Assistant update yet? It was suppose to role out yesterday. Just wondering since the default for this phone is Moto assistant if we will get it or not.
Love the Nougat update
Gary
Click to expand...
Click to collapse
I woke up this morning and I finally got the assistant. just an FYI
I got it too. However, while it unlocks the phone when locked and the screen being on, it will not wake the phone when saying ok google. You hear the sound prompt that it heard you, but nothing ever follows up and the screen stays black
I am on a Galaxy S8 and Android 7.0.
Following this guidance, http://lifehacker.com/how-to-create-custom-voice-commands-with-tasker-and-aut-1282209195, I installed Tasker and AutoVoice. Google app already installed. I enabled Autovoice accessibility service and AutoVoice Google Now integration.
OK Google is enabled on all screens.
However, when I say "OK Google, use Autovoice" Google consistantly comes back with "It looks like your AutoVoice account is not linked yet." How do I do this?
When I run AutoVoice Testing with my trigger words, they work. I have another 6.0 Android device where all this (Tasker, Autovoice, Google Now) works seamlessly.
Is there some other step required for S8 / Android 7.0 go get AutoVoice integrated with Google Now?
SomebodySysop said:
I am on a Galaxy S8 and Android 7.0.
Following this guidance, http://lifehacker.com/how-to-create-custom-voice-commands-with-tasker-and-aut-1282209195, I installed Tasker and AutoVoice. Google app already installed. I enabled Autovoice accessibility service and AutoVoice Google Now integration.
OK Google is enabled on all screens.
However, when I say "OK Google, use Autovoice" Google consistantly comes back with "It looks like your AutoVoice account is not linked yet." How do I do this?
When I run AutoVoice Testing with my trigger words, they work. I have another 6.0 Android device where all this (Tasker, Autovoice, Google Now) works seamlessly.
Is there some other step required for S8 / Android 7.0 go get AutoVoice integrated with Google Now?
Click to expand...
Click to collapse
There is a difference between using the Google now voice search and using Google assistant. The running service is for Google now. The screenshot you posted is of Google assistant, in which you have to be apart of the Google + community for the app in order for it to work.
If you're just looking for basic usage, use Google now voicesearch and not Google assistant
Acoustichayes said:
There is a difference between using the Google now voice search and using Google assistant. The running service is for Google now. The screenshot you posted is of Google assistant, in which you have to be apart of the Google + community for the app in order for it to work.
If you're just looking for basic usage, use Google now voicesearch and not Google assistant
Click to expand...
Click to collapse
Thank you very much! This is the first clue I've been handed to the source of my problem. You are right. On my px5 head unit, there are no settings for Google Assistant. On my S8, there are. However, I don't know why they are there, or how to disable Google Assistant without disabling OK Google. When I disable GA and speak "OK Google", it immediately asks me to turn GA back on to respond. Do you know how I can resolve this? Again, thanks!
Acoustichayes said:
There is a difference between using the Google now voice search and using Google assistant. The running service is for Google now. The screenshot you posted is of Google assistant, in which you have to be apart of the Google + community for the app in order for it to work.
If you're just looking for basic usage, use Google now voicesearch and not Google assistant
Click to expand...
Click to collapse
SomebodySysop said:
Thank you very much! This is the first clue I've been handed to the source of my problem. You are right. On my px5 head unit, there are no settings for Google Assistant. On my S8, there are. However, I don't know why they are there, or how to disable Google Assistant without disabling OK Google. When I disable GA and speak "OK Google", it immediately asks me to turn GA back on to respond. Do you know how I can resolve this? Again, thanks!
Click to expand...
Click to collapse
Never mind. I found it: https://android.gadgethacks.com/how...ndroid-device-switch-back-google-now-0174676/
Problem is, don't have root on Galaxy S8. Google REALLY needs to give us the option for something like this instead of forcing it down our throats whether we like it or not!!!
SomebodySysop said:
Never mind. I found it: https://android.gadgethacks.com/how...ndroid-device-switch-back-google-now-0174676/
Problem is, don't have root on Galaxy S8. Google REALLY needs to give us the option for something like this instead of forcing it down our throats whether we like it or not!!!
Click to expand...
Click to collapse
You should be able to do it with a shortcut. I use Nova launcher and just use the voice search shortcut and it uses Google now. Or if you have a Google search bar on your screen with the mic in it, that should default to Google voice search and not assistant
Acoustichayes said:
You should be able to do it with a shortcut. I use Nova launcher and just use the voice search shortcut and it uses Google now. Or if you have a Google search bar on your screen with the mic in it, that should default to Google voice search and not assistant
Click to expand...
Click to collapse
Whoa! You're right again! Pressing mic in Google search bar allows me to speak autovoice trigger I set up -- and it works! Mucho thanks!
SomebodySysop said:
Whoa! You're right again! Pressing mic in Google search bar allows me to speak autovoice trigger I set up -- and it works! Mucho thanks!
Click to expand...
Click to collapse
No problem man. I use tasker, autovoice, and autoremote religiously haha. Too much home automation and laziness not to utilize them. You should look into the natural language it can now use. Takes a while to understand and set up, but after that, it's much better than regular recognize
Acoustichayes said:
You should be able to do it with a shortcut. I use Nova launcher and just use the voice search shortcut and it uses Google now. Or if you have a Google search bar on your screen with the mic in it, that should default to Google voice search and not assistant
Click to expand...
Click to collapse
SomebodySysop said:
Whoa! You're right again! Pressing mic in Google search bar allows me to speak autovoice trigger I set up -- and it works! Mucho thanks!
Click to expand...
Click to collapse
Acoustichayes said:
No problem man. I use tasker, autovoice, and autoremote religiously haha. Too much home automation and laziness not to utilize them. You should look into the natural language it can now use. Takes a while to understand and set up, but after that, it's much better than regular recognize
Click to expand...
Click to collapse
I'm having fun, and pulling my hair out, just trying to get this going right now. At least twice this week I was in my car (head unit not installed yet) and really wanted to send time sensitive messages on my s8 using Google Voice. I don't text and drive, religiously. But being able to say "google voice text so-and-so" would have been quite useful.
One last, final question: I've been learning tasker/autovoice on a rooted px5. Just got this galaxy s8 and, of course, it's not rooted. Looks like I shell commands a lot in my profiles, particularly "input keyword" and "input text".
So, if I want to send %avcommnofilter as response to app, do you recommend autoinput for that?
SomebodySysop said:
I'm having fun, and pulling my hair out, just trying to get this going right now. At least twice this week I was in my car (head unit not installed yet) and really wanted to send time sensitive messages on my s8 using Google Voice. I don't text and drive, religiously. But being able to say "google voice text so-and-so" would have been quite useful.
One last, final question: I've been learning tasker/autovoice on a rooted px5. Just got this galaxy s8 and, of course, it's not rooted. Looks like I shell commands a lot in my profiles, particularly "input keyword" and "input text".
So, if I want to send %avcommnofilter as response to app, do you recommend autoinput for that?
Click to expand...
Click to collapse
Figured out this issue here: https://forum.xda-developers.com/u/...to-screen-rooted-device-t3620540#post72644822
SomebodySysop said:
Figured out this issue here: https://forum.xda-developers.com/u/...to-screen-rooted-device-t3620540#post72644822
Click to expand...
Click to collapse
My apologies for not responding! Got caught up with root searching and things of the sort. But im glad you figured it out!
Acoustichayes said:
There is a difference between using the Google now voice search and using Google assistant. The running service is for Google now. The screenshot you posted is of Google assistant, in which you have to be apart of the Google + community for the app in order for it to work.
If you're just looking for basic usage, use Google now voicesearch and not Google assistant
Click to expand...
Click to collapse
FINALLY! This is how you link AutoVoice (or any 3rd party app) to Google Assistant: https://productforums.google.com/d/msg/websearch/HwJUpkrHPr4/xIJACIlEAwAJ
So, you have to say "OK, Google, ask Autovoice to...." followed by your AutoVoice command. Still wish I could just say "OK, Google" then command, but this will do for now.
Anyone else having trouble doing the voice training for the "hey Google" hotword? I am able to setup "ok Google" but not "hey Google" for the life of me. I've uninstalled the Google app, cleared data and cache and still no "hey Google". Using Moto g5 plus 64gb retus. 110% stock and on the newest update 137-93-4. Any information or suggestions to get it working would be much appreciated. Thanks!!
Moto voice has problems with Google assistant. Disable moto voice. You may test Android Mic Fix module from magisk.
Pragnan Saha said:
Moto voice has problems with Google assistant. Disable moto voice. You may test Android Mic Fix module from magisk.
Click to expand...
Click to collapse
I think you misunderstood what I'm saying. My mic works fine. I can setup "ok google" it just doesn't have the prompt to train "hey Google" after I've setup "ok Google". And correct me if I'm wrong but the g5 plus doesn't have Moto voice
I faced the same problem & my Moto E4 Plus also doesn't have Moto Voice, but disabling or uninstalling Moto app fixed the issue. Maybe give that a try.
Just tried it on mine. Running the latest update, January security patch, latest Google update (March 26/beta), full stock. Open Assistant - tap the menu button in the to right - tap the menu (three dot button) - select phone - retrain voice model. It will ask you to say "ok Google" twice then "hey Google" twice. After that it should respond to either prompt.
Sent from my Moto G (5) Plus using Tapatalk
riggerman0421 said:
Just tried it on mine. Running the latest update, January security patch, latest Google update (March 26/beta), full stock. Open Assistant - tap the menu button in the to right - tap the menu (three dot button) - select phone - retrain voice model. It will ask you to say "ok Google" twice then "hey Google" twice. After that it should respond to either prompt.
Click to expand...
Click to collapse
Seems to be the firmware update. I'm on November security patch and my voice model is 3x Ok Google.
Sent from my Moto G5 Plus using XDA Labs
I also used to have this problem.. but it was solved after the January security patch.... Try downgrading the google app version... It was a temporary solution for me..