Database Develop

HTC One with Google now Everywhere can't hear me.

My problem is not, not having access to to the features of Google now everywhere. after installing it as a system app I unlocked the features. My problem is that it can not detect my voice very well at all(The "OK Google" activation that is)! I have to put it right up to my mouth for it to even register that I have said anything. While if I push the search button it can hear me fine an arms length away. I think it must have something to do with saving power or something. But it is useless to me if I have to hold it up to my mouth. Anyone had the same problem?

Bluetooth audio switches to internal speaker on unlock

The Setup
Moto X (2013)
Android 4.4.4 (unrooted)
Network: Republic Wireless
The Story
It all started a couple of days ago, I lost my phone while at work, I logged onto the Motorola website, remote locked the phone, remotely left a message on the phone with my contact info, and then I made the phone ring remotely to bring it to attention of passers nearby. Shortly after I recovered my phone, I went to the settings and unlocked the phone as that is my prefered setting.
The Problem
Since I got the phone back I've noticed a problem with bluetooth and headphone audio and unusual behavior when unlocking the phone. 1st, when I unlock the phone it makes a noise, and it is the same sound that is used to indicate volume level when you raise or lower volume with the volume buttons, it no longer makes the "click" sound upon unlock. 2nd, whenever I listen to music, via bluetooth or headphones, and if i unlock the phone the audio switches over to the phones internal speakers, but the phone still thinks it is playing audio out of the bluetooth speaker or headphone. In order to get back on the bluetooth speaker I have to dissconect from the speaker and reconnect and for headphones I just to unplug and plug back in.
What I have tried
I have tried turning on and off my phone, Unpairing and reparing my device. I tried to go into my settings, find the bluetooth app and wipe the memory and disable and enable the app, but I could not successfully do that. Searched google and XDA for an answers but I can not find any results that I think resemble my problem. Please help oh great wise and powerful 1337 lords.
Edit* Something else I forgot to mention, another problem is now my phone will not stay in silent or vibrate, I can put it in those modes but as soon as I unlock it, the volume comes back on.

Try Settings > Sounds > Screen Lock Sound.
See if that is checked, or unchecked, toggle a few times and see if that helps?

fury683 said:
Try Settings > Sounds > Screen Lock Sound.
See if that is checked, or unchecked, toggle a few times and see if that helps?
Click to expand...
Click to collapse
Thanks but I have actually tried that, I even did it again just for the heck of it. Something else I forgot to mention, another problem is now my phone will not stay in silent or vibrate, I can put it in those modes but as soon as I unlock it, the volume comes back on.

DCX2 said:
Thanks but I have actually tried that, I even did it again just for the heck of it. Something else I forgot to mention, another problem is now my phone will not stay in silent or vibrate, I can put it in those modes but as soon as I unlock it, the volume comes back on.
Click to expand...
Click to collapse
It seems like something with the Moto Remote services might be interfering. Did you try going in and disabling the stuff on the website? Or disable to Moto app as an administrator in the settings so it stops overriding things? Seems like things are stuck in whatever the Moto app is trying to do if it thinks it's still lost?

fury683 said:
It seems like something with the Moto Remote services might be interfering. Did you try going in and disabling the stuff on the website? Or disable to Moto app as an administrator in the settings so it stops overriding things? Seems like things are stuck in whatever the Moto app is trying to do if it thinks it's still lost?
Click to expand...
Click to collapse
The moto remote services theory has been in the back of my mind, I'll have to explore the website to see if there is an option to disable or reset the service. As far as disabling the moto app as an admin, is there something special I have to do in order the disable apps as in admin? I was under the impression that anything I did on my phone was done as an admin.

DCX2 said:
The moto remote services theory has been in the back of my mind, I'll have to explore the website to see if there is an option to disable or reset the service. As far as disabling the moto app as an admin, is there something special I have to do in order the disable apps as in admin? I was under the impression that anything I did on my phone was done as an admin.
Click to expand...
Click to collapse
In Settings > Security > Device Administrators there should be a list of apps that are activated as admins. Try turning the Moto one off. Might be called Local Wipe Policy maybe?

Problem solved
So I was able to fix the problem!!!
What I did was log onto the motorola website used to track my phone. I made the phone ring ring from the website tracker. After I unlock the phone, I noticed that my phone stopped making the volume adjustment noise upon unlock. My phone is now properly playing bluetooth and headphone audio with out issue now. Thanks for suggesting that I go to the motorola website!

Can't Retrain "OK Google"

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!

"OK Google" from lockscreen. Have to unlock to use any voice commands now.

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.

OK Google - very poor functionality

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?