[bruejam]

Right up front this is probably an oddly specific tech support issue, but I'm about out of ideas and thought I'd come to the braintrust for help.

I had a Google Pixel 3 when I took delivery of the Integra. Connected it right away and had no issues with Wireless AA. Due to ongoing battery issues, however, I upgraded to a Pixel 6 Pro over the weekend. I went through the phone connection in the Integra screen, paired right away, and Android Auto started. Everything worked on the screen as expected and I thought I was good.

However, the next time I started the car, Android Auto did not start. It was paired via bluetooth, but when I hit the Smartphone icon on the screen all I saw was my old phone, then a message that indicated my device isn't compatible with the vehicle.

Both the Pixel 3 and Pixel 6 are Android 12.

I've tried unpairing (forget connection on my phone and delete the phone from the car) and starting from scratch, both via the Smartphone icon and Bluetooth icon on the screen. Same results. Bluetooth pairs quickly, my phone shows that it's trying to start Android Auto, but the compatibility message ultimately comes up. I've gone through the Acura documentation as well as AA documentation with no apparent answers. The last thing I can think of is connecting via USB, which I'm going to try this afternoon. If that works, I'll update my post and this will all have been for nothing. In the meantime, however, any ideas? I might resign myself to the device truly being incompatible if I hadn't seen it work the first time.

 

[cmoretti]

I have a Samsung Galaxy S22+ and am having the exact same issue. Connected perfectly at first and now after a few days says it's no longer compatible.

 

[Integra23]

Right up front this is probably an oddly specific tech support issue, but I'm about out of ideas and thought I'd come to the braintrust for help.

I had a Google Pixel 3 when I took delivery of the Integra. Connected it right away and had no issues with Wireless AA. Due to ongoing battery issues, however, I upgraded to a Pixel 6 Pro over the weekend. I went through the phone connection in the Integra screen, paired right away, and Android Auto started. Everything worked on the screen as expected and I thought I was good.

However, the next time I started the car, Android Auto did not start. It was paired via bluetooth, but when I hit the Smartphone icon on the screen all I saw was my old phone, then a message that indicated my device isn't compatible with the vehicle.

Both the Pixel 3 and Pixel 6 are Android 12.

I've tried unpairing (forget connection on my phone and delete the phone from the car) and starting from scratch, both via the Smartphone icon and Bluetooth icon on the screen. Same results. Bluetooth pairs quickly, my phone shows that it's trying to start Android Auto, but the compatibility message ultimately comes up. I've gone through the Acura documentation as well as AA documentation with no apparent answers. The last thing I can think of is connecting via USB, which I'm going to try this afternoon. If that works, I'll update my post and this will all have been for nothing. In the meantime, however, any ideas? I might resign myself to the device truly being incompatible if I hadn't seen it work the first time.

No issues here on my Pixel 6. Maybe reset the head unit to factory settings? Mine connects every day for the last month with no issues.

 

[bruejam]

I have a Samsung Galaxy S22+ and am having the exact same issue. Connected perfectly at first and now after a few days says it's no longer compatible.

Mine is working now. I don't really have an explanation for why, but here's what I did.

I plugged it in with USB and Android Auto started almost immediately. I let it run for a few minutes and then unplugged the cable to see if it would stay up. It did not. So I plugged it back in and nothing. I pulled the plug and plugged it in again and it worked. Left it plugged in for my commute home.

I parked and turned off my car. A bit later, I went to run some errands. Not even thinking about it, I put my phone on the wireless charger and left my neighborhood. After a couple of minutes, Android Auto started. It kept working to my destination and fired right up when I left to come back home.

I guess what I'm suggesting is to try plugging it in with the USB, maybe several times, until it maybe just works?

Man I'm good at this. I should write owners manuals or something. 🤣

 

[Pepe El Toro]

Same here. Pixel 6, and having the issue both wireless and wired. The first days the issue was constantly happening, after that it happens after a few hours of being connected (wired/wireless).

I have noticed two common patterns.
1) It happens after a few hours, and when it does, I've noticed that my phone is quite warm. Could be an issue with my phone overheating? Maybe, maybe not.

2) Most recently it threw an error on my phone stating: "Being connected to a VPN may prevent Android Auto from starting". This might be more specific to having GoogleFi as your service provider (which I do) since it opens up a VPN automatically with it.

