Yes, this was removed from desktop Chrome (Win/Mac/Linux).It still exists on Android.

No feedback was received in the last 30 days from reporter "myschlongis@gmail.com", so archiving this. Please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

The problem still exists for isolated users.
It is unrelated to the removed 'OK Google' hotword activation.

Do: Click on the microphone in chrome at google.com
Get: No Internet Connection page.

The longest current open chrome help thread is 
  https://productforums.google.com/forum/#!topic/chrome/cwERAcdlq6M

The help forum sees about ~10 posts/week for this problem.

If this reopens this bug, I can provide feedback but nothing definitive.

See also 
 bug 417304  (bitdefender, wontFix), 
 bug 242861  (closed, speech quota fix)

It looks on that thread like the reporter has Chrome 57.  Voice search devs -- was this removed from desktop at a later point, but the backend has now been removed too, and so old versions of Chrome give a bad error message?  Trying to figure out the actual problem here.

pkasting@ - Thanks for picking this up.  See my cmt#4 for the failure use case. Same as the original author, just clearer.

Only affects isolated users.  Appears out of the blue after it was working for years, maybe after a chrome update, after other software (extensions or apps) have been installed and removed sometime in the past.  So far, cannot be replicated.

Persists across: remove & reinstall chrome, incognito, guest, alternate profiles, browser reset; canary, beta

Can be found on vanilla Win10, windows defender, windows firewall;
win7, win8.1, mac.

Affects some other google speech2text services (google docs voice typing),
but not others (youtube).

This feels like different malware failures for different users.  The No Internet connection message gives no clue about why the www.google.com:443 mic access port has been blocked. How can we trace this?

If you have a virtual Win10 sandbox to play with, I will dig out refs to pkgs that may cause the problem.

There are a few users we can ask to perform experiments, if they are simple enough.

I've scanned ~50 report threads & ~200 failures.  I have a programming bkgrnd.  Ask a technical question and I can dig out the history.

Use case:
-go to www.google.com, on chrome, get a search box with a microphone
-type in a simple search, like 'weather <your zipcode>'; works fine
-click the mic, 
  if healthy, speak the same search: works fine
  if broken, the 'Speak now' page flashes briefly (~1s), 
  then get the 'No Internet connection page' (see attached)

Deleted: NoINetConn-Airplane.png 16.2 KB

	NoINetConn-Airplane.png 16.2 KB View Download

The critical thing you didn't report is what version of Chrome this occurs with.  For example, knowing it occurs with Chrome 61 would be relevant.

Re: bisect: Since 2013 (bug 24286, speech api quota fix), a few reports monthly, since June 2017 several per week.

2 active cases (Tim, G.E.), both stable m59, Win10, Win8.1 respectively
Tim has a new HP laptop, it's never worked
G.E's worked for years, started failing mid April, 
probably after catching an embedded Chromium PUP 
from Freemake Video Downloader

I think there's also a current Mac case, several more windows users.

I will look for a recent Canary - since this has independent User Data.

close enuf?

Check out my summary here.  Broad strokes of the context.
  https://productforums.google.com/d/msg/chrome/cwERAcdlq6M/_b8U23NNEgAJ

6/19 Wanda: fails in Canary (windows?)
7/9  Joe Sparks: mic ok in hangouts, fails google.com voice search

Source: same chrome help forum as cmt#9: 
https://productforums.google.com/d/msg/chrome/cwERAcdlq6M/XtSiwOHwAwAJ

OK, Canary on 6/19 was Chrome 61.

I don't know how to help further here since I don't work on any of this stuff, but hopefully this gave the bug enough of a shove for some voice devs to do something.

pkasting: Thanks.

Is there anything we can look at in chrome://net-internals or the dev-console to trace the mic access?

here is my chrome net export file, created for capture me hitting the mic button twice, and receiving the "no internet connection" message.

Deleted: chrome-net-export-log.json 397 KB

chrome-net-export-log.json 397 KB View Download

Joe: Thanks.

All: The scenario & instructions for catching the net-export .json log are here: https://productforums.google.com/d/msg/chrome/cwERAcdlq6M/lFO0D1UzCAAJ

fenpeppertree posted this in the forum.

He's currently at 59.0.3071.115, Win10 Home. 

Problem persists since Feb v56, also in canary, after cleanup tool, clear cache and cookies, in incognito

net-export log attached

Deleted: chrome-net-export-log-fenpeppMicNoINetConn.json 257 KB

chrome-net-export-log-fenpeppMicNoINetConn.json 257 KB View Download

Joe: Can you attach a screenshot of the Google search page where you clicked the microphone?  Need to document the log context.

Thanks, Larry

