Ok google was working fine but now when I tap the mic button on Google search its says can't open microphone. Please help. Also went to settings and all apps and couldn't find google search
Try a reboot, if not go to applications, Google voice, clear cashe/data.
Pp.
Same thing just happened to me. Had use OK Google earlier today and now the mic will not open. Since this has happen to others, what is the fix?
Google voice clear cashe does nothing
OK Google works fine on both my Samsung Galaxy S and my Nexus 7, so why did it have mic issue only on my Galaxy S5?
Same with me any solutions yet?
Try a reboot, no one has reported what worked for them.
Pp.
go to settings .
then go to installed apps.
then scroll down and select google app.
scroll down and select permission manager.
just wait a bit and you will get all the permission options.
now make sure that a green tick beside "record audio" and "make phone call" option.
if not the just click on the particular option and select "accept".
thank you.
make enjoy to have a great device or a gadget.
Its not about permissions i guess
badinfluence12001 said:
Same with me any solutions yet?
Click to expand...
Click to collapse
In simple words - another proggie uses this process and keeps the mic busy. As soon as it releases the mic it will become available to OkDoodle).
Just check it our - restart the phone and as soon as you can tap the mic - it will work. then it will say the same thing - cannot open the microphone.
Solution. In my case i had to find and delete an app that was using the mic non-stop - it was navigator. Go to settings>applications>app manager>slide to running applications. Now "stop" an app that uses any sort of microphone input - it could be a navigation, a dictaphone, a keyboard (remember, theres a little mic icon in da corner). It did help me to resolve this issue. Unfortunately, I am now using a google navi instead of my preferred one...
technically: record the log file of processes, check which process opens this -
android.media.AudioRecord;
android.media.MediaRecorder;
android.media.AudioFormat
Another good reason to keep stock Google apps that work properly.
Pp.
the same problem....
balashandr is right, I had the same problem and the solution for me was to uninstall a voice assistant had installed, restart the phone and ready (I have a Note4 by the way)
You're welcome hopefully
If you have the app audiko ringtones uninstall it and your mic will work instantly it worked perfectly for me. When I went s voice it told me that another app was using my microphone so I remembered that app that I just installed deleted it and boom my mic is fixed
Thanks a lot Helperthehelper
You're right. Since latest update a couple of days Audiko app blocks other app usage to microphone.
I've stopped the Audiko process and my phone it's perfect
Thanks
Helperthehelper thanks so much .. audiko is the problem
Alternative method
An alternative method is to modify the app permissions and ignore microphone. You get to keep the app and the problem is solved as well.
Thank you so much it worked for me!
ok google only works once after a restart then will only hear the ok google part. I installed a voice app yesterday called discord I disabled it first then tried no luck again only working after a restart and then only hearing ok google. I completely uninstalled the discord app and restarted and STILL only works right one time, then after only hears the ok google part. I have systematically turned off any app I could access to microphone only set for google. STILL no joy.
is this a ok google thing? or is my phone buggered?
editing to confirm that nothing happens after my phone hears my say ok google, hears ok google just fine but then nothing else after
Turning off s voice worked for me. I was also getting can't open microphone when using ok google on any screen
finally i found the problem, just go to samsung s voice and turn off mic permission
android Q builds for many phones have a google assistant glitch, deny mic perms to google app fixes it and regular microphone works again
Flash Google Nano Gapps
MrJesseJay said:
Ok google was working fine but now when I tap the mic button on Google search its says can't open microphone. Please help. Also went to settings and all apps and couldn't find google search
Click to expand...
Click to collapse
Try flashing nano gapps then clear cache
Related
Since updating my i747 to 4.3 OTA, when starting up S-Voice the voice feedback prompts (the app reading the results back to me) are always muted, requiring me to push the button on the lower-left to turn the voice responses on. This only fixes things temporarily, since the next time the app starts from scratch the feedback is muted again. It seems like it should be the other way around by default. This isn't related to my phone's volume control, either. The update to 4.3 works well otherwise, as I did a factory reset after installing. Can someone else with the same config tell me whether or not this is happening to them? I want to know if this is a software bug or if I might need to restore the firmware in the future.
EDIT: I found the cause! It's Greenify's accessibility service.
v voice muted solved
Go this path
Accessibility -vision .-switch acess. ...
and off it
Enjoy s voice feed back......
Thanks
[email protected]
Just for background, this issue happens on a clean install of PAC-man or SlimKat 4.4.4.
I got the google now update that allows hotword detection on any screen, but using it causes a crash, no matter what command.
I can try to send a text, navigate somewhere, or search, but after it processes my voice the app FCs.
The weird thing is that if you turn off audio history after enabling hotword detection, it will work a couple times, but then start crashing again.
It crashes every time with audio history enabled.
There was problems with this back when people sideloaded the google experience launcher and the hotword would crash the device, but this is official, so I think it is a different problem. I have not had the chance to test it on official TW roms, but if I can't find a fix I will load a backup and see if the problem persists.
Open Google Search and go into Settings > Voice. Make sure 'Bluetooth Headset' is ticked. That fixed the issue for me.
LooseSeal said:
Open Google Search and go into Settings > Voice. Make sure 'Bluetooth Headset' is ticked. That fixed the issue for me.
Click to expand...
Click to collapse
Fixed it for me as well, thanks!
Fixed for me too, wtf crazy Google nkw
Many thanks
Hi Everyone. I hope you could help me with my situation.
I had the watch about a month now. It was working nicely till a couple of days ago, the ok google stopped working.
When I tap the screen twice, there is a red G speak now. I cant tap on that icon. When replying a sms, the watch doesn't go into the voice recognising mode. I also tried sync with another phone.
I tried resetting to factory default. Reinstalling android wear and moto connect. Still doesn't work. I even tried the settings in Google settings, re recognising the ok google..
Running out of options.. Please help
When the red G Speak now appears do the following:
Speak.
This is the new design since Wear 2.0 Update
I spoke ...
but nothing happens...
Ferderico said:
I spoke ...
but nothing happens...
Click to expand...
Click to collapse
Strange, could your microphone have something in the little hole?
i doubt that something is stuck in the little hole at the 9 o'clock position.
cos if i tap on Speak Now - it should have some bars which emulates a sound equaliser... but in my case, there isnt.
So i suspect is a setting. ... sigh..~ btw i am using Samsung Note 4
Ok, excuse me for my upper post.
But without the further infos you have now given, i could not resist to write this.
Test the microphone with an other app.
SleepAsAndroid, LED Music Controller or any soundrecorder which uses the moto360 microphone.
Have you rooted your Samsung and are you restricting apps with xprivacy or a similar program?
If the sound test fails I think your microphone is broken...
Try this. My problem was that "OK Google" only working from Voice Settings Screen using Moto 360 with my Samsung Galaxy S4 running Lollipop. I could not get the "OK Google" feature to work anywhere EXCEPT when I had the SETTINGS/MY DEVICE/LANGUAGE AND INPUT/GOOGLE VOICE TYPING screen open on my phone. Turns out that you have to have the GOOGLE NOW LAUNCHER as the home screen software. It will not work with the TOUCHWIZ HOME as the home screen software. To change this, go to SETTINGS/MORE/DEFAULT APPLICATIONS/HOME and select GOOGLE NOW LAUNCHER.
Static sound coming out
I am having the same issue. Also I am using a custom rom for note 4. I have tried the solution above and it doesnt work. I installed the "wear audio recorder" app and I only hear static sound... Is there an app or something to see if the communication between components working?
On my N910V running VRU2CPF3 CM13.0-20160724, I have noticed a very strange behavior with the Google Now app (recently re-branded as simply, the "Google" app). Immediately after a phone call (and during other circumstances I haven't identified precisely yet), the Google app will lost the ability to "hear" me, even if I press the microphone button and start talking. The "ok Google" function doesn't work during the issue either, nor can I retrain the ok google voice model because it plain doesn't register any mic input. I can make calls and people hear me fine, and I can record audio on my camera, so my microphone is working.
The issue always goes away if I reboot, but eventually comes back, even if I haven't made any calls. On one occasion, I got the mic function for the Google App back after opening my phone app, then lost it after closing my phone app. On another occasion, I got the mic function back for the Google app after uninstalling Google Chrome and Chrome Beta (per this post). I was also able to get functionality back once by plugging in an external headset and then unplugging it, and another time by force killing all open apps. All of these "fixes" failed to fix the issue this time around - strange, right? Again, reboot always gives a temporary fix, and a phone call usually (not always) causes the issue to occur. I have found at least one individual with the same issue (khalil) here
I have tried a fresh install of the system, and the issue seems to go away for hours or even days at a time, but always comes back. I froze every user installed app on my phone using Titanium backup to see if an app was the issue, but the issue persisted. However, the issue does not seem to occur when booted into safe mode (which screams of software problem). I am currently in the process of reflashing a blank system to see if the issue persists without any user apps.
This behavior is not specific to this operating system; I had a similar issue when I was on stock unrooted 5.1.1. I did not notice the issue on Jasmine rom running 6.0.1, but I also didn't run it for very long. I seem to recall having a similar issue with my Galaxy S3 on CM11 (though it was a while ago so I can't confirm the truth of this!), so I suspect that something about my setup is to blame, rather than the hardware.
One more juicy tidbit: force uninstalling the google app fixed the issue for a day, then the app started force closing on launch, and no amount of finagling would stop the force closing. For the record, I've flashed google apps mini from opengapps.
I don't know what tools to use for proper logging of hardware - ie, when an application has control of the mic or not. I suspect that the issue is coming from improper ending of microphone use state in a certain program.
I have been using the Moto Z2 Play for almost a year now, and the feature i used every day is waking the phone when the screen is off by using the OK/Hey Google command.
The tooltip in the Google voice match settings used to read: Access your assistant any time you say "OK Google", even if your screen is off or you're using your favorite apps.
However after updating the Google app to version 8.28 the tooltip changed to "whenever your screen is ON" instead of "even if your screen is off".
And sure enough, the phone will no longer respond to commands until i pick up the phone and manually turn on the screen, which defeats the purpose.
Why was this feature removed? I have tried everything and finally had to uninstall Google updates and install an older version(8.24) from apk mirror to get Assistant to work properly again.
What is even more puzzling to me is that this problem seems specific to my Z2 Play, i have the latest Google app version(8.28) on my Xiaomi phone, and the tooltip still says "even if your screen is off" and it works as it should.
I tried Googling this issue, i checked the Motorolla support forums, the Google assistant support forums etc. and couldn't find any mention of this issue.
This has also happened to me! I thought I just needed to reboot the phone to maybe fix a background service that had stopped, but I also see that "...even when your screen is off" has been removed from the Voice settings. This is one of the features that made the Moto Z line attractive to me, and I literally use (well, used) the feature several times a day, especially while driving. I also use Android Auto and now I have to either touch the microphone on my truck's head unit screen, press and hold the voice button on the steering wheel for 3 seconds, or unlock my phone so I can talk to it. I have a self-built Android Auto in my other car and it also has this issue, which I now know is not related to either car's system. Thank you for posting and bringing this to our attention.
I think this must be a bug in the latest Google app. Does anyone know where we can submit bug reports for the app, or voice control/Google Assistant in general?
Has any else experienced this problem, or does anyone have ideas about what to do to potentially resolve it? Surely OP and I can't be the only two people who have witnessed this issue.
tropho said:
Has any else experienced this problem, or does anyone have ideas about what to do to potentially resolve it? Surely OP and I can't be the only two people who have witnessed this issue.
Click to expand...
Click to collapse
It is likely that there just aren't many Z2 play users who frequent xda, and the ones that do never noticed the issue because they don't use the feature.