Hello everyone. It's a couple of days I have facing this weird issue: when I make a phone call on the other side they can't hear me properly, it's not a matter of volume but of quality and the conversation results very difficult, instead, if I turn on the loudspeaker they can hear me. If I come back to the speakerphone sometime they can hear me, sometime not.
So I tought it's an hardware issue and I tried to record my voice with an audiorecorer app forcing it to use the principal microphone and it never fails.
Now that the hardware issue it's excluded I started thinking about a software issue or maybe some conflicts between apps.
At the end it turns out it was the "Ok google" detection to enter in conflict with the main microphone and deactivating it solved the issue.
Now, because I use it a lot but, at the same time, a phone is intended to make phone calls, is there anyone facing the same issue? Did someone find a workaround to make them both working?
P.s.: I'm on latest slimLP, AK 131 and latest firmware from CM12.
facing the same problem
I have the same issue with the call quality. I'm on roaming for the past 2 days. This problem started when I received a call using the headset connected. Now even when the headset is not present, the person on the other end keeps complaining about the voice vibrating. Putting on speaker fixes it but going back to the regular earpiece brings the problem back. Another thing I noticed is during the call the volume rocker doesn't have any control over the volume. The sliders goes up and down but the volume is unaffected. I have tried rebooting the phone and clearing cache many times now. Waiting for someone with a solution.
I'm on stock CM11S rooted with xposed installed.
Facing the same issue
This issue has cropped up all of a sudden recently for me too. The people on the other side of the call say they cant hear me. Occasionally some calls go through just fine though. Tested mic with recording software and it records voice just fine! I'm on the latest Sabermod with AK Kernel.
Uninstall any call recording app and try again.
Sent from my A0001 using Tapatalk
I have the same problem from time to time. CM12 nightlies. Very annoying. Sometimes it is OK sometimes not.
Martin-Doc said:
Uninstall any call recording app and try again.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
When I first noticed it I had no call recording app installed neither I have now. It was fixed disabling "ok google" detection.
Thanks for the tip. I just disabled 'OK Google' detection in 'any screens'. Let us see whether it fixes the problem.
I tried uninstalling the hangouts dialer and then reinstalling it. So far it looks fine. Will update if i get the problem again.
Flyingdaddy said:
Thanks for the tip. I just disabled 'OK Google' detection in 'any screens'. Let us see whether it fixes the problem.
Click to expand...
Click to collapse
So you left ON the "ok google" on the app? What about phone calls? Do they seem fine?
Yes I left OK Google in the Google app. I only disabled it for every screen. It seems to work OK. Hope I'm clear (I' m French)
Flyingdaddy said:
Yes I left OK Google in the Google app. I only disabled it for every screen. It seems to work OK. Hope I'm clear (I' m French)
Click to expand...
Click to collapse
I'm Italian so we are on the same boat!
Ok so now I'll try activating it too for the app only, let's see how it goes.
P.s.: Tried to make a phone call and it works flawlessly. I hope CM fixes this bug soon!
Awesome, got this problem out of the blue, and disabling Google voice everywhere fixed it. Thanks!
After two day of testing this modification issue of the same bug one the LG G2 works perfectly in all situation during call ( headset, voicecall etc.. ) and doesn't decrease quality on other apps like camera, skype etc..
in Cm12 build.prop replace this two line :
ro.qc.sdk.audio.fluencetype=fluence
persist.audio.fluence.voicecall=true
With this:
ro.qc.sdk.audio.ssr=false
ro.qc.sdk.audio.fluencetype=fluence
persist.audio.fluence.mode=endfire
persist.audio.handset.mic=digital
persist.audio.voicecall.mic=0
persist.audio.voice.clarity=none
persist.audio.aanc.enable=false
persist.audio.handset_rx_type=DEFAULT
persist.audio.nsenabled=ON
persist.speaker.prot.enable=false
persist.audio.spkcall_2mic=OFF
Infinityyy said:
Awesome, got this problem out of the blue, and disabling Google voice everywhere fixed it. Thanks!
Click to expand...
Click to collapse
Many thanks to @sambaeallegria who first proposed this solution
thank you @sambaeallegria i also got this problem out of the blue and your tip fixed it!
many thanks
Today I received an update for "google app" from play store but I can't try now to make a call. Did someone noticed any improvement activating "ok google everywhere"?
Flyingdaddy said:
Yes I left OK Google in the Google app. I only disabled it for every screen. It seems to work OK. Hope I'm clear (I' m French)
Click to expand...
Click to collapse
How to disable "ok google everywhere"?
blank420 said:
How to disable "ok google everywhere"?
Click to expand...
Click to collapse
Go to google search settings, then voice, "ok google" recognition and left enabled only the first slider (from app).
sambaeallegria said:
Go to google search settings, then voice, "ok google" recognition and left enabled only the first slider (from app).
Click to expand...
Click to collapse
Thanks!
Related
the Mic detection range for "ok Google" is really bad on OPO, I pretty much need to hold the phone next to my mouth to activate it, anyone have a fix for it? what cause this problem?
tpboi said:
the Mic detection range for "ok Google" is really bad on OPO, I pretty much need to hold the phone next to my mouth to activate it, anyone have a fix for it? what cause this problem?
Click to expand...
Click to collapse
Mine has this problem as well. Hoping for a fix.
Same issue here. After initiating OK Google, the mic range for voice recognition is fine.
Can every one who has this problem vote for this issue on JIRA? https://jira.cyanogenmod.org/browse/BACON-8?jql=project = BACON
This needs to be escalated. It's annoying that such a basic function is broken on the OnePlus One.
Latest CM11 nightly still has this issue.
Just wrote a very simple app called BT GNow, which activates Google Now rather than the default Android Voice Dialer when you hit the hands-free button on your Bluetooth headset. Surprisingly, I can't seem to find another app that accomplishes this simple function. Bluetooth Launch does this to an extent, but the UI is difficult, it requires some configuration, it seems to me to cause wakelock problems, and the instance of Google Now that it starts takes off where Google Now left off (so you are often brought to an old search rather than an opportunity to speak a new voice command).
BT GNow keeps only a limited wakelock, requires no configuration (other than configuring Google Now to accept input from your Bluetooth device and possibly disabling the native Voice Dialer), and starts a fresh instance of Google Now each time.
Here's the Play Store link: https://play.google.com/store/apps/details?id=com.vibaroo.btnow
And the (minimal) website that describes the setup: https://sites.google.com/site/btgoognow/home
Great will try tomorrow
I will try now, great APP man:good:
Fail, my bluetooth now is not working, i tried, factory reset, re-flash system but not working more
Wow, great app. Makes my bluetooth headset and Google Now work as I always expected it would have to begin with.
I noticed that there was a problem with the screen locking and not responding to touches if lockscreen security is enabled and Google Now is interrupted. Solved this problem with the latest version and also improved wakelock control by sticking an icon in the corner of the screen. The icon disappears when the screen is turned off, and the phone is kept awake only as long as the icon is present.
Got rid of the icon that people seemed to dislike (made it invisible).
Donations?
New Feature
Some have reported problems with BT GNow not effectively bypassing the lockscreen. To address this, I've added an option that requires you to say "OK Google" after pressing your handsfree button; this in effect lets Google Now handle the lockscreen itself. You can activate this option by clicking on the app in the launcher and choosing the "OK Google" option.
Note that if you choose this option, you have to make sure that "OK Google" detection is set to work "From any screen": Google Now > Settings > Voice > 'OK Google' Detection > From any screen (checked or set to "on").
Is there a way to use this with non-BT headphones? I have the 3 button control on my headphones and would love to be able to use this app to bypass the voice dialer.
Dzinic said:
Is there a way to use this with non-BT headphones? I have the 3 button control on my headphones and would love to be able to use this app to bypass the voice dialer.
Click to expand...
Click to collapse
I'm not sure. Embarrassing to admit that I don't have a wired headset to try it with. At least one user has reported that it does work with wired headsets, though. Have you tried it?
NYZack said:
I'm not sure. Embarrassing to admit that I don't have a wired headset to try it with. At least one user has reported that it does work with wired headsets, though. Have you tried it?
Click to expand...
Click to collapse
I tried using both of the options but both seem to lead to the voice dialer unfortunately.
Dzinic said:
I tried using both of the options but both seem to lead to the voice dialer unfortunately.
Click to expand...
Click to collapse
Did you try disabling the voice dialer (as in the instructions)?
NYZack said:
Did you try disabling the voice dialer (as in the instructions)?
Click to expand...
Click to collapse
I did follow the instructions up to the Voice Dialer point due to not being able to find the Voice Dialer app in the "All" section. I don't know whether I'm blind or lollipop merged it into another application.
Dzinic said:
I did follow the instructions up to the Voice Dialer point due to not being able to find the Voice Dialer app in the "All" section. I don't know whether I'm blind or lollipop merged it into another application.
Click to expand...
Click to collapse
Hmm. You're right. Since upgrading to Lollipop I don't see it on my phone either. I'll see if I can get a hold of a wired headset to try to troubleshoot it.
You should go Bluetooth!
NYZack said:
Hmm. You're right. Since upgrading to Lollipop I don't see it on my phone either. I'll see if I can get a hold of a wired headset to try to troubleshoot it.
You should go Bluetooth!
Click to expand...
Click to collapse
Don't go out and get one just to fix my problem! I just don't use my phone for music enough to justify investing in a bluetooth, haha. Thanks for looking into it.
:thumbup:
Thanks!
Amazing! I'm currently using your app to simulate the MotoX experience on a Nexus 5 (pressing just the button on a Moto Hint to query the Nexus 5). I'm still having a problem with the sound from the headset seeminly not being routed through to the phone after I say "Ok Google" (even though I've got the option enabled within Google Now's settings), but I'll keep working at it.
patientzero said:
Amazing! I'm currently using your app to simulate the MotoX experience on a Nexus 5 (pressing just the button on a Moto Hint to query the Nexus 5). I'm still having a problem with the sound from the headset seeminly not being routed through to the phone after I say "Ok Google" (even though I've got the option enabled within Google Now's settings), but I'll keep working at it.
Click to expand...
Click to collapse
I've noticed that problem if you have more than one bluetooth device connected at once - for instance, if your phone is connected to your car's bluetooth or a stereo headset while connected to your Moto Hint. I'm considering options to try to fix this. In the meantime, perhaps it's better not to use the "OK Google" option and just launch directly from the bluetooth button?
My friend has same thing on his iPhone. I can now use google now with handsfree, when i driving my car. Thanks! The Coolest app on my week!
Wishlist ....
Given the code you have already written here is a little wish from me ... could you implement that the HFP bluetooth headsets just do not launch any application - just volume up and down.
xperia Z, TWIINS bluetooth headset for motorcylce, mono Bluetooth to route Navi output to headset - whenever I press volume down I get the stupid voicedialer or -if disabled- a black screen. I do not want to make any phoncalls on a fast bike!
Thanks in advance.
DrT_Music
Why am I getting this message when I do a video recording?
"Camera is currently recording audio.com.google.android.googlequicksearchbox:interactor will not be able to record right now"
Clicking ok does not make the message disappear.
Why and what does that mean?
Thank you for any advise.
rimz808 said:
Why am I getting this message when I do a video recording?
"Camera is currently recording audio.com.google.android.googlequicksearchbox:interactor will not be able to record right now"
Clicking ok does not make the message disappear.
Why and what does that mean?
Thank you for any advise.
Click to expand...
Click to collapse
I did some research and found out that it happens when "Ok google" voice detection is activated. When I turn that feature off, the error message does not appear. However, I do use "ok google" frequently and do not want to turn it off. Is this a bug or is there a solution so that "ok google" can be turned on without having that error message?
turn on camera
swipe left for settings.
touch audio controls
turn off audio controls (you can turn on "show audio icon on main screen" as this will allow you to easily turn on audio picture taking)
Thanks it seems to be ok now. I had same problem till now, but didnt really bother to find solution.
Sent from my MHA-L29 using Tapatalk
But this happens all the time, like when i run shazam or try to record video... Its extremely annoying... Is there any way to disable this message without disabling my "ok google?"
Seems that this didnt fix my problem. Yesterday I recorded video and git this errors poping on my screen again. Any way to fix this?
Sent from my MHA-L29 using Tapatalk
I was having this issue and eventually had to disable "Ok Google From Any Screen." However, last night my phone upgraded to Google Assistant, and on a lark I re-enabled Ok Google From Any Screen... So far no issues while recording video, no issues using Duo or any other apps in which "Ok Google" would hijack the microphone. I'll report back if there are any changes, but so far so good.
Yancy
---------- Post added at 05:53 PM ---------- Previous post was at 05:48 PM ----------
Annnnndddd.... never mind, the bug just popped up again.: rolleyes:
still happening with me even with GA.....
Anyone found a solution to this? Since the "OK Google detection from any screen" setting had disappeared in the Google App settings, the only solution I found works is to take away Microphone permission from Google App's permission list. This fixes the problem, but rendered GA totally unusable... would really appreciate any ideas on this...
I've not found a solution yet, it's driving me crazy. I use ok Google so I don't want to turn that off but the constant messages when recording are annoying as hell.
Anyone having mic problem with P40 pro during the call? The other side cannot hear me when I use normal mode to talk. But when I turn on the speaker it is fixed and they can hear me well. Is it hardware ot software problem? Mine is 10.1.0.154.
It is annoying. I have tried factory reset, safe mode and still having the problem.
But it seems fine in whatsapp and messenger call though.
Please help me.
Sorry literally 0 issues with mine ... Other the face unlock not working with a bloody mask ?
olaf2k4 said:
Sorry literally 0 issues with mine ... Other the face unlock not working with a bloody mask
Click to expand...
Click to collapse
I just want to know that it is software or hardware issue. Because this is very annoying.
Try to go in Support app and then at Troubleshooting...one of those options from there should test mic also as I remember.
Ye Thwin said:
Anyone having mic problem with P40 pro during the call? The other side cannot hear me when I use normal mode to talk. But when I turn on the speaker it is fixed and they can hear me well. Is it hardware ot software problem? Mine is 10.1.0.154.
It is annoying. I have tried factory reset, safe mode and still having the problem.
But it seems fine in whatsapp and messenger call though.
Please help me.
Click to expand...
Click to collapse
Hello, has your microphone returned to normal?
I have the same problem, the call works well on the speaker because it uses the upper microphone. But the bottom microphone has a very low volume, making the other person not hear the voice on calls.
That's what I deduced from the tests and the support app. I'm afraid of being a hardware problem, I recently purchased the smartphone.
The microphone appears to be wet or dirty.
Wagner Seilert said:
Hello, has your microphone returned to normal?
I have the same problem, the call works well on the speaker because it uses the upper microphone. But the bottom microphone has a very low volume, making the other person not hear the voice on calls.
That's what I deduced from the tests and the support app. I'm afraid of being a hardware problem, I recently purchased the smartphone.
The microphone appears to be wet or dirty.
Click to expand...
Click to collapse
I am still having the problem. How to clear the microphone? The hole is very small.
Hi did u find a solution?
S22 ultra on verizon.
This started in the last two weeks. If I connect to bluetooth, either android auto in the car or a Jabra headset. Ok Google functions while using them, but as soon as disconnected does not work further. In fact it appears Google voice keyboard, google assistant, and google voice search simply cannot hear me. In each case the a amplitude lines do not move, as if I am being silent. If I turn off Bluetooth, and turn off voice matching, and wait some undetermined amount of time and turn voice match back on, on Google resumes responding. It seems like it is only listening for the disconnected Bluetooth connection not my microphone. However the microphone use indicator, green dot, does appear. If I make a phone call or use voice recorder the mic is working, just not in Google apps.
Again, this only happens after Bluetooth use, and only appears a problem in Google apps assistant, voice search, or Google keyboard.
Also, rebooting has no effect, so far its been 2 days since I was in the car and still not working.
and today i tried changing the language in google to no effect. Then i tried switching to bixby and still it did not indicate it could hear me. I turned off voice match, i cleared cache and data from the assistant app, i cleared data on the google app. I rebooted and cleared cache from the boot menu
i made 2 phone calls and both worked. I used the sound recorder app, that worked, but no app that uses background listening, even when they are in the foreground, indicates it can hear anything.
I've rebooted several times. and tonight, out of no where, just for the f of it I said "ok google" and it is working again and probably will until i connect to bluetooth again.ugh
Anyone have a suggestion for the next time this happens?
You have given permission to microphone access?
You want to ensure ok google is turned on in your Google settings.
justinturner said:
You have given permission to microphone access?
Click to expand...
Click to collapse
Yep the little green mic access shows up each time.
Rubby1025 said:
You want to ensure ok google is turned on in your Google settings.
Click to expand...
Click to collapse
It is, and it's enabled in Google voice typing and Google search, as well as Bixby.
So after working for 10 minutes last night, back to the same symptom ok google not responding, Google voice keyboard not hearing anything, voice search same, Bixby more of the same.
This seems like the issue I had with android auto where maps disappears because something was being put in deep sleep. F'ing Samsung. I don't need you to protect my battery so aggressively.
Anyone have a suggestion?
couldn't take it anymore so i wiped the phone and started over. It has happened twice since. it almost seems like if ok google has been triggered but nothing is asked of it, that breaks it. although i have had it connect up to android auto in the car once or twice in the last week so maybe it is still that. I have no idea.
When it wasn't working to say ok google in the car it can still be triggered with the steering wheel button, but if it is not connected to the car, trying to trigger it manually does not work, it will not "hear" when the mic is supposedly active. But phone calls and sound recorder work fine.