+++ This bug was initially created as a clone of Bug #874572 +++ Currently, one can not use the device system microphone despite the browser activity being sent to the background and paused. Attempts to launch the device microphone yield a runtime exception: I/decoder (23207): ERROR: Exception thrown from GoogleRecognizer.read() W/System.err(23207): java.io.IOException: couldn't start recording, state is:1 W/System.err(23207): at com.google.android.speech.audio.MicrophoneInputStream.ensureStartedLocked(MicrophoneInputStream.java:119) W/System.err(23207): at com.google.android.speech.audio.MicrophoneInputStream.read(MicrophoneInputStream.java:159) W/System.err(23207): at com.google.common.io.ByteStreams.read(ByteStreams.java:806) W/System.err(23207): at com.google.android.speech.audio.Tee.readFromDelegate(Tee.java:374) W/System.err(23207): at com.google.android.speech.audio.Tee.readLeader(Tee.java:267) W/System.err(23207): at com.google.android.speech.audio.Tee$TeeLeaderInputStream.read(Tee.java:464) W/System.err(23207): at java.io.InputStream.read(InputStream.java:163) W/System.err(23207): at com.google.android.speech.audio.AudioSource$CaptureThread.run(AudioSource.java:198) i) http://mozilla.github.io/webrtc-landing/gum_test.html ii) Tap 'Audio' iii) Hit the device home-button iv) Launch Google Now, use the microphone in the search bar or on your home-screen in the search widget We can not prohibit users from using core system applications on their devices. The browser should release the lock on the microphone media when the browser is paused. -- HTC One (Android 4.1, Nightly 05/21) LG Nexus 4 (Android 4.2.2, Nightly 05/21)

Not a blocker for pref on.

This is how we spec'd it (camera off, mic on in the background). The behavior was certainly subject to debate about what the right thing to do is. This behavior is at least consistent with google hangouts, so hopefully will match user expectations.

(In reply to Brad Lassey [:blassey] from comment #2) > This is how we spec'd it (camera off, mic on in the background). The > behavior was certainly subject to debate about what the right thing to do > is. This behavior is at least consistent with google hangouts, so hopefully > will match user expectations. Talked with Randell about this. This sounds okay given that other Android apps do the same. We do think though that if we get a lot of user complaints about this that we should re-evaluate this. But for now, this is okay to be a WONTFIX.

Can we verify that Google Hangouts does this? Initiate a video hangout, hit the home button, attempt to conduct a Google Now search through the microphone.

(In reply to Aaron Train [:aaronmt] from comment #4) > Can we verify that Google Hangouts does this? Initiate a video hangout, hit > the home button, attempt to conduct a Google Now search through the > microphone. That's probably worthwhile to check. Can you check that?

Yes. This seems to be the way Google does it too. I couldn't use Google Now microphone search (same error in logcat) 'Microphone unavailable, retry?' until I ended the Google Hangout.