Spent some time digging into Android SDV, where the car splits into separate VMs and the instrument cluster gets its own renderer (HAR) that draws before Android has even booted. What got me interested is the harder part: how to combine two completely different HMI worlds, SDV Media and Android IVI, into one seamless experience on a single screen, with two separate tech stacks running side by side.
To make sure I understood the whole path, I fed it Doom. The renderer doesn't know what Doom is, it just gets a GL surface node in a Figma-authored UI tree, same as a speedometer.
A few things that surprised me:
- the safety domain runs Rust, not Android, and talks to Android over gRPC across the hypervisor
- the UI is authored in Figma and exported as a design file, not written as code, and it's responsive, the same file adapts to different screen sizes
- all of it is in AOSP and runs in Cuttlefish, no special hardware needed
Full write-up with the details: https://medium.com/@passenger6/i-ran-doom-on-android-sdvs-high-availability-renderer-har-and-learned-how-the-software-defined-e8ccf962311e
Happy to answer questions about the architecture.
submitted by /u/Aggravating-Block336[link] [comments]