Can't Connect Oneplus One to Android Auto in Honda Civic 2016

I am unable to connect my Oneplus One to my Honda Civic 2016's head unit through Android Auto. There are two possible scenarios after plugging in the phone. I either get an error message on my head unit saying a charging error occurred and that I have to verify that I am using an Android Auto compatible phone/cable and the phone won't charge, or the phone charges just fine, but nothing happens on the head unit.

I've tried a lot of things to fix this, possible solutions that have worked for others. For example, I've tried many ROMs, that is Oxygen OS 2.1.4, Cyanogen Mod 13 nightlies, Cyanogen Mod 12.1 with Resurrection Remix and I currently have Resurrection Remix M v5.1.7 installed. None of them have worked. I've tried all the different USB modes, charging only, PTP, MTP, USB Ethernet and MIDI, all of them with debugging on and off. Some people have reported that denying access to messages through Bluetooth have also helped, but no luck for me. I've tried the Oneplus cable and a third party cable, but no luck either. Finally, having started to think the problem might lay with the head unit, I plugged in someone else's phone, a Moto G, and it worked first try, like a charm. I've also tried my phone in a Chevrolet Malibu 2016, no connection there either. Obviously, something's wrong with my phone, but I can't find out what. Any help with this would be appreciated!

Thanks!

2016 Honda Civic - Android-based Headunit - North American version

Hello all,
I've looked through a lot of information online, and am not able to find anything.
Here's the situation, as many of you probably know, the headunit in the 2016 Honda Civic, for all markets - is Android-based.
Another fact that some of you may not know, is that the headunit is the same for both navigation-equiped models (aka Touring) and non-navi models; all of the head-units have a built in GPS, however Honda seems to have disabled the/or not installed the app for Navigation (Garmin-based).
When you fire up the headunit, you have an "Apps" section, which includes the standard stuff - Gallery, calculator, etc, however you also have an "App Installer" app, which looks for APKs.
You can throw an APK onto any USB drive and it will pick it up, however, it will not install - when you select the APK, the installer will be grayed out.
On previous models, (model year 2015), you could get around this by renaming the APK, however that trick does not work on the 2016 North-American trim.

Does anyone know if any progress has been made into this, or how the unit has a "Whitelist" app pool? Perhaps a "package name" approach - i.e. com.honda.navigation - that's contained in some sort of global whitelist?

Any advice is greatly appreciated!
It really irks me when a manufacturer soft-locks features that are already built in, and doesn't even offer you the alternative to unlock them....