How Did You Cook It? About Honda’s AOSP-Based IVI (in-Vehicle Infotainment) System
summary
Honda builds an in‑house IVI stack based on AOSP and OSS, starting from a two‑person team to a global effort that ships in a production Accord, using Android 11 LTS lines and vendor kernel work to meet vehicle constraints. The project applies OpenChain (ISO/IEC 5230) self‑certification, generates an SPDX Lite SBOM, measures boot and audio latency, minimizes OSS customization, and reports that the system meets Honda quality targets and launch timelines.
AI-written summary · about
chapters (13)
- 0:00Honda’s IVI software intro
- 4:47Honda’s in-house platform
- 7:56Honda’s dev culture
- 13:30Development speed challenges
- 17:15AutomotiveSPICE processes
- 20:21Coding standards & static analysis
- 22:59AOSP boot time optimization
- 25:31AOSP LTS importance
- 28:20GKI config challenges
- 30:55Audio input sharing
- 32:34EMMC flash monitoring
- 34:04Open source compliance
- 35:56Final message
related talks
41mHow Did You Cook It? About Honda’s AOSP-Based IVI (in-Vehicle Infotainment) System
36mChallenges developing an Android based system for 2-wheel …
37mOpen source and Android Automotive OS
48mAn Introduction to Android Automotive OS
28mXen in OSS based In--Vehicle Infotainment Systems
07mKeynote: Honda’s Journey and Challenges Toward Software-Defined Vehicles
26mLinux in Cars: So What?
49mOpen Source in Every Car with Automotive Grade Linux