Hi all,
Recently got a nexus 6 to replace a busted nexus 5, and noticed one of the issues i have with the nexus 6 is that it really struggles to pick up my voice for different tones/volumes. the nexus 5 would pick up the OK google detection almost no matter how i said it. i also noticed when i set up the recordings on my nexus 6 it also struggled to detect my voice, would often make me re-do the recording. ive re-recorded a few times but it stills seems fairly touchy. any thoughts?
Thanks
alex2190 said:
Hi all,
Recently got a nexus 6 to replace a busted nexus 5, and noticed one of the issues i have with the nexus 6 is that it really struggles to pick up my voice for different tones/volumes. the nexus 5 would pick up the OK google detection almost no matter how i said it. i also noticed when i set up the recordings on my nexus 6 it also struggled to detect my voice, would often make me re-do the recording. ive re-recorded a few times but it stills seems fairly touchy. any thoughts?
Thanks
Click to expand...
Click to collapse
Stock or custom? I've noticed the struggling to record issue while setting up, but only on custom ROMs. Also, you should mention which version number of Google services you have, so we can determine if it needs updating.
stock 5.1.1 factory imaged (tmobile) when i got it a couple of weeks ago.
7.5.71 GP services.
the detection is OK, the speech detection is really good once ok google is activated, it just doesnt like the way i say it sometimes. normal american english, no real accent.
if i say "OK Google" it doesnt like it, usually prefers something like "OK GOOGle"
edit i also notice if i pick the phone up and it does the preview-wake it kind of locks out ok google detection for a couple seconds as well. kind of annoying
Related
After the recent update of the "Google" app version to v4.1.24.1672412.arm I was presented with new settings within Google Now and I decided to activate the "Ok Google" hotword detection on any screen on or off. Since then I noticed that the hot word activation occurs at random times when I am just talking normally to someone and it will start recognizing what I am saying (no mention of "ok google") or if I am in subway (NYC) listening to music or just using my phone and the subway stop announcement comes on and it will activate (this has been happening fairly consistently). Any random spoken voices of other people.
I am not sure why this is occuring, I even re-trained my voice a few times but it still continues to occur. Anyone else experience something similar ?
Note: Nexus 6 is completely stock not rooted or even bootloader unlocked.
intothevoid said:
After the recent update of the "Google" app version to v4.1.24.1672412.arm I was presented with new settings within Google Now and I decided to activate the "Ok Google" hotword detection on any screen on or off. Since then I noticed that the hot word activation occurs at random times when I am just talking normally to someone and it will start recognizing what I am saying (no mention of "ok google") or if I am in subway (NYC) listening to music or just using my phone and the subway stop announcement comes on and it will activate (this has been happening fairly consistently). Any random spoken voices of other people.
I am not sure why this is occuring, I even re-trained my voice a few times but it still continues to occur. Anyone else experience something similar ?
Note: Nexus 6 is completely stock not rooted or even bootloader unlocked.
Click to expand...
Click to collapse
I've been experiencing this to but only when I'm driving in my truck with the radio on.
neopolotin75 said:
I've been experiencing this to but only when I'm driving in my truck with the radio on.
Click to expand...
Click to collapse
Good to know I am not the only one!
Delete the app Data , start fresh.
Dxtra said:
Delete the app Data , start fresh.
Click to expand...
Click to collapse
Yeah I did that this morning to see if it happens again. It has been ok so far.
Happens to me a lot while I am giving training and the training was in Arabic ?
Sent from my Nexus 6 using Tapatalk
I switched from the Moto Voice app to the OK Google because the Moto X voice app is terrible. Everything was working great until a few days ago. OK Google only works from the home screen now. Does anyone else have this issue? Is there a work-around to fix it? Thanks!
I'm assuming that the "From any screen" option is checked in the Google app?
imaginaryenemy said:
I'm assuming that the "From any screen" option is checked in the Google app?
Click to expand...
Click to collapse
Correct, and I did the training. It works perfectly on my Moto G. My Moto X has been acting quirky so I am getting an advanced replacement from Motorola. They are now charging a $25 "Premium Fee" for advance replacement. I hate this company ever since Lenovo took over and this will be my last Motorola phone.
Having the same issue.
Starting to regret this phone deeply.
I just realized that I hadn't checked it since my update to 5.1, and it no longer works for me either. It is not a feature I use, but it is a shame that it is broken.
Me neither, which makes me think it's a server side error.
Broken on my Moto X running 5.1 stock or CM 12.1 and my Nexus 5 in the same scenarios, so I think it's a bug in the app not with our phone.
chrisrozon said:
Me neither, which makes me think it's a server side error.
Click to expand...
Click to collapse
raptir said:
Broken on my Moto X running 5.1 stock or CM 12.1 and my Nexus 5 in the same scenarios, so I think it's a bug in the app not with our phone.
Click to expand...
Click to collapse
These certainly sound like the most likely causes, however, is it strange that we are the only people talking about this? If it were a global problem, I would think more people would be complaining.
I had this exact issue and figured out quite a simple fix.
All you need to do is going to the "Moto" app and disable the "Moto Voice" function. The moto voice function apparently takes control of the mic at all times, stopping google now from doing so. Once I disabled the Moto Voice, I could enable Google Now / Ok Google from all screens and didn't get the "microphone is in use, please restart device" error message anymore.
Hope this helps
Yugnoswam said:
I had this exact issue and figured out quite a simple fix.
Click to expand...
Click to collapse
This is not the problem being discussed here. The problem is, after being setup properly, the "OK Google" command only works on the homescreens. Not on the lock screen, not when an app in is the foreground. Are you able to use "OK Google" in these instances?
imaginaryenemy said:
This is not the problem being discussed here. The problem is, after being setup properly, the "OK Google" command only works on the homescreens. Not on the lock screen, not when an app in is the foreground. Are you able to use "OK Google" in these instances?
Click to expand...
Click to collapse
It seems intermittent ever since the last Motorola OTA I received. I can't seem to do OK google from my homescreen anymore although it will occasionally wake from lock screens and in an app if I use it, it will pull me out of the app to the Google Now search screen. I think the whole thing is pretty much bugged to be honest :/
I've found just going into the google search and hitting the mic button much more reliable and thus faster.
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!
Hi to everyone,
Lately I began to experience a weird issue on my OnePlus 3T. More precisely the GoogleNow application starts by itself when the phone is off. It wouldn't be a problem if it weren't talking after it registerd the voice around. Google previously eliminated the unlock of the phone with the voice recognition feature so I suppose it's a bug in OxygenOS. Has someone else experienced this ? Any solution ?
P.S. Sometimes I use Google Now therefore I prefer it to be enabled.
Sometimes not even fully saying OK Google will still activate it. Like"OK G..."
tzbigworm said:
Sometimes not even fully saying OK Google will still activate it. Like"OK G..."
Click to expand...
Click to collapse
The funny part - the "OK Google" doesn't work when the phone is off. I tried several times without success.
Since I think past november, Google Assistant stopped working correctly in my device (spes, 128/6, global) and others from friends (spes, 128/4, global).
The symtoms are, it does react to "Hey Google" (or "Ok Google") but then, when its time to give the order, it doesnt listen, it stays here, with the four colored line like waiting for the sound but the line stays quiet and doesnt move when I talk, like if the mic were not working.
Didn't work after updates, through MIUI 12/13 and Android 11/12.
Anyone have some trick to make it work?
Thanks.
Have same issue but sometimes Google assistant works and sometimes it acts like that, also I noticed that Google assistant doesn't work when screen turned off for some time, it does react to 'Ok Google' if screen just turned off or between couple of minutes of turning off the screen, after that it doesn't respond, I believe it has something to do with MIUI optimization so I already set Assistant as No restrictions in battery saving settings but still, same issue.. hope someone help with that.. I used to use Google assistant for long time so I got annoyed because of this bug..
I also tried battery saving options, retraining my voice, reinstalling, erasing cache, data, etc., but nothing. :-(
Some time ago doing research about the subject I read something about Google not supporting Google Assistant anymore , because it was not giving enough money or something like this, maybe our device is more or less unsupported now. Can't find the article now. I would like to know if this is an issue on others Redmi phones, the 11S, 11Pro, etc.
Google Assistant might be doomed: Division “reorganizes” to focus on Bard
The Google Assistant makes no money and hasn't released hardware in two years.
arstechnica.com
Hi All,
I'm not surprised by this at all.... like other's here, I noticed Google Assistant (GA) had stopped responding after I updated from Android 11/MIUI 12.5 to Android 12/MIUI 13. I kinda wasn't bothered, gave up on it... that was until the other day. I called out to my GA Home Mini, and noticed my phone responded again, where as it hadnt uptil then. The only thing I noticed at the time was my phone was being charged at the time, which kinda implies based on above, whether it is power related in latest update. As being on mains power, it seemed to work like used too.
I am shocked and gutted to hear Google have given up on GA, although that said, not surprised... as I noticed all my GA's around the house (1x Google Home, 2x Home Mini's, 1x Google Hub) have all become dumb in the last year or so, during the Plandemic... I thought it was when we changed Router settings to let our neighbour use our WiFi when they ISP issues, then reverting back to our normal Router settings, it became less Smart.
Noticed GA was either getting the answers wrong, or not at all... I'm so annoyed, I barely use the GAs now and just type it on a Tablet if I need an answer... defeets the point of an Assistant??
Google advancing, saving human interaction and becoming smarter?? We're going backwards arn't we...??
Why does Google launch so many products, when at the time of the launch, brilliant, but then kill them off before they've finished/polished it off... In my eyes, GAs still needed far more work, nowhere near what they advertised, at least not in the UK... USA is a different story !!
Keep calling out to GA "Send feedback" GA responds "What needs fixing/improving" I then reply "EVERYTHING!!!"
Lister
rel87 said:
Since I think past november, Google Assistant stopped working correctly in my device (spes, 128/6, global) and others from friends (spes, 128/4, global).
The symtoms are, it does react to "Hey Google" (or "Ok Google") but then, when its time to give the order, it doesnt listen, it stays here, with the four colored line like waiting for the sound but the line stays quiet and doesnt move when I talk, like if the mic were not working.
Didn't work after updates, through MIUI 12/13 and Android 11/12.
Anyone have some trick to make it work?
Thanks.
Click to expand...
Click to collapse
Got exacly the same problem on a brand new Redmi Note 11 with original rom.
First I flashed the Xiaomi.eu Rom, still the same problem.
Since two days I'm running the pixelexperience rom and it works perfecly fine.
What I found out is: xiaomi removed some important parts from android because the google assistant isn't allowed in china. It seems like even in the eu and us versions of the rom they broke the assistant.
Since the xiaomi.eu rom is based on the original one it also just dosn't work.
Looks like any rom based on the aosp works fine.
Tks for the heads up @NeoCortex, I'll check the PE thread.
With today's firmware (MIUI Global 14.0.2, Android 13) it's working again!!