Bringing Android 13 to Tesla vehicles with Flutter Web
summary
A Chromium gateway hosts a full Android 13 build that streams a hardware‑encoded virtual display over WebSockets to a Flutter Web frontend, using a headless DRM display and Broadcom encoder for low CPU overhead. Networking uses a 5 GHz AP, DNS spoofing and iptables; audio streams 48 kHz PCM to the browser; USB tethering and GPS are proxied into Android. Prototype becomes a packaged image for Raspberry Pi install in 15 minutes, is GPL3 open source, has ~5,000 daily active users and a bug that cost four months and 200 comments.
AI-written summary · about
chapters (14)
- 0:00Introduction and speaker
- 1:30Why Flutter for Tesla infotainment
- 3:15Hardware and proof of concept
- 5:45Next steps and deployment
- 7:31Core system components
- 10:20Android framework modifications
- 12:07Flutter front-end challenges
- 13:56Virtual display and WebGL
- 16:02Touchscreen and audio streaming
- 17:27GPS and Android port integration
- 18:31Android port and development process
- 20:15CI and testing setup
- 21:19Results and community impact
- 22:47Conclusion and future
related talks
08mPavel Guzhikov at RIT++ 2012
05mLightning Talk: Flutter Based Instrument Cluster App for Automotive Grade Linux
13mRevolutionizing Smart Device Interfaces with Flutter: Any Screen, Any...
37mFlutter at scale
48mDart, I'm your Flutter
06mLightning Talk: Flutter Based Applications for IVI Dashboard
36mFlutter-Google's latest innovation for mobile, web, and desktop apps
34mAndroid with a side of Flutter, please