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 Android 11/12 qpr3 and upstream Linux LTS kernels, starts the software effort with started with two people and scales to two development sites, and ships the first production IVI in an Accord with responsive UX and multi‑speaker audio across 32+ outputs. Tooling choices include OpenChain and SPDX Lite for license compliance and an Excel‑based SBOM, workarounds for GKI kernel constraints, audio input sharing fixes, and eMMC write‑size tuning to meet automotive reliability.
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
50mHow To Accelerate Software Defined Vehicle(SDV) With OSS
42mAccelerating Software Defined Vehicles Through Open Source Software
36mChallenges developing an Android based system for 2-wheel …
49mOpen Source in Every Car with Automotive Grade Linux
23mAutomotive Crowdsourcing
48mAn Introduction to Android Automotive OS
07mKeynote: Honda’s Journey and Challenges Toward Software-Defined Vehicles