No longer connecting after Marshmallow update

[jonesyvoor]

Updated to Marshmallow today with my Verizon Galaxy Note 5 and plugged in my phone and Android Auto didn't launch.

Anyone else have issues after updating?

Posted via the Android Central App

 

[Uncle Eliot]

I had the same issue.

Go to Settings/Developer Options/USB Configuration
Click on the USB Configuration and then click MTP

See if that helps.

 

[stephendaviscxo]

I have the same problem with my HTC M9 and 2015 Sonata. I tried that fix and it didn't work.

 

[jonesyvoor]

It doesn't seem to stay on MTP. It always defaults back to charging. When I do switch it back to MTP it does seem to recognize Android Auto but I get a message on my phone telling me to park my car, even when it's parked.

Honestly I think I have a corrupt version of Marshmallow. My WiFi reception is bad, my battery is draining faster and my notifications aren't working right.

Posted via the Android Central App

 

[Uncle Eliot]

Mine doesn't stay on MTP either so I make the change before driving off. Then AA immediately starts up. Maybe someone knows of a fix or Google will straighten it out. I had few issues prior to the update.

 

[anon(187199)]

Its not google's problem. Its samsung or htc or whomever modified 6.0. AOSP roms don't have these issues.

 

[scott_0]

Its not google's problem. Its samsung or htc or whomever modified 6.0. AOSP roms don't have these issues.

Im not so sure its a Samsung problem either, could be a vehicle manufacturer problem. I just got my S7 last night, I was scared it wasnt going to work with Android Auto on my Pioneer 8100nex, I went through the setup process and permissions, no issues what so ever for me here! I tested it by disconnecting, and reconnecting and it auto started with no issues. I did make sure USB debugging was enabled, and I didnt have to mess with the MTP setting at all, it was already set to MTP and stays set to that. and it could be placebo, but the S7 seems to sound better over AA than my S7 did