From Dashboard to Driver Display

on YouTube ↗13m

" summary

Demonstrates shipping Android Automotive apps onto non‑Android driver clusters by streaming a chosen activity via H.264 1080p stream using Qt’s ActivityView and QtRemoteSurfaceView, sacrificing touch but keeping latency low; shows a single 3D engine with multiple viewports that renders once and projects synchronized scenes to central and driver displays, used in Mercedes/Hyundai/Ford prototypes; claims very low CPU and RAM on clients with only one background renderer and shows working prototypes across QNX, Automotive Grade Linux and Ubuntu.

AI-written summary · about

" chapters (6)

1. 0:00Automotive dashboard evolution
2. 1:27Large central screens problems
3. 2:50Digital clusters non-Android
4. 4:12Streaming apps to displays
5. 8:52Sharing 3D scenes
6. 12:02Solution benefits

" related talks

• 32mAndroid Auto: Rolling Droid gather no moss (en)Damien Cavaillès · Droidcon Paris 2015
• 38mDeveloping Apps for Android Auto.Arnav Gupta · GDG DevFest Gorky 2017
• 29mHow Android Automotive Helps Us to Design and Build In-Car User ExperiencesCasper Kessels · droidcon Berlin 2022
• 37mAndroid Canvas: Building one of the worlds largest Interactive DataViz exp.Supratim Chakaborty · 360|AnDev 2019
• 37mBuilding One of the World's Largest Interactive Data Visualisation ExperiencesSupratim Chakraborty · droidcon SF 2019
• 44mBuilding and Launching Android Automotive Apps to the App StoreMaxim Lebold, Saverio Labella, Matthias Ostermeier · droidcon Berlin 2024
• 34mBuild apps for Android Auto and Android Automotive OSBen Sagmoe · droidcon Berlin 2024
• 31mSoftware Defined Vehicle and Android Automotive OSMarius Mailat · droidcon Berlin 2024