Data on wheels
summary
Panelists argue Android Auto stays focused on infotainment today and does not expose low‑level ECUs or CAN data, while some OEMs run Android on control units and Bosch offers SDKs for HMI integration; Tesla proves OTA updates in minutes for non‑safety systems but suppliers insist ECU updates require workshop-level controls. Security needs a safety‑certified Linux kernel and new threat models for connected sensors; insurers already use black‑box telematics and Germany treats data belongs to driver under German law, with Android Auto limited to infotainment and ongoing work on standard APIs (W3C / OEM efforts).
AI-written summary · about
chapters (18)
- 0:00Android Auto introduction
- 1:11Panelist introductions
- 3:20Tech giants fears in cars
- 6:29Android for car software
- 7:53Startup challenges in auto tech
- 11:26Security in connected cars
- 16:48Data ownership and privacy
- 22:03Insurance and autonomous driving
- 25:35Profits from car data
- 29:49Google’s automotive dominance
- 34:06Android Auto limitations
- 37:15Future of car data access
- 42:32OEMs in-house software
- 45:01Tesla’s OTA updates
- 47:35Standardizing fleet data
- 51:03W3C vehicle API
- 52:53Audience engagement
- 53:14Automotive industry future
related talks
37mGet in the fast lane; Android Automotive OS
31mSoftware Defined Vehicle and Android Automotive OS
35mThe Future of 3rd Party App Ecosystems in Cars
36mLet's get this Droid on the road
18mAndroid in Automotive, the Real Fragmentation
09mWhat's new with Android for cars
41mPanel: Tackling Automotive Hardware Vulnerabilities
48mAn Introduction to Android Automotive OS