[banksdad]

So I have had this problem on my BOLT that I have NOT been having in my Rav4. My Android Auto crashes randomly in my bolt and has done so with 2 different phones even when trying multiple different cables (all USB-C). These same phones, and their cables, have not had the same problem running AA on my Rav4. So I took it in multiple times and the dealership has not been able to re-produce. I tried yet another phone with micro-usb on the BOLT and it has not experienced the problem yet. They are going to switch out the USB hub on the car today. Crossing my fingers.

So my question is this...

Has anyone else had similar crashing problems and is your phone regular USB? Or USB-C?

 

[martinknutson]

So I have had this problem on my BOLT that I have NOT been having in my Rav4. My Android Auto crashes randomly in my bolt and has done so with 2 different phones even when trying multiple different cables (all USB-C). These same phones, and their cables, have not had the same problem running AA on my Rav4. So I took it in multiple times and the dealership has not been able to re-produce. I tried yet another phone with micro-usb on the BOLT and it has not experienced the problem yet. They are going to switch out the USB hub on the car today. Crossing my fingers.

So my question is this...

Has anyone else had similar crashing problems and is your phone regular USB? Or USB-C?

I have used 2 USB-C phones (Nexus 6p and Pixel 2 XL) without issue...

 

[Cataract2]

Can try a different cable. Never hurts.

 

[quiddity]

I use a XZ1 Compact which has USB-C. No probs.

 

[vansmack]

I had a Pixel 2XL with the Bolt that crashed constantly with the OEM Google USB-C cable.

I switched to this Anker Cable and my dropouts were greatly reduced, but not perfect.

I have since switched to the Pixel 3XL and still use that Anker cable, and haven't had a single dropout (since Oct 2018).

I'm pretty sure my problem was a poor USB-C port in the Pixel 2XL, but given that you've tried multiple phones and cables, yours might be the USB-A port. Hopefully, swapping it out fixes the problem.

 

[jvandonsel]

I found that having my Android phone connected via USB-C while the phone was sitting in the wireless charging cup caused AA to drop out frequently. I now don't use wireless charging and instead just put my phone in a cup holder. Since this change I've had almost no dropouts.

 

[Cataract2]

I found that having my Android phone connected via USB-C while the phone was sitting in the wireless charging cup caused AA to drop out frequently. I now don't use wireless charging and instead just put my phone in a cup holder. Since this change I've had almost no dropouts.

Yeah, the car really doesn't like having it plugged in and put in the phone cup holder. I went ahead and got the proclip https://www.proclipusa.com/ and attached a RAM ball to it. Will use my RAM Xmount to hold the phone from now on.

 

[banksdad]

So I guess people didn't fully read my OP. My phone only exhibits the problem on the BOLT. Same phone and cables (yes I tried 4 now - so it is NOT the cable) never has that problem on my RAV4 with that phone and all its cables. At this point, I am growing convinced it is the BOLT that has issue with USB-C. I had the port switched out and that did not resolve the problem. But I have also not been able to produce this problem on a micro-usb based phone.

 

[Nook]

I have a Motorola S5plus and find Android Auto glitchy enough that I don't use it. It doesn't help you, but you're not alone.
I really only care about getting the map displayed.

 

[JayBolt]

Hello @banksdad,

I've had my Bolt since Dec 18 and I love it. That said, Ive also had issues with Android Auto.

I will spare this crowd my opinion on being forced to use a 3rd party app over an embedded GPS, though I'm sure you can tell where I stand. Regardless, I bit the bullet and have been using the app. I'm not sure if it is buggy Bolt systems or Android OS on my particular phone (LG V30), but I suspect memory cache issues may be to blame. I once called On-Star and they had me shut down the car for 5 minutes before restarting everything. That was the first clue, though that could be the remedy for many things. However, I've also noticed times where my phone seems not to "transmit" the Android Auto screen and functionality to the car's screen even though BT is connected along with the cord. The remedy has sometimes been to disconnect all radio, restart phone, and try again. Annoying, but usually works out.

