IssueTracker

I had the same issue and resolved this by stopping the listener and prompting the user to to interact with the device when they where ready to begin talking again.

This is a limited fix as this prevents persistent listening waiting for voice interactions. You could continually restart the listener ever few seconds (I picked about 3 seconds for the time out) but on 4.1 on the Nexus 7 this causes a loud beep noise indicating the service is ready so it would likely drive a user nuts if you implemented it like this.

Given the uncontrollable beep noise and the lack of response to any of the recent SpeechRecognizer issues, I feel like this may have been intentional changes and they have no updated the documentation yet to tell us. Fingers crossed it was unintentional.

[Comment deleted]

I don't think it is intentional because the SpeechRecognizer is still listening as indicated by the calls to onRmsChanged and when you call stopListening it does call onResults with what was said even if it's been a minute or more.

If we can get access to the offline recognition in 4.1 that will take a huge load off the Google servers. :^D

I came across the same problem like you. But I have tried it on my nexus 7 with Android 4.2.1 and the problem still seems to be unsolved.

please fix this bug asap.

I am incredibly disappointed to see that this bug remains unresolved in 4.2.2, even with the offline recognition.

This bug seriously impacts all developers of Voice-driven applications, and appears to have been introduced in Jellybean 4.1.  All 2.3.X and 4.0.X devices appear to function correctly.  That's quite unfortunate given the rapidly shrinking importance of all OS versions lower than 4.1.

There's a tremendous potential for this feature in games and tools development, but this bug destroys it.  Can we get some response on this?

Same problem im my applications. Please do something.

There's any solution for this bug?

Re-pressing the microphone icon each time it stops working brings it back to life on my Samsung galaxy 2 on Boost Mobile.

I also get this issue, but when i restart device its works fine for a sometime but then after same error occured, is that any workaround for this bug ?

This is a show-stopper for our app, as it relies on continuous recognition. It'd be nice to get some feedback on what is clearly a crippling bug.

I have tried it on my nexus 7 with Android 4.3. The bug remains unresolved. Waiting for Android 5.0?

Definitely an important issue to resolve. Odd how it was working before and has been lingering for so long.

Please see related links below. It would be great if you could comment in the Google Product Forum post to confirm the issues and also star/contribute to the enhancement request. We really need to give Google a kick up the backside on these issues.

It's so frustrating that this is still not fixed.

https://code.google.com/p/android/issues/detail?id=59145

https://productforums.google.com/d/msg/mobile/PZMX9vmPPhQ/VVV14VmN4REJ

Ridiculous bug. How it even possible to make mistakes like this one. Do you need beta testers, Google?

it is evident google forbids any voice recognition to thrive...!

are there any news regard the bug relented of voice recognition very short listening time or ERROR_RECOGNIZER_BUSY all the time?    

Same problem here. After more than 1 year this bug was not closed?!? Shame.

I've encountered it on my Acer Iconia tablet running 4.1.2.

However, everything is fine on my Nexus 4 running 4.2.2 - RecognitionListener.onError() is called as expected after 5 seconds with error 6 - ERROR_SPEECH_TIMEOUT. Very odd considering above reports of it persisting.

One more data point - on 4.1.2, I'm seeing onError() finally called AFTER TEN MINUTES, with code 4

[Comment deleted]

have the bug been fixed in android 5.0.1 ?

Hey All, We are still facing the same issue. Is it fixed now.

No, and since Google marked the ticket obsolete, it's likely that they never will fix this.

Amazing...

here is an another struggling developer for the same bug, help us Google we have faith in you.

please help about this issue

This bug is so annoying

I feel very hopeless about this. Please fix this issue.