[Android General] donaldta:
I can tell you absolutely for sure that it will not affect your cruise control buttons. Those buttons are routed into your car's ECU so that it facilitates cruise control. The media buttons on your steering wheels are routed to your radio. The Axxess ASWC-1 (all SWC adapters actually) are designed to intercept the connections from your old stereo and convert the signals to the appropriate for the new head unit. So, unless the Cadillac designers were smoking crack and drunk while designing your car, those cruise control signals should not go any where near your radio.

What year is your Cadillac CTS-V? I am assuming it is 2007 by the url of the picture that you linked. For some reason, I cannot pull up instructions for any year older than 2009 at the website for Axxess' ASWC/ASWC-1 Vehicle Instruction Guide. For the newer models, it has a link to GM 44 way wiring instructions but nothing comes up for 2007 or older.

I got my Axxess USB-CAB and AX-SWC-PARROT cables today. Since the SWC that came with the ASWCSTALK has a 4 pin UART connector, I was able to confirm that it was the original ASWC since the ASWC-1 has a built-in micro USB port instead. Anyways, I was only able to update it from version 2.28 (7/10/12) to 2.29 (11/20/12). Unfortunately, this is not current enough to contain the "PARROT radio type for autodetection (Type #14)" from version 3.17 (10/18/13). It is pretty sad that the original SWC hasn't been updated for over a year. Guess that I'll have to bring this up with technical support again. *sigh*

Incidentally, I installed it on the Parrot Asteroid Smart anyways but it won't only detect the head unit as Eclipse and the Asteroid Smart would not connect with it. But, I assumed it wasn't going to work since I was not able to update the ASWC to the current version.

---------- Post added at 07:13 PM ---------- Previous post was at 07:12 PM ----------

On a sidenote, I upgraded to v2.1.5 on my Asteroid Smart today and it was pretty much a pain in the ass. It wouldn't complete the process unless I removed all the unnecessary connection except for the flash drive that had the PLF file. The first attempt, it wouldn't not reboot after the last bar filled. I let it sit there for a half-an-hour and it would not boot. Anyways, I called Parrot's tech support and explained what happened and without even trying to troubleshoot, he said that I probably bricked the unit then gave me instructions to brute force an install. And said if that didn't work to send an email to parrot support to arrange for a swap. *le sigh*

Anyways, at that point it was an hour later and so I rebooted. It automatically restarted the update process over again but still would not complete. It worked on the third time around, but by then I had removed just about everything from the USB and SWC ports except for the flash drive. This time it completed. So, I avoided having to send the unit in. Then after the system had rebooted I had noticed that all my modifications in the /system directory was gone. I had to restore them, it is a good thing I kept a backup of most of them.

Afterwards, I found a problem with the Google Play. It would not load completely. Turns out that there was a problem with com.google.android.gsf (Google Framework). After, I connected to the system to ADB, I found out that it would not install or work due to shared user incompatibilities. After I checked "dumpsys packages", I found out that it was conflicting with the shared user associated with com.google.android.gms (Google Play Services). All it took to install Google Framework was to uninstall Google Play Services. Oddly enough, I was able to reinstall Google Play Service after Google Framework and it did not complain about shared user incompatibilities. I cannot get my head around why that is, but whatever.

At least the the system appears to be a little more stable, even though it took me a while to get it back to "normal" ...at least by my standards.