• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Initializing... Voice input

D

Dignan17

Well-Known Member
I have a Galaxy Nexus running Jelly Bean (flashed Verizon version).

I'm absolutely loving the experience Jelly Bean offers, and Google Now plus the expanded voice capabilities are incredible.

I've been having one problem with the voice input, though. It seems that I regularly get "Initializing..." when I try to use it! It'll just sit there and say "Initializing..." and not budge. Even more frustrating, if I hit the back button to get out of it, just as the app is exiting, it'll come out of its funk and tell me to say something, but the app immediately exits.

So far it seems like this only happens when I'm connected to any device via bluetooth. If I disable bluetooth or am not near any of my devices, there's absolutely no problem.

Is this a known bug? Is there anything I can do about it other than constantly turning my bluetooth off and on?

Thanks!
 
I also have this problem, and I can verify that it does have something to do with bluetooth. When connected to my jvc car stereo, it freezes on initializing.
 
I'm sorry you're having this problem too, but I'm glad I'm not crazy or something!

When it happens, it just doesn't work, and that's frustrating. But the worst part is that when this happens, the second I hit the "back" button, it'll all of a sudden start working...for about .25 seconds before the app exits. That part is insanely frustrating!

I wonder what the problem is...
 
I get that problem occasionally too and I can concur that it has something to do with Bluetooth. What I DONT get is that it goes to turn on the mic and start listening yet when it does (and doesn't get stuck) it uses the PHONE'S mic instead of the BT headset!! WTF?
 
The issue seems to be specifically related to the Bluetooth Media Audio sync. When I connect my Gnex to my Jawbone, I have a 'Phone audio' and a 'Media audio' option. When 'Media audio' is unchecked, the "initializing" problem goes away. Vice-versa when rechecking the 'Media audio' option, the issue comes back. This happens with Stock JB 4.1.1 and CM10 JB 4.1.1.

So if you pair with a phone device and not media device, you are golden. Unfortunately, I like (and miss) have media routed to my jawbone. The flip side is showing off voice capabilities of Jelly Bean;)

I think an upcoming release of Gapps will correct the issue. I only see "gapps-jb-20120726-signed.zip" on the goo.im/gapps website:/
 
I think you're probably right about this. Sadly, I simply can't forgo the BT Music profile, since I use it every single day in the car. Naturally, the car is also a great place for voice commands, so that stinks that I can't use them.
 
I'm having this problem as well except I have the problem with media audio UNCHECKED. And it's exactly like has been explained above - once you hit the back button, it comes out of the initializing a split second before exiting. If I open up Voice Input again, a lot of times it will work. Sometimes it takes 3 or 4 times of opening though. Very frustrating.
 
Ok, the problem is with Bluetooth Audio, not just Bluetooth, it's with Bluetooth AUDIO! I have a Jawbone Era, it obviously has Bluetooth for phone calls, but I also listen to music on it. I have the option to disconnect the Bluetooth Audio. I tested this many different ways, when I have no Bluetooth, it works perfect. Never says "initializing", ever. When I have my bluetooth connected with voice and audio, it with either flash initializing for a moment and then worked, or just does not work at all. I then disconnected the audio portion of my Jawbone and just left voice calling and again Google Voice Search worked perfectly never flashing initializing. The problem 100% lies with Bluetooth Audio. Very disappointing for sure, I listen to music at work all day through my Jawbone. This takes away from my Jelly Bean experience!! Please fix Google!!!
 
You must log in or register to reply here.
Back
Top Bottom