Google SDV: Missed Chance or Game Changer? — An External View on AAOS SDV

Google has recently released Android 17 and, with it, the AAOS Software-Defined Vehicle (SDV) stack.

We've read all the docs. We've looked at all the source code. We've had many questions.

We're bringing most of the answers — and an honest, external view on SDV's opportunities and shortcomings, from a team that has been working on AAOS since its earliest days.

Come to our talk if you've ever wondered:

1. What hardware runs AAOS SDV — and where do multi-VM, VirtIO and hypervisors fit in?
2. How do Vehicle HAL and the new SDV services relate — replace, layer, or coexist?
3. What is the service catalog, and how do VSIDL, AIDL, protobuf and SOME/IP come together?
4. What is changing in the tooling: ASfP, Cuttlefish, Rust, modular OTA?

We close with a summary and our evaluation:

- What is still missing — can SDV cover all your ECUs today?
- What already works well?
- What still needs to improve?
- Which OEMs are likely to adopt SDV — and which probably won't?