Minimum Phone Required for a "Good" Experience?

[cz9h3d]

Any suggestions in regards to the minimum phone required for a good Android Auto Experience? Let me preface this by noting I use all 3 phone platforms (have used CarPlay with my iPhone 5S), probably have a preference for Android, but am tired of having a less-than-desirable experience in the Android world.

I have an LG G2, and a Moto X2013, both on Lollipop, that I've used on my OEM vehicle radio. The LG is "spotty" in regards to whether I am even able to use it, let alone have a good experience (sometimes no issues, other times things are slow). The Moto X 2013 is actually probably better (but besides being tiny, the screen has to be on and unlocked each time I connect it to my car).

As I look to potentially upgrade my Android experience - focusing on year-old phones at a good price (Nexus 6, LG Flex 2, etc) - I can't help but think I'm not going to be happy and have a good overall experience unless I pop for a Nexus 6P. And I'm referring mainly to phone (and Android Auto) sluggishness / slowdown.

 

[Phil Nickinson]

I've used a LOT of phones with Android Auto. Generally speaking, anything that doesn't mess with what happens when you connect a phone to a computer. Nexus is best. Motorola, too. (Though they did have weird problems with the Moto E, right?) Samsung seems to have gotten things together, and LG worked fine, last I saw.

I'd avoid Huawei like the plague IRT Android Auto connections.

If there's anything y'all need tested, sing out. I might have it here.

 

[biotron2000]

Nexus 6 worked very well. My LG V10 has to be connected 2-3 times to get AA to start.

 

[Uncle Eliot]

I'm using the Samsung Note 5. What I've found is that I have to use the proper USB cable for AA to connect. Using the cable that came with the phone and waiting 20-30 seconds AA consistently connects.

Out of curiosity I've tried several different USB cables and found that the cable that came with the phone allows AA to start up. This is in a 2016 Honda Accord. AA is great once connected. I'm very pleased with it.

 

[cz9h3d]

LOL - yes, my identification of issues is usually met with the question of whether I'm using the cable that came with my phone - I have a house full of micro USB's and certainly have no idea which one came with my phones! However I am using high quality Anker Powerline cables.

 

[Deputy1]

I just purchased a 2016 Honda Civic Touring Sedan. I'm able to connect my Note 5 with no issues via Bluetooth, but when I go to the smartphone connection screen, it says phone not compatible with voice recognition. I find it hard to believe that the latest flagship phone would be incompatible with Android Auto, but I can't figure it out.

Posted via the Android Central App

 

[Uncle Eliot]

Possibly you missed something because my Note 5 works great on the 2016 Honda Accord.

 

[cz9h3d]

Just sold my LG G2 on Swappa - pretty useless to me if it just doesn't work well with Android Auto. On a positive note, my Moto X 2013 works pretty well.

 

[Deputy1]

Possibly you missed something because my Note 5 works great on the 2016 Honda Accord.

I sure did. It was an error on my part. On the part of the screen that says smartphone connection, that is where Android Auto would connect via the 2.0 usb port. Works like a charm.