[CapeCodID4]

Anyone else in a constant battle with the ID.4 over the phone's connectivity, specifically the wired one? I have a slightly older phone (OnePlus 6T) that doesn't support wireless Android Auto (it has Android 10). The phone and AA works fine (sort of) if the phone is connected via USB, but it seems like EVERY TIME I enter the car I have to delete and re-add the phone via the in-car connected devices app. The phone stays connected via Bluetooth fine, and even will register that it thinks it's connected via AA, but you can't get anything to appear on the ID.4s screen. You can often actually hear (and see on the smaller display) turn-by-turn navigation coming from the phone and the music will continue to play/stream off the phone, but the Google Maps / Waze / whatever won't display. Deleting the phone and re-adding it works every time, but seems like a ridiculous workaround. My only thought for now is maybe a sub-par USB cable? It works fine in another car, though.

Anyone else seen this and -- better yet -- found a solution? (I'm at the point where I'm ready to spend more money upgrading my phone. Yes... first world problems...)

 

[eb2143]

I have a OnePlus 6 running Oxygen OS 11.1.1.1 with none of these issues and it supports wireless. Though usually I use wired to keep phone battery charged up.

 

[CapeCodID4]

I have a OnePlus 6 running Oxygen OS 11.1.1.1 with none of these issues and it supports wireless. Though usually I use wired to keep phone battery charged up.

My phone is a T-Mobile version and Oxygen Updater doesn't work on it. (I realize there are probably other options. Maybe I'll keep investigating.) Still seems odd that a phone on a USB connection would be inferior to one on Wireless AA as far as ease of connectivity and maintaining and remembering the connection.

 

[ericy]

Unfortunately not all Android phones are identical - different manufacturers have introduced features in different releases. I have a Galaxy Note 9, with Android 10, and wireless AA is flawless. So it sort of leaves you in a no-mans zone between VW and OnePlus as to where the problem really lies..

 

[Froggy]

Apple 🍎 works fine. Embrace the dark side.

 

[ericy]

Apple 🍎 works fine. Embrace the dark side.

Never!

 

[ddx]

I have a Samsung S20 and it works great... actually, too great. It seems to do everything in its power to make sure the Android Auto (wireless) is connected properly. For example sometimes I disabled WiFi for whatever reasons, and when I turn on the ID.4 it connects to my phone via bluetooth and reenable WiFi by itself for whatever it needs to make sure AA is working properly.

 

[CapeCodID4]

I have a Samsung S20 and it works great... actually, too great. It seems to do everything in its power to make sure the Android Auto (wireless) is connected properly. For example sometimes I disabled WiFi for whatever reasons, and when I turn on the ID.4 it connects to my phone via bluetooth and reenable WiFi by itself for whatever it needs to make sure AA is working properly.

Pretty sure AA needs a 5Ghz network to transfer data from the phone to the car, so that makes sense...?

 

[LifeInJ]

I have a Pixel 5 and I am ready to yeet my phone out of the car. After multiple resets of AA and what phones the VW is aware of, I am still getting multiple permissions requests every time I get in the car. When using the USB-c port, Android will enable bluetooth, which sets of a cascade of permissions requests. After accepting and always allowing, they still appear. And when I don't plug the phone in, the phone itself starts providing all kinds of notifications every 30 seconds until I either connect it to the car via usb-c or manually turn off bluetooth.

This warning shows almost every time I'm in the car. Also, when I go to the notification from AA asknig for permission, AA will flash a message saying to use the car screen....and the notificaiton is still there on the phone and the car. Tapping 'App-Connect' makes makes the notificaiton go away, but then it'll reappear after a few seconds. 🤬

(Not looking for tech support, just venting )

 

[thomas_y3]

Anyone else in a constant battle with the ID.4 over the phone's connectivity, specifically the wired one? I have a slightly older phone (OnePlus 6T) that doesn't support wireless Android Auto (it has Android 10). The phone and AA works fine (sort of) if the phone is connected via USB, but it seems like EVERY TIME I enter the car I have to delete and re-add the phone via the in-car connected devices app. The phone stays connected via Bluetooth fine, and even will register that it thinks it's connected via AA, but you can't get anything to appear on the ID.4s screen. You can often actually hear (and see on the smaller display) turn-by-turn navigation coming from the phone and the music will continue to play/stream off the phone, but the Google Maps / Waze / whatever won't display. Deleting the phone and re-adding it works every time, but seems like a ridiculous workaround. My only thought for now is maybe a sub-par USB cable? It works fine in another car, though.

Anyone else seen this and -- better yet -- found a solution? (I'm at the point where I'm ready to spend more money upgrading my phone. Yes... first world problems...)

