An Introduction to Android Automotive OS
summary
Android Automotive OS ships in production cars like Polestar 2 and is available from AOSP but the open build is not production ready — default home and apps are placeholders and manufacturers must implement working HVAC, nav and backend services. Vehicle integration uses a VHAL exposing ~150 vehicle properties over binder to a car service and android.car.jar; many permissions are signature/privileged so only system apps may toggle doors or windows. Cameras use a separate EVS so rear-view must appear within 2s; audio uses multiple output “buses” and chimes are routed outside Android.
AI-written summary · about
chapters (22)
- 0:00Intro
- 3:09The Android Open Source Project
- 4:18Google Automotive Services (GAS)
- 6:01Architecture of Android Automotive
- 8:03Vehicle HAL
- 9:41System Property Identifiers
- 12:29Properties
- 15:12Car service
- 15:57Car Manager
- 17:44Digression: Android permissions
- 23:49Instrument cluster display
- 25:53Third party apps
- 28:19Developing for Automotive
- 29:21Automotive AVD
- 30:23Exterior cameras
- 34:14Typical control flow
- 35:15Display sharing
- 35:59What is special about audio in vehicles?
- 36:57Automotive sounds and streams
- 38:49Audio contexts
- 39:05Physical streams, contexts and buses
- 41:05Conclusion
related talks
37mOpen source and Android Automotive OS
37mGet in the fast lane; Android Automotive OS
34mBuild apps for Android Auto and Android Automotive OS
31mHow to build Android apps for cars
18mAndroid in Automotive, the Real Fragmentation
14mHow to Build Android Apps for Cars
31mSoftware Defined Vehicle and Android Automotive OS
36mLet's get this Droid on the road