Database Info

Google Assistant Voice Match

Can anyone tell me why I'm experiencing these settings being grayed out on my phone? I've had Google assistant working fine before, but it hasn't been lately and this appears to be why. Language settings haven't changed since it was working before.

I have thé same trouble sincères thé Google voice match was updated

Same issue for me, in Italian language.

With the latest builds it's possible to turn the phone on with OK Google, but unlocking it doesn't work. Still asks for pin/fingerprint. Anyone see a solution for this?

Homestar1217 said:
Can anyone tell me why I'm experiencing these settings being grayed out on my phone? I've had Google assistant working fine before, but it hasn't been lately and this appears to be why. Language settings haven't changed since it was working before.
Click to expand...
Click to collapse
It's currently the same on all roms, it's working if you use a gsi

Flatric said:
It's currently the same on all roms, it's working if you use a gsi
Click to expand...
Click to collapse
Good to know I'm not alone!

You are not alone! This happened to me a few weeks back. All my searching leads to gapps verification, or shall I say use of gapps instead of built into system. This feature does work once again using gsi with Google apps pre-installed as well as pixel exp ROM, as they are verified there.
Sent from my Mi MIX 2S using Tapatalk

Hi,
Same problem here in french language.
Voice Match used to work last week. Activation by pressing home is not working too.
I have to launch the app by clicking it

I have solved with last update MIUI Global 10.0.9.0

duraaraa said:
With the latest builds it's possible to turn the phone on with OK Google, but unlocking it doesn't work. Still asks for pin/fingerprint. Anyone see a solution for this?
Click to expand...
Click to collapse
I am still having this problem.

Same here, it stopped working about a week ago. Tried everything: retraining model, changing language from “English (Ireland)” to “English (United Kingdom)”… nothing works. I have to press the button to activate the assistant. I'm using the Pixel Experience ROM by Psy_Man – amazing ROM BTW, super stable.

Which version of the Google app do you use? I installed the 8.65.6.21.arm64, and Voice Match works on it.

I am experiencing the same issue ever since I flashed AEX. Pixel Experience was working fine and no issue with assistant but after the problem appeared all ROMs stopped working. I am currently on MIUI global because it's so far the only ROM that has it working, but it still requires faceunlock/fingerprint to unlock the phone though it does wake up by saying OK Google.
I have not tried any GSI ROMs because I don't know if they are good enough as daily drivers but if anyone has a recommendation will definitely try it out.

jamesyuli said:
I have not tried any GSI ROMs because I don't know if they are good enough as daily drivers but if anyone has a recommendation will definitely try it out.
Click to expand...
Click to collapse
I tried out OctopusOS ROM GSI. Very stable, could be a daily. I used it for a few days. But I prefer to be able to use a true dark theme. Didn't have issues with Google hot words at all. A few tweaks and some magisk modules help it out.
https://forum.xda-developers.com/pr...led-device-development/9-0-octopusos-t3859233

I observe this behavior in all ROMs, except the pixel experience gsi, and variations of the official miui ROM, including the EU versions. I haven't tried other gsi ROMs, but the one I tried worked perfect, except for Bluetooth audio which didn't work at all, so it was not fit to be a daily driver for me.
1/2 - Trying OctopusOS Today! Installation was very frustrating and in the end the exact word of the guide here https://forum.xda-developers.com/xiaomi-mi-mix-2s/how-to/how-to-install-gsi-roms-pass-safetynet-t3814298 worked to get the rom booted (Doing the image install in TWRP did not work, but doing it over fastboot did). I'll report back on how it works. If this is a bust, I'll probably try Havoc next.
Update - So this is new. Bluetooth works! However it's one step forward, one step back again. voice match works from the home screen, but I do not have any options to re-train or delete voice match data, and while the option to enable access with voice match no longer says "not available in selected language", it is still greyed out and cannot be turned on. Updating google only adds "While Driving" to voice match menu, and it is turned on. very strange. I'll play with magisk a little and then try havok.

Voice Match is working again in latest AOSIP

Flatric said:
Voice Match is working again in latest AOSIP
Click to expand...
Click to collapse
There's also a changelog entry for PE that hotword enrollment was fixed! More stuff to try!

Let us know if it stays. Everytime I've flashed and setup as new, it worked fine for a few days, but then would just stop, and grey out like above. So far doesn't matter what version I'm using, and none of the fixes anywhere work.
Sent from my Mi MIX 2S using Tapatalk

