Leapmotor: found an internal AutoSDK
I have been experimenting with the Leapmotor C10 infotainment system. It runs Android 11 under Leap OS, and I was able to install App Manager on it. From there, I extracted some APKs and found references to what appears to be an internal, non publicly documented vehicle SDK.
I built a small proof of concept app, and it can already communicate with the car through this SDK. So far I can read things like:
- Speed
- SOC
- Range
- Gear
- Charging status
- GPS / NMEA
- Some HVAC and vehicle properties
- Model info
- Callback based updates and polling
Screenshot attached.
My question for people familiar with openpilot internals:
Assuming the vehicle SDK can be mapped properly, would it be technically realistic to adapt openpilot, panda, or parts of the openpilot stack into a standalone Android application running on the car head unit?
I understand openpilot is normally built around comma hardware, Linux, panda, CAN access, safety hooks, controls, model execution, logging, UI, and a very specific safety architecture. I am not trying to bypass safety or immediately control the car from Android. I am trying to understand the architecture path.
Has anyone tried using an OEM Android head unit SDK as the vehicle interface layer for openpilot research?
To be clear: this is currently read only. I am looking for guidance on feasibility and architecture before touching anything safety critical.