I use both Android and iOS and they have there pluses and minuses. As stated previously, one you enter the world of Apple, they are in control. Android is a more "open" system but with that comes a little more instability. As far as Android Auto vs CarPlay, I give the edge to Apple. It's seamless and elegant in it's connectivity however it is not as customizable as Android auto. That being said, CarPlay is getting better and better (Waze support, split screen, etc.)

My US phone is a iPhone 12 pro and it works fantastic in my 2017 vette (with Alexa Auto). I rarely use my Ireland Android here in the states but I use it over there quite a bit and it works fine with my Audi, no problem.

Hope that helps,
Mark

 

I have a Moto G7 and connects fast using my usb cable for projection to the infotainment display. The only irritation for me is when I stop someplace and turn the car off. When I get back in I have to open the console lid and open the phone again to connect. In other words, if the phone display goes dark when not used after a minute or so while in the store or whatever, and I have to go through wake up routine. You would think when you start the car the phone would just project to my display. But NO, I have to wake it up.
I don't know if the iphone behaves in that manner or not.

 

This is one of the reasons that I stopped using my Moto G7 in my C7 too.

 

Interesting, thanks.
I would have predicted about a 50-50 split.

 

What do you use now? Another Android model, or an iphone? thanks.

 

Don't do it! I have a 3 yr old android Moto Z force that syncs with my 14 Vette no problem. Make sure you restart your phone once in a while. I had a hard time syncing mine at 1st. I shut the car off, turned off bluetooth on my phone and rebooted it. Started the car, turned on the phone.. It detected the info system right away and has been good ever since..

 

Still the same Motorola moto g7.

 

By and large, both phones are capable of doing the same things. The real difference is the ecosystem you find yourself under. With Apple, you are dictated that "Thou shalt use only Apple", with Android you can use a number of options. If you're a neophyte WRT technology you might use your phone for very limited uses and not try to connect to services and the like in the cloud. Android leans on Google apps/products and services, but you can use other ones. For example, while you can use Google Maps on both Android and iPhones you can't use Apple Maps on Android. Similarly with apps like iMessage, etc (I'm sure there is more but I'm not an iPerson). This contributes to that locked-in feeling with Apple as Apple has no incentive to code up a method for you to leave that walled garden nor will it play nice with such apps. Apple generally doesn't care about you unless you drink that Kool-Aid. On Android, you can rely on all the Google services or venture out to other apps - your choice. With Apple you use Apple only, no choice. I've always viewed this is being stuck up.

I don't understand this "pro". I can as easily say that Google products work with Google products. So what. What you are missing is the word "only" as in Apple products only work with Apple products (generally true, not 100% true).

It generally is difficult because Apple doesn't make any effort to make such a transition possible. It's like that proprietary vs open source argument.

But the other argument implied above is payment. In my approximately 12 years of using Android, aside from buying the phone, the grand total of my purchases on apps for Android is under $10 - 12 years - $10. I think this sums it up for me:




I wish we had a better definition of "connect" here. By connect do we mean connect via Bluetooth? Or connect to Android Auto/CarPlay? For Bluetooth, as I understand it, it's a handshaking and polling kinda thing. The car's Bluetooth and the phone periodically check for new connections to make. They do this at some interval, let's say 30 seconds. So if you enter the car and the count is at 28 seconds you'll connect quickly. If it just cycled around 1 again you're gonna have to wait.

Another factor is the Bluetooth driver. It's continuously updated so if you have an older version of Android it could be that that Bluetooth driver has not been updated and if you update to a newer version of Android your problems will go away.

As for the connection to AA (not as versed in CP) I've noticed that after plugging in the USB cable AA will not project until at least the Bluetooth has connected. However, lately, the newer versions of AA seem to connect very quickly, at least starting to play Media almost as soon as connected. I'm not sure if the newer versions of AA update on older versions of Android. I'm on Android 10.0.

 

I have a 2014 Z-51 and have no problems sync up with an Android phone but to play music I do use a Music player app Pi Music player