noobtoob said:
Let us know if it stays. Everytime I've flashed and setup as new, it worked fine for a few days, but then would just stop, and grey out like above. So far doesn't matter what version I'm using, and none of the fixes anywhere work.
Sent from my Mi MIX 2S using Tapatalk
Click to expand...
Click to collapse
almost 24 hours so far on the 12/30 build of Pixel Experience with no issues. The rom just runs flawlessly, and I love the pixel live wallpapers. OK Google still working with none of the voice options greyed out. Android wear device working too (Explorist 4). Auto bright, and lock/unlock good too. Battery seems good so far. These points aren't relevant, but everything else seems to work good.
I know Pixel experience is not very dense on details for install so here's my process.
Use MiFlash to flash fastboot version of latest developer rom
Re-flash TWRP, enter wipe menu and wipe (Not format, NOT the one you have to type y-e-s) the first four options, Dalvik, Cache, System, and Data.
Flash your rom
Boot! (Regardless of whether or not it makes a difference, I like to let it sit on the first screen for a little, and then after 2-5 mins, I'll restart, before setting it up)
Oh! And I've had less issues since I installed MIUI, went into settings, and Signed out of my Mi Account. Not sure if it makes a difference, but I no longer have to "authenticate" and unlock after I install MIUI. This confused me because I read that unlocking BL automatically disables find my phone, but evidently not.
---------- Post added at 10:41 AM ---------- Previous post was at 10:39 AM ----------
Gopena said:
I observe this behavior in all ROMs, except the pixel experience gsi, and variations of the official miui ROM, including the EU versions. I haven't tried other gsi ROMs, but the one I tried worked perfect, except for Bluetooth audio which didn't work at all, so it was not fit to be a daily driver for me.
1/2 - Trying OctopusOS Today! Installation was very frustrating and in the end the exact word of the guide here https://forum.xda-developers.com/xiaomi-mi-mix-2s/how-to/how-to-install-gsi-roms-pass-safetynet-t3814298 worked to get the rom booted (Doing the image install in TWRP did not work, but doing it over fastboot did). I'll report back on how it works. If this is a bust, I'll probably try Havoc next.
Update - So this is new. Bluetooth works! However it's one step forward, one step back again. voice match works from the home screen, but I do not have any options to re-train or delete voice match data, and while the option to enable access with voice match no longer says "not available in selected language", it is still greyed out and cannot be turned on. Updating google only adds "While Driving" to voice match menu, and it is turned on. very strange. I'll play with magisk a little and then try havoc.
Click to expand...
Click to collapse
1/3 Didn't post this yesterday, I tried Havoc as well and it behaved like miui, no OK Google to wake & Unlock, but ok google from lockscreen brought up the pin pad, and unlocking with pin or FP would allow google assistant to activate. Havoc also had no bluetooth audio.

Google Assistant (ok google) not working

hey,
As the title suggests i cant use Google assistant on the Chinese rom
if i actually go into the Google app it will work, but with voice widget on the screen it doesn't recognise any voice. or work at all
in Google app Settings/Voice/Voice Match
''Access with Voice Match'' is greyed out and cant be turned on no matter what i do.
no issue on my other devices.
work around would be appreciated
thanks

Same Problem Here. I don't even get notifications of the Google calendar even though all settings are turned on... -.- it really sucks. Won't ever buy that crap again.
Is that problem happening to the guys with global ROM too?

FUKU_ said:
Same Problem Here. I don't even get notifications of the Google calendar even though all settings are turned on... -.- it really sucks. Won't ever buy that crap again.
Is that problem happening to the guys with global ROM too?
Click to expand...
Click to collapse
No problems with my global version. I've learned my lesson in buying Chinese versions just for the sake of having a particular phone. Having said that my Chinese Xiaomi Mi Mix 2 didn't have a problem either.

chinese rom probably disabled it

"Ok google" not working on locked and turned off screen.

Hi, a have a problem with my POCO X3 NFC.
After update of MIUI 12 "ok google" on locked and turned off screen stopped working.
Before the update, it was working perfectly. Now "ok google" is working only when the screen is on, also when the phone is locked.
I have tried almost everything, uninstalling updates of google app, recording new voice for google assistant, but have no solution still...
Can you help me?
For me, this feature is very important.
With greetings,
Łukasz G.

Hello, go to your "google" app to launch discover, then on the bottom right you should have "More", then choose "settings" -> "voice" at the bottom you should see "voice from headset/locked phone" : turn that ON and it should work.
(My phone is not in english so the exact names might be a bit different)

I've done what you said... nothing changed.

same here.. just won't work, on poco f 1 worked fine

black_dott said:
same here.. just won't work, on poco f 1 worked fine
Click to expand...
Click to collapse
did you try factory reset?

no i didn't

Is there any solution to this problem??
Also "ok google" using Bluetooth device not working also (settings are ok)...
Can in it be a problem with the POCO microphone and constant listening?

Czy ktoś znalazł rozwiązanie problemu??

The same here. Tried to get updated, reseted Google app. Nothing, so pity!

I am on MIUI Global 12.0.4 with all voice option enabled but, like @grabolukasz , 'ok google' only works if I'm with the screen on (even if locked).
@grabolukasz are you sure it worked before the update?

Hello. Same issue with my Samsung Galaxy A3 2017

Same problem with my poco 3. It's never worked for me. Very frustrating. :-(

i am curious why people use that ok google. isn't on bloatware list for removal?

Afaik google blocked that and made it only pixel exclusive some years back. I have a 5t and was using omnitreskmod. It got screenoff voice commands working but after some months it didnt work and i remember people saying blame google... But still, i wouldnt use it now as it will drain battery.

There are ways to do it (google it).
But it is not safe (google can mistake somebody's voice for yours), so it got removed.
You can do it through bt/wired earphones etc

I'm also looking to have this.
But it is not safe (google can mistake somebody's voice for yours), so it got removed.
You can do it through bt/wired earphones etc
Click to expand...
Click to collapse
This is not an issue, you can disable "personal results" in the lock screen.
Afaik google blocked that and made it only pixel exclusive some years back. I have a 5t and was using omnitreskmod. It got screenoff voice commands working but after some months it didnt work and i remember people saying blame google... But still, i wouldnt use it now as it will drain battery.
Click to expand...
Click to collapse
This is not true, my mi 9T Pro/K20 Pro has this feature and works great without issues.
I mainly used this feature to tell google to turn on/off lights. And required me to unlock the phone to execute the command. But I would use google smart lock (mi band) to have my phone unlocked while at home.

In poco F3 eea original rom Is It working good but you have to check in system apps an app called Qualcomm voice assist that are installed and working... Only on poco rom the phone Is It compatibile with this app... On Xiaomi Eu or One Os don't working because if you search this app don't exists and on Google play store are not available... Sorry my bad english guys ... i Hope you understand

Incredible! That seems to solve the problem. Its working fine for 2 days now! Thanks a lot man!
In my case 'qualcomm voice assist' didn't have access to microphone for some reason.

The same here with Poco F3 miui 12.5.4 EU
not working when device locked
and works poorly otherwise (not sensitive at all)

Calls not connecting on AOSP ROM

Just flashed Resurrection. Everything is cool except my calls don't connect. When I dial, the call immediately ends. If I toggle airplane mode a few times the call will finally connect. I figured this is an AOSP thing. Does anyone know of a fix?
Metro pcs is my service provider by the way

Bump.. been checking around and I've found nothing. However I'm able to dial Google voice numbers without issue

DonSolo said:
Does anyone know of a fix?
Click to expand...
Click to collapse
I know a fix, but you're not going to like it. Flash something else. See if the problem persist. If not, boom, problem fixed. If yes, make a log. Post it in the ROM thread together with problem description. Wait for fix.
edit:
If the same problem persist also on another ROM could be also HW problem.

jeryll said:
I know a fix, but you're not going to like it. Flash something else. See if the problem persist. If not, boom, problem fixed. If yes, make a log. Post it in the ROM thread together with problem description. Wait for fix.
edit:
If the same problem persist also on another ROM could be also HW problem.
Click to expand...
Click to collapse
I actually love flashing new ROMs lol. Unfortunately flashing a different rom didn't help. Same thing is happening. I ended up flashing Official Android 11 Pixel Experience.
At this point I'm sure it's an AOSP thing or custom ROM (don't think it's HW atm). When my bootloader was locked for the "168 hour" wait period I was able to make all of the outbound calls I wanted. I'll post some logs in both threads just for the record while I continue to find a fix.

I've found a workaround for my issue. I installed an MIUI ROM. I've been able to make calls without issue.
Not sure why MIUI allows me to dial out and AOSP doesn't. If anyone can chime in, that would be awesome. Otherwise I'll rock with MIUI ROMs for the time being.

DonSolo said:
I've found a workaround for my issue. I installed an MIUI ROM. I've been able to make calls without issue.
Not sure why MIUI allows me to dial out and AOSP doesn't. If anyone can chime in, that would be awesome. Otherwise I'll rock with MIUI ROMs for the time being.
Click to expand...
Click to collapse
I am now on pixel experience android 11 rom.I am also facing the same issue.Should I shift to miui rom?

Mushfiq Khan said:
I am now on pixel experience android 11 rom.I am also facing the same issue.Should I shift to miui rom?
Click to expand...
Click to collapse
Pixel Experience hasn't been updated for a long time if I'm not mistaken.
I personally use ArrowOS 12.1 and have no issues. Even automatic call recording works for me

Noter2017 said:
Pixel Experience hasn't been updated for a long time if I'm not mistaken.
I personally use ArrowOS 12.1 and have no issues. Even automatic call recording works for me
Click to expand...
Click to collapse
I was previously on awaken os android 13 version.I noticed this call problem when I was on that rom.So I shifted to pixel experience.
But I just turned off Volte toggle and now calls are seems to be working.So could it be issue from my network provider side?

Mushfiq Khan said:
I was previously on awaken os android 13 version.I noticed this call problem when I was on that rom.So I shifted to pixel experience.
But I just turned off Volte toggle and now calls are seems to be working.So could it be issue from my network provider side?
Click to expand...
Click to collapse
To be absolutely sure that it's your provider's fault, I would probably also flash MIUI to be 100% sure

Noter2017 said:
To be absolutely sure that it's your provider's fault, I would probably also flash MIUI to be 100% sure
Click to expand...
Click to collapse
Will any miui based rom work?Like Eu rom?

Not your usual "Hey Google" is not responding problem.

So.. I have this problem where (wait for it...) "Hey Google" doesn't respond, BUT (before you stop reading) it only stops responding after I've been on a voice call. Weird, eh?
Here are some fun facts:
1. To get it to respond again, all I have to do is manually open and close Google Assistant by tapping on the screen, then "Hey Google" will generally behave itself and respond until I get another voice call. Sounds easy (I even have a Tasker routine to automate the process), but it's still a chore and it's always a bit hit and miss.
2. I've tried every generic solution I can find on the internet, including retraining the voice model, deleting the cache and data, factory reset etc etc...
3. This issue is 100% specific to the OnePlus 8T running Android 13 (F.13, F.15 & F.62). I used MSM tool to go back to Android 11 and "Hey Google" worked like a charm. I took the OTA updates to Android 12, still working fine. As soon as I took the OTA update to Android 13 (guess what?) yep, the problem came back! No other apps were installed, only the apps built in to the stock ROM.
4. I've tried a number of custom ROMs. All Android 13 ROMs I've tried have this same problem. (Android 12 based ROMs not affected.) I've also tried EU, Global and Indian Firmware.
I sent feedback to OnePlus already, so hopefully we'll get a fix. In the meantime, please, if anyone has a workaround please let me know.
If you don't have a solution but want to complain about the problem here, I'll give you a listening ear.

706mix said:
So.. I have this problem where (wait for it...) "Hey Google" doesn't respond, BUT (before you stop reading) it only stops responding after I've been on a voice call. Weird, eh?
Here are some fun facts:
1. To get it to respond again, all I have to do is manually open and close Google Assistant by tapping on the screen, then "Hey Google" will generally behave itself and respond until I get another voice call. Sounds easy (I even have a Tasker routine to automate the process), but it's still a chore and it's always a bit hit and miss.
If you don't have a solution but want to complain about the problem here, I'll give you a listening ear.
Click to expand...
Click to collapse
Maybe the process of Google Assistant is killed in background by stock memory cleaner or some app?
Try whitelisting it (disable memory optimization and so on).

Rootk1t said:
Maybe the process of Google Assistant is killed in background by stock memory cleaner or some app?
Try whitelisting it (disable memory optimization and so on).
Click to expand...
Click to collapse
Thanks for the suggestion. The Google app is already set to 'Unrestricted' - are there any other processes/apps that should also be set to 'Unrestricted'?
I'm wondering if the Qualcomm Voice Assist Aqstic Audio Codec is not being implemented properly in Android 13.

So, I finally received a reply from OnePlus Support. They have asked me to send a screen recording of me saying "Hey Google" and the phone not responding. Sounds fair. I'll have to go back to stock OOS13 so they can see that the issue is not just with custom ROMs.
Oh well, guess I'll get round to that when I have a spare day...
(At least we can do a nandroid backup with TWRP these days. )

Please, if anyone is running an Android 13 ROM (stock or custom) on their 8T, please can you check if "Hey Google" is working properly on your device after making or receiving a call?
Please post on this thread whether it worked or not, and what ROM you are using. Thank you.

Here's a little update in case anyone's interested...
I sent OnePlus Support a screen recording of the malfunction. Today I received this reply:
I contact you due to the malfuntion of Google Assistant.
There is a need to solve this issue in the next update of Android. The version Android 13.1 will be pushed in June and please inform us if the issue still persists.
Best regards,
Klaudia
OnePlus customer service
Click to expand...
Click to collapse