Sync 3 - 3.4 & Android Auto Issue - Need Help

[SturdBurger]

Recently updated my sync 3 to 3.4 and this morning, Android Auto showed up for the first time this morning, but after about 20 seconds, it no longer showed up and I don't have Android auto navigation. Just wondering if I need to try a new cable or if there is some underlying issue with Android Auto.

Every now and again, during the 20 seconds of of Android auto, I would receive an error saying "USB hub not recognized" or "USB not recognized"

Using a USB 3.0 cable for my pixel 7 pro, the hook up is USB to USB-c.

Thanks in advance for any suggestions or troubleshooting tips

 

[thecman02]

I'm not the guru on Sync versions, but there is a newer USB hub that you can put in that has USB-C and that 3.4 will recognize.
https://www.amazon.com/carplay-Modu...65&mcid=740fc69dcab93256852c48b08db7878d&th=1

 

[sonicmn]

Recently updated my sync 3 to 3.4 and this morning, Android Auto showed up for the first time this morning, but after about 20 seconds, it no longer showed up and I don't have Android auto navigation. Just wondering if I need to try a new cable or if there is some underlying issue with Android Auto.

Every now and again, during the 20 seconds of of Android auto, I would receive an error saying "USB hub not recognized" or "USB not recognized"

Using a USB 3.0 cable for my pixel 7 pro, the hook up is USB to USB-c.

Thanks in advance for any suggestions or troubleshooting tips

Not sure if this is the cause, but it has given me issues in the past regarding intermittent connection issues. It might be worth checking the USB-C port on your phone to make sure it is not full of pocket lint to see if that is preventing a proper connection since you are saying that it is intermittent.

 

[flbchbm]

Not sure if this is the cause, but it has given me issues in the past regarding intermittent connection issues. It might be worth checking the USB-C port on your phone to make sure it is not full of pocket lint to see if that is preventing a proper connection since you are saying that it is intermittent.

And just bc the cable worked with your pixel, don't assume it will with the android. I have experienced an issue in the past and a shorter, high quality cable resolved it. 3-4ft is preferred, but you can get away with 6, but I humbly don't recommend. ymmv. Sync 3.4, hellifiknow, but I also recommend the usb C module. simple swap, but that damn center console has to come up. ugh....

 

[thecman02]

Definitely sounds like a cable is on the way out.

Sorry I didn't read the post very well. Definitely try a different cable and also try a different USB port. I would also fully restart the car (turn car off and open door to kill the keep alive relay) between trying these things. I've had issues where for unexplained reasons the port wasn't being recognized.

 

[SturdBurger]

Seems like it was a cable issue, swapped it with a new cable this morning and Android auto registered and stayed open with no issues!

Still might consider getting that newer USB module, having a USB-C port would be nice.

Thanks everyone for the suggestions and recommendations

 

[SteveS]

Don't need a USB-C port. Just use cables that are A to C. That's what we've been doing.

 

[jpk1998]

update?

 

[Nitelife]

Had similar issues with AA and my Pixel phone. It was a bad cable. I got a new cable at Target and have had no further issues.

 

[SturdBurger]

New cable solved the issue it seems like. I didn't need to update the USB harness at this point, but I may still do that in the future.