Android Auto · Kotlin · Side Project November 2026

A Video Player
for My Car

I wanted one small thing: to watch a video on the car's screen while parked and waiting. The apps advertised for it are paid and installed from outside Google Play, so I tried building my own. The code took an afternoon. Getting it onto the dashboard took two weeks, four phones and a detour through the Play Console.

The Idea

My car runs BMW's iDrive 8 and supports Android Auto. Android Auto deliberately has no video apps, because a screen in front of the driver should not play video while the car moves. Google is rolling out official video for parked cars, but it needs a recent phone and support from the car maker, and neither had reached me yet.

So the goal was narrow: a personal app that lists the video files stored on the phone and plays one on the car display, only while the car is standing still. Above walking speed the picture is replaced by a notice and only the sound continues. That rule was in the first version, not added later.

The App Itself

The app is written in Kotlin and is small: a handful of files built on two Google libraries, the Car App Library for everything Android Auto shows, and Media3 for playback. On the phone it has a single screen that asks for permission to read videos. In the car it has a list of files and four buttons: list, previous, play or pause, next.

I am not an Android developer. I described what I wanted to an AI assistant, it wrote the project, and I built it in Android Studio. It compiled on the first try, which told me nothing, because nothing had run in a car yet.

Four Phones Later

I assumed any Android device from a drawer would do for testing. Each one taught me a requirement I had not known about:

→
A tablet. The app installed and found my videos, but Android Auto does not exist on tablets. The car paired with it over Bluetooth for calls and nothing else.
→
An old Galaxy J7. Its Android version is too old for current Android Auto.
→
A Galaxy A12. New enough, but its Wi-Fi is 2.4 GHz only. Wireless Android Auto needs 5 GHz, and my car offers Android Auto only wirelessly, so the USB cable I kept reaching for was never an option.
→
A Redmi Note 8 Pro from 2019. Android 11 and dual-band Wi-Fi. It connected to the car on the first attempt.
Lesson Check the head unit before the phone. Bluetooth only introduces the two devices; the picture travels over a direct 5 GHz Wi-Fi link. A phone that pairs for calls can still be useless for Android Auto.

Installed Is Not the Same as Visible

With a working phone, the app was installed and running, and it still did not appear on the car screen. Android Auto only shows apps it trusts, and trust means the app came from Google Play.

There is a developer setting for apps from unknown sources. On this phone it changed nothing. The other shortcut I tried changed nothing either. Play's internal app sharing, meant for passing a build to a colleague, refused the upload because the app did not exist on Play yet.

What worked was the documented route for testing a car app in a real vehicle: an internal testing track in the Play Console. The app is uploaded as a signed bundle, released to a list of testers that contains exactly one account, mine, and installed from the Play Store like any other app. Nobody else can see or install it. Ten minutes later it was on the dashboard.

Worth saying plainly This is a private test build for one device. Video is not an open app category on Android Auto, so it is not something Google would approve for public release in this form, and I am not distributing it. The internal track exists for testing on your own hardware, and that is all I use it for.

Small Things That Cost a Build Each

→
Target API level. The first upload was rejected because new apps must target the latest Android API level. Two numbers in the build file, one more build.
→
Version codes are single use. I discarded a draft release and uploaded again with the same version code. Play remembers every code it has ever seen, even in a discarded draft.
→
The tester is the phone's account. The tester list has to contain the Google account signed in to the Play Store on the device, which was not the account I develop with.
→
"Can't download" is often just "not yet". Right after publishing, the Play Store showed the app and refused to install it. A few minutes later the same button worked.
→
Xiaomi asks on the phone. Installing from a computer over USB fails with "canceled by user" unless you confirm a prompt on the phone's own screen within a few seconds.

Where It Stands

It works. A cartoon from the public-domain shelves of the Internet Archive played on the car display in a parking garage, with sound through the car speakers. Android Auto keeps its own side panel next to the video on a wide screen, so the picture does not fill the display yet. That is the next thing to look at, along with testing the speed cut-off properly, from the passenger seat, with someone else driving.

The pattern is the same one I keep running into with side projects: the program was the small part. The work was in everything around it, which phone, which radio band, which install path a platform is willing to trust. None of that was in the code, and all of it decided whether the code could run.