I should also qualify this a bit and explain that my day job often requires a lot of hopping in and out of my car, which means lots of connects and disconnects throughout the day. I find I can go as much as 10 days or so before the issue arises again.

Good luck!

 

[banksdad]

Hello @banksdad,

I've had my Bolt since Dec 18 and I love it. That said, Ive also had issues with Android Auto.

I will spare this crowd my opinion on being forced to use a 3rd party app over an embedded GPS, though I'm sure you can tell where I stand. Regardless, I bit the bullet and have been using the app. I'm not sure if it is buggy Bolt systems or Android OS on my particular phone (LG V30), but I suspect memory cache issues may be to blame. I once called On-Star and they had me shut down the car for 5 minutes before restarting everything. That was the first clue, though that could be the remedy for many things. However, I've also noticed times where my phone seems not to "transmit" the Android Auto screen and functionality to the car's screen even though BT is connected along with the cord. The remedy has sometimes been to disconnect all radio, restart phone, and try again. Annoying, but usually works out.

I should also qualify this a bit and explain that my day job often requires a lot of hopping in and out of my car, which means lots of connects and disconnects throughout the day. I find I can go as much as 10 days or so before the issue arises again.

Good luck!

Thanks for sharing your experience, but it isn't much like mine. My problem is that AA cuts out randomly and it does it specifically with a USB-C based phone. The solution does not require turning the car off for 5 minutes. It literally just requires unplugging and re-plugging. This happens daily for USB-C phone specifically. To me, that seems like a bug. The only way this could be proven is if someone else can test both types of phones.

 

[27258]

Another disaffected Android Auto user here. No matter what I try as just will not appear on the dash screen about half the time seemingly at random.

 

[p7wang]

I am getting the same problem with my Moto G6. I have plugged in a 12 volt charger and it works fine... it's not the cable. The phone would cycle between charging and not charging. The in-car USB ports are not sending enough power.

Still trying to figure out the way ahead, probably need to use my old Moto G5 to run Android Auto. And have that phone either tether off the in-car wifi (if I continue it) or tether off my Moto G6.

My son's iPhone 7 Plus with Apple Carplay works fine.


2019 Bolt Premier

 

[One1whaoo.]

Never had any problems with AA at all in the Bolt.
I've used a Sony Compact and an Essential PH-1, both USB-C, with no issues at all, unless I didn't plug the cable far enough into the socket on the phone (then the car doesn't see the phone at all).
I always place the phones into the pocket (where else?), again, with no problems at all.
Never had any problems with AA at all in the Bolt.

 

[MikeyBolt]

Just another data point. I'm using an older LG V20 with USB-C cable. Haven't had any problems on my 2019 Premier.

Mike

 

[p7wang]

Never had any problems with AA at all in the Bolt.
I've used a Sony Compact and an Essential PH-1, both USB-C, with no issues at all, unless I didn't plug the cable far enough into the socket on the phone (then the car doesn't see the phone at all).
I always place the phones into the pocket (where else?), again, with no problems at all.
Never had any problems with AA at all in the Bolt.

You mean that weird pocket in the front next to the 12v?

BTW, I tested it again but with case removed and then putting the cable back in... does seem to be a physical connection issue. Sigh...

 

[One1whaoo.]

The slot that is supposed to charge phones which have some sort of wireless charging (my phones don't).

 

[p7wang]

Yeah, that tiny pocket is way small.

 

[ArizonaJon]

Yeah, that tiny pocket is way small.

Unfortunately, the near field charging only works with the phone and charging device very close together. Thus with a large case on the phone, it won't fit into the holder.

 

[JamesH]

Brought home a 2020 Premier last week. The dealer could not get my Google Pixel 2 XL to connect to AA, said it was the cable. I tried another cable and it did not work. Found there was a separate app to download for Android 10. Tried the new app and it still did not work. I tried an oem cable, and I was able to connect on two straight occasions. Thought the problem was fixed, but alas I was wrong as I have not been able to connect over the last several drives. I'll try one more cable tomorrow. If that is not it, then it is the car or phone. I have heard of other issues with the Pixel 2. We will see.