Hello everyone!
I noticed a problem when Google Now's "Ok Google" detection is turned on. The problem is that it uses the mic all the time (ok, it's normal as it is supposed to be listening all the time) which prevents the camera, Duo, or any other app using the mic to work properly. As soon as I disable this option, everything works fine again.
I'm on a Chinese 64Gb version with a C900B133 rom flashed on it. Did anyone else notice the problem and find a work around?
Have a good one guys!
Just clear the data and it will work fine
Hey
Since I have my s8+ this app keeps freezing on me. Sometimes it works, but that's not often. I open the app and it is just staying on A and the arrow is not transparent as it should while tuning. It's also not a setting because non of the buttons are working.
I've tried clearing data and cashe and I've just flashed renovate ice 3.0 so it's not a rom issue as it occurred on both stock and custom.
I've had a s7 edge and it was working fine there (also nougat)
Also it's the official app from play store.
Anyone an idea how to fix this?
Thanks in advance!
I use cleartune all the time, I haven't had any issues. Have you tried uninstalling/reinstalling? I have a tmobile so I don't know about custom ROMs as we have no custom ROMs.
sanjsrik said:
I use cleartune all the time, I haven't had any issues. Have you tried uninstalling/reinstalling? I have a tmobile so I don't know about custom ROMs as we have no custom ROMs.
Click to expand...
Click to collapse
Yes I've reinstalled it but that doesn't do the job
When i run discord it blocks the mic in clear tune from working. You proably have some app blocking it cause it taking over the mic.
The problem for me is im runnign into issue with this being in stable in andriod 9 stock tmobile. I dont think they have updated the app in a while. Drag cause this is the best tuner app on the market for sure
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.
So I had a couple of Moto X Plays laying around which I wanted to repurpose as "Google Home" and security camera. So I take the necessary steps to install and update Google. Trying out Assistant gives me the: "Google recognized your voice, all set" -sequence and shuts of the toggle for voice match again. Weird! So I keep trying solutions upon solutions and I even revert back to stock rom 7.1.1 and to my surprise it start working again, that is, until I update my Google app again. Now somewhere Google seems to have decided not to support older ROMs anymore. Because guess what: that same version still works fine on my daily driver Samsung Galaxy S9 stock ROM. I am wondering: Is Google deliberately making newer versions of the Google App have Voice Match fail on these older roms (7.1.1 stock and 7.1.2) or am I just being an idiot?
That said I'm gonna try and find out which version of Google App I can get my older ROM to have voice match again.
I noticed recently that "Ok Google" voice activation of the Assistant was no longer working. It took me a long time to notice because I only use this feature when driving longer distances, something I haven't been doing much during the pandemic.
With the newer versions if I say "Ok Google" or "Hey Google" there is no response. If I manually launch the Assistant ie long press on Home button it comes up and I can press the microphone and it works. If I try to retrain the voice model it tells me it's having issues connecting, and I cannot get past this message. It's clearly not a connectivity issue because I can use other Google apps and surf the web just fine.
I was curious when this had stopped working so I did some testing:
10.97.8.21 original version that came with the OS update, working
11.19.12.21 working
11.19.17.21 working
11.21.9.21 not working
11.27.6.21 not working
11.30.12.21 not working
11.39.7.23 not working
11.43.8.23 not working
12.2.11.23 not working
12.6.8.23 not working
12.10.7.23 not working
Obviously I didn't test every single version available but it seems that it broke between 11.19.x.x and 11.21.x.x. I was not able to find a good 11.20.x.x to download and test, so I can't rule that version out.
For now I've reverted to 11.19.17.21 but I'm concerned about security running that old of a version.
Any idea what might have changed in between those two versions to make this stop working?
Anyone else have similar experiences?