The phone should not really be relevant if Google were ever to get its act together. My work iPhone 6s serves up Carplay instantly and without issue. Connection problems is a well known issue across all android phones and car infotainment hardware.
The real fact is the update is nothing more then camo for Google to collect more of your data by forcing Maps/Waze to now autostart and give Google high precision location data. I might give them a pass for it if they focused on making their product work as much as they focused on data collection
The difference between Apple & Google is that on the iPhone, Carplay is integrated into the phone's OS. I tried iPhone ACP as a test months ago. Yes, it was great that it instantly worked (and the UI was better than AA). On Android, AA is an App. That means less control of the AA App by Google & by each phone manufacturer & each manufacturer mucks with OS making each configuration slightly different. Apple has the advantage of making both the hardware & software so is in total control of everything except for the stuff on the car. Google has the disadvantage that they don't build most of the Android phone hardware so are not in complete control of the nav "food chain". Google should integrate phone nav into their OS. That's what they are probably doing by moving AA to Google Assistant & G-maps. BTW, there is no forced auto-start of the AA/Maps/Waze.
If you are concerned about Google/Apple knowing your location, don't use a smartphone & use the Afla Nav if you have that option. All phones report location whether or not you are running a nav app.
So, if you like your Apple - keep your Apple. If you like your Android - keep your Android. If you don't like either, use the built-in Nav. If you don't have that option, I guess it's paper maps.
This got off-topic (AA wide-screen & new UI) so I'll guit.