Now what do to? Well, the only way to get this fixed, aside from our own tricks we might discover, would be to submit feedback back to google. Within the android auto app on the phone, and by clicking the 3 dots on the upper right corner, we can select "Send Feedback" and submit our problem. Best approach will be to select and allow the "System Logs" to go with it so they can investigate the situation and promptly fix it (hopefully they will, as it is annoying).


Oh, and AcuraLink also gave me some trouble.. But that is another story...

 

[A-Spec]

I have a Samsung Galaxy S22+ and am having the exact same issue. Connected perfectly at first and now after a few days says it's no longer compatible.

Welcome to the forum @cmoretti How long as the compatibility issue been happening for?

 

[A-Spec]

Mine is working now. I don't really have an explanation for why, but here's what I did.

I plugged it in with USB and Android Auto started almost immediately. I let it run for a few minutes and then unplugged the cable to see if it would stay up. It did not. So I plugged it back in and nothing. I pulled the plug and plugged it in again and it worked. Left it plugged in for my commute home.

I parked and turned off my car. A bit later, I went to run some errands. Not even thinking about it, I put my phone on the wireless charger and left my neighborhood. After a couple of minutes, Android Auto started. It kept working to my destination and fired right up when I left to come back home.

I guess what I'm suggesting is to try plugging it in with the USB, maybe several times, until it maybe just works?

Man I'm good at this. I should write owners manuals or something. 🤣

Have there been any issues since you plugged your phone in? I guess that helps the car recognize which phone to prioritize?

 

[cmoretti]

Welcome to the forum @cmoretti How long as the compatibility issue been happening for?

It only started happening yesterday and I haven't been able to get it to reconnect since. I connected it through wire this morning, but it only came on for a minute and then stopped working and wouldn't reconnect through the wire again. Still have Bluetooth control, but nothing in terms of android auto.

 

[bruejam]

Have there been any issues since you plugged your phone in? I guess that helps the car recognize which phone to prioritize?

No issues so far... wireless AA popped up this morning before I was even out of my driveway.

 

[bruejam]

It only started happening yesterday and I haven't been able to get it to reconnect since. I connected it through wire this morning, but it only came on for a minute and then stopped working and wouldn't reconnect through the wire again. Still have Bluetooth control, but nothing in terms of android auto.

If you haven't already, try forgetting the bluetooth connection from your phone and deleting it from the car if it shows up in either the device list or the bluetooth list. Then plug the USB in and let it all detect automatically. I've had luck with that in the past.

 

[cmoretti]

If you haven't already, try forgetting the bluetooth connection from your phone and deleting it from the car if it shows up in either the device list or the bluetooth list. Then plug the USB in and let it all detect automatically. I've had luck with that in the past.

I deleted it out of my phone's Bluetooth and the car for a second time and forever whatever reason that did the trick this time. Has been working perfectly ever since, so here's to hoping it stays that way!

 

[bruejam]

I deleted it out of my phone's Bluetooth and the car for a second time and forever whatever reason that did the trick this time. Has been working perfectly ever since, so here's to hoping it stays that way!

That's the part of this that's so frustrating to me. It seems like you just have to randomly struggle through for a while and then for no apparent or consistent reason it starts working. I'm sure a deep dive into both systems would eventually show a root cause, but on the surface setup seems very flaky. I don't feel like it's on the car side either... I'm pretty sure Android Auto is suspect.

 

[cmoretti]

That's the part of this that's so frustrating to me. It seems like you just have to randomly struggle through for a while and then for no apparent or consistent reason it starts working. I'm sure a deep dive into both systems would eventually show a root cause, but on the surface setup seems very flaky. I don't feel like it's on the car side either... I'm pretty sure Android Auto is suspect.

I agree, and I feel like you're not far off. This is the first car I've had with the option of wireless android auto and I've heard complaints just in general with its operation from other people, so possibly there could be a bug in there that is triggering the issue.

 

[bruejam]

Wanted to check in with a weird Android Auto issue I had yesterday. I haven't had any wireless AA connectivity issues since I originally got it working. Tuesday night, I put my car away and everything was fine. Hopped in yesterday morning to leave for work and my phone wouldn't connect at all. I tried all the usual tricks that I could, forgetting the device from the car, forgetting the bluetooth connection from the phone, starting from scratch, etc. Nothing. I didn't have my cable with me, but I grabbed one from my desk and tried that method midday. Connected via USB, Android Auto started immediately and everything seemed fine. Unplugged it, and back to nothing. Still randomly saw the compatibility error message and couldn't get wireless AA to work. The phone would pair via bluetooth, though. I gave up and went back in to work for the afternoon.

