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
Related
Interesting one, and can't figure out why it's happening - so if anyone has any thoughts x)
Flashed L tonight, all went smoothly and generally everything is fine. The only weird thing is that Google Voice search has stopped working. I press the Voice search button, and it just doesn't pick up any sound. I trying saying "ok google", and it doesn't pick that up either. Also, along with that, Text to Speech refuses to work too, tried with different languages and different voice packs.
Any ideas?
I know I had to go into the Google Now settings and activate the "OK Google" from any screen, to get it to work.
I had the same problem when setting another language as the primary language, then switching back to English, but something seemed bugged.
Removing all the other languages and restoring English (US) only, and finally rebooting, resolved the issue. Hope this helps.
themcfly said:
I had the same problem when setting another language as the primary language, then switching back to English, but something seemed bugged.
Removing all the other languages and restoring English (US) only, and finally rebooting, resolved the issue. Hope this helps.
Click to expand...
Click to collapse
Hmm, just gave that a try, no dice Was it just the Voice language or the whole phone that you had to change?
The weird thing is, it's like it's not even connecting to the microphone, just sits there listening and not hearing anything x)
Yes, that was exactly the same behavior i had with mine. I also ended up trying to configure Ok Google from any screen, and the voice training feature didn't hear anything, remaining stuck on the 1st of 3 verifications.
Maybe you can try going to Settings > App > All > Google Search and deleting cache/data to restore it brand new.
themcfly said:
Yes, that was exactly the same behavior i had with mine. I also ended up trying to configure Ok Google from any screen, and the voice training feature didn't hear anything, remaining stuck on the 1st of 3 verifications.
Maybe you can try going to Settings > App > All > Google Search and deleting cache/data to restore it brand new.
Click to expand...
Click to collapse
Tried that, and reflashing it, factory reset etc. Turns out the problem is slightly wider than just that not working though - It's killed the Microphone completely, can't make voice calls, it's like it's just not picking up the mix exists for some reason :S
It takes time to activate, there is a backend update of google going on while you select your language, but eventually comes back on.
Try voice typing if your believe the mic is not doing any good for "ok google"
gamer.11 said:
It takes time to activate, there is a backend update of google going on while you select your language, but eventually comes back on.
Click to expand...
Click to collapse
Wouldn't really explain why my Microphone doesn't work at all, even in phone calls though
Reoryn said:
Wouldn't really explain why my Microphone doesn't work at all, even in phone calls though
Click to expand...
Click to collapse
just to try it out to rule out whether it's the telephony app or in effect a bug which affects 5.0 as a whole(which i highly doubt, because i have mine working like a charm) Hell mine even works on off-screen while charging.
gamer.11 said:
just to try it out to rule out whether it's the telephony app or in effect a bug which affects 5.0 as a whole(which i highly doubt, because i have mine working like a charm) Hell mine even works on off-screen while charging.
Click to expand...
Click to collapse
Ok, voice search nothing, voice typing nothing, Making Phone calls, nothing x) The only thing I haven't managed to try yet is downloading a 3rd party voice recorder app - but unfortunately I'm on GSM at work and for some reason, Lollipop is refusing to connect to the wifi as well. Good times
Might just flash it back to 4.4.4 and wait for the OTA upgrade to see if that does it better
Just as an additional - managed to download a voice recorder app.... Nothing either. So the whole OS isn't picking up the Microphone. Curiouser and curiouser
Oh hell.... I'm going to hang my head in shame now and hand in any tehcy credentials I may have once had.
I have a Pressy.... I forgot it was plugged in... I didn't install the app. Lollipop saw it as a headset and mic.
In conclusion: I'm an idiot. That is all x) Thank you for anyone who tried to help though.
I have the exact same problem but no pressy. Could it mean that there is a fault with the headphone jack?
Reoryn said:
Oh hell.... I'm going to hang my head in shame now and hand in any tehcy credentials I may have once had.
I have a Pressy.... I forgot it was plugged in... I didn't install the app. Lollipop saw it as a headset and mic.
In conclusion: I'm an idiot. That is all x) Thank you for anyone who tried to help though.
Click to expand...
Click to collapse
Lol
My mic is not working, i dont know what to do????? any help, just update to lollipop cuz receive the update message, but now i dont have mic. need help...
If my phone is on for more than 10 minutes, I lose calling functionality. When I try to call someone, it freezes and the Pixel becomes unresponsive, forcing me to hold down power for 10 seconds for a reboot. After this, it works just fine for another 10 or so minutes.
I have no idea when calling functionality begins to be lost because I can still send and receive texts, but I can't make or receive calls. I don't even get a wave of missed calls or anything when it works after a reboot.
Google Assistant has it's own issues when this happens too. It won't come up with "Hey, Google" at all. When I long press the home button, Google Assistant comes up, but I just get the floating dots. Fortunately, it doesn't freeze when I try this. Restart the phone and I'm good for about 10 minutes or so. I tried installing 3rd party calling apps, but the problem persists.
Hoping this is a Pie issue and waiting for the next security patch, will likely do a sideload flash-all. Any suggestions as to what the problem is from? Could my SIM card be the problem? Any apps I could try to help narrow down the issue? I had no issues with Oreo.
Thanks in advance.
Tried rebooting in safe mode. Slightly similar results: works fine for about 10 minutes but then it's just the mic not working. I can make and receive calls with out the phone freezing, but no mic.
mbstone said:
If my phone is on for more than 10 minutes, I lose calling functionality. When I try to call someone, it freezes and the Pixel becomes unresponsive, forcing me to hold down power for 10 seconds for a reboot. After this, it works just fine for another 10 or so minutes.
Click to expand...
Click to collapse
I have a similar issue with a used Pixel I purchased. I couldn't place or receive calls, with everything else working fine. Did the prerequisite online searches with results finding most everyone experiencing this issue chalking it up to hardware but I'm still thinking software. I tried a different phone app (drupe-enabled as default) with some success, then the problem returned (a few days later, rarely get/make calls). The default google phone app (version 23.0) fails every time. Currently looking into TWRP/Root and hoping to eliminate certain default apps to experiment further. Will be keeping an eye on this post! :cyclops:
--- Three weeks later ---
Could there be an issue within google play services with phone dialer app (any/or stock app)?
After continued issues I parked phone in drawer a bit then pulled out and tinkered with a few weeks later. Tried to isolate problem using logcat and on a hunch I flashed TWRP and a custom ROM but NOT any gapps package. Sticking sim in and using the built in phone app (Resurrection Remix -com.android.dialer) it works without issue. What? I flashed gapps (correct version/etc) and sure enough the problem returned. Went back to rom minus gapps, works fine. So, with straight up stock rom - stock phone dialer fails, custom rom - it works without a gapps package but not with.
Aimless Rambler said:
I have a similar issue with a used Pixel I purchased. I couldn't place or receive calls, everything else working fine. Did the prerequisite online searches with results finding most everyone experiencing this issue chalking it up to hardware but I'm still thinking software. I tried a different phone app (drupe-enabled as default) with some success, then the problem returned (about 5 days later). The default google phone app (version 23.0) fails every time. Currently looking into TWRP/Root and hoping to eliminate certain default apps to experiment further. Will be keeping an eye on this post! :cyclops:
Click to expand...
Click to collapse
Went back to Oreo before I had the problems and... problems persist. I'm sad. I had the privilege of speaking to someone from Google Support who was very knowledgeable. Unfortunately, my best option from the rep was to take it in to one of their authorized repair places.
Are you guys on Verizon? I'm having this problem with my dad's pixel on vzw.
brkshr said:
Are you guys on Verizon? I'm having this problem with my dad's pixel on vzw.
Click to expand...
Click to collapse
AT&T
---------- Post added at 07:47 AM ---------- Previous post was at 07:45 AM ----------
mbstone said:
Went back to Oreo before I had the problems and... problems persist. I'm sad. I had the privilege of speaking to someone from Google Support who was very knowledgeable. Unfortunately, my best option from the rep was to take it in to one of their authorized repair places.
Click to expand...
Click to collapse
--- Three weeks later ---
Could there be an issue within google play services with phone dialer app (any/or stock app)?
See my updated post (# 3) for what I've tried since..
Vzw ended up replacing my dad's phone through extended warranty. I talked to Google for awhile. Multiple factory resets, factory image installs, tried older phone apks. Nothing worked.
brkshr said:
Vzw ended up replacing my dad's phone through extended warranty. I talked to Google for awhile. Multiple factory resets, factory image installs, tried older phone apks. Nothing worked.
Click to expand...
Click to collapse
Older/newer phone dialer apps didn't work for me either ... custom rom and eliminating google play services did (no gapps). I'm still tinkering with the device ... installing frequently used apps using F-droid and Yalp, will test it. Not quite sure why but it works.
I ended up flashing Lineageos for Microg, presents it's own problems in the learning experience but it works.
Nothing ever worked in the end. No, not with Verizon. Bought through Canadian carrier called Fido.
Called Google tech and they weren't overly helpful. I started a chat with a Google Tech and they suggested I take it to UBreakIFix. They did a free diagnostic test and I referenced https://support.google.com/pixelphone/forum/AAAAb4-OgUsIW_gxTpXX3s/?hl=by that thread. Said they'd fix it for free even thought I was out of warranty. Got a new motherboard and my phone works like a charm.
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??
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)
Phone: Redmi Note 10 Pro Max, Poco X3 ProOS: Android 11, on MIUI 12.5 and MIUI 12
Issue:
When I pick Voice to be my default call redirecting app, it does not make calls.
The Phone app just stays stuck on dialing and never dials. Never rings on the other end either.
Sometimes, it causes the phone app to stop functioning altogether to the point that I have to restart the phone to regain functionality. I have sought help for the issue all over the internet and cannot seem to get any info on it.
I don't have an issue with going into Voice app itself and making the call over Wifi. It just will not redirect via the phone app, which was very convienient.
I believe it might be specific to Xiaomi phones, but then again, I used a Phone that uses Google Dialer, and it is the same result, albeit, it was also a Xiaomi phone with Global ROM containing Google apps as defaults.
I believe this to be an issue with Xiaomi ROMs. If I make the call from any other Android 11 ROM, the call works just fine.
Any assistance with this will be very helpful. Google Voice is my most used app on my phone.
No one else is having these issues? Or is it that people don't use Google Voice as much?
Given all permission it requires? Allow auto-start up? Is the phone you said working fine a Xiaomi phone with custom Rom Android 11?
If custom Rom works fine, then it's MIUI's problem.
If it's MIUI problem, ask in Xiaomi official forum or online customer support service.
If custom Rom still having issue, it might be Google Voice issue. Either hardware or software issue.
I have given it all the permissions it needs. And I do believe it might be a Xiaomi thing because I have installed other phone apps and they too can't work. I've posted the issue in Xiaomi forums.
I was hoping other people might be facing the same issue and could help with solutions
Try turn off MIUI optimization in developer menu and see if it works.
Maybe also try this
https://www.reddit.com/r/Xiaomi/comments/bqasnd
MIUI optimization is nowhere to be found in this ROM. I am looking to see how I can disable it otherwise.
Damionix said:
MIUI optimization is nowhere to be found in this ROM. I am looking to see how I can disable it otherwise.
Click to expand...
Click to collapse
Go into developer setting, scroll down to the botton, press the reset to default setting multiple times. Then the MIUI optimization should show up.
I saw that, and tried it several times but it would not appear.
Damionix said:
I saw that, and tried it several times but it would not appear.
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...eming-turn-on-miui-optimization-gone.4254555/
pl1992aw said:
https://forum.xda-developers.com/t/...eming-turn-on-miui-optimization-gone.4254555/
Click to expand...
Click to collapse
Thanks. That made it show up. I tried the call with optimization off, same thing. Optimization on, and still the same thing. I think it's a problem with Miui itself. Something in Miui is blocking voice from making calls when it's being redirected.