Why do I hear no sound when I call "ok Google?"

[Philcraft]

Try running the app clean master from play store

It sounds weird but it worked. Running Clean Master fixed the problem. Thx

 

[NOLATechy]

I just got off the phone with Nexus support and they say it is a "known issue" and are contacting Google directly. I informed them that if this was a decision Google made on purpose, it is a HORRIBLE, STUPID decision! People rely on this "beep" to know when to start asking their question and if you're not holding the phone, you surely can't feel a vibration. Google needs to fix this and fix it now! If/when I hear back from Nexus Support, I'll post additional information. It's bad enough for Android to have Samsung phones blowing up, we surely don't need loss of functionality with Google Now pushing Android users over to Apple!

 

[Andy Xheli]

I'm having the same issue on my Nexus 6P "Google Now Not Giving Response Sound". Google better find a fix.

Just called Support they told me to send them a feedback with the issue that i'm having.

 

[GeneValgene]

Ok guys....out of desperation I tried @Christopher Kolle and @Philcraft's method - which was to use that Clean Master App. I think all these cleaning apps are kind of a scam, but I was so frustrated I would try anything. I downloaded the Clean Master Lite edition, installed, granted the specified permissions, and ran and deleted all the files it told me to. I thought there was no chance in hell this would work....

Lo and behold, it works! So I have no idea how Google is applying this Google Now update, but it's screwing up the sound. The Clean Master App must be deleting the offending cache file. The OK Google notification sound is back!!!

Thanks @Christopher Kolle!

 

[Andy Xheli]

Thanks GeneValgene & Christopher Kolle! Just tried that also and it worked for me. Per Google support recommendation: Send feedback to google on this issue so they can fix it via a update. I'm having my family members send feedback on this the more the better.

 

[anon(847090)]

It sounds weird but it worked. Running Clean Master fixed the problem. Thx

nice trolling

 

[Andy Xheli]

You're Welcome

 

[NebsTV]

Like a lot of you, this problem happened to me in the past few days. Nexus 5 for me. Searching for an answer I found this thread. Installing the Clean Master app seemed like the best solution, so I gave it a shot, and it DID WORK. But, after doing some investigation, not for the reason a lot of you may think.

When using the app, it asks you to turn on permissions for it in Settings>Accessibility>Services. For some reason, and don't ask me why because I don't know, THIS is what triggers the OK Google sound to work again! Thing is, you don't NEED Clean Master do to this. I found just enabling Switch Access in Accessibility works as well.

So there you go. Just enable Switch Access and you got your sound back. Again though, just don't ask me WHY it works.

 

[Philcraft]

So there you go. Just enable Switch Access and you got your sound back. Again though, just don't ask me WHY it works.

Thx @NebsTV. That`s it! I've uninstalled Clean Master, made the settings as you've recommended and got my beloved beep back.

 

[Douglas Kirschman]

I'm right there with you guys. Nexus 6 original and just started happening today. I clear data and it seems to fix it for a few minutes up to an hour but always reverts back to the issue. Glad I found this thread, was about to format the phone out of frustration. At least I'm not the only one. I assume we will need an app update to fix this...

This just started happening to me 2 days ago. Like most people on this thread, it seems to have happened after an update or two. Driving me nuts. Motorola Nexus 6.

 

[Cwluc]

Don't know why, didn't care how, but since I didn't have the service option under accessibility I installed Clean Master. Tone is back. Thank you. Like many of you I was going insane without that sound.

 

[J Flanagan]

Neither option works for me S7 EDGE. Last update from Google just now didn't fix it either. Come on Google!

 

[Philcraft]

@J Flanagan If neither turning ON switch access nor installing and running the Clean Master app fixed the bug, then you maybe should try another Cleaner App (Yes, I know, they are normally quite useless) like Clean Booster. For some people it worked.

 

[MIghtyTBird]

Genius - Worked perfectly - Thank You!

 

[KillerQ]

This just started happening to me 2 days ago. Like most people on this thread, it seems to have happened after an update or two. Driving me nuts. Motorola Nexus 6.

I uninstalled and reinstalled "Google app" and its back to working flawlessly.

 

[MILES_LONG]

My Nexus 6p running nugat doesn't have this setting "switch access" under "settings, Accessibility" or anywhere else.
Is there another work around that doesn't include this cleaning app that wants access to nearly everything on the phone.

 

[MILES_LONG]

against my better judgement i installed an ran the cleaning app.

the google audio prompt began working immediately immediately started .
I then deleted the intrusive app and the audio prompt stopped working immediately.

Any other ideas?

 

[Philcraft]

My Nexus 6p running nugat doesn't have this setting "switch access" under "settings, Accessibility" or anywhere else.
Is there another work around that doesn't include this cleaning app that wants access to nearly everything on the phone.

If you don't have the option to turn switch access ON, you can try to install Google Talk back or re-enable it and then go back to accessibility and the switch access option should be there

 

[mhpp]

If you don't have the option to turn switch access ON, you can try to install Google Talk back or re-enable it and then go back to accessibility and the switch access option should be there

That did the trick! Thanks!
Exact same problem, but couldn't get over installing this pseudo-cleaning app.
Had no option for switch access so I couldn't enable it.

After installing Talk back I got two new options in accessibility settings, one for TalkBack itself and one for the switch access. Enabled the last and it worked!

Damn, never thought THIS would solve it! Glad I found this thread!

 

[spevman]

I can indeed confirm that enabling Switch Access did the trick. I'm running Android 6.0.1 on a Galaxy 6 Edge Plus. Thank you! This has been driving me crazy all week!