Open source and Android Automotive OS
summary
Android Automotive OS sits on AOSP but major pieces are closed: BSPs, VHALs, proprietary codecs and vendor drivers force OEMs to choose between licensing Google Automotive Services (GAS) with extra certifications and update commitments or assembling third‑party stacks that cause API fragmentation. Open efforts include DRM HW composer and Mesa GPU drivers, COVESA work on a VSS vehicle signal standard and unified push, and a community that already has over 1,000 ASPdev members.
AI-written summary · about
chapters (14)
- 0:00Open source and Android Automotive
- 1:05Why open source matters
- 4:34Open vs closed parts
- 7:05Closed-source BSP challenges
- 10:20Building from AOSP
- 11:22Google Automotive Services limits
- 15:55GAS licensing hurdles
- 17:22Fragmentation in non-GAS
- 20:37Kavisa standardizing apps
- 23:24Open source communities
- 27:18Android open source history
- 30:33Google’s open source shift
- 33:20Support open source in Android
- 34:28ASP Devs community
related talks
48mAn Introduction to Android Automotive OS
31mSoftware Defined Vehicle and Android Automotive OS
18mAndroid in Automotive, the Real Fragmentation
37mGet in the fast lane; Android Automotive OS
34mBuild apps for Android Auto and Android Automotive OS
13mPorting Android Automotive on Xen
42mThe Embedded Android Developer's BoF
36mLet's get this Droid on the road
