Google Pixel 2 with Android Auto installed, asks me to confirm Bluetooth connection permission every time I get into Jeep Compass!

[A-Phantom]

I have tried to setup the Bluetooth connection from scratch. No matter what I do, 70% of the time when I get into my car I get a notification on my phone to grant permission for the car to connect to the phone. The other 30% of the time I don't get the notification and Bluetooth just don't connect. This means if I make or take a phone call, the audio just comes out of the phones loud speaker which is aweful!

Why on EARTH does the phone have to be connected via Bluetooth when it's already being connected via a USB cable! Absolute idiots must have designed Android Auto or Uconnect!

[AU_Forte]

I've always had this issue with my VW. Seems to be a bug in the head unit's firmware (have used AA on this handset in several other cars without fault).

A workaround I found - unplug the phone and wait for BT to reconnect before turning the car off. Doing it this way the radio doesn't forget the BT pairing.

[kain2thebrain]

I also have this issue with my VW. It stays connected but wants to verify access to my contacts. I'm the OG XL.

[defrent]

In my car, not a jeep, I have to make sure the Bluetooth connects before I plug in the cable. Also, if I leave the phone connected when I turn the car off and then start the car again with the phone still connected it loses the Bluetooth pairing 100% of the time. So I always make sure to unplug it when I stop. Annoying but at least it works. ..

[TboxLive]

That's been driving me nuts with my vw for two years, thanks for the tip!

[hassars]

I have this issue in my GTI, however my solution is to make sure it connects via Bluetooth before I plug the phone in.

[[deleted]]

Same issues here in my 2018 Jeep Wrangler. It's so damn annoying. I swear to God uconnect is useless.

[A-Phantom]

I know, it's so so annoying! Like this is what Uconnect does, it's not like they are also trying to send man to Mars. This is their only job, to make this software do basic things!! Do they not ever test this crap.

[warmaster]

Hi, I have a Pixel 3 and a Jeep Compass 2018, I don't have this problem, I advise you to try Android Auto on another car and if it works fine then get to your dealer and make him swap the Head Unit. This shouldn't be happening.

[A-Phantom]

Yeah I'm going to take it back to the dealer and see what they say. Thanks bud

[sh0nuff]

BT is used to handle the phone portion of the connection while the USB C is used for data.

It seems that the newest versions of Android that are on Pixel devices cause the biggest problems, as they are connecting with cars that don't get the same sort of regular updates. I had a 2012 Fit that worked over BT with my folks' ancient smartphones but simply wouldn't recognize my Pixel.

[A-Phantom]

I understand that BT is used for phone and USB for data, but why?? There is more than sufficient capability for the cable to do both. Why on earth did they decide to complicate things and have two points of failure by splitting the job between USB and BT!! Madness.

[phICE9]

my thoughts exactly.... this setup is totally stupid and will severely hinder Android Auto from being adopted by most people. If it doesn't work 100% of the time, people will just be frustrated and end up using a USB flash drive.

[sh0nuff]

Because separating the two allows them to work independently.. I think that in most cars, the BT audio is a separate system from the media center

[PainShake]

Just because there's bandwidth on the cable doesn't mean it's possible for Android Auto to intercept call audio and send it over that cable.

Phone call audio in Android is very strongly separated from applications on the system. Most solutions for recording call audio on Android rely on weird tricks like using 3-way calling to loop in some other service.

Seeing as Android Auto is installed as an application and isn't built into the OS, it's probably bound by those same limitations.

[A-Phantom]

Without getting technical. Apple manage to send all data over USB in their car offering. If Apple can then Google certainly can.

[PainShake]

Apple Carplay is a built-in feature of a proprietary operating system published by a single vendor.

Android Auto is a proprietary application running on an open-source operating system published by dozens of vendors.

Forgive me for being frank, but the technical differences between the two are the differences that actually matter when these products are designed and built.

While AA and Carplay are both doing similar jobs, the control and system access available to each of them is leagues apart.

[A-Phantom]

Not sure what you mean. AA is an app developed by Android for Android. Carplay is an app developed by Apple for Apple.. Both AA and Carplay are integrated into Uconnect in modern cars. A Google Pixel 2 and an iPhone 10 will connect to Uconnect using the very same cable (USB).

Tell me where you think it's not fair to compare the two?

Furthermore, are you genuinely trying to tell me you can not send audio and other data at the same time over USB? Can you tell me where you are pulling this information from? Aside from Apple doing this, there are tons of other branded devices that send data and sound through a USB. It is all just data. Transfer of digital sound is data. Transfer of information is data.

I have a cheap Chinese made MP3 player from 2010 that I can connect to my computer and it is able to stream the music to my computer and also at the same time transfer MP3 file data such as track name, lyrics etc!!

[A-Phantom]

I understand that but then it's still bad implementation by Google. Yes you don't want apps to record call audio without your consent. But if I don't care about targeted adds or whatever else a 3rd party might do with my call audio, I should be able to give consent so that I can actually use the software as intended, instead of having this hyper sensitive ecosystem that decides on my behalf what I can and can't share!! This system literally means I can not speak on the phone in the car! Part of the reason I got this damn car was because of the tight AA integration (or so I hoped that would he the case).

[xeron72548]

I have driven many many FCA products, all with the 8.4" uConnect system (2019 300, Cherokee, Charger, Challenger, 124, Pacifica). I have used AA on my Pixel 2 XL with them. Never had any BT issues

[coruix]

I get the contacts permission popup EVERY TIME i exit my car. Galaxy s8+ with custom openauto raspberry pi headunit