So I installed the 4100nex and mapped the audio controls to my 2005 Altima SE-R steering wheel controls but It doesn't have a microphone button. So every time I want to search for something I have to touch the mic button on the head unit while using android auto. I DON'T want to have to do this and was wondering why OK Google won't work even after setting my M8 to always listen for the commands? Does android auto app automatically turn off that function when connected to the HU? I am sure other folks with cars without microphone buttons and android auto head units have similar issues?
Thanks!
search the mtc keys thread and you'll will find your answer
If this is the answer than I am assuming the OK Google always listening isn't supported within Android auto.
it's not, but if you used an imaestro datalink for the steering wheel you can reprogram it and set a button for the mic
mburke178 said:
it's not, but if you used an imaestro datalink for the steering wheel you can reprogram it and set a button for the mic
Click to expand...
Click to collapse
Nope it's a pac audio swi-rc. I thought Android auto was supposed to be true hands free but but I guess not if have to push a button to activate it. A little dissapponting. I've contacted google and asked about it. Well see what they say. Maybe an app update could add it.
Related
I have a 2013 Chevy Spark with bluetooth. It has the voice control activation button on the steering wheel. When I had my Galaxy Note, this would activate S-Talk and I could use voice controls through the car. When I try with the One, an app pops up and quickly closes on the phone, then the radio says voice control isn't supported, but half the time if I start talking, the voice control works anyways. Does anyone know if there is a way to fix this? I am on ARHD, but I had the same issue when I was still completely stock with a locked bootloader. This could be a deal breaker because I do a ton of driving and use voice control a ton.
I am unable to use any of my wired headsets with the Nexus 6. The middle button launches Google Now during a call. On the Nexus 5, the same headsets toggled Mute with that button. I have tried apps to reprogram the button (like Headset Button Controller) but they can not override the Google Now function.
Is anyone else seeing this? Any ideas?
Same problem here! Can't find a way to reassign the button to media control or something else. It always starts Google Voice Search.
If pressed when phone is locked I get a message telling me I have to unlock the phone to use Google Voice Search!
Headset Button ControllerTrial did not work!
play.google.com/store/apps/details?id=com.kober.headset
Does turning of Bluetooth headset in Settings, Search & Now, Voice do anything to correct this problem?
stevemw said:
Does turning of Bluetooth headset in Settings, Search & Now, Voice do anything to correct this problem?
Click to expand...
Click to collapse
It's off as default. Benn off the whole time.
Bought SUPRA NiTRO earbuds, problem solved.
I get this odd tapping/knocking sound when Ok, Google is listening for a command. It does NOT go away after I send a text via voice until I tap the mic icon again and tell it something like stop or **** off. It then says ok or whatever and the knocking noise that pulses with the mic listening .. will actually go away. It started after I updated Google App. I'm on the beta testers list.
I removed the Google App a cache and retrained the voice recognition again ... to no avail.
I'm using a Nexus 6P. It's got stock Android but is rooted with systemless root. Phone works fine except when attached to AA.
Beta testers list for what ?
I think "OK Google" on the phone is not intended to be compatible with AA.
When in AA you are expected to tap the headunit mic icon, or use the steering wheel control for mic to send a voice command through AA.
If "OK Google" works at all while in AA mode, that's more accidental than intentional.
mikereidis said:
Beta testers list for what ?
I think "OK Google" on the phone is not intended to be compatible with AA.
When in AA you are expected to tap the headunit mic icon, or use the steering wheel control for mic to send a voice command through AA.
If "OK Google" works at all while in AA mode, that's more accidental than intentional.
Click to expand...
Click to collapse
oops. Sorry. I meant tapping the icon and saying "Text <person>" .. the mic pulsates and makes this tapping or knocking sound. It was getting stuck. It like OK, Google seem to require a decent network connection to even function properly. I went back outside after I made this post and it worked fine. It still made the little annoying sound but didn't get stuck. I was driving down Highway 280 here in Northern California which runs between 2 mountain ranges and has always kicked me down to 3G/H from LTE. I think this was it but I'm not sure since the voice search is pulled from the phone through AA and it's done by Google App. And like I said .. I use the current beta so I thought maybe it was releated to the update for Google App from yesterday. I simply don't know. It was just irritating and I was hoping it wasn't just "oh .. you have a **** network connection in places so it's going to work kinda janky sometimes."
Thanks!!
Hi guys
I have been using Android Auto for a couple of months now and I noticed that Android Auto has problems to understand what I am saying while driving. I don't have this problem when I use voice commands with the standard navigation on my headunit so I started wondering: does Android Auto use the microphone of the headunit? Or is it only using the built-in microphone of my phone?
That would at least explain why Android Auto has so much difficulties to understand what I'm saying while driving. If AA uses the microphone of my phone, is there any way to force AA to use the microphone of my headunit?
I'm not right sure on this. I use a Pioneer head unit with AA and if using Google maps it seems to understand fine but when I use voice commands to play an artist or playlist in Google music then the 'assistant' behaves like a complete idiot. I suspect it uses the head unit mike as mine is just behind the steering column where the phone is tucked away in front of gearstick.
Hello, I'm using Android Auto 3.1.581054 on my Honor 8 smartphone, and the Sync3 v3.0 multimedia system on a Ford Fiesta mk8.
If I don't use AA, i can push the voice activation button on the steering wheel, and dictate commands to access some of the car's functions (for example, change FM radio station).
When i connect my smartphone via USB and enable AA (e.g., to use google maps on the car's screen), the google assistant overtakes the steering wheel voice activation button; I can therefore only use it to dictate Android functions on the phone (maps directions, send whatsapp message, etc). I can't control via voice the car's functions anymore, at least until I disconnect the USB cable, because obviously Android knows and can nothing about the car's FM radio or whatever.
This is a very unfortunate behaviour, because to change the FM radio channel I now have to fiddle with the car's touch screen controls, that is very distracting while driving.
Is there a way to manage this problem? I heard that, on some previous versions (of what? AA? Sync3?), pushing the steering wheel voice activation button once triggered the car's Sync3 recognition, while pushing it for 3 seconds would trigger the google assistant recognition. Is it true? What happened to this function? E.g., see https://productforums.google.com/forum/#!topic/android-auto/SNCguGKYiZE
Doesn't answer your direct question, but I'm also using a Mk8 Fiesta, and wanted to point out that if you're already on one of Radio audio sources you can use the steering wheel next and previous track buttons to switch between stations within the preset group you're in. I've only tried this on DAB but it probably works on FM as well.
I've also found that sometimes it's possible to select whichever source and station you would like from a list using the steering wheel menu button (provided you're looking at the audio screen on the instrument cluster - not sure if all the trims have this functionality?). This works all the time without Android Auto connected, and sometimes when you're within Android Auto, but not always. I think this might be to do with starting up a radio source before connecting the phone, and making sure not to start any audio playing within Android Auto. Haven't had chance to properly test this yet.
Let me know if you discover any tricks!