Joe ran his test from the Google.com page
Source: forum link from above

Deleted: net-export-JoeGoogle-com.jpg 130 KB

	net-export-JoeGoogle-com.jpg 130 KB View Download

I am having the same problem It started right after I got a piece of malware called Chromium When I remove the malware that's when it started for me

DarkPeps - Can you join us at the help Forum - I think we've got more affected listeners there than here - and give the details of how Mic-No Internet started for you?  (or here)
https://productforums.google.com/d/msg/chrome/cwERAcdlq6M

a) Was the mic ok until you did the uninstall?
b) Where did you snag the bad Chromium from?  

Chromium is the safe, public, shared core of Chrome, but can be misconfigured and then redistributed.  If we can find a bad version, maybe we can back track to the cause.

There are also reports of uninstalling the bad Chromium, that fixed the problem.

darkpeps: Do you know how you picked up the bad Chromium?

It would really help if I could find a way to trigger this problem on a test machine.  By the time I backtrack on a bad software bundle, it's usually been cleaned up.

Larry, attached is the installer for "MainType" (a font management tool). I am pretty sure this is the one that brought me the bad chromium and I think some other wares I didn't want, but it has been over 2 month since i used it and I'm afraid to launch it again.

Deleted: MainTypeSetup.zip 16.2 MB

MainTypeSetup.zip 16.2 MB Download

I am one of those stricken, rather suddenly, with this problem.  My mic WORKS on other sites, just not Google - both search and Google Translate.  I get the same thing as everyone else.  I click on the mic icon and it is active for about 1/2 a second and then I get the erroneous "No Internet Connection." 

I NEED this to work.  Translations to English that don't use a standard keyboard are IMPOSSIBLE for me at this moment. 

I have both Chromium AND Chrome and it works on neither.  I have installed both - deleting my profile and EVERYTHING and installed Chrome alone then Chromium alone, and neither worked.  I have run every malware/virus scan known to man.  

I tried to use the voice search while logging and attached is my network log. 

Deleted: chrome-net-export-log.json 1.6 MB

chrome-net-export-log.json 1.6 MB View Download

#22 - what do you mean by "WORKS"? Does speech recognition work, or does only the microphone work? The two are only loosely related in that if you cannot use the microphone anywhere, you will probably not be able to use speech recognition, but not the other way around.

Because you mentioned the bad Chromium, I suggest that everyone here look for the Google API key environmental variables. My suspicion is that something (rogue or just naïve) added those environmental variables instead of embedding keys within their Chromium/Chromium based distribution.

In order to clear those variables, at least on Windows 7 -
1. You can press on the Windows key on your keyboard together with R (so WinKey + R)
2. Enter/copy and paste there -
C:\Windows\System32\SystemPropertiesAdvanced.exe
3. Click on "OK".
4. Click on "Environmental Variables...".
5. Look for any of the following anywhere in that window -
GOOGLE_API_KEY
GOOGLE_DEFAULT_CLIENT_ID
GOOGLE_DEFAULT_CLIENT_SECRET
6. Delete only them (but not others! Do not clear the lists!).
7. Restart Chrome (if that does not work, restart Windows).

Phistuck: Thanks for the env suggestion.  I posted this to the forum thread.

There are 2 users at the moment where canary didn't work, but is now working and stable remains broken. I also think it has to do with the speechAPI service failing. 

Is there a difference between how canary and stable use the GOOGLE env vars?

See (my) cmt#4 for the working definition of broken - Click the mic, get 'No internet connection'. 

I see the lack of distinction by users about 'mic works everywhere else'. 
Usually it boils down to speech-to-text works elsewhere just not on google.com search page.

Phistuck: Works as in the microphone WORKS on every other site EXCEPT Google sites.  

Phistuck:  THAT DID IT! I ♥ you! I deleted those as you suggested and VOILA! I'm back in business!  I cannot tell you how thankful I am.  

#24 - I am not sure whether it landed already, but a proposal floated around for ignoring those variables in Google Chrome (but not Chromium). If the canary is fine now, it sounds like the change was made and that it really was the culprit and ignoring those variables fixed it for them.

> Usually it boils down to speech-to-text works elsewhere just not on google.com search page.
Huh, I am not sure there are differences between the google.com implementation and others (as long as they use the speech recognition API and not WebRTC and their custom API). The only difference I have in mind is perhaps the per-site-permission, but I think you already covered that in your proposed solutions.


#25 - yes, the technical definition of "WORKS" differs greatly between normal users and browser developers. :) But...
#26 - as long as it works, I will not bore your with the difference. :)
Sounds like it will soon not be a problem anymore, because Chrome will simply ignore those.

