# Android Auto Published articles for Android Auto. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## CarPlay And Android Auto From One Codename One API DevFeed: [CarPlay And Android Auto From One Codename One API]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-07-04T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [API](), [iOS](), [LineageOS]() Tags: [android-auto](), [api](), [app](), [apple](), [google]() ### AI overview Codename One adds Apple CarPlay and Google Android Auto support through a portable, template-based API. The build system injects platform-specific wiring only when car support is used, while navigation surfaces remain partly incomplete and deployment still requires platform approval and relevant entitlements. ### Source excerpt Codename One now projects driver-safe app screens to Apple CarPlay and Google Android Auto through one portable template API. ## Hilt in Android Auto: From Manual Factories to a Cleaner Screen Provider DevFeed: [Hilt in Android Auto: From Manual Factories to a Cleaner Screen Provider]() Original publisher: [Read original article]() Author: FunkyMuse Published: 2026-06-05T09:30:00Z Content type: tutorial Language: en Sources: [FunkyMuse]() Topics: [Android](), [Dagger](), [Dependency management](), [App](), [Testing]() Tags: [android](), [android-auto](), [dagger](), [dependency-management](), [di](), [how-to](), [testing]() ### AI overview A tutorial on replacing manual dependency wiring in an Android Auto Car App with compile-time dependency injection using Hilt. It explains using Hilt entry points, screen providers, multibinding, and a central module to reduce constructor boilerplate and improve testability. ### Source excerpt If you've ever followed the Android Auto Codelabs, you've seen the "sample" way of building a Car App. It works, it's functional, but as soon as you try to scale it beyond a simple demo, you hit a wall: Dependency Management. Keep in mind this is only one way to wire things, I'm pretty sure many others exist, I'm exploring things on Android Auto and Android Wear lately and how to connect and w... ## Interpreting voice results for Android media apps in cars DevFeed: [Interpreting voice results for Android media apps in cars]() Original publisher: [Read original article]() Author: Danny Preussler Published: 2022-01-10T21:33:42Z Content type: tutorial Language: en Sources: [Stories by Danny Preussler on Medium]() Topics: [Android](), [App](), [Code](), [Query (disambiguation)](), [Google]() Tags: [android](), [android-app-development](), [android-auto](), [androiddev](), [apps](), [audio](), [callback](), [car](), [code](), [google](), [google-assistant](), [integration](), [manifest](), [voice]() ### AI overview This article explains how Android Auto voice searches are delivered to a music app such as SoundCloud. It compares the documented use of MediaStore.EXTRA_MEDIA_FOCUS with observed behavior, reporting that Assistant currently returns a focus value that is not defined as an SDK constant. ### Source excerpt When working on the Android Auto integration for SoundCloud, I stumbled upon an interesting issue. When it comes to implementing voice actions, things you read in the documentation might differ a bit from reality. Voice commands are very critical while driving a car. You want the driver to keep looking at the street, keep his hands on the steering wheel, instead of interacting with any screen. This is why when building for Android Auto, Automotive OS, and Assistant Driving Mode you have to support basic voice searches. For a music app like ours, the idea is simple. A user can say something like: "Play Moderat on SoundCloud" Under the hood The Assistant will break down our sentence for interpretation: " " The verb (Play) and the app (SoundCloud) in the above command were meant for the system. It will then wake up the app mentioned (if it declared auto support via manifest) and, as we asked for verb "Play", the method MediaSessionCompat.Callback.onPlayFromSearch() will be called with the remaining query ("Moderat") as the argument. This query of "what to play" can still mean different things though. How do you know if Moderat is a band or a song? Don't worry, the Assistant will help us also here. It already got some idea what our query could mean, if we asked for an artist, an album, or a specific track. But be aware, it behaves slightly differently than officially documented. According to documentation we are supposed to write code like this: val mediaFocus = extras?.getString(MediaStore.EXTRA_MEDIA_FOCUS) if (mediaFocus == MediaStore.Audio.Artists.ENTRY_CONTENT_TYPE) { isArtistFocus = true artist = extras.getString(MediaStore.EXTRA_MEDIA_ARTIST) We are suppose to check for a bundle entry with the key MediaStore.EXTRA_MEDIA_FOCUS . This will give us a hint on how best to interpret the query. The value of the constant MediaStore.EXTRA_MEDIA_ARTIST checked above is vnd.android.cursor.item/artist and there are similar constants related to