I have an OnePlus 7T and wireless AA worked great up until couple months ago to where the connection would drop then quickly reconnect like every few minutes. so i don't use it now. hoping the next OTA ID.4 update would resolve this.

 

[ddx]

Pretty sure AA needs a 5Ghz network to transfer data from the phone to the car, so that makes sense...?

Yeah, I guess so, its fine for me not complaining, but just something I noticed. It is better it does it by itself than having to bug me every time I forgot to turn wifi back on.

 

[CapeCodID4]

(Not looking for tech support, just venting )

Interesting. My wife has a Pixel 4(a?) and her phone works pretty flawlessly with AA wireless... :/

 

[LifeInJ]

Interesting. My wife has a Pixel 4(a?) and her phone works pretty flawlessly with AA wireless... :/

I know, it should just work, especially with a Google phone running pure Android. I'm assuming it's something with the phone and AA app on my phone... I'm thinking a factory reset of the phone would solve all my problems. But it'd be a hassle to re-set up everything up.

Maybe I should get a new Pixel 6 just in case

 

[Ciscovet]

I have a pixel 4a as well and it works flawless for me too. I also only use AA in wireless mode. Maybe reinstalling AA and using the wireless connection might work for you.

 

[CapeCodID4]

Maybe I should get a new Pixel 6 just in case

I have one in my "cart" as we speak but am reluctant to hit the "Buy" button as I don't really need a new phone. A case of FOMO, I think...

 

[Ciscovet]

Pixels are excellent phones for the money. I recommend waiting for black Friday since they usually deep discount their phones.

 

[oldtechie]

Anyone else in a constant battle with the ID.4 over the phone's connectivity, specifically the wired one? I have a slightly older phone (OnePlus 6T) that doesn't support wireless Android Auto (it has Android 10). The phone and AA works fine (sort of) if the phone is connected via USB, but it seems like EVERY TIME I enter the car I have to delete and re-add the phone via the in-car connected devices app. The phone stays connected via Bluetooth fine, and even will register that it thinks it's connected via AA, but you can't get anything to appear on the ID.4s screen. You can often actually hear (and see on the smaller display) turn-by-turn navigation coming from the phone and the music will continue to play/stream off the phone, but the Google Maps / Waze / whatever won't display. Deleting the phone and re-adding it works every time, but seems like a ridiculous workaround. My only thought for now is maybe a sub-par USB cable? It works fine in another car, though.

Anyone else seen this and -- better yet -- found a solution? (I'm at the point where I'm ready to spend more money upgrading my phone. Yes... first world problems...)

I'm a long time user of Oneplus phones. What you are experiencing is not unique to the ID.4, connecting a Oneplus running Android 10 is troublesome in many vehicles. Just upgrade the phone to Android 11, the problems will disappear. And yes 11 is available for the 6T, I have Android 11 on my two Oneplus 6 phones. It might be necessary to download the upgrade and install it manually, but that's very simple.

 

[thomas_y3]

in my previous post a few days back saying when using wireless AA with my OnePlus 7T that the connection keeps dropping and reconnecting every few minutes. Well, got the Android 11 update and wireless AA is working fine now(knock on wood).

 

[Mbrakel]

Anyone else in a constant battle with the ID.4 over the phone's connectivity, specifically the wired one? I have a slightly older phone (OnePlus 6T) that doesn't support wireless Android Auto (it has Android 10). The phone and AA works fine (sort of) if the phone is connected via USB, but it seems like EVERY TIME I enter the car I have to delete and re-add the phone via the in-car connected devices app. The phone stays connected via Bluetooth fine, and even will register that it thinks it's connected via AA, but you can't get anything to appear on the ID.4s screen. You can often actually hear (and see on the smaller display) turn-by-turn navigation coming from the phone and the music will continue to play/stream off the phone, but the Google Maps / Waze / whatever won't display. Deleting the phone and re-adding it works every time, but seems like a ridiculous workaround. My only thought for now is maybe a sub-par USB cable? It works fine in another car, though.

Anyone else seen this and -- better yet -- found a solution? (I'm at the point where I'm ready to spend more money upgrading my phone. Yes... first world problems...)

My older HUAWEI P10 with android 9 has exactly the same issue, always connects by USB to some extent, always gives audio, and navigation on the dash. Even listens to my shout outs to Google assistant. But more than half of the times, the AA screen won't pop up. Sometimes it does work like a charm. Not sure yet why it is intermittent, seems like a boot sync issue or something.

I guess it's because my phone is already 3 years old, but still hope for a magical update of either phone or car that fixes it.