Please help figuring out EV-features for AndroidAuto

[manio]

Hi Guys,
I am an aa-proxy-rs developer. It's an opensource project for doing a Wireless AndroidAuto proxy between the car and the phone using RaspberryPi. Recently we did some progress and we are able to act as a MITM - modifying the packets on-the-fly and we added some nice features, like changing DPI of the display or disabling audio sinks....

We would love to provide the EV routing functionality in GoogleMaps (for example providing real-time traction battery level using data from OBD) for cars which doesn't have such a features, because they are too old or not updated anymore by manufacturers (like my Renault Zoe EV ).

Our problem is figuring out AndroidAuto protocol with the new EV-routing features which are available eg for your Mach-E cars. As these are relatively new Google features and only for specific cars, it's not common to find such a cars anywhere - to plug the Pi and grab the logs easily by us
That's why we're asking to help here...

The help would consist of:
- grabbing some RaspberryPi (besides Raspberry Pi 3 B+ which is unfortunately not supported)
- flashing prepared SD-card image with with aa-proxy-rs and full logging enabled
- plugging the RPi it to your Mach-E's USB port (for wired AndroidAuto side)
- and connecting any Android Phone wirelessly to the RPi...

We only need a small sample of AA protocol data exchanged. The crucial thing for us is how the car HeadUnit is sending the battery level to Android (how it encapsulates, in what message types, etc). The rest of the protocol is mainly known for us. Google unfortunately doesn't provide a documentation for this and this AndroidAuto protocol is mostly reverse-engineered.

We (and users) would be very grateful for your help, so if you like to help with this, please reply here or contact me directly.

regards!

Sponsored

 

[nlions]

I was with you until right after "Hi Guys"

 

[RickMachE]

Brand new member wants me to give him access to my vehicle. Nope.

 

[rhfritz]

Hi Guys,
I am an aa-proxy-rs developer. It's an opensource project for doing a Wireless AndroidAuto proxy between the car and the phone using RaspberryPi. Recently we did some progress and we are able to act as a MITM - modifying the packets on-the-fly and we added some nice features, like changing DPI of the display or disabling audio sinks....

We would love to provide the EV routing functionality in GoogleMaps (for example providing real-time traction battery level using data from OBD) for cars which doesn't have such a features, because they are too old or not updated anymore by manufacturers (like my Renault Zoe EV ).

Our problem is figuring out AndroidAuto protocol with the new EV-routing features which are available eg for your Mach-E cars. As these are relatively new Google features and only for specific cars, it's not common to find such a cars anywhere - to plug the Pi and grab the logs easily by us
That's why we're asking to help here...

The help would consist of:
- grabbing some RaspberryPi (besides Raspberry Pi 3 B+ which is unfortunately not supported)
- flashing prepared SD-card image with with aa-proxy-rs and full logging enabled
- plugging the RPi it to your Mach-E's USB port (for wired AndroidAuto side)
- and connecting any Android Phone wirelessly to the RPi...

We only need a small sample of AA protocol data exchanged. The crucial thing for us is how the car HeadUnit is sending the battery level to Android (how it encapsulates, in what message types, etc). The rest of the protocol is mainly known for us. Google unfortunately doesn't provide a documentation for this and this AndroidAuto protocol is mostly reverse-engineered.

We (and users) would be very grateful for your help, so if you like to help with this, please reply here or contact me directly.

regards!

Manio,

You had me until you excluded the Pi 3 B+ which is sitting on my desk for another project.

Would using adb logcat on a connected phone be of any use?

Rob

 

[manio]

Manio,

You had me until you excluded the Pi 3 B+ which is sitting on my desk for another project.

Ouch
Raspberry Pi 3 Model B does not have OTG-enabled USB port, which is required for the RPi to run in USB device mode. So this is a hardware limitation in this Pi

Would using adb logcat on a connected phone be of any use?

Rob

thank you Rob, we are thinking... but for the first sight - `logcat` is rather not quite helpful as it gives only very simple logs, not a AA traffic

 

[smhenn]

@manio I have Pi 4 lying around not being used and I'd be happy to assist. DM me and let me know what needs to be done!

 

[godnet23]

Hi,
If I understand correctly, this project does not make sense in Mustang Mach-e, as you can already do wireless AndroidAuto. Is it like this?
Or do you want to build something like carlinkit with a Raspberry Pi?

 

[manio]

If I understand correctly, this project does not make sense in Mustang Mach-e, as you can already do wireless AndroidAuto. Is it like this?

As long as you don't need additional MITM features like `video-in-motion`, DPI changing or enabling Developer Mode to be able to use any AA application - then true - doesn't make sense because you have the Wireless AA out of the box.

Or do you want to build something like carlinkit with a Raspberry Pi?

Yeah, you can say so.

Sponsored