[Phil Nickinson]

So ... Day 1, on build NDE63P. Connected to a Pioneer AVH-4100NEX (on the Dec. 16, 2015 1.053 update firmware).

I first connected with the same cable I've been using with the Nexus 6P. Worked for a minute or so, then froze. Tried the cable that came with the Pixel. Even worse — resolution issues. (That thing where things are just all jacked up on the display, like they don't fit.

Oh, the joys of being an early adopter.

[Andrew DeFaria]

Disheartening... Why does this keep happening? It's not that difficult of a thing is it? I mean you're just drawing on a screen and sending back touch coordinates right?

[Phil Nickinson]

The head units can be touchy when it comes to cables. Which is ridiculous, I know.

[OliverK]

No issues at all with the built in AA on my VW Golf R. Pixel XL works perfectly.

[Andrew DeFaria]

Exactly, it's ridiculous. And it's not the cables. If you have a cable that works, and I do, it should always work - unless it breaks, in which case it should never work again.

[jstew182]

So ... Day 1, on build NDE63P. Connected to a Pioneer AVH-4100NEX (on the Dec. 16, 2015 1.053 update firmware).

I first connected with the same cable I've been using with the Nexus 6P. Worked for a minute or so, then froze. Tried the cable that came with the Pixel. Even worse — resolution issues. (That thing where things are just all jacked up on the display, like they don't fit.

Oh, the joys of being an early adopter.

Yeah this is an absolute shame. I have the 4100nex as well and tried connecting my pixel xl to it today. I can't seem to get it working at all. It launches on my phone but the head unit either just stays on a black screen or has the disclaimer screen pop up (and usually shifted off the screen) but the couple times it popped up correctly the touch screen on the head unit won't respond. I plug my Nexus 6p (on beta 7.1.1) into the same cable, works without issue...I think I'm finally at my breaking point of being a beta tester for new hardware when they charge nearly twice as much for a broken experience from my Nexus 6p...for some reason I have always been pretty understanding of issues with Nexus but paying nearly $1000 for a phone and dealing with the same issues...I just can't be as accepting.

[Cant Miss]

Pixel is being returned. Going back to 6P.

Been on Android for almost 5 years, but if this is Google's new premium (priced) user experience I'm thinking my next phone will be 10th anniversary iPhone.

[osho841]

It could be a problem with the NEX4100 too though since it is reported to be working on other head units. In which case it is Pioneer's issue to deal with. It sucks because there are too many places to point the finger at. I just go ta 4100 nex and now I am afraid this will happen to me next year when update my phone.

[Cant Miss]

It could be a problem with the NEX4100 too though since it is reported to be working on other head units. In which case it is Pioneer's issue to deal with. It sucks because there are too many places to point the finger at.

I point my finger at Google since it works with two different Motos on lollipop, and Nexus 6P on 7.0 and even dev preview of 7.1.1.

Something changed with the Pixel that Google needs to address (guessing it is an USB issue).

[Tony DiLascio]

So ... Day 1, on build NDE63P. Connected to a Pioneer AVH-4100NEX (on the Dec. 16, 2015 1.053 update firmware).

I first connected with the same cable I've been using with the Nexus 6P. Worked for a minute or so, then froze. Tried the cable that came with the Pixel. Even worse — resolution issues. (That thing where things are just all jacked up on the display, like they don't fit.

Oh, the joys of being an early adopter.

So I received my Pixel XL today & attempted to connect it to my Pioneer AVH-4100NEX head unit I've used since Android Auto came out in 2015. I've successfully used the Nexus 6 & 6P with no issues. However, the Pixel XL won't connect, instead giving me the error message "Communication Error 7 - your car's software didn't pass Android Auto security checks". I've no issues connecting the phone fully to the head unit's Bluetooth system, but Android Auto won't connect. Is this a known issue? I'm hoping it is & that a fix is forthcoming.

[Cant Miss]

Report it from Android Auto feedback, otherwise it certainly won't be fixed.

[dekii86]

A couple days ago I tried a colleagues Pixel briefly on my Pioneer AVH-X8850BT (Australia) - seemed to work with no resolution or other issues. Allowed me to get into Spotify, phone dialing and Google Maps. I get my Pixel XL today in the mail so will be testing it out some more. Fingers crossed!!!

[KidCuda]

Any update from anyone? My Pixel will be arriving around Thanksgiving and I'll be looking for a head unit, probably the 4200.

[1dcsailor]

Doesn't work for me.

I run my Pixel XL with a Kenwood 893s and when I plug it in with the USB cable that comes with the Pixel XL it opens up Android Auto on the head-unit and then the Android auto touchscreen interface stops responding and the audio stops. I have to disconnect the usb cable to get bluetooth audio and the touchscreen working again. My Kenwood Unit, Android auto app, and google play services are all running the latest software and it still doesn't work smh. I sent in feed back via the Android Auto app today. Hopefully this gets fixed asap.

[cam30era]

Exactly, it's ridiculous. And it's not the cables. If you have a cable that works, and I do, it should always work - unless it breaks, in which case it should never work again.

FWIW: my Pixel XL works fine (every time) with both my 2016 Corvette and my wife's '16 Ford Edge.

[nofaithineli]

Pixel also works seamlessly with 2015 Genesis stock head unit.

[wtherrell]

Pioneer advised that you need to go to the website and turn off AVIC - sync to get AA working properly with Nougat until they can resolve this problem.

[Phil Nickinson]

Decided it was a cable thing. I finally found one that works. Everything's cool now.

[gomike1978]

What cable works? I am in the same boat as you.

[gomike1978]

Decided it was a cable thing. I finally found one that works. Everything's cool now.

What cable did you find that works?

[Phil Nickinson]

What cable works? I am in the same boat as you.

I'm using this one now:

http://moderndad.com/3ou4n

[gomike1978]

I'm using this one now:

http://moderndad.com/3ou4n

What length?

[fragilemn]

I have a 2015 Hyundai Sonata stock headunit and my Pixel XL works flawlessly so far. I have thus far only used the USB cable that Google sent me and it seems to work like a charm. Also the phone charges while using AA in my Sonata, which I know is not the case for some phones in the Sonata.

[tcatnat]

I had my first long run with AA today and overall I faired well. Pixel connected to 2017 Audi A4 fine and launched AA. Some brief observations from 6 hours of driving today, more than 5 of those hours on the highway.

At one point I noticed some artifacts on the car screen while Google maps was in night mode. Seemed to last about 15 minutes. Also regarding Google Maps, the alternate route pop ups (the squares that pop up to show an alternate route will be 10 minutes slower while driving) are not accurate and confusing. At one point I had the option to take 1 of 3 routes at a junction and the square popped up but I could not tell which route it was referring to. It's much more obvious when using it on the Pixel.

On the first 2.5 hour leg of my trip I was using Google Maps and Pandora through AA and on four separate occasions Pandora randomly switched to Google Play Music. Nothing like going from the middle of White Christmas to the middle of Blackened in the blink of an eye. This did not happen once on my 2.5 hour trip back.

The only other thing that did not work as expected was voice commands. When connected to AA and pressing the talk button on the steering wheel I am supposed to be connecting to Google voice commands but instead I am connecting to Audi MMI voice commands.

This was the first time I used AA so I'm still in learning mode.

[Pedrore]

To trigger voice prompt, use a long press on your voice command button