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!
Related
First, a HUGE thanks to this community, both the O4X and xda, as a whole. Can't tell you how many times the collective expertise here has saved my...
To my issue: on occasion, my phone mutes itself. The onscreen display doesn't show my end as being muted (pressing and repressing does nothing). I end up having to end the call and call again, which is a pain after being on hold for 20 minutes.
I can find no rhyme or reason for this behavior either. Most of the time it's on outgoing calls, but happens on incoming also. Happens across networks (VZW, AT&T) and with landlines (calling my bank). This has happened in the morning, afternoon and at night, though it doesn't happen in the middle of a call, only the beginning. Just seems to be random.
I've browsed through the 3845#*880#/hidden menu but didn't find any sort of relevant tests. If anyone has any thoughts and/or solutions as to what's going on, be happy to hear 'em.
Thanks
tadees said:
First, a HUGE thanks to this community, both the O4X and xda, as a whole. Can't tell you how many times the collective expertise here has saved my...
To my issue: on occasion, my phone mutes itself. The onscreen display doesn't show my end as being muted (pressing and repressing does nothing). I end up having to end the call and call again, which is a pain after being on hold for 20 minutes.
I can find no rhyme or reason for this behavior either. Most of the time it's on outgoing calls, but happens on incoming also. Happens across networks (VZW, AT&T) and with landlines (calling my bank). This has happened in the morning, afternoon and at night, though it doesn't happen in the middle of a call, only the beginning. Just seems to be random.
I've browsed through the 3845#*880#/hidden menu but didn't find any sort of relevant tests. If anyone has any thoughts and/or solutions as to what's going on, be happy to hear 'em.
Thanks
Click to expand...
Click to collapse
i had this issue, pinpointed it down to viber, for some reason. uninstalled it, and it works fine now. a workaround is, during the call, switch to speaker, then normal again, your mic should be working for a minute or so
Flying_Bear said:
i had this issue, pinpointed it down to viber, for some reason. uninstalled it, and it works fine now. a workaround is, during the call, switch to speaker, then normal again, your mic should be working for a minute or so
Click to expand...
Click to collapse
Thanks for the timely reply Flying_Bear.
I don't have Viber installed (assuming it's an app/service called Viber, not com.lge.viber or something). The sole reason I went root was to clean out the bevy of junk that comes preinstalled. Unfortunately, your work-around didn't work either. Just called my bank and switching between speaker and earpiece had no effect; the operator still couldn't hear me.
Any other guesses?
I did find this from another thread, reads like CM10 might do the trick, but I'd rather not go that route if possible. This seems to be a known, albeit infrequent, yet annoying issue.
tadees said:
Thanks for the timely reply Flying_Bear.
I don't have Viber installed (assuming it's an app/service called Viber, not com.lge.viber or something). The sole reason I went root was to clean out the bevy of junk that comes preinstalled. Unfortunately, your work-around didn't work either. Just called my bank and switching between speaker and earpiece had no effect; the operator still couldn't hear me.
Any other guesses?
I did find this from another thread, reads like CM10 might do the trick, but I'd rather not go that route if possible. This seems to be a known, albeit infrequent, yet annoying issue.
Click to expand...
Click to collapse
oh well, it seems that our problems, even though they have similar simptoms, aren't caused by the same thing. i can't give you much, except the standard factory reset / reflash .kdz advice. good luck!
Flying_Bear said:
i can't give you much, except the standard factory reset / reflash .kdz advice. good luck!
Click to expand...
Click to collapse
ah well, thanks for trying. :cheers:
Is anyone experiencing their phone waking up and waiting for you to ask it something? It's happened just sitting on the counter, my pocket or streaming music/podcasts. It happens at least one or more times a day, I tried retraining it for my voice a few times but still happens.
FSRBIKER said:
Is anyone experiencing their phone waking up and waiting for you to ask it something? It's happened just sitting on the counter, my pocket or streaming music/podcasts. It happens at least one or more times a day, I tried retraining it for my voice a few times but still happens.
Click to expand...
Click to collapse
Go retrain it once more in a completely silent room. You should be able to hear nothing except air moving (fan, a/c, etc.). Then report back.
FSRBIKER said:
Is anyone experiencing their phone waking up and waiting for you to ask it something? It's happened just sitting on the counter, my pocket or streaming music/podcasts. It happens at least one or more times a day, I tried retraining it for my voice a few times but still happens.
Click to expand...
Click to collapse
Biggest thing is keep it at arm's length. Like really, extend your arm to the fullest, and then speak normally. Try it.
natezire71 said:
Go retrain it once more in a completely silent room. You should be able to hear nothing except air moving (fan, a/c, etc.). Then report back.
Click to expand...
Click to collapse
jhnl33 said:
Biggest thing is keep it at arm's length. Like really, extend your arm to the fullest, and then speak normally. Try it.
Click to expand...
Click to collapse
The last time I walked out to my garage to be away from any noise, I'll try again today and make sure I hold it at arm's length(tried that on initial setup)
FSRBIKER said:
The last time I walked out to my garage to be away from any noise, I'll try again today and make sure I hold it at arm's length(tried that on initial setup)
Click to expand...
Click to collapse
Good luck! I had the same issue as you in the beginning. I uninstalled updates and reinstalled to try to make sure previous cache and settings were cleared and re-trained at arms length and now it works pretty well!
FSRBIKER said:
The last time I walked out to my garage to be away from any noise, I'll try again today and make sure I hold it at arm's length(tried that on initial setup)
Click to expand...
Click to collapse
also, make sure you use the same pitch and cadence when saying it. If i want the phone to pick up my voice easier, i can say ok google now when training it in slightly different ways. But then my phone also comes on and thinks im saying it when no one has said anything close to ok google now. If you make sure everything sounds the exact same when saying it, i didn't run into any problems. But i can't wake the phone up when i first wake up in the morning lol. I always try but i apparently sound like death whenever i first wake up.
jayboyyyy said:
also, make sure you use the same pitch and cadence when saying it. If i want the phone to pick up my voice easier, i can say ok google now when training it in slightly different ways. But then my phone also comes on and thinks im saying it when no one has said anything close to ok google now. If you make sure everything sounds the exact same when saying it, i didn't run into any problems. But i can't wake the phone up when i first wake up in the morning lol. I always try but i apparently sound like death whenever i first wake up.
Click to expand...
Click to collapse
I agree, try using the same voice for all three samples. I know that early on people were suggesting you say it with slightly different speed etc but I have found it is best to try to say it the same all three times and let the software in the Moto X handle slightly variations automatically.
Mine wakes up all day sitting on my desk at work. I do talk about Google a lot, but I never say my phrase. It's funny some of the stuff I see it type...
Sent from my XT1060 using Tapatalk
This is an interesting thread for me. I had the Note 3 (hi galaxy) and Nexus 5 (ok google). Both of them would think I was talking to them when I wasn't, and I have almost the opposite problem with the Moto X. I have a hard time to get it to listen. I re-trained, re-trained, re-trained.. My wife's phone works flawlessly. I do love that we train our voices because she uses here touchless control all the time right next to me and my phone has yet to mistake mine for hers.
Maybe I need shorter arms.
OK quick update, I uninstalled the Touchless Control update and retrained my Moto X again in my garage this morning. It's been about 7 hours and it hasn't once yet turned itself on. I streamed music, have been in congested areas with people, a business meeting and it's working perfectly now.
I'm going to wait for 24 hours to make sure it's still working correctly and then install the update to the app.
About ready to scream!
The touchless control on my Moto X Developer Edition is extremely sensitive. Anytime anyone talks in the office that I work in, the dang phone comes on and waits for someone to give it a command. All anyone has to do is say "OK" and it does this even when I don't want it to. I've tried retraining the phone multiple times and it doesn't seem to help me out at all. I'm going to be so glad when the Lollipop update finally rolls out for this phone so I can get retrain this with a different launch phrase that will not be so easy to trigger on my phone. In the meantime, has anyone been able to get the sensitivity adjusted on this phone? If so, how? I'm thinking of going to Cyanogenmod 12.1 until Lollipop rolls out for the XT1060,
Any help that I can get on this would be greatly appreciated.
Cindy
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.
Good afternoon,
I have had a Nokia 8 for a few weeks now and have now found that my microphone only works during calls. While I'm on the phone everything works normally but in all other apps nothing happens, e.g. in Whatsapp you only hear a short crack when you hear a voice message and then nothing, although you have said something (see attachment), also other apps that use the microphone like the Google Home App or a guitar vocal app don't work. Of course the permissions are set correctly for all apps but apparently this has no effect (see attachment). I've already written with Nokia Support, but after 14 mails about permissions, emptying caches and doing softresets they couldn't help me. Finally I was told to wait for the next Android update and hope that my problem was fixed there, or I should send my phone back to the dealer. My hope now is that one of you has an idea what could be the cause of the problem.
Thank you for your time!
- Joeigel
Attachments:
picload.org/view/dclcpodg/screenshot_20181201-165257.png.html
picload.org/view/dclcpodr/screenshot_20181201-165237.png.html
Audio Message from Whatsapp:
instaud.io/30ZI
Hello to everyone there,
I have next problem on my Nokia 8:
When somebody calls me or when I call someone on viber, I turn on speakers and other side can't hear me. Also when I put it on video call the same issue conitnuous to take. Regular GSM calls or viber VoIp calls works great as well as video calls with headphones.
I open ticket to a viber about this problem, and they told me I need to contact my manufacturer.
Yesterday I installed an Android pie from beta labs, but the problem still exists. How do you think the problem is hardware?
ratola said:
Hello to everyone there,
I have next problem on my Nokia 8:
When somebody calls me or when I call someone on viber, I turn on speakers and other side can't hear me. Also when I put it on video call the same issue conitnuous to take. Regular GSM calls or viber VoIp calls works great as well as video calls with headphones.
I open ticket to a viber about this problem, and they told me I need to contact my manufacturer.
Yesterday I installed an Android pie from beta labs, but the problem still exists. How do you think the problem is hardware?
Click to expand...
Click to collapse
Hi ratola,
you can dial *#*#372733#*#* for a hidden FQC test menu, here you can test each mic seperated, i guess in your case it's the second mic in the top-speaker.
- Joeigel
Joeigel27 said:
Good afternoon,
I have had a Nokia 8 for a few weeks now and have now found that my microphone only works during calls. While I'm on the phone everything works normally but in all other apps nothing happens, e.g. in Whatsapp you only hear a short crack when you hear a voice message and then nothing, although you have said something (see attachment), also other apps that use the microphone like the Google Home App or a guitar vocal app don't work. Of course the permissions are set correctly for all apps but apparently this has no effect (see attachment). I've already written with Nokia Support, but after 14 mails about permissions, emptying caches and doing softresets they couldn't help me. Finally I was told to wait for the next Android update and hope that my problem was fixed there, or I should send my phone back to the dealer. My hope now is that one of you has an idea what could be the cause of the problem.
Thank you for your time!
- Joeigel
Attachments:
picload.org/view/dclcpodg/screenshot_20181201-165257.png.html
picload.org/view/dclcpodr/screenshot_20181201-165237.png.html
Audio Message from Whatsapp:
instaud.io/30ZI
Click to expand...
Click to collapse
Hi Joeigel, unfortunately I have the same issue (and story regarding contacting support). The only way I can make calls via for instance WhatsApp is by using a handfree headset, or setting it to speaker-mode.
Waiting for the Android 9 release, if this isn't fixed with it, I'll send it in for warranty.
I do have another issue with the phone, and that's when I unlock my phone using the fingerprint scanner, 1 out of 4 times or so, the phone enables split screenmode. Do you (or someone else here) have similar experiences. It's quite annoying.
Update: Installed Pie, and no improvement. Issues still persists. Returning the phone today.
Sorry for the late response, my phone is also on it's way back to GB...
Joeigel27 said:
Sorry for the late response, my phone is also on it's way back to GB...
Click to expand...
Click to collapse
Ok, just got an update from the repair-center, they replaced a part and it should work OK now. Curious to see what they did and if it's resolved. Have to wait until it's shipped back. But keep us also posted about your progress
Off-topic: another issue I sometimes experience is when I unlock my phone with fingerprint, it sometimes switches automatically to the split-screen mode. It happens quite often and it's a bit annoying. Did you experience something similar with your Nokia?
odyon said:
Ok, just got an update from the repair-center, they replaced a part and it should work OK now. Curious to see what they did and if it's resolved. Have to wait until it's shipped back. But keep us also posted about your progress
Off-topic: another issue I sometimes experience is when I unlock my phone with fingerprint, it sometimes switches automatically to the split-screen mode. It happens quite often and it's a bit annoying. Did you experience something similar with your Nokia?
Click to expand...
Click to collapse
I didn't experienced something like this. Did they send it back to you yet? Maybe they fixed both... ^^'
Microphone issue here too.
Internal mic on front facing camera is the culprit. I noticed a few weeks back that my 'ok google' hotwords were no longer working. This became a problem after I installed the december security patch. I rolled back to the november security patch and this did temporarily fix the issue, after I had gone through the initial setup of the phone, my 'ok google' hotwords worked, until i went to use the camera to see if the issue still existed... unfortunately it does. Contemplating rolling back to july to see if the issue is resolved, or trying to move forward and installing pie.
nagesco said:
Microphone issue here too.
Internal mic on front facing camera is the culprit. I noticed a few weeks back that my 'ok google' hotwords were no longer working. This became a problem after I installed the december security patch. I rolled back to the november security patch and this did temporarily fix the issue, after I had gone through the initial setup of the phone, my 'ok google' hotwords worked, until i went to use the camera to see if the issue still existed... unfortunately it does. Contemplating rolling back to july to see if the issue is resolved, or trying to move forward and installing pie.
Click to expand...
Click to collapse
Could any up or downgrade fix it?
Joeigel27 said:
Could any up or downgrade fix it?
Click to expand...
Click to collapse
I've tried going up or down, I have oreo and pie on each of my A/B partitions and it does nothing. When i downgraded to oreo it worked for awhile but updating the google app or some sort of background service broke it again. Its definately mic 3 that has a fault, it has background interference noise when i do the test, it also occurs when recording video with the front facing mic on camera, the problem with the mic never goes away, after up/downgrading, I can't say whether this is related since it works prior to updating. rolling back/disabling doesn't solve the problem for the apps. Microphone/earpiece holes are clean and undamaged.
nagesco said:
I've tried going up or down, I have oreo and pie on each of my A/B partitions and it does nothing. When i downgraded to oreo it worked for awhile but updating the google app or some sort of background service broke it again. Its definately mic 3 that has a fault, it has background interference noise when i do the test, it also occurs when recording video with the front facing mic on camera, the problem with the mic never goes away, after up/downgrading, I can't say whether this is related since it works prior to updating. rolling back/disabling doesn't solve the problem for the apps. Microphone/earpiece holes are clean and undamaged.
Click to expand...
Click to collapse
After further testing of this issue, the 'OK Google' issue is still present, if I want to ask google assistant 'ok google' the microphone barely picks up anything or even my question, practically screaming into the microphone is the only way to activate it, this matches with the results on my google activity, listening to my recordings of my queries shows evidence that the microphone sensitivity is way too low.
HOWEVER, when using google assistant by means of pressing the microphone and then asking the question, the result is clear and understandable and doesn't suffer from volume issues, I can't pinpoint if this is an issue with the Nokia specifically, it is not a problem with any other application that uses the microphone.
Having the same issue with Mic 3. It means I can't use it in speakerphone mode during calls or in Skype. It doesn't prevent me from using the Google assistant though.
My smartphone was sent in and repaired (complete motorboard replaced). During the time it was gone Android 9 came out, so I'm not sure if it was the repair or the software update.
But it works again without any problems
Kind regards
Joeigel
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!!