Android Auto first impressions thread (and ask us anything!)

I have a Google Play Music question: How is the browsing? Are you able to reach your library easily through menus, rather than voice?

Does anyone here also own an iPod? (is that blasphemy here?) Are you able to play this on your Pioneers while also using Google Maps?
 
I have a Google Play Music question: How is the browsing? Are you able to reach your library easily through menus, rather than voice?

So far, not great. No album/artist lists or anything. So start making playlists. Or search, I guess. Explore is there, though.

Does anyone here also own an iPod? (is that blasphemy here?) Are you able to play this on your Pioneers while also using Google Maps?

Hmmmmmm. Don't think that'll work because it's using a separate input, just like you can't do BT/CD simultaneously, ya know?
 
Do you absolutely have to plug in your phone to get it to function? Like maps, Google music, and pocket cast?
 
Does Maps still show you alternative routes on the main map while navigating with the time differential displayed on the map?
 
Hi guys,
Is there a setting either in the avh -4100nex itself or the tune in radio app that sets location?
My app thinks I'm about 1500 miles away from where I am while searching for local stations. (tunein works fine while not on android auto)
 
I have a Google Play Music question: How is the browsing? Are you able to reach your library easily through menus, rather than voice?

Does anyone here also own an iPod? (is that blasphemy here?) Are you able to play this on your Pioneers while also using Google Maps?


Like Phil said, the browsing is pretty minimal. You get the basics, like Listen, Playlists, Radio (if you're an All Access subscriber) or Instant Mix (if you're not a subscriber). The idea is that they don't want you doing too much browsing/scrolling/reading. You can use voice to access anything in your library (or All Access). For example, I asked it to "Play Thriller" and it started playing Michael Jackson's Thriller album (the entire album, not just the single track). If a song is also the title of an album, then it defaults to playing the album (if you have it, or if you have All Access).

As for the iPod, assuming you're not talking about Apple's Car Play, you can hook it up to USB 1 and treat it like any media source. Any music source will run simultaneously with Google Maps. You can switch back and forth with the unit's "Mode" button or use the Home button to go to the main screen and select your AV source from there.

Functions that seem to work simultaneously are Navigation, any AV sound source (one at a time), and system alerts (speeding, speed cameras, etc.). Any navigation or system alert lowers the volume (or mutes, depending on setting) any music you're playing. Phone calls mute all other sounds except navigation/alerts. So no music playing while on the phone.
 
Does Maps still show you alternative routes on the main map while navigating with the time differential displayed on the map?

Yes, just like Google Maps on your phone. Only difference is that you get bigger buttons and quick menus for things like alternate routes, POIs, etc.

On my system, Google Maps is behaving much better, due to it using the head unit's GPS antenna (which is a lot stronger than my phone's antenna). No more "dancing around" or "flipping around while at a standstill in traffic".

My system also has built-in GPS/Nav, so I have that as a fallback. It uses Here Maps. Not a bad system at all. It even has some traffic and road conditions info (which is picks up from the HD radio stations). It's a nice option for times when you can't get a data signal.

As for Google Maps, it also adjusts the color scheme based on whether you have your headlights on or not (as opposed to time of day or ambient light detection) on my phone.
 
So I have a couple of questions.

