[dick_w]

AA is one of the reasons we chose Honda.

What were the reasons you chose your phone?

We have a '16 Civic Touring and an '18 CR-V Touring. Since we got the '16 Civic we've had Nexus 5, 5x, Pixel, and Pixel2 phones. AA has always worked. Some versions of AA on the phone side have been more or less stable. My point is that the Android version, and patches to it, on the phone side also is relevant. And many (most) Android manufacturers/carriers don't give a rip--kinda like Honda.

 

[dick_w]

You are very fortunate to not have the connectivity problems so may other people have.

Agreed. Having phones that get at least some bug fixes for the OS may be part of this. How many Android OS updates have you gotten from HTC? This is in no way entirely, or even primarily, a Honda problem. I understand the HTC10 was a flagship phone the hour it came out. And that there are lots of people with different cars and AA problems.

Some people thought AA would be a magic bullet to get around infotainment obsolescence. But it depends on the auto infotainment core OS and the AA specific code. (Honda has not updated any of this for 5th gen CR-V. Are there bugs in it specific to AA? How would we know? There certainly are non AA-specific bugs in it.) And it depends on the phone OS side of the interface, and the phone makers have to care to fix any bugs there. Most barely care about updating sold phones for security bugs, much less things like the USB and Bluetooth stacks that AA depends on or any AA specific bits in the core OS. It also depends on the AA app on the phone. At least Google has worked issues with it.

Hardware eventually fails. Software eventually works. Unless it's auto infotainment software, in which case you will replace the car before getting updates to make it work.