Honda Civic 2016 and Android Auto

just1ncase17

New member
Nov 22, 2016
1
0
0
I'm looking to get a Google Pixel to use the Android Auto experience in my Honda Civic 2016. I was wondering if there's anyone in this forum who has any experience (positive/negative) to fill me in on what to expect.

Currently, I have an iPhone 6 and tried playing around with Carplay, but I dislike Apple Maps. Based on my experience, Apple Maps does not provide accurate directions or traffic information in comparison to Google Maps. Carplay has been glitchy and very inconsistent while I'm driving.

With that being said, am I going to experience the same thing? or is it worth the switch (me being a loyal Apple iPhone user since the iPhone 4 came out)? I've carefully searched the forum to see any information before posting this and the consensus seemed to be mixed and some of the posts are old. So, I'm hoping to find out if there has been any improvements on AA since then.

Thanks and I appreciate your help. :)
 
I can't directly address your concern from Honda experience standpoint, but I can tell you that my Pixel XL with Android Auto works great with both my 2016 Chevrolet and my wife's 2016 Ford Edge. Google maps works flawlessly (for me). Your music experience with Android vs iPhone might take some getting used to, though.
 
AA worked perfect in my 2016 Honda Civic with both a Pixel and all Moto Phones.
 
I have a 2016 Honda Civic and I used CarPlay before getting my Pixel. In my opinion Android Auto is much better than CarPlay. I like the interface much better. The buttons for the main functionality (Navigation, Phone and Music) are always in the same place even if you are in an app. With CarPlay when you want to switch apps you have to hit the home button and then find your app from a grid of icons (possibly having to swipe to a new page as well). I haven't had any glitches with AA. On the other hand, I had a consistent problem with CarPlay where if my phone was plugged in to the lightning cable when I was first starting the car, more times than not I would get an error stating that my phone was not compatible with CarPlay. I would have to unplug and replug the phone in to get it to work. Very annoying.
 
I have an LG G4 connected to a 2016 Hyundai Sonata Hybrid. Connecting it was not too difficult. I am disappointed that AA requires a USB connection instead of Bluetooth. My phone requires 2.1a to fully charge. The car USB output is half that. For any trip of distance, the phone will go dead. Using the phone , connected to the cars audio/nav system via Bluetooth, I can use a quick charger and not have the phone go dead. It's a great idea getting to use the 8" screen in the car, but not if the phone goes dead.
 
Have you ever experienced 'map stops refreshing' addressed by Google? https://support.google.com/androidauto/answer/6395843?hl=en Some people reported that it has been fixed in the recent OTA update. Did you receive it? I noticed that in AA 2.0, things are better but I haven't tried the navigation out. I'm heavily relying on navigation, and if it goes wrong, I will be in a complete panic. Because of the 'map stops refreshing' issue, I am currently using a backup phone as a GPS.
 

Members online

Forum statistics

Threads
954,016
Messages
6,960,263
Members
3,162,898
Latest member
dkpiper