How is the quality of the voice input, especially compared to BT? To test this, you can first connect your phone through BT like you normally would any radio (make sure the "bluetooth headset" option is enabled in the Voice settings of Google Now). Then, make some commands. Then disconnect from BT, connect to Android Auto and make commands. Then compare the quality of the voice recordings in the account history. (If it's not too much to ask :)) Also, please state if you have a N4/5 or N6. N6 is the only Nexus that supports HFP 1.6 with wideband audio. IME even wideband BT is way worse than the inbuilt mic or a wired headset (though likely not noticeable in phone calls).

The second question is a follow-up from last page, how are the night colors? Is the background bluish like the pictures posted in the previous page? Are surrounding traffic and streets easily visible, or are they obscured by the dark gray, like they are currently in the phone app?

Thanks a lot guys.
 
Oh no. It's the perfect day in Minnesota for a little impulse buy and I have just enough time today to pull this off.

Any recommendations for an aftermarket remote starter that can be installed at the same time that has a great Android integration?

Thanks!
 
Oh no. It's the perfect day in Minnesota for a little impulse buy and I have just enough time today to pull this off.

Any recommendations for an aftermarket remote starter that can be installed at the same time that has a great Android integration?

Thanks!

Viper works pretty well on Android. the app is ugly now but has a refresh coming with android wear support!
 
So I have a couple of questions.

How is the quality of the voice input, especially compared to BT? To test this, you can first connect your phone through BT like you normally would any radio (make sure the "bluetooth headset" option is enabled in the Voice settings of Google Now). Then, make some commands. Then disconnect from BT, connect to Android Auto and make commands. Then compare the quality of the voice recordings in the account history. (If it's not too much to ask :)) Also, please state if you have a N4/5 or N6. N6 is the only Nexus that supports HFP 1.6 with wideband audio. IME even wideband BT is way worse than the inbuilt mic or a wired headset (though likely not noticeable in phone calls).

The second question is a follow-up from last page, how are the night colors? Is the background bluish like the pictures posted in the previous page? Are surrounding traffic and streets easily visible, or are they obscured by the dark gray, like they are currently in the phone app?

Thanks a lot guys.

The bluetooth comparison is unnecessary and impossible to do because Android Auto uses Bluetooth for phone calls (despite the fact that the phone is connected via USB). So the quality of your phone call is still going to be within the limits of Bluetooth (and of course your overall cellular signal). With that said, the quality on my system is outstanding.

As for the nighttime colors in Google Maps, it uses the dark blue background. Streets and objects are very visible. It's a marked improvement over the dark gray. I really have no complaints with the overall experience with Google Maps on Android Auto. It certainly behaves every bit as good (and often better) than my phone did on its own.
 
Thus far, if I had to voice a complaint about Android Auto, it would be the same complaint I have about Android Wear: No true support for Google Voice numbers when doing SMS texting. No matter what you do, you can't initiate a text or reply to one with your Google Voice phone number. It insists on using your phone's carrier-assigned number (which I don't ever use for any of my communication). Phone calls go out through my Google Voice number just fine; but not texts.

I haven't tested Hangouts instant messages yet. I suspect those should work fine (as they do with Android Wear). Of course, with Android Wear, you still can't initiate a Hangouts instant message (you can only reply to one). As I said, I have yet to test this on Android Auto, but I suspect it's the same situation.

I've provided feedback to Google (through the Feedback option in the Android Auto app), requesting real support for Google Voice phone numbers; but who knows if they will ever listen and do something about it. As it stands, replying to texts with Android Auto is not a good solution for me (a Google Voice user).

On another note, pertaining to these Pioneer head units, I have noticed that while they have the ability to pair to more than one phone at a time, they cannot dynamically switch between them for Bluetooth calls. In other words, if I hook up my personal phone to Android Auto (which still uses Bluetooth for calls), and also pair my work mobile to the head unit, if a call comes in on my work phone, I still can't answer it via Bluetooth. I have to choose which phone is the "active" Bluetooth device on the head unit. Only one can be "active" (i.e. able to make/receive calls). I literally have to go into a menu and choose which phone I want to use for calls during my drive. So if you use two phones, forget about using both of them on the Pioneer units.

My Jabra Freeway Bluetooth car speaker can maintain two phones and will allow both of them to make/receive calls, on the fly. Once both phones are paired, I don't have to select anything or make any changes to settings on the unit. So, it looks like I'm going to keep my Jabra Freeway on its visor and use it for my work mobile, while I keep my personal phone attached to my head unit for Android Auto. That way, I can still keep both phones hands-free. That's a shame, considering the price of these head units.

P.S. Checking voicemail with Android Auto's "Voicemail" option in the dialer is also a no-go for Google Voice users. It dials your carrier number (which doesn't contain your Google Voice voicemails), so it's worthless.
 
Last edited:
Like Phil said, the browsing is pretty minimal. You get the basics, like Listen, Playlists, Radio (if you're an All Access subscriber) or Instant Mix (if you're not a subscriber). The idea is that they don't want you doing too much browsing/scrolling/reading. You can use voice to access anything in your library (or All Access). For example, I asked it to "Play Thriller" and it started playing Michael Jackson's Thriller album (the entire album, not just the single track). If a song is also the title of an album, then it defaults to playing the album (if you have it, or if you have All Access).

As for the iPod, assuming you're not talking about Apple's Car Play, you can hook it up to USB 1 and treat it like any media source. Any music source will run simultaneously with Google Maps. You can switch back and forth with the unit's "Mode" button or use the Home button to go to the main screen and select your AV source from there.

Functions that seem to work simultaneously are Navigation, any AV sound source (one at a time), and system alerts (speeding, speed cameras, etc.). Any navigation or system alert lowers the volume (or mutes, depending on setting) any music you're playing. Phone calls mute all other sounds except navigation/alerts. So no music playing while on the phone.

Great. And yes, I meant a non-CarPlay iPod Classic.
Hoping that with it being run from an app, the Google Play Music functionality expands over time. But good news. If Kenwood's HUs don't do the trick, I may consider hopping on to an 8100NEX (for the added comfort of "offline" nav).
 
So, at this point in time, was it worth the cost to upgrade your head unit, or is it still a bit of a novelty/cool tech toy for people who need to be on the cutting edge, but may deal with a lot of bugs or weak app support? I'm guessing that as more of these hit the market and they have a bit of time to settle in, they will become a better value (both in terms of lower prices, even slightly, and better development/app support)
 
Anyone else having issues with Google voice command on Android Auto app? I'm using a Verizon Galaxy S5 w/ Lollipop 5.0. Android Auto loads on the Pioneer deck and the microphone comes up, however nothing happens on the deck with you press the mic icon. Buddy of mine has an HTC on Sprint and and voice command works fine.
 
So, at this point in time, was it worth the cost to upgrade your head unit, or is it still a bit of a novelty/cool tech toy for people who need to be on the cutting edge (buggy, very much a 1.0, etc.?). I'm guessing that as more of these hit the market and they have a bit of time to settle in, they will become a better value (both in terms of lower prices, even slightly, and better development/app support)

For me, it was certainly worth the upgrade. I was replacing a 10-year old non-touchscreen outdated nav head unit that was having problems (display would blank out whenever it felt like it). Back then, it was state of the art, but now it is just an embarrassment. With the iDataLink module, I've retained my steering wheel controls, and with the system's integration into my OBDII, I don't miss much from the old system. I'm just scratching the surface on the unit's capabilities. As I learn more, I'm pleasantly surprised with some things, and annoyed with others (mostly with lack of proper Google Voice number support, since that's the only number I use).

There will always be some early-adopter pain (both technical and financial), but I've found that it's worth it (to me). Overall, I'm pleased.
 
Anyone else having issues with Google voice command on Android Auto app? I'm using a Verizon Galaxy S5 w/ Lollipop 5.0. Android Auto loads on the Pioneer deck and the microphone comes up, however nothing happens on the deck with you press the mic icon. Buddy of mine has an HTC on Sprint and and voice command works fine.

Do you mean that the screen is non-responsive when you press the microphone icon (like it's grayed-out)? I'm going to ask a silly question: Do you have the external microphone wired properly?
 
Do you mean that the screen is non-responsive when you press the microphone icon (like it's grayed-out)? I'm going to ask a silly question: Do you have the external microphone wired properly?
Or did you use the mic that was included with the unit?
I made the mistake of plugging in the mic from my previous jvc head unit since it was already wired under the console. Nothing worked correctly until I took everything apart and installed the correct one.