End of the day, started the car and as soon as the screen started up I was greeted by a message, "Would you like to enable wireless Android Auto for this device?" Hit OK and it immediately started working. Haven't had any issues since then. The only thing I can figure is there was some sort of update overnight to my phone that caused it to quit working. My current Android Auto version is 7.8.622514. Just noting it here so I can come back to it if I lose connectivity again. If that's what it is, it seems crazy to me that the connection would be so fragile. Again, I don't think this is an Integra issue.

 

[vzalamea]

Wanted to check in with a weird Android Auto issue I had yesterday. I haven't had any wireless AA connectivity issues since I originally got it working. Tuesday night, I put my car away and everything was fine. Hopped in yesterday morning to leave for work and my phone wouldn't connect at all. I tried all the usual tricks that I could, forgetting the device from the car, forgetting the bluetooth connection from the phone, starting from scratch, etc. Nothing. I didn't have my cable with me, but I grabbed one from my desk and tried that method midday. Connected via USB, Android Auto started immediately and everything seemed fine. Unplugged it, and back to nothing. Still randomly saw the compatibility error message and couldn't get wireless AA to work. The phone would pair via bluetooth, though. I gave up and went back in to work for the afternoon.

End of the day, started the car and as soon as the screen started up I was greeted by a message, "Would you like to enable wireless Android Auto for this device?" Hit OK and it immediately started working. Haven't had any issues since then. The only thing I can figure is there was some sort of update overnight to my phone that caused it to quit working. My current Android Auto version is 7.8.622514. Just noting it here so I can come back to it if I lose connectivity again. If that's what it is, it seems crazy to me that the connection would be so fragile. Again, I don't think this is an Integra issue.
[/

 

[vzalamea]

Similar issue here. S22 Ultra paired to 2023 Acura Integra 6MT.

When enabling wireless Android Auto, it seems the car sets up a WiFi access point that the phone connects to. My phone starts to connect to an access point named "Car-1ce1" and immediately disconnects. The WiFi AP is then no longer listed in the list of available APs. So I'm suspecting it's an issue with the car and not the phone. The last time this happened, I was able to reconnect after doing a Factory Data Reset on the car. Now, even that doesn't work. So frustrating.

 

[VTEC Goes Bwaah]

Similar issue here. S22 Ultra paired to 2023 Acura Integra 6MT.

When enabling wireless Android Auto, it seems the car sets up a WiFi access point that the phone connects to. My phone starts to connect to an access point named "Car-1ce1" and immediately disconnects. The WiFi AP is then no longer listed in the list of available APs. So I'm suspecting it's an issue with the car and not the phone. The last time this happened, I was able to reconnect after doing a Factory Data Reset on the car. Now, even that doesn't work. So frustrating.

Hey @vzalamea welcome to the forum! Connectivity issues have been a thing with the new Civic. Owners have been talking about it on the Civic forum. I guess the same thing is now happening with the Integra.

When did you pick up your Integra?

Android Auto issues

I just bought my 2022 Civic Sport. When I connect my s21 ultra via cable to my car and use android auto, every 60 seconds or so it will stop and state my media has switched to Bluetooth. Then it will go back to android auto after a few seconds and it's just an endless cycle unless I unpair my...

www.civic11forum.com

 

[vzalamea]

Hey @vzalamea welcome to the forum! Connectivity issues have been a thing with the new Civic. Owners have been talking about it on the Civic forum. I guess the same thing is now happening with the Integra.

When did you pick up your Integra?

Android Auto issues

I just bought my 2022 Civic Sport. When I connect my s21 ultra via cable to my car and use android auto, every 60 seconds or so it will stop and state my media has switched to Bluetooth. Then it will go back to android auto after a few seconds and it's just an endless cycle unless I unpair my...

www.civic11forum.com

I've had the car just over a month (July 13).

Maybe I'll load an older version of Android Auto from APKMirror (https://www.apkmirror.com/?post_type=app_release&searchtype=apk&s=android+auto) on my phone, then do a factory data reset in the car and see what happens.

 

[vzalamea]

Problem solved. I installed a daily build of the 8.0 beta (arm64) from APKMirror.com. Phone connected fine and Spotify is working again through AA.

 

[RedIntegy]

I had the issue of where it stopped working a day or two after I got the car. I believe the fix is to unpair your phone from the vehicle and turn off the vehicle's WIFI, re-enable it and pair with the car again via Bluetooth. This seems to be working as I turned off and on the car twice and AA kicked on right away. Will provide an update in a few more days.