I switched phones a little while back, and didn't take the time to set everything up on my watch. I've tried a couple times to use "OK Google" to get my watch to set a timer or call someone or something, and gave up and did it manually rather than trying to investigate why it wasn't working. Since this is the original moto 360, and therefore stuck on Android Wear 1.4 (I think), any searching I do for information is difficult because everyone is talking more about Wear 2.0 or Wear OS. The best I can tell, I should be able to enable this feature in Settings > Personalization, but that option doesn't exist on my watch. Any thoughts on where this should be configured, or did Google just decide to remove this feature from our device?
Ok, nevermind. I figured it out. I went into the Google app on my phone > Settings > Voice > Voice Match > Access with Voice Match. I'm guessing if this isn't turned on on the phone, it won't work on the watch. There still doesn't seem to be a setting for this on the watch itself, but this should work.
Related
OK Google hotword detection doesn't work at all for me. I can manually select the microphone in Google Now and voice search works, but it doesn't detect OK Google. Furthermore I can't set up OK Google hotword detection from any screen. I can get to the screen where it says to say OK Google three times, which I do, but nothing at all happens. Audio History is on, language is English (US). I don't see any setting on the phone or in Google that would seem to block it.
Weirdly this post was originally only going to be about setting up the hotword detection from any screen, I've never been able to set that up, but at the very least, detection from Google Now worked fine. But just testing it when typing this post up, I realized that even that doesn't work anymore, but it did like a week ago.
I'm rooted but basically stock, no custom recovery. Only change would be deleting a couple stock apps and adding back/home/menu softkeys at the bottom of the screen. What gives? Anyone have an idea?
Simple as disabling on screen phone in settings
I had the same problem and disabling on screen phone in settings fixed it instantly.
problem resolved
cover to mute
tonyguy2000 said:
problem resolved
Click to expand...
Click to collapse
Very curious what the issue was, and how it was resolved. I went the Asus Support chat route, and was supremely disappointed when they sent me to their website, had me do a reset, a reinstall of the Zenwatch Manager, then decided it must be a hardware issue, and told me it would need to be sent in to be serviced.
If cover to mute doesnt work, and the app wont save the selection when I click apply...but cover works for other features....why blame the watch hardware? Seems more likely to be a phone software issue than watch hardware.
Support had no clue. The watch is saying install android wear, the phone indicates that Zenwatch Manager requires and uses Android Wear configuration, and the guy is telling me I dont need to install Android Wear. Very frustrating half hour!
Not working for me either
I can't get incoming calls (Nexus 5, stock Lollipop 5.0.1) to mute using the feature either. Could it be related to the fact that I wear the watch on my right wrist?
nah, sounds like a hardware issue... send it in for service.
nah, sounds like a hardware issue... send it in for service.
Are you putting your palm ON the watch? That's what I have to do with my Moto 360.
cover to mute
What's odd, is cover with palm does work for other things....if you want to return to dismiss whatever is on screen, and return to the watch screen, so the cover function works! And the phone calls can be answered or dismissed from the watch with a right or left swipe. Its just that function in zenwatch manager.
Here was my solution
I had this problem too, and found a solution.
PROBLEM: On my phone, in the Zenwatch Manager app, under the "Cover to Mute" setting, I would tick the box next to "Incoming call", then "apply", but when I would go back into that setting, the box would be unticked.
SOLUTION:: On the WATCH, start FoneHelper (touch the clock to get the main menu--where it says "speak now" up top--scroll down and press the menu item "start", scroll and press "fonehelper). You will then have the option to toggl "Cover to Mute." I was able to enable the setting from that screen.
*Incidentally, when I do it that way, I can immediately see that choice reflected on my phone, in the Zenwatch Manager App. I still cannot use the Zenwatch Manager to enable this setting, but I've succesfully done it via my watch multiple times.
Hopefully this is helpful for someone else as well.
Confirmed resolution!
nlwclark said:
I had this problem too, and found a solution.
PROBLEM: On my phone, in the Zenwatch Manager app, under the "Cover to Mute" setting, I would tick the box next to "Incoming call", then "apply", but when I would go back into that setting, the box would be unticked.
SOLUTION:: On the WATCH, start FoneHelper (touch the clock to get the main menu--says "speak now" up top--scroll down and press the menu item "start", scroll and press "fonehelper). You will then have the option to toggl "Cover to Mute." I was able to enable the setting from that.
*Incidentally, when I do it that way, I can immediately see that choice reflected on my phone, in the Zenwatch Manager App. I still cannot use the Zenwatch Manager to enable this setting, but I've succesfully done it via my watch multiple times
Hopefully this is helpful for someone else as well.
Click to expand...
Click to collapse
That's it! Even Asus support was stumped, but that setting is the cause/solution!
Thanks for taking the time to provide such a well written response! Thanks again! +++
Thank you so much. Having the same problem and this totally fixed it for me!
On Nexus 5 and Android 5.1 installed this does not help. Problem is, that Watch put Phone into "Interrupt priority" state, which allows only important events to ring or vibrate. But this setting does not prevent ring or vibration, which is already in progress during the incoming call. I tried to use Takser app to set Silent mode on, ringer off, vibrate off, interrupt mode to None - but none of them helped. It can mute the ringer, but not the vibration. But then i figured out the solution. First, you need a rooted phone. Then create Tasker profile for variable set event "%INTERRUPT~priority". This will trigger event, when Watch will set the phone to "interrupt priority state". Create a task for this profile to just simulate pressing volume down key: select Button action to do this. This will completly mute the call.
Also, ASUS support told me, that this issue will be fixed in android 5.1.1 in the middle of may.
Ever since the Lollipop upgrade, the only way I can get "Ok Google" recognition to work from all screens is to disable S Voice. But when I do that, I can no longer voice-control the built-in camera app (it tells me I have to enable S Voice).
Is there a way to fix this, or are we now forced to abandon one of these two useful features?
Gary02468 said:
Ever since the Lollipop upgrade, the only way I can get "Ok Google" recognition to work from all screens is to disable S Voice. But when I do that, I can no longer voice-control the built-in camera app (it tells me I have to enable S Voice).
Is there a way to fix this, or are we now forced to abandon one of these two useful features?
Click to expand...
Click to collapse
Are you sure you have that option activated in the camera under settings?
Also, I'm not a s/voice user myself, but I don't have it disabled. I just removed it from being activated from the home button.
Kamau54 said:
Are you sure you have that option activated in the camera under settings?
Click to expand...
Click to collapse
It turns off when I disable S Voice. If I try to turn it back on, it tells me I need to enable S Voice first.
Also, I'm not a s/voice user myself, but I don't have it disabled. I just removed it from being activated from the home button.
Click to expand...
Click to collapse
And does that let you use "Ok Google" recognition from all screens (including the lockscreen)? For me, that option in the Google Now settings is greyed out unless I disable S Voice.
No. Disable Svoice, activate ok google detection. Open your camera app and turn on voice. It will ask to enable Svoice. Enable it. Ok google voice still works on all screens and voice recognition works in the camera app as well.
Exactly correct.
erick161 said:
No. Disable Svoice, activate ok google detection. Open your camera app and turn on voice. It will ask to enable Svoice. Enable it. Ok google voice still works on all screens and voice recognition works in the camera app as well.
Click to expand...
Click to collapse
Works great. Thank you!
Ok Google Fix
This may help those who updated to 5.0.1 on the At&t Note 4. It may work for other note 4's. This applies if you already had Google Now set to work on all screens along with various other settings and now they are greyed out. If you never could get Google Now to work on all screens in 4.4.4 that is a different problem.
1. Disable S Voice, the Samsung voice control. Simply go to apps and disable it.
2. Either Restart your Phone, or Power it Off then turn it back on.
3. Try the settings in Google Now Voice again. The first setting which probably worked before - "From The Google App" should still be able to be toggled on and off.
The Second setting, "From Any Screen" May now work and let you train your voice. A clue is the very bottom of the screen "Train Voice Model" and "Delete Voice Model" should no longer be greyed out.
If the second setting gets you to the next screen now where you say Google Now three times but nothing happens, go to the next the step.
4. Put your Note 4 into safe mode. You will not be looking for any programs that might be blocking Google Now as you might expect. I know what is blocking it, it's S Voice that even though is turned off is still blocking it.
If you do not understand safe mode, or have any reservations doing it, don't. Though I feel it is a safe thing to do, I am not going to give instructions how to do it, you can find it online easily. I take no responsibility if you find how to do it then make a mistake somehow and screw up your phone.
5. Once in safe mode, and staying in safe mode and when the phone has loaded everything it is going to load, go to the Google Now settings again and you should see all settings available now. In the second setting "From Any Screen" toggle it on and when it takes you to the voice training do the three steps of Google Now voice training.
At that point you are done. Remember, there are other settings that may affect the use of Google Now but if you had it working before the Lollipop upgrade those settings should not have changed.
6. Simply restart the Note 4 and Google Now should work from any screen again.
7. You should be able to restart S Voice at this point if you need it, primarily for the camera voice commands. I decided to leave mine disabled since I rarely to never use the camera voice commands. You do not need S Voice to be active to use Google Now.
tampa8 said:
This may help those who updated to 5.0.1 on the At&t Note 4. It may work for other note 4's. This applies if you already had Google Now set to work on all screens along with various other settings and now they are greyed out. If you never could get Google Now to work on all screens in 4.4.4 that is a different problem.
1. Disable S Voice, the Samsung voice control. Simply go to apps and disable it.
2. Either Restart your Phone, or Power it Off then turn it back on.
3. Try the settings in Google Now Voice again. The first setting which probably worked before - "From The Google App" should still be able to be toggled on and off.
The Second setting, "From Any Screen" May now work and let you train your voice. A clue is the very bottom of the screen "Train Voice Model" and "Delete Voice Model" should no longer be greyed out.
If the second setting gets you to the next screen now where you say Google Now three times but nothing happens, go to the next the step.
4. Put your Note 4 into safe mode. You will not be looking for any programs that might be blocking Google Now as you might expect. I know what is blocking it, it's S Voice that even though is turned off is still blocking it.
If you do not understand safe mode, or have any reservations doing it, don't. Though I feel it is a safe thing to do, I am not going to give instructions how to do it, you can find it online easily. I take no responsibility if you find how to do it then make a mistake somehow and screw up your phone.
5. Once in safe mode, and staying in safe mode and when the phone has loaded everything it is going to load, go to the Google Now settings again and you should see all settings available now. In the second setting "From Any Screen" toggle it on and when it takes you to the voice training do the three steps of Google Now voice training.
At that point you are done. Remember, there are other settings that may affect the use of Google Now but if you had it working before the Lollipop upgrade those settings should not have changed.
6. Simply restart the Note 4 and Google Now should work from any screen again.
7. You should be able to restart S Voice at this point if you need it, primarily for the camera voice commands. I decided to leave mine disabled since I rarely to never use the camera voice commands. You do not need S Voice to be active to use Google Now.
Click to expand...
Click to collapse
Used to
Worked at stage 3. Reenabling S Voice rebroke OkGoogle. RE Disabled S Voice. All that's changed is either the screen must be on or it must be plugged in. Like my Note Pro. Used to just need to be on..screen off and all.
That's a change with Lollipop and not a "problem." (now it is screen on or charging) It appears Ok Google no longer works with the screen off by design, at least on the Note 4.
I can keep S Voice on after doing the steps. (Though I have since turned it off) Try doing all the steps and while in safe mode turn off then on the settings. It's possible this makes Ok Google the "default" over S Voice.
My Moto 360 Gen 1 was working fine until two days ago. For no reason, the "call" voice commend no longer calls. It will go through the whole calling animation, and then returns to the watch face. Nothing triggers on the phone. Other voice commands still work. I can still text, open navigation and set alarm through my watch.
I have reset the watch and reinstalled Android Wear app, but nothing change. Anyone else experiencing this? :crying:
edit: It is not just the voice command. When I go to "contact" on my watch, and click "call" with my finger, the animation on the watch will appear, but calling won't trigger on the phone.
Actually, I figured it out. For some reason, the phone app lost its default priority. So every time I tried to call via my watch, the phone doesn't know which app (phone or google hangout dialer) to open. Resetting the default calling app fixed it.
I have the latest wear OS on my Huawei watch and now when someone calls me i am not able to listen and talk through the watch. Has anyone experienced this after the update?
Check in "Settings" > "Connectivity" > "Bluetooth" and see if "Play phone voice call on watch" is enabled. I found mine was disabled when I had previously has it enabled before the update.
I have enabled that setting but it still does not let me receive and talk through the watch inspector gadget style.
Maybe try turning the watch setting off then back on again? Or check the settings on your phone for "HUAWEI WATCH 0257" under your paired bluetooth devices. The layout of this depends on your phone and the version of Android it's running. For me on my Moto Z2 Play running 8.0 its: "Settings" > "Connected devices" > "Bluetooth", There is a little cog to the right of "HUAWEI WATCH 0257". In that pop up window under "Use for" I have "Phone audio" enabled.
Beyond that, I'm not sure what else to say. I don't use my watch like that often.
Factoty reset my watch and its now working. Man that was way to much like hard work
Fingers crossed that help you
I had exactly the same problem. It started after downloading and using additional watch faces.
I had to reset to factory settings, the watch faces returned to default, all OK.