I don't recall whether this has ever worked (can't remember whether I tried it prior to a couple of weeks ago), but I have a Nexus 5 paired to my EX model. Unpaired, I can either say "OK Google" followed by a command such as "what's the weather like?" or "navigate to Six Flags", and it does this.

However, once I start the car and the bluetooth pairing becomes active, I can either say "OK Google" or press the microphone button, either of which brings up the voice command screen, but then it does nothing. As I speak, it isn't hearing anything I say -- the red microphone doesn't show the pulsating rings as speech is being heard, as it would while unpaired. Eventually it times out, having received no command.

Has anyone else gotten the Google Now voice input to work while the phone is paired to your car? Does this just not work, or do I have some setting wrong? I've tried removing the pairing from both devices and re-establishing.

 

I heard Androids don't work yet. Honda said, it will later on end of this year

 

Thank you for that -- though this depends on what is being looked for. by "Android doesn't work yet", that is true of the HondaLink app set which offers really tight integration with the car and the ability to use the phone on the large in-dash screen for navigation. Currently those additional features and navigation are implemented on iOS but not on Android.

Quite a bit does work, though -- BlueTooth audio connectivity is pretty good. I can play any phone audio via the car, get track info on the screen, control it to some extent through the car (not as completely as if HondaLink were available), take and make phone calls, etc.

The particular problem I was having was with Google Now, the voice search/assistant feature, which had oddly disabled the voice input while Bluetooth was connected.

An update: By backing up my data, wiping the phone, and restoring, this now works perfectly. Something had apparently gotten out of whack on the phone and resetting corrected it. Whether something had gotten corrupted or some setting had gotten flipped wrong, this was the fix.

 

Could you be more specific about what "this" is that now works perfectly? Thanks!

 

Yes -- it was the problem I described in the original post. To repleat that, voice commands weren't being heard by the phone when Google Now was activated (either by saying "OK Google" or pressing the microphone button on the phone).

 

Did you make sure in the Google Now settings under "Voice" that you have Bluetooth settings checked? Just wondering [I don't have a Fit just yet]

 

To be honest, I have since forgotten all of what I did and did not try in order to get this working. I spent a lot of time going through settings on the phone and *probably* did ensure that this setting was checked, but I cannot be certain that I didn't fail to check this. In the end, whatever had gone wrong was fixed by factory reset. Not that this is a big deal to do for me -- I'm rooted and it takes little time to restore everything using Titanium Backup.

I'd guess that since I restored every single app + data, that either something in the OS had gotten corrupted or I missed a crucial setting. App interference can be ruled out. If I think about it I might try to disable that setting and see if it reproduces the undesired behavior.

The good news is, though, that a whole lot of things do work decently with the car even without the tighter integration we will get from the new generation of HondaLink app which is due out eventually. I still wish to be able to use the big screen to display and interact with my phone's navigation while driving, but oh well.