Today I used Google Maps on my 2018 Acura MDX with Android Auto support. While using turn by turn directions with audio notifications enabled and listening to the vehicle's FM radio or Sirius XM, I noticed the vehicle switch audio input back to Android Auto after turn by turn directions were spoken. If the directions were short such as "turn left" the unit would resume the audio source that was in use. If the direction instructions were a bit longer the audio source switched to Android Auto. I was forced to manually switch back to the previous source. Pretty annoying. This happened consistently during my drive.
Anyone come across this issue?
Related
I installed a new head unit in my 2006 Toyota Avalon a JVC KWV230BT. The phone is a Nexus 6 running PureNexus 7.1.2-20170509-OFFICIAL. The problem happens with both Google Maps and Waze. When connected via Bluetooth to the head unit the voice from the map application has the first syllable of the first word cut off. This problem also happen using a stock Samsung S7. However the phone via bluetooth work fine no issues. I have done some searching and many folks report this issue however have yet to fine a good fix. I did try a couple of apps the let you redirect the audio to a different profile did not seem to help.
Thanks
Joe
Here is a much better explaination:
Background: A bluetooth device must detect a preset amount of A2DP audio stream to trigger open a gate allowing the stream to actually play through the device. For users, this means roughly 1 to 2 seconds of audio can be lost at the beginning of a stream. The gate closes a short period of time after the audio stream terminates. Audio content is lost each time the gate must be triggered open. According to Apple, the trigger threshold is controlled by the bluetooth device manufacturer.
The trigger delay can be a significant problem for navigation apps with text-to-speech (TTS) enabled.
An instruction spoken via the iP4's built-in speaker has no delay and sounds like, "In one mile at the T junction turn right onto First Street."
But the same instruction over bluetooth loses words and becomes, "…tion turn right on First Street."
If something holds the gate open -- for example streaming background audio by iPod or Pandora -- then when a navigation app interrupts with a TTS instruction none of it is lost.
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!
In Android Auto, When I'm listening some music from my phone and having G. Maps on the screen, there's always some lags in music when the map's moving (like in an higwith exit road)
I have a rooted Pixel 3 and a Mazda 3 2018 (Android Auto from MZD AIO)
I've seen in developper's options many options about bluetooth, what should be the best parameters?
Thanks!
I see the same thing when using my Chinese dongle on my android head unit. I've played around with developer settings in Android auto and the settings on the dongle and nothing seemed to help. It seems to be something low level in the dongle (in your case the head unit or mod app) that causes this where moving the map seems to overwhelm to the system.
Using the same headunit and phone but instead using Emils' head unit reloaded application I do not get any sound issues, even when running in 720p mode.
It seems like the issue we're seeing is more to do with the Android auto implementation in hardware/software.
Ok, I'll try it and see how it's going. Thanks
I finally managed to get Bixby Routines reinstalled on my phone (it was in the Galaxy store and I somehow either missed it every single time I looked, or they just added it). I am using it to send Spotify to my various bluetooth devices while all my notifications play on the phone. I have it set up with 3 devices - an Anker Soundcore, a pair of SkullCandy Ink'd Wireless earbuds, and my 2015 VW Golf. I'm running into some weird issues, though. Note that all 3 routines are set up the same way - IF BT is connected to X, THEN App: Spotify / Audio Device: Bluetooth
1. Whenever Separate App Sound is initiated, either on the previously connected device or a different device, it throws up the "Change main audio output device?" notification, meaning every time I connect to BT, I have to do that. If that's the case, why bother with the routine and not just toggle the SAS with each device manually since I need to interact anyway? When I do toggle it manually and hit OK on the notification, it works flawlessly, sending Spotify to BT and everything else (IG, Messages, YouTube, etc.) through the phone's speakers.
2. With the way the Golf head unit connects to BT, it kind of connects, then disconnects, then connects again, making the phone get weird mixed messages which triggers the routine in a weird way. Is there a way to delay the BT connection on the phone until the head unit is fully booted up?
The only thing I can figure is that maybe I'm not technically following the "make sure you choose an audio device that is different from your main audio output device." rule since when I'm connected to BT, that's the main audio output.
This one is really annoying me - with my new Dacia Jogger, I've found that Android Auto always thinks I'm driving, even when parked, with the engine off. The problem with this is some navigation apps completely disable the ability to search for a destination, so I can't progam in a route once I'm connected! Also Gameshack is disabled because AA thinks I'm driving too.
There any way to fix this or stop AA from disabling interactions?
Your headunit has a wire connected to the handbrake sensor in your car, and this way it knows if you're parked and can't restrict some activities. This information is passed from the headunit's firmware to Android Auto internally, and this way Android Auto can restrict or allow you to do some stuff like use the touchpad, use certain buttons, etc.
In order to save money (or due to a bad Android Auto implementation), some headunits don't send handbrake status information to Android Auto. This way you can use the onscreen voice button all the time (in the lower corner of Android Auto) even if the car is moving, but the downside is that some Android Features get broken, like Gamesnacks or alphabetic search in lists. They can do this for a number of reasons, like not having a dedicated voice button in the steering wheel or headunit, but it's not the ideal case.
I suggest you to find other people with the same car model and see if their cars behave in the same way. If so, then this is a headunit problem and the carmaker should release a fix. If this only happens in your car, I would check if there's a wiring issue in the handbrake or something similar is happening.
you might also want to check if there's some settings menu in your headunit with some option to check this.
You can also try to sync a new phone over bluetooth to your car headunit while parked. If it refuses because the car is moving (even if is not) then it could be a wiring issue.