Related
EDIT: I have modified this post to focus more on getting google now/touchless control to stop making calls. I think this should be doable, but I'm banging my head against the wall trying to figure out how?!?
Please read my second post. However, feel free to comment on the other questions below as they are still bugging me too.
I know I talk louder than most folks. When I ran the touchless control training on my Moto X Dev Ed, I have to really talk lower than I normally do. Is there some way to adjust the mic level so I can talk normal?
Also, sometimes I have to say "ok google now" a few times to get the phone to respond, maybe once out of every 10 times this happens. Any suggestions on this?
Additionally, sometimes it will try to call a contact when the phone is locked after I say "ok google now", even though I have this option unchecked under settings->touchless controls. What gives?
I'm running a stock 4.4.2 rom that is unlocked and rooted . Touchless Controls version 4.3.11.1 and Google Search version 3.3.11.1069658.arm.
I really love the phone and bought it to control my home with my voice (which works great for the most part). Hopefully someone has suggestions on fixing these small issues.
Update: disabling all Touchless Control commands for the phone lock screen does nothing.
I went to Touchless Controls -> Comamnds while locked -> unchecked everything, but my phone still makes calls when I say "call [contact name]" and the phone is locked, along with the other commands. What a joke!?! Does Google test software before publishing it?!? I guess simple if/then logic is beyond a company to get right before releasing an app.
For Google Search I also ensured Google Search->Settings->Phone search->Contacts is unchecked. I also unchecked everything else. Google Search->Settings->Accounts & privacy->Contact recognition is also unchecked and Perosnal results is turned off. Google Search/Touchless Control still uses my contact information to make calls (without my consent) regardless of these settings too.
Allowing it to make calls would be fine if it didn't randomly misunderstand a command and try to make a call.
etc6849 said:
Update: disabling all Touchless Control commands for the phone lock screen does nothing.
I went to Touchless Controls -> Comamnds while locked -> unchecked everything, but my phone still makes calls when I say "call [contact name]" and the phone is locked, along with the other commands. What a joke!?! Does Google test software before publishing it?!? I guess simple if/then logic is beyond a company to get right before releasing an app.
For Google Search I also ensured Google Search->Settings->Phone search->Contacts is unchecked. I also unchecked everything else. Google Search->Settings->Accounts & privacy->Contact recognition is also unchecked and Perosnal results is turned off. Google Search/Touchless Control still uses my contact information to make calls (without my consent) regardless of these settings too.
Allowing it to make calls would be fine if it didn't randomly misunderstand a command and try to make a call.
Click to expand...
Click to collapse
I cannot get control of Google search volume during a Bluetooth connection with my Jawbone.
http://forum.xda-developers.com/moto-x/general/workaround-fix-loud-prompt-google-voice-t2725610
Your bluetooth volume issue sounds crazy. You'd think Motorola's engineer's could spot such simple issues assuming they actually use their products, but I guess not. The phone is really well engineered otherwise. These types of errors might be ok for beta software, but not after many revisions.
I've used the "OK Google" feature for a long time on the Nexus 6. I run the stock OS always upgrading through 5, 6, 7 and now 7.1.1. The problem is too many false positives. Frequently "OK" is enough to trigger without the "Google".
So I thought I would retrain. I've tried this on 6.x , 7, and 7.1.1 and it always fails. I get one of several error messages, "bad timing", "too noisy", "too loud". It never even succeeds for one of the 3 required samples.
When I trained originally probably back on 5.x I had no trouble with the training, but there have always been false positives, though more now than before.
If I record my voice the playback is crystal clear, in fact If I play back a recording of "OK Google" it happily triggers. I have tried retraining in safe mode, and it has the same failures. I go out of the way to make sure I am in a completely quiet environment when training.
I'm tempted to delete my old training, but fear that I will still not be able to train, and have nothing.
Any ideas?
Be persistent, and make sure the room you are in has NO noises whatsoever. The issues with Google voice commands are common in the AOSP ROMs, whereas stock ROMs function correctly.
Strephon Alkhalikoi said:
Be persistent, and make sure the room you are in has NO noises whatsoever. The issues with Google voice commands are common in the AOSP ROMs, whereas stock ROMs function correctly.
Click to expand...
Click to collapse
I've always used the official stock Google firmware, quiet room, MANY repetitions all fail on the Nexus 6. Same room, Nexus 9, same stock official version, retrains work every time.
As I've pointed out already, I never had this problem on the stock ROMs, but on AOSP training was a nightmare. When the phone thinks your laptop's chill mat is too loud, it's a problem. However persistence in this case paid off.
Strephon Alkhalikoi said:
Be persistent, and make sure the room you are in has NO noises whatsoever. The issues with Google voice commands are common in the AOSP ROMs, whereas stock ROMs function correctly.
Click to expand...
Click to collapse
No amount of persistence worked. What did work was using a bluetooth headphone for input. It accepts the training every time. Strange since recording from the phone mics are crystal clear. Can't understand why I had to go to bluetooth for the training.
That said no matter how much training I did, it still triggered much of the time on "OK" without the Google, which is problematic for me.
I did find a solution to that. Since I could now train, I trained it to take "KO Google", and "KO" is not part of my normal usage.
I've not had this problem but my phone makes me reset the OK Google in every boot. Anyone else experience this?
tApPeD fROM mY nExUs 6
Check the thread you made. I replied there.
Strephon Alkhalikoi said:
Be persistent, and make sure the room you are in has NO noises whatsoever. The issues with Google voice commands are common in the AOSP ROMs, whereas stock ROMs function correctly.
Click to expand...
Click to collapse
I agree with original poster. It is not an issue of the room not being quiet enough. I too have a Nexus 6 and I am using completely stock Android. In my first year of ownership I never had trouble training or retraining the command trigger.. I'm in a completely silent room with no fans or anything, and holding the phone at normal distance, the trainer says it can't hear me or there's a problem with the microphone. If I hold it a little closer or speak louder it says I'm too close or too loud. By the way it continually fails. Luckily my original voice training is intact so I still use that.
My microphone does actually work though because my voice dictation works perfectly, as evidenced by this entire post which I am voice dictating. Also as the original poster said, recording my voice or ambient​ audio sounds perfectly fine when I play it back.
---------- Post added 25-04-2017 at 12:07 AM ---------- Previous post was 24-04-2017 at 11:24 PM ----------
kmandel said:
. I get one of several error messages, "bad timing", "too noisy", "too loud". It never even succeeds for one of the 3 required samples.
If I record my voice the playback is crystal clear, in fact If I play back a recording of "OK Google" it happily triggers. I have tried retraining in safe mode, and it has the same failures. I go out of the way to make sure I am in a completely quiet environment when training.
Click to expand...
Click to collapse
Regarding the issue where the training screen does not hear your voice properly, it turns out that the language your phone is set to matters, which seems obvious but in my case I was using UK English (because I like it when my maps and other apps talk to me in a British female voice).
I changed it back to American English and the voice retraining immediately started working! After I retrained it, I then put my phone back on British English. Its been working nicely.
Another tip I came across from other forums is to check your accessibility settings, and either completely disable them or check which apps have accessability permissions and disable all of them or in particular some of the less established third-party apps. Some of these apps hijack the microphone access in non-standard ways. I assume once you have made the retraining work, you can then allow those apps once again.
For me it never came to that, the language settings were the culprit..
One final tip that other users have said worked for them was to uninstall the Google app, which does not truly uninstall it but just removes all the updates. Then reapply the updates and restart the phone. This works for some users.
Tarototh said:
I agree with original poster. It is not an issue of the room not being quiet enough. I too have a Nexus 6 and I am using completely stock Android. In my first year of ownership I never had trouble training or retraining the command trigger.. I'm in a completely silent room with no fans or anything, and holding the phone at normal distance, the trainer says it can't hear me or there's a problem with the microphone. If I hold it a little closer or speak louder it says I'm too close or too loud. By the way it continually fails. Luckily my original voice training is intact so I still use that.
My microphone does actually work though because my voice dictation works perfectly, as evidenced by this entire post which I am voice dictating. Also as the original poster said, recording my voice or ambient​ audio sounds perfectly fine when I play it back.
Click to expand...
Click to collapse
When this thread was initially active, a broad spectrum of custom ROM users - including myself - were having problems training the Google Assistant. From what I recall of the issue, the problem was related to the Motorola Always On Voice app and was resolved by Motorola pushing out a new voice app that was incorporated into Google's Android 7.1.1 builds.
Stock ROMs, including debloated ROMs based off stock, never had this issue. So it's a surprise to me that you had issues. I would suspect yours is a different issue from the one being discussed here, because from personal experience I guarantee the hardware was not the issue when the OP originally posted this thread.
I can attest to the accessibility settings being the issue when the system fails to recognize you saying "OK Google" during voice retraining. In my case I own a Bluetooth headset which had accessibility settings. I believe this was so that it would give me voice feedback for some notifications. When I turned off the accessibility settings for my Samsung U Level Pro Bluetooth headphones I was able to go back and retrain my voice model with no problem!
I've just upgraded from Pixel XL to Note8 and mostly I am very pleased, but for the very disappointing lack of proper implementation of Google Now/Assistant.
When the screen is off, I say OK Google, and the screen comes on ready for my command. Then I ask something and I get "Can't reach Google at the moment." This is absolute nonsense. I am sitting at my desk, 1m from my fibre optic router and I get 60mb download speeds. I am also connected to 4g from my desk, and if I run any app using the net, it works fine. I always get my emails, WhatsApp, Duo, Allo etc... so no problem there.
Other variations, things that sometimes happen:
1/ "OK Google" with screen off - the phone makes it's listening sound, but the screen stays off, then a minute later when I switch the screen on manually, I get the answer to my question!
2/ "OK Google" with screen off - the phone makes two sounds, the listening one then the cancelling one almost simultaneously
3/ "OK Google" with screen of - no response at all.
Anyone know what is going on here?
Thanks,
Mark.
fredphoesh said:
I've just upgraded from Pixel XL to Note8 and mostly I am very pleased, but for the very disappointing lack of proper implementation of Google Now/Assistant.
When the screen is off, I say OK Google, and the screen comes on ready for my command. Then I ask something and I get "Can't reach Google at the moment." This is absolute nonsense. I am sitting at my desk, 1m from my fibre optic router and I get 60mb download speeds. I am also connected to 4g from my desk, and if I run any app using the net, it works fine. I always get my emails, WhatsApp, Duo, Allo etc... so no problem there.
Other variations, things that sometimes happen:
1/ "OK Google" with screen off - the phone makes it's listening sound, but the screen stays off, then a minute later when I switch the screen on manually, I get the answer to my question!
2/ "OK Google" with screen off - the phone makes two sounds, the listening one then the cancelling one almost simultaneously
3/ "OK Google" with screen of - no response at all.
Anyone know what is going on here?
Thanks,
Mark.
Click to expand...
Click to collapse
they broke ok google about a year ago, very sad.
SOLUTION!
Hello again all.
After much searching, I tired something suggested back in 2015 by someone... an obvious suggestion, but not something EE tech support or Samsung had suggested.
Go to Settings>Apps>Google
Then go to Storage
Clear Cache
Clear Data
Reboot.
The suggestion was to try force close Google app, but that would not work, I tried a few times, but then just cleared Cache and Data, rebooted and it works perfectly, just like my Pixel XL
Woo hoo!!
Mark.
fredphoesh said:
Hello again all.
After much searching, I tired something suggested back in 2015 by someone... an obvious suggestion, but not something EE tech support or Samsung had suggested.
Go to Settings>Apps>Google
Then go to Storage
Clear Cache
Clear Data
Reboot.
The suggestion was to try force close Google app, but that would not work, I tried a few times, but then just cleared Cache and Data, rebooted and it works perfectly, just like my Pixel XL
Woo hoo!!
Mark.
Click to expand...
Click to collapse
This doesn't work for me. Even after clearing cache and data, rebooting, starting Assistant and running through the setup again, I get the same behavior with the screen off, a message that says "Can't reach Google at the moment."
I had this problem, disabled Bixby, works properly now.
Sent from my SM-N950U using Tapatalk
Liface said:
This doesn't work for me. Even after clearing cache and data, rebooting, starting Assistant and running through the setup again, I get the same behavior with the screen off, a message that says "Can't reach Google at the moment."
Click to expand...
Click to collapse
Check that your battery saving modes are not killing the Google app from running in the background. This is the most likely scenario, that the app isn't running at all.
Mine get borked every time I toggle between power saving modes. I like to use Extreme power saver for overnight and Medium mode at work.
Medium mode straight up breaks OK Google. Not sure if this is by design or a bug, but it just will not hear me.
Coming out of either mode (and extreme is the worst) and neither "Hi Bixby" or "OK Google" work until I do another full reboot. Sometimes I have to reboot then go back into Google voice setting to switch the option back on manually. If I try to do this before the reboot the option is greyed out and I can't move it. Sometimes just the reboot is enough.
It's random as hell and extremely annoying. I have submitted the bug to Samsung via the feature in the Samsung Members app, but that was over two weeks ago and has seen no response.
Interesting post. My wife's OK Google voice doesn't work but mine does. Both USA T MO version. With works I'm referring to having the Google widget on home screen and saying the sentence OK Google. Mine responds and hers doesn't. With screen ON.
Sent from my SM-N950U using Tapatalk
fredphoesh said:
Check that your battery saving modes are not killing the Google app from running in the background. This is the most likely scenario, that the app isn't running at all.
Click to expand...
Click to collapse
That's not it, I rarely use battery saving mode and this happens 100% of the time.
Ok google for me just does not work.
Anyone get a fix for this?
"Ok Google" works when screen is on, but if I say it while the screen is off, it makes the noise and I get edge lighting indicating it's listening, however it doesn't respond and when I manually turn on the screen assistant is open saying "can't reach Google at the moment."
Power saving mode is off, tried disabling Bixby, clearing cache, nothing.
Hellothere37 said:
clearing cache, nothing.
Click to expand...
Click to collapse
so clearing cache of Google app and rebooting did not help at all?
bizarre, that fixed it for me...
I have a UK version.
I'd phone Samsung!
I'm frustrated too because I can't figure out how to use it while in power saving mode. I thought I added it correctly in the optimized battery usage apps (disabled google, ok google enrollment and voice assitant there). I can't see it as an option to select under unmonitored apps. Any idea what I'm missing?
Thanks for any help
This is strange to hear. Mine has worked flawlessly, as good as my pixel XL. Screen off and locked or not. I say ok Google, phone unlocks, and then I ask it whatever. Only thing ive done is disabled bixby by way of BK disabler.
Sent from my SM-N950U using Tapatalk
May be coincidental but I have not the slightest problem, and yeah, I uninstalled the Bixter. One thing I have read somewhere or other is that the OK Goog command is also subject to the level you set for Bix. In other words with sensitivity turned down for Bix it's also turned down for Goog. I never tested that one but might be worth looking at...
gingi999 said:
they broke ok google about a year ago, very sad.
Click to expand...
Click to collapse
So two things I wanted to mention the first one was my old phone case actually covered one of the microphone holes. Meaning the cut-out wasn't there so I used a drill and made a hole and it fixed part of the problem.
I have to be honest with you the Note 8 solved all the OK Google problems that I was having the past. For example the lockscreen didn't used to work and it works now I mean it was really a piece of trash with my Galaxy S7 Edge and now I can't imagine living without it.
Having problems like the first post where google assistant/ok google is non responsive all around. I've noticed that if I clear cache and data it falls back to just "ok google" and it work all the time. If I activate the google assitant with ok google it fails immediately. Who can fix this?
I have face unlock set up on my phone but if I want to set my alarm for example by saying 'ok Google set an alarm' the phone asks for me to show my face which isn't practical. I've looked in the settings but nothing seems to work.
Can anyone see something im missing?
Cheers
I have this problem as well. I use the Google Assistant quite a bit whilst driving, so it is really annoying that i have to then unlock the phone
Yep, same problem. 'Unlock with voice' doesn't really work. I've found this on other phones too. Be great if anyone has a solution.
Bluetooth unlock with the car set as the linked device?
Did anyone find a fix for this? It is annoying as hell.
So I have found two issues so far looking to see if any of you have ran into the same issue and if you have figured out a fix.
First one is when I connect a usb flash drive and I don't move any data to it I hit eject it ejects just fine. If I move a movie or music or photos and I hit eject it doesn't eject and reboots the phone.
Second thing I have found and I believe it's just the new assistant needs some fine tuning. When I use the 3 button navigation and use the old assistant I can say "ok google call home on speakerphone" and it will place a call on speakerphone. When I use the new assistant with gesture navigation it never turns on speakerphone. This can be a potential issue if you need help and the speakerphone doesn't activate. Which happened to me when my back went out and I couldn't get to my phone. Luckily I still had my pixel 2 xl when this happened I was able to call my wife. I contacted google and made them aware and sent them a log so hopefully they will fix this. Has anyone else seen these issues or better yet found a fix.
One other thing I have naptime installed and when at the gym I try to use theh hand gestures with soli and they seem to be really bad. I am wondering if naptime is putting soli to sleep and also how close do you need to be to the phone for the gestures to work.
bigv5150 said:
So I have found two issues so far looking to see if any of you have ran into the same issue and if you have figured out a fix.
First one is when I connect a usb flash drive and I don't move any data to it I hit eject it ejects just fine. If I move a movie or music or photos and I hit eject it doesn't eject and reboots the phone.
Second thing I have found and I believe it's just the new assistant needs some fine tuning. When I use the 3 button navigation and use the old assistant I can say "ok google call home on speakerphone" and it will place a call on speakerphone. When I use the new assistant with gesture navigation it never turns on speakerphone. This can be a potential issue if you need help and the speakerphone doesn't activate. Which happened to me when my back went out and I couldn't get to my phone. Luckily I still had my pixel 2 xl when this happened I was able to call my wife. I contacted google and made them aware and sent them a log so hopefully they will fix this. Has anyone else seen these issues or better yet found a fix.
One other thing I have naptime installed and when at the gym I try to use theh hand gestures with soli and they seem to be really bad. I am wondering if naptime is putting soli to sleep and also how close do you need to be to the phone for the gestures to work.
Click to expand...
Click to collapse
How long do you wait until you try to eject it after moving music/photos to it? Maybe give it a minute or two before trying? It may still be trying to write to the card.
blazinazn said:
How long do you wait until you try to eject it after moving music/photos to it? Maybe give it a minute or two before trying? It may still be trying to write to the card.
Click to expand...
Click to collapse
I will try it but it's not like I do it immediately its just weird my pixel 2 xl never did it
I waited a few seconds and instead of doing it from the drop down menu I went into settings>storage and ejected it took forever but ejected and didn't reboot.
Also why does it start out moving massive amounts of data like 60 mb a sec then slows to a crawl 1-3 mb a sec