Unfortunately, it means that many people have not-well-behaved (but not necessarily malicious) software installed on their system. :( But I cannot fix the entire world.

Phistuck - thanks again

Re: works elsewhere and speech-to-text page differences.

Other, non-google pages use different speech-to-text internals.
That it works elsewhere just means there's a problem with the Google APIs.

Google speech-to-text is used for different Google apps, and there may be subtle (historic) implementation differences.
Besides voice search (google.com), it's used for 
  google docs voice typing
  google translate
  youtube has been mentioned
  ...

Thanks again.  Posted once more to the forum, hoping for more confirmations.

Phistuck (shop talk)

How'd we get lucky that you just happened to drop in and make a suggestion?

If you have any commit or CL refs for the Canary fix, I'm interested in tracking this.  It might be something that the Cleanup tool team should look into.

Are there other failure modes you can think of that might benefit from this (type of) fix?  I might scan the forum if I knew what to look for.

#29 -
:)
I guess posting this to a Chromium group (albeit the wrong one ;)) was beneficial (and I guess I was intrigued enough to star the issue).

It landed on June 20th, 2017 -
https://chromium.googlesource.com/chromium/src.git/+/156c7095f41e676fbdd780ead1450be6aaff6d53

I think it can break anything that involves a Google API.
Chrome Sync, Cloud Print, signing into Chrome, geolocation, Google based spell checking, translation...
You can find a (perhaps exhaustive) list here -
https://www.chromium.org/developers/how-tos/api-keys

It sounds like the core issue here is a dupe of  bug 710575 .  Kudos to Phistuck for connecting the dots!  This should be fixed in Chrome 61.

I think there is still improvement that can be made to the error reporting for voice search.  If bad API keys cause a problem, then "no internet connection" is not a helpful way of reporting that to the user.  This would have been easier to track down with good error reporting, so morphing the bug to be about that.

phistuck@ - In the forum, fenpepper reports losing the mic display in google.com after deleting the 3 env vars.  
mfh#26 reported its safe and works.

Any ideas why fenpepper lost the mic? Still missing after PC restart.
I'm waiting for him to provide some feedback...

forum:
https://productforums.google.com/forum/#!topic/chrome/cwERAcdlq6M

pkasting@ -  bug 710575  was a good read. This (717419) could be merged there too or marked as a duplicate.

Re: better error reporting: The 'No internet connection' label was very misleading, as it didn't mention the speech context. 
'No internet connection for speech recognition' would have been better, but still left us digging thru the weeds.

If there's a better way than grabbing net-internals to trace problems, let me know.

#31 - I think it is a bit out of scope for the Chromium issue tracker, though, as the error screen is implemented by Google Search, I believe.

#32 - I would make sure they are actually using Google Chrome and not something that looks like Google Chrome.

phistuck@ re: fen mic not displayed: Fen is an L4 user, has posted screenshots, done several reinstalls, logged net-internals, was OK in canary.. 
I'm pretty sure this is Chrome.

I can't tell if the missing mic is in canary or stable.

#34 - according to the last post by fenpeppertree, it sounds like the microphone is missing in both of the versions. It is interesting that Chrome has an update error as well - that suggests that the connection to (some) Google sites is blocked somehow.
(Sorry for not responding to the original thread instead, I am already swamped with many e-mails)

fenpeppertree - mic not displayed at google.com solved by reinstalling chrome, after revo uninstall, and env var cleanup.  Mic voice search now working.
See forum: https://productforums.google.com/forum/#!topic/chrome/cwERAcdlq6M

@pkasting, #31 - Morphing title: From a CM perspective this is problematic. There are links to this thread expecting a 'search mic - no internet connection' title, content and history, in many places.

I would prefer creating a separate follow-on bug with appropriate links.

Whatever the Google/Chromium policy is works for me.

A follow-on to  bug 710575  is probably also the best place for getting a better error msg: change /No internet connection/No speech internet connection/ for the API failure.

@pkasting, #31 - Morphing title: 

Bug 722688 was created for better error handling for translation, primarily text-to-text.  It might be appropriate to integrate voice search with that.

re: fenpeppertree - mic not displayed: For some combination of extensions including 'Awesome New Tab Page' (ANTP), the google.com mic is not displayed. ANTP by itself is not enough to inhibit the mic display.

forum: https://productforums.google.com/d/msg/chrome/cwERAcdlq6M/B_sl6TI9AwAJ

This problem is fixed in version 61, 
 available now in Dev (61.0.3159.5) and soon in Beta; 
or use the env cleanup for the current version 60.

I intentionally did not merge with bug 722688, as it's in a different component owned by different people.  The fixes would be unrelated.