Related
Hi all,
I'm having a problem with my mi4i when I have voice calls the microphone doesn't register any sound. It works fine on speakerphone and on doing recordings which leads me to believe this is software and not hardware.
I've tried removing the google voice detection stuff by inhibiting it, as i saw elsewhere this was a problem. I couldn't find any options about noise cancellation which may be malfunctioning.
I'm currently using the most up to date MIUI rom (MIUI 7.0.3.0, android version 5.0.2 LRX22G, kernel 3.10.49) but was previously using the ressurection remix. Both times I had the same problem; I was hoping that with the update to the latest MIUI it would fix this problem, but alas it hasn't.
If anyone has any ideas of how to fix this it would be appreciated.
Also, thanks to all the people out there working on ROMs and fixes!
Thanks
zero
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.
My Google Pixels microphone randomly died after some point in its lifespan, but happened recently. First i updated version to Android Q Beta 1 (and it was working all right on that version) but when i updated it to Android Q Beta 2 (microphone stopped working and whole UI experience was buggy, some apps not working, random restarts, etc...) but then i got it back on Android Pie, and it worked for few minutes into boot and died yet again... Then i installed custom ROM (Pixel Dust) with TWRP recovery and Root, but nothing of those helped, then i got it back on Android Pie via adb sideload OTA. That didn't help either... So i don't know is it the software problem (because it seems to work first few minutes after i boot it) or is it the hardware problem. I use my phone mostly for phone calls and now because microphone is dead, it lost its functionality... But speaker was working,earpiece and 3.5mm jack.. Any suggestions??
i'm having a similar problem at the moment. Since the April OTA update, phone calls stopped working. Even when using a BT headset. I tried reverting to Full Recovery Image from february, but that only helped a bit. Also, any other audio app was not able to use the speaker. With the Feb version, youtube and google music were back working, but phone calls are still not possible, causing the telephone app to freeze. I was thinking about installing some custom rom too, but that doesn't seem to do the trick. Did you try to wipe the cache in recovery?
Update
found three possible workarounds for people having the same issue, perhaps one of those helps. I'll go through them today evening.
You could try enabling the "Disable USB audio routing" in developer options and see if that works for you. It did work for me
Click to expand...
Click to collapse
A couple of days ago one of the CEs here pointed out to me that I needed to enable the setting for wired headphones in Google Settings > Search, Assistant & Voice > Voice > Hands Free and toggle on the ‘wired headset’ setting,
Click to expand...
Click to collapse
Change your launcher, for example, on nova launcher, disallow permission to microphone for google app and never let him this permission, do not use google assistant.
Click to expand...
Click to collapse
LaTerminator said:
My Google Pixels microphone randomly died after some point in its lifespan, but happened recently. First i updated version to Android Q Beta 1 (and it was working all right on that version) but when i updated it to Android Q Beta 2 (microphone stopped working and whole UI experience was buggy, some apps not working, random restarts, etc...) but then i got it back on Android Pie, and it worked for few minutes into boot and died yet again... Then i installed custom ROM (Pixel Dust) with TWRP recovery and Root, but nothing of those helped, then i got it back on Android Pie via adb sideload OTA. That didn't help either... So i don't know is it the software problem (because it seems to work first few minutes after i boot it) or is it the hardware problem. I use my phone mostly for phone calls and now because microphone is dead, it lost its functionality... But speaker was working,earpiece and 3.5mm jack.. Any suggestions??
Click to expand...
Click to collapse
Maybe is a kernel error..but definitely is not a hardware problem. maybe try changing kernels. o downgrading to 7.
since none of the above tricks worked in my case, i booted TWRP to clean the caches. Didn't bring any good result. So i flashed ElementalX Kernel and now i got some kind of a better result, even if it's still weird. Everything works now except incoming calls. I can actively call other persons, use whatsapp or facebook audio calls and all is good. Only if i receive calls, still mic is muted.
I will try everything from above, and hopefully something will actually work and get my Pixel back in life. I will get you updated guys.
Thanks for the support.
toxic_garden said:
i'm having a similar problem at the moment. Since the April OTA update, phone calls stopped working. Even when using a BT headset. I tried reverting to Full Recovery Image from february, but that only helped a bit. Also, any other audio app was not able to use the speaker. With the Feb version, youtube and google music were back working, but phone calls are still not possible, causing the telephone app to freeze. I was thinking about installing some custom rom too, but that doesn't seem to do the trick. Did you try to wipe the cache in recovery?
Update
found three possible workarounds for people having the same issue, perhaps one of those helps. I'll go through them today evening.
Click to expand...
Click to collapse
None of those helped so far, i'll try flashing some kernel then...
I discovered that when i try to record with my camera video, it says "Can't record audio. Another app is using the mic." Also when i try to record audio message on Messenger app, as soon as i click on microphone icon it says some error.
Update, my sound and video won't record, both on Youtube or Instagram or any kind of video audio playback.
Update
I flashed ElementalX kernel and same stuff happened, phone calls and microphone was working for first 30 minutes then it got back to old days, not working as usual. Now i think this is hardware problem
LaTerminator said:
Update
I flashed ElementalX kernel and same stuff happened, phone calls and microphone was working for first 30 minutes then it got back to old days, not working as usual. Now i think this is hardware problem
Click to expand...
Click to collapse
have you tried chaging vendor image, or getting a vendor image from a working pixel?
I installed lineageos 16 without gapps and is working good for hours until installed gapps.
ericksidaroth said:
have you tried chaging vendor image, or getting a vendor image from a working pixel?
Click to expand...
Click to collapse
how do i change vendor image actually??
Hello,
I am fairly new to this so please tell me when I miss some information and I will try to deliver as fast as possible.
I downloaded and installed this inofficial Lineageos 17.1 by ripee and joshuadoes (https://forum.xda-developers.com/t/...rofltexx-lineageos-17-1.4063781/post-84238527). It all worked and I would be VERY happy. Unfortunately though, the dialer app, even though it has access to the microphone, does not even request using it (says it has never used it). In calls, my voice is not transmitted. I still hear the voice of the other person though.
Can anyone help me? Is there a way to install another dialer app as the primary app? I tried TrueCaller with no luck. I tried rebooting, and re-installing the custom rom and testing it without anything else installed. It does not work. Calling through WhatsApp and Signal, for example, works. Also the mic is working for videos etc.
Hope you can help me out, and thanks in advance for any ideas. I really like the LineageOS 17.1 experience but not being able to do voice calls is a dealbreaker for me
I have a similar issue. however I can't hear audio during calls as well as the app not accessing the microphone. I have a Samsung A11 and I am using the a GSI LineageOS build from Andy Yan. I have tried with LineageOS 17 and 18.
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