Pixel 3XL and Uconnect Issues

[MikeofNC]

Just upgraded my phone to the new Pixel 3 XL. Tried connecting it to get Android Auto starting and pairing and nothing happened. The phone itself gets a charge and it sees that it is connected but AA will not start up. Dreading going to the dealership to see if there is anything that they can do firmware wise to fix it.

Sponsored

 

[cbournis]

I just got a pixel 3 xl and it works.. took two tries but it did it's sync and now us paired and working.

 

[dangerz]

Try changing your cable. Sounds like that cable doesn't have a data port, or one that's not compatible.

 

[cbournis]

Been a few days now with my pixel 3xl.... Doesn't always connect... I plugged it in using multiple cables but it says charging and then stops... Only way to get it to recognize is to reboot the phone...

 

[kurt13]

I first tried connecting my new Pixel 3 using the USB-C in the media plug. It told me to complete the Android Auto setup on my phone but it wouldn't work.

I got a new cable from Amazon and connected to the USB plug in the console and it works great. AA is so much more responsive with a new Pixel as compared to my old S7. By the way, I think these red cables look hot in my Firecracker Red Rubi.

https://www.amazon.com/gp/product/B07FK7LMCF/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1

One more thing- my AA does have a bug that sometimes I can't adjust XM radio with the phone plugged in. I disconnect the phone and volume control returns. I think it's already a known issue for Google though.

 

[swozey]

I'm on day 4 of no Android Auto on my Samsung S8 from any cable in my front 2 ports (usbc or usb to usbc). I probably have 6 different cables in my glovebox right now that I used to try when it'd break.

I typically give up until it fixes itself, but this has been the longest. Usually it works the next morning but I have had it go out for 2 days before.

I'm going to finally give in and reset the thing. I'm sure it'll break on my next roadtrip, like usual.

I will say, when I switched to a usbc-usbc cable it worked FAR better, faster and I probably had an entire month without ever losing AA.

edit: If you're googling for suggestions remember these are used in a ton of FCAs, so I'm just looking up Uconnect problems directly, not specifying Jeep/Wrangler. There are some good threads; https://www.pacificaforums.com/foru...ect-carplay-android-auto-do-not-activate.html

edit: I bet I disabled the Phone device mirroring they mention. I remember seeing it and not knowing what it was..

edit3: Nope.. I had smartphone mirroring on... lol. Fuck I hate going to dealers but I guess that'll be on the menu if it doesn't kick in tomorrow.

 

[Command Line RC]

Using Android Auto on my Pixel 3 is a hit or miss at times. Sometimes it connects up and then sometimes I have to play with it in order to get it to function. Pixel 2 connected right up every time. I'm using the factory OEM cable as well.

 

[RajCaj]

I came to the forums to see if others were having problems with their Pixel 3 phones....

I don't think the problems we are experiencing are related to the UConnect head unit. My old Samsung S6 Active worked with AA flawlessly.

