Well... my phone's battery calibration seems to be utterly off, as it has died on me a few times now between an indicated 10-20% battery. I didn't even know this was a thing until now, but according to some random websites a few 0-100 cycles while staying at both extremes should fix that
I never really charge the thing to a full 100% or empty it below say 15%, so maybe that's why it happened. First charge to a full 100% (not 99 or sth) already showed there was something off, since it took about an hour until it finally ticked over from 99 to 100% - I still left it charging for another two hours or so and had it play a 10hr nyan cat video at max brightness last night until it shut off from an empty battery (some time in the middle of the night), as supposedly keeping it empty for a few hours also helps. Now slowly creeping back towards 100%, I'm interested to see whether the last % will again take ages or not...
That' funny, my old phone WAS a Moto G 5 and I had no real problem with the occasional slowdown...
You'd think the entire processing etc. was happening on the phone with AA/CP, but maybe the uselessness was due to the headunit? automotive types and software usually aren't a great match, so I'd totally expect them to be able to create a horrible user experience despite the fact that the entire content is being delivered from a phone...
May have just been that in that particular case the CP integration was done much better than the AA integration - if that's at all possible.
Need to buy some usb A cables first though...
If you don't mind me asking: why? Simply curious... for charging or is it a necessity for CP?