Why I built it
The head unit in my car runs Android 11 on a 2017 chip with under 2 GB of RAM. It came with a home screen that looked like nobody had tested it in a moving car: tiny icons, and a clock that was the smallest thing on the display. I cleaned out the extra apps first, then realised memory was never the real problem. I had to squint at that screen at every red light.
What it does
- Drive mode. Above 30 km/h the layout collapses to four large tiles and the speed becomes the biggest thing on screen. It goes back below 18. Two thresholds, because a single one makes the screen flicker in slow traffic.
- Trip stats. A trip is a whole journey, not an ignition cycle, so a drive with a tea stop stays one trip. Average speed counts moving time only.
- Night-friendly look. True black background and app icons that fill their tiles. The speed readout is amber, like an instrument cluster.
- Small. 2.1 MB and no third-party libraries, which suits the hardware.
What went wrong first
It compiled cleanly and looked right on my laptop. On the real panel it crashed three times in the first five minutes. The worst one was invisible: a launcher that crashes inside setup still shows the home screen, which is exactly what a working launcher looks like.
The full story, with the causes, is in the blog post: I Built My Own Android Car Launcher.
Where it stands
Drive mode and trip stats still need real driving to test, so they ride along on the next long trip. The code is public on GitHub.