Since I've updated to the Pixel 3 XL, AA doesn't always load when I plug the phone in (using Google's USB C to USB C cable). Unplugging & replugging, and restarting the phone doesn't always work

Also, using AA navigation will mute anything I have playing on the radio for the front two speakers while navigation instructions are given...which works as intended, but the audio does not return to the front speakers once the navigation instructions are finished. Once this happens, volume controls for the head unit no longer works to raise or lower the volume for all speakers.

As a workaround, I have to trigger AA's voice command (OK Google), give it some command, and then after the response finishes, audio will return to the front speakers and the volume controls will work again.

However, if another navigation instruction comes through (turn right here..etc.), it starts all over again.

I contacted Google and these issues are known bugs with Pixel 3 / XL phones & AA. There will be an update to the Google Play Services coming soon that should fix it. For the time being, you can opt-in to beta test google software and try the beta version of Google Play Services to see if that helps.

All that said, there are people having the same, and other, issues with Pixel 3 phones & AA on head units in Hondas, Kias, and other car manufactures.

 

[ormandj]

FWIW, I have a Pixel 3 and AA in my current Audi and have had no issues since launch. Seems to depend on person/cable/etc - it's all over the map. Two of my co-workers also have Pixel 3s and no issues, but one other with a 3XL has had problems. Swapping cables fixed it for them. We're all using USB-C to A cables, since our current cars don't support C. Hope whatever it is gets fixed before my Jeep arrives!

 

[cbournis]

Update... I am a Beta tester and the current google play services is even worse v 14.5.75 updated on Nov 6th... It fixes the muted speaker issue but the phone will not connect to AA .. I plug it in... It says charging and then Unable to Charge and stops... I used to be able to unplug and plug back in.. and it worked.. or even reboot and it would work... The past few days only in the mornings it will NOT connect... It wont even acknowledge that it is plugged in... No messages telling me that it is charging or not...

This is getting annoying.... My Pixel XL worked great even on Android 9.... The Pixel 3XL is having too many issues with AA...

 

[RajCaj]

Update... I am a Beta tester and the current google play services is even worse v 14.5.75 updated on Nov 6th... It fixes the muted speaker issue but the phone will not connect to AA .. I plug it in... It says charging and then Unable to Charge and stops... I used to be able to unplug and plug back in.. and it worked.. or even reboot and it would work... The past few days only in the mornings it will NOT connect... It wont even acknowledge that it is plugged in... No messages telling me that it is charging or not...

This is getting annoying.... My Pixel XL worked great even on Android 9.... The Pixel 3XL is having too many issues with AA...

Same here...I downloaded the new beta version of Google Play Services, upon the request of the Google support tech, and it fixed the issue with volume being muted on the front speakers, and loss of audio control.

Unfortunately, I've not been able to get AA to load on the head unit since. Where plugging in the phone was hit or miss to activate AA on the old version, it straight up doesn't work now.

Same as the post above, I can see the charge lightning bolt pop up on the battery for a second and then it goes away.

I hope the issue a new beta build before rolling this out to Production

 

[cbournis]

Same here...I downloaded the new beta version of Google Play Services, upon the request of the Google support tech, and it fixed the issue with volume being muted on the front speakers, and loss of audio control.

Unfortunately, I've not been able to get AA to load on the head unit since. Where plugging in the phone was hit or miss to activate AA on the old version, it straight up doesn't work now.

Same as the post above, I can see the charge lightning bolt pop up on the battery for a second and then it goes away.

I hope the issue a new beta build before rolling this out to Production

Only way to get it to work now is to turn off phone and then restart it. Once it loads up then plug it in and it works.

 

[DanW]

My Pixel 3XL has been hit or miss, too. I just ordered those red cables that @kurt13 linked. Hope that helps.

Thanks for the link, Kurt!

 

[RajCaj]

Only way to get it to work now is to turn off phone and then restart it. Once it loads up then plug it in and it works.

I've tried....I've restarted the phone, then plugged it in the USB C port...no dice. I've tried restarting the phone with it plugged in..no dice.

I reached out to FCA and learned that Google sends updates to FCA, when they make changes to their software, so that the UConnect system can accommodate the changes. It makes sense to me that a beta version of Google Play Services, that hasn't been sent to FCA for updating, may no longer work correctly.

This would make sense that the old "official" version of Google Play Services would work...although with bugs, but the beta version not at all.

 

[RubiRob]

Please check out this link:

https://productforums.google.com/forum/#!msg/android-auto/1NmG3ojHX_k/R1UEvrdRCQAJ

I posted it as it won't work at all for me via type C anymore. It DOES work, actually flawlessly, via the Type A port in the center console. However, using that port we only get slow charging. This seems, to me at least, that there's some kind of handshake or authentication issue between the phone and the Type C port on our wrangler that is causing the phone to completely disable charging from it.

Before this I had a Pixel 2 XL, and it worked consistently via the type C port.

The more people who will +1 the issue and post, the more attention it will get. Please take a look. There's already an Android Auto Specialist in the thread.

Sponsored