What do you mean with doggy approach? I am thinking of simulating a keyboard however I have absolutely no experience on usb communication. I should be pretty easy actually if we know how google supports controller buttons.Not really I'm affraid, the only "documentation" we have is what Mike have left inside the code while he reverse engineered the software.... I used a "doggy" approach for keyboard support, namely simulating touches..... while it isn't the most desirable way to do things it works.
I dont plan to use a keyboard but 2 rotary encoders; one for navigation, one for volume control. And I want to put some buttons to switch application.by doggy approach I mean that I'm listening to keypresses and if key M is pressed for example I send a touch_event which correspond to touching the screen where the map icon is. This is all fine, but if you want to use the keyboard to enter letters for example when searching for an address, and you press the M guess what will happen
Having said this my app version is designed for Android devices (tablets) where you don't have a keyboard, yeah you might hook it into a JoyCon to connect it to your car steering wheel remote, but you still won't have a full keyboard.
Android Auto is supposed to be able to handle rotary input, but we are missing the documentation on that...
Your only option to figure this out is by firing AA DHU up and looking at the packets with Wireshark. But the protocol itself is based on Android Open Accessory Protocol with unknown (not really, Mike has figured out a lot of it) commands and logic behind it.
Since Google appears to be permanently banning software based Headunit apps, I am going to have to abandon Google Play as a means of distribution.
I'm guessing that Paypal sales/donations are the way to go.
I've attached the latest June 16 release.
Thanks for all your support !