# Android Auto

Android Auto is a phone-integrated system that connects an Android phone to a compatible car, bringing apps to the car display for interaction through the screen and voice actions.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Android Auto Not Connecting After One UI 9? Google Has a Fix for Galaxy Phones

DevFeed: [Android Auto Not Connecting After One UI 9? Google Has a Fix for Galaxy Phones](<https://devfeed.tech/articles/android-auto-not-connecting-after-one-ui-9-google-has-a-fix-for-galaxy-phones-116229.md>)

Original publisher: [Read original article](<https://www.techrepublic.com/article/news-android-auto-one-ui-9-fix/>)

Author: TechRepublic Staff

Published: 2026-11-04T09:38:03Z

Content type: news

Language: en

Sources: [TechRepublic](<https://devfeed.tech/sources/techrepublic.md>)

Topics: [Android Auto](<https://devfeed.tech/topics/android-auto.md>), [Android](<https://devfeed.tech/topics/android.md>), [Google](<https://devfeed.tech/topics/google.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-17](<https://devfeed.tech/tags/android-17.md>), [android-auto](<https://devfeed.tech/tags/android-auto.md>), [android-auto-troubleshooting](<https://devfeed.tech/tags/android-auto-troubleshooting.md>), [bluetooth](<https://devfeed.tech/tags/bluetooth.md>), [firmware](<https://devfeed.tech/tags/firmware.md>), [galaxy](<https://devfeed.tech/tags/galaxy.md>), [galaxy-s24](<https://devfeed.tech/tags/galaxy-s24.md>), [galaxy-s25](<https://devfeed.tech/tags/galaxy-s25.md>), [galaxy-s26](<https://devfeed.tech/tags/galaxy-s26.md>), [galaxy-software-updates](<https://devfeed.tech/tags/galaxy-software-updates.md>), [google](<https://devfeed.tech/tags/google.md>), [guide](<https://devfeed.tech/tags/guide.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [news](<https://devfeed.tech/tags/news.md>), [one-ui-9](<https://devfeed.tech/tags/one-ui-9.md>), [operating-systems](<https://devfeed.tech/tags/operating-systems.md>), [samsung](<https://devfeed.tech/tags/samsung.md>), [samsung-galaxy](<https://devfeed.tech/tags/samsung-galaxy.md>), [usb](<https://devfeed.tech/tags/usb.md>)

### AI overview

Google confirmed on Nov. 2 that a fix was rolling out for Android Auto connection failures reported after Galaxy phones received Android 17-based One UI 9. Users described failed or repeatedly dropping connections, including over USB; complaints involved Galaxy S26 and A55 devices, while one comparison found a One UI 9 S24 Ultra failing and a One UI 8.5 S25 Edge connecting. This suggests a possible software-related issue but does not establish its cause or prevalence. Google gave no delivery method, affected-device list, or completion date. While waiting, Samsung recommends restarting and updating the phone, clearing Android Auto's cache, and checking Bluetooth pairing. Samsung says One UI 8 defaults USB to charging only; select "Transferring files / Android Auto" from the USB notification. Google also recommends checking the cable and vehicle settings, restarting infotainment, and updating aftermarket receiver firmware. These checks may rule out common problems but are not confirmed fixes for the One UI 9 issue.

### Source excerpt

Some Galaxy owners report failed connections even over USB. Google's fix is rolling out, but its delivery method and completion date remain unclear. The post Android Auto Not Connecting After One UI 9? Google Has a Fix for Galaxy Phones appeared first on TechRepublic.

## NEMESIS Gives You Control Over Your Hyundai Head Unit

DevFeed: [NEMESIS Gives You Control Over Your Hyundai Head Unit](<https://devfeed.tech/articles/nemesis-gives-you-control-over-your-hyundai-head-unit-113295.md>)

Original publisher: [Read original article](<https://hackaday.com/2026/11/02/nemesis-gives-you-control-over-your-hyundai-head-unit/>)

Author: Navarre Bartz

Published: 2026-11-03T06:00:35Z

Content type: news

Language: en

Sources: [Hackaday](<https://devfeed.tech/sources/hackaday.md>)

Topics: [Android Auto](<https://devfeed.tech/topics/android-auto.md>)

Tags: [android-auto](<https://devfeed.tech/tags/android-auto.md>), [apple-carplay](<https://devfeed.tech/tags/apple-carplay.md>), [car-hacks](<https://devfeed.tech/tags/car-hacks.md>), [hacks](<https://devfeed.tech/tags/hacks.md>), [hyundai](<https://devfeed.tech/tags/hyundai.md>), [infotainment](<https://devfeed.tech/tags/infotainment.md>), [infotainment-hack](<https://devfeed.tech/tags/infotainment-hack.md>), [navigation](<https://devfeed.tech/tags/navigation.md>), [ota](<https://devfeed.tech/tags/ota.md>)

### AI overview

NEMESIS uses a flaw in Hyundai's over-the-air update system to unlock features on supported Gen5W head units. It may enable wireless Android Auto or Apple CarPlay and show their turn-by-turn navigation cues on the driver cluster and heads-up display. The excerpt says many Hyundai and Kia vehicles from 2015-2019 use Gen5W, but the exploit requires an OTA-capable unit whose software version contains "S5W_M"; "S5W_L" is unsupported. Listed exceptions include the Hyundai Elantra, Kia Forte, Hyundai Ioniq 6, and Canadian vehicles using the system.

### Source excerpt

Whether it's to make more money or because of licensing disagreements, car companies often restrict the abilities of the infotainment units in their vehicles. They can do so much more, ...read more

## CVE-2026-118610 - Alpine iLX-F511 Android Auto Service Stack-based Buffer Overflow Remote Code Execution Vulnerability

DevFeed: [CVE-2026-118610 - Alpine iLX-F511 Android Auto Service Stack-based Buffer Overflow Remote Code Execution Vulnerability](<https://devfeed.tech/articles/cve-2026-118610-alpine-ilx-f511-android-auto-service-stack-based-buffer-overflow-remote-code-execution-vulnerability-105370.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-118610>)

Author: cvefeed.io

Published: 2026-10-28T17:18:28Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [Android Auto](<https://devfeed.tech/topics/android-auto.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [allows](<https://devfeed.tech/tags/allows.md>), [alpine](<https://devfeed.tech/tags/alpine.md>), [android](<https://devfeed.tech/tags/android.md>), [android-auto](<https://devfeed.tech/tags/android-auto.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [buffer-overflow](<https://devfeed.tech/tags/buffer-overflow.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [context](<https://devfeed.tech/tags/context.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-118610](<https://devfeed.tech/tags/cve-2026-118610.md>), [data](<https://devfeed.tech/tags/data.md>), [devices](<https://devfeed.tech/tags/devices.md>), [execution](<https://devfeed.tech/tags/execution.md>), [exploit](<https://devfeed.tech/tags/exploit.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [remote-code-execution-vulnerability](<https://devfeed.tech/tags/remote-code-execution-vulnerability.md>), [service](<https://devfeed.tech/tags/service.md>), [stack](<https://devfeed.tech/tags/stack.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

CVE-2026-118610 is rated high (8.8) and affects the Android Auto service on Alpine iLX-F511 devices. The description says a network-adjacent attacker needs no authentication to exploit improper validation of user-supplied data length before it is copied into a fixed-length stack buffer. Successful exploitation can execute arbitrary code as root. The excerpt does not identify affected versions.

### Source excerpt

CVE ID :CVE-2026-118610 Published : Oct. 28, 2026, 5:18 p.m. | 1 hour, 56 minutes ago Description :Alpine iLX-F511 Android Auto Service Stack-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Alpine iLX-F511 devices. Authentication is not required to exploit this vulnerability. The specific flaw exists within the Android Auto service. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-29015. Severity: 8.8 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## ZDI-26-827: (0Day) (Pwn2Own) Alpine iLX-F511 Android Auto Connection Handler Stack-based Buffer Overflow Remote Code Execution Vulnerability

DevFeed: [ZDI-26-827: (0Day) (Pwn2Own) Alpine iLX-F511 Android Auto Connection Handler Stack-based Buffer Overflow Remote Code Execution Vulnerability](<https://devfeed.tech/articles/zdi-26-827-0day-pwn2own-alpine-ilx-f511-android-auto-connection-handler-stack-based-buffer-overflow-remote-code-execution-vulnerability-106023.md>)

Original publisher: [Read original article](<http://www.zerodayinitiative.com/advisories/ZDI-26-827/>)

Published: 2026-10-28T05:00:00Z

Content type: news

Language: en

Sources: [Zero Day Initiative](<https://devfeed.tech/sources/zero-day-initiative.md>)

Topics: [Exploit](<https://devfeed.tech/topics/exploit.md>), [Android Auto](<https://devfeed.tech/topics/android-auto.md>)

Tags: [alpine](<https://devfeed.tech/tags/alpine.md>), [android](<https://devfeed.tech/tags/android.md>), [android-auto](<https://devfeed.tech/tags/android-auto.md>), [buffer-overflow](<https://devfeed.tech/tags/buffer-overflow.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [pwn2own](<https://devfeed.tech/tags/pwn2own.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

The Alpine iLX-F511 has a stack-based buffer overflow in its Android Auto connection handler: user-supplied data is copied into a fixed-length stack buffer without proper length validation. A physically present attacker needs no authentication and could exploit the flaw to execute code as root. ZDI assigns CVE-2026-118609 and a CVSS rating of 6.8. The advisory says the salient mitigation is to restrict interaction with the product; it provides no fix details.

### Source excerpt

This vulnerability allows physically present attackers to execute arbitrary code on affected installations of Alpine iLX-F511 devices. Authentication is not required to exploit this vulnerability. The ZDI has assigned a CVSS rating of 6.8. The following CVEs are assigned: CVE-2026-118609.

## ZDI-26-828: (0Day) (Pwn2Own) Alpine iLX-F511 Android Auto Service Stack-based Buffer Overflow Remote Code Execution Vulnerability

DevFeed: [ZDI-26-828: (0Day) (Pwn2Own) Alpine iLX-F511 Android Auto Service Stack-based Buffer Overflow Remote Code Execution Vulnerability](<https://devfeed.tech/articles/zdi-26-828-0day-pwn2own-alpine-ilx-f511-android-auto-service-stack-based-buffer-overflow-remote-code-execution-vulnerability-106024.md>)

Original publisher: [Read original article](<http://www.zerodayinitiative.com/advisories/ZDI-26-828/>)

Published: 2026-10-28T05:00:00Z

Content type: news

Language: en

Sources: [Zero Day Initiative](<https://devfeed.tech/sources/zero-day-initiative.md>)

Topics: [Exploit](<https://devfeed.tech/topics/exploit.md>), [Android Auto](<https://devfeed.tech/topics/android-auto.md>)

Tags: [alpine](<https://devfeed.tech/tags/alpine.md>), [android](<https://devfeed.tech/tags/android.md>), [android-auto](<https://devfeed.tech/tags/android-auto.md>), [buffer-overflow](<https://devfeed.tech/tags/buffer-overflow.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [pwn2own](<https://devfeed.tech/tags/pwn2own.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

The Alpine iLX-F511 Android Auto service has a stack-based buffer overflow that network-adjacent attackers can exploit without authentication. The flaw is failure to validate the length of user-supplied data before copying it into a fixed-length stack buffer, allowing code execution as root. ZDI rates it CVSS 8.8 and assigns CVE-2026-118610. The advisory says the salient mitigation is to restrict interaction with the product; it describes the case as a 0-day.

### Source excerpt

This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Alpine iLX-F511 devices. Authentication is not required to exploit this vulnerability. The ZDI has assigned a CVSS rating of 8.8. The following CVEs are assigned: CVE-2026-118610.

## Google Play now lets anyone build private, vibe-coded apps that run on Android

DevFeed: [Google Play now lets anyone build private, vibe-coded apps that run on Android](<https://devfeed.tech/articles/google-play-now-lets-anyone-build-private-vibe-coded-apps-that-run-on-android-86019.md>)

Original publisher: [Read original article](<https://techcrunch.com/2026/10/13/google-play-now-supports-private-vibe-coded-apps-built-just-for-you/>)

Author: Sarah Perez

Published: 2026-10-13T17:00:00Z

Content type: news

Language: en

Sources: [TechCrunch | AI News & Artificial Intelligence](<https://devfeed.tech/sources/techcrunch-ai-news-artificial-intelligence.md>)

Topics: [Google Play](<https://devfeed.tech/topics/google-play.md>), [Android](<https://devfeed.tech/topics/android.md>), [Android Auto](<https://devfeed.tech/topics/android-auto.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [android](<https://devfeed.tech/tags/android.md>), [app-development](<https://devfeed.tech/tags/app-development.md>), [apps](<https://devfeed.tech/tags/apps.md>), [future-of-apps](<https://devfeed.tech/tags/future-of-apps.md>), [google](<https://devfeed.tech/tags/google.md>), [google-ai-studio](<https://devfeed.tech/tags/google-ai-studio.md>), [google-play](<https://devfeed.tech/tags/google-play.md>), [vibe-coding](<https://devfeed.tech/tags/vibe-coding.md>)

### AI overview

Google Play now lets users run AI-created personal Android apps privately on their own devices without publishing them publicly. The apps must still follow Play policies, and Google plans to add sharing with trusted groups. The article also describes upcoming Play Store features for game discovery, community interaction, app comparisons, and age-appropriate experiences.

### Source excerpt

Google is making it easier to build and use personal Android apps created with AI, without having to make them available to everyone on the Play Store.

## How to bring an Android game to Android Auto and Android Automotive OS

DevFeed: [How to bring an Android game to Android Auto and Android Automotive OS](<https://devfeed.tech/articles/bring-your-android-game-to-the-car-screen-today-57434.md>)

Original publisher: [Read original article](<https://android-developers.googleblog.com/2026/09/bring-android-game-to-car-screen.html>)

Author: Android Developers (noreply@blogger.com)

Published: 2026-09-21T16:00:48Z

Content type: tutorial

Language: en

Sources: [Android Developers](<https://devfeed.tech/sources/android-developers-blog.md>)

Topics: [Android Auto](<https://devfeed.tech/topics/android-auto.md>), [Android](<https://devfeed.tech/topics/android.md>), [Google Play](<https://devfeed.tech/topics/google-play.md>), [Mobile](<https://devfeed.tech/topics/mobile.md>)

Tags: [adaptive](<https://devfeed.tech/tags/adaptive.md>), [android](<https://devfeed.tech/tags/android.md>), [android-15](<https://devfeed.tech/tags/android-15.md>), [android-auto](<https://devfeed.tech/tags/android-auto.md>), [developers](<https://devfeed.tech/tags/developers.md>), [google-play](<https://devfeed.tech/tags/google-play.md>), [how-to](<https://devfeed.tech/tags/how-to.md>)

### AI overview

This tutorial explains how developers can adapt an existing Android game for car screens now that games on Android Auto and Android Automotive OS are generally available. It covers manifest configuration, Android Auto support declarations, Google Play distribution tracks, and restrictions for parked-only apps.

### Source excerpt

Posted by Jan Kleinert, Developer Relations Engineer, Android for Cars Today, the games category for Android Auto and cars powered by Android Automotive OS with Google built-in is officially graduating from beta to general availability. Our early access partners have already been bringing games to the parked-only experience for cars, and you can browse these in our latest collections of games for Android Auto and games for Android Automotive OS. Bringing your game to cars lets you reach users in their vehicles during natural downtime, such as while waiting at a charging station or for a curbside order pickup. Today's milestone means that we're opening up access so developers can now publish games to the open testing and production tracks on Google Play. In this post, we'll cover how to adapt your existing Android game for the car screen, focusing on key technical requirements and publishing criteria. Implement car support for your game If you're already following best practices for building adaptive apps, bringing an existing Android game to cars primarily involves configuring your app manifest and ensuring your game respects the vehicle parked state. Mark your app as a game To distribute your app in the games category, you need to explicitly declare its category. Add the android:appCategory="game" attribute to the <application> element of your manifest file: <application ... android:appCategory="game"> ... </application> Declare support for Android Auto Games are supported on Android Auto on devices running Android 15 and higher. To declare that your game supports Android Auto, include this <category> element in the intent filter of an activity in your manifest file: <activity ... <intent-filter> <action android:name="android.intent.action.MAIN" /> ... <category android:name="android.intent.category.CAR_LAUNCHER" /> </intent-filter> </activity> Generally, the android.intent.category.CAR_LAUNCHER category element is placed in the same intent filter as the android.in

## Bring your Android game to the car screen today

DevFeed: [Bring your Android game to the car screen today](<https://devfeed.tech/articles/bring-your-android-game-to-the-car-screen-today-88688.md>)

Original publisher: [Read original article](<https://developer.android.com/blog/posts/bring-your-android-game-to-the-car-screen-today>)

Author: Jan Kleinert

Published: 2026-09-21T00:00:00Z

Content type: tutorial

Language: en

Sources: [Android Developers](<https://devfeed.tech/sources/android-developers-blog.md>)

Topics: [Android Auto](<https://devfeed.tech/topics/android-auto.md>), [Android](<https://devfeed.tech/topics/android.md>)

Tags: [android-auto](<https://devfeed.tech/tags/android-auto.md>), [android-automotive-os](<https://devfeed.tech/tags/android-automotive-os.md>), [app-quality](<https://devfeed.tech/tags/app-quality.md>), [charging-station](<https://devfeed.tech/tags/charging-station.md>), [game](<https://devfeed.tech/tags/game.md>), [product-news](<https://devfeed.tech/tags/product-news.md>)

### AI overview

Android Auto and Android Automotive OS now generally support games, with developers able to publish to open testing and production tracks on Google Play. The article explains the manifest declarations, parked-state behavior, controller and screen support, testing, and publishing steps for adapting an Android game to cars.

### Source excerpt

Today, the games category for Android Auto and cars powered by Android Automotive OS with Google built-in is officially graduating from beta to general availability.

## 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](<https://devfeed.tech/articles/hilt-in-android-auto-from-manual-factories-to-a-cleaner-screen-provider-22963.md>)

Original publisher: [Read original article](<https://funkymuse.github.io/posts/car-sample-with-hilt/>)

Author: FunkyMuse

Published: 2026-06-05T09:30:00Z

Content type: tutorial

Language: en

Sources: [FunkyMuse](<https://devfeed.tech/sources/funkymuse.md>)

Topics: [dagger-hilt](<https://devfeed.tech/topics/dagger-hilt.md>), [Android Auto](<https://devfeed.tech/topics/android-auto.md>), [Dagger](<https://devfeed.tech/topics/dagger.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-auto](<https://devfeed.tech/tags/android-auto.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [dependency-management](<https://devfeed.tech/tags/dependency-management.md>), [di](<https://devfeed.tech/tags/di.md>), [hilt](<https://devfeed.tech/tags/hilt.md>), [screen](<https://devfeed.tech/tags/screen.md>)

### AI overview

The excerpt proposes using Hilt multibinding to avoid manually passing a factory for every Android Auto screen. A `ScreenProvider` resolves screens from a map of `ScreenFactory` bindings, and a `Navigator` uses that provider to push screens; the session uses the provider for the initial screen. Screens can then use ordinary constructors and the navigator, without `@AssistedInject` factories. Because a `MainScreen` factory needs the navigator while the navigator depends on the screen provider and its factory map, injecting `Provider<Navigator>` delays resolution and breaks the circular dependency. The author presents this as an exploratory approach, not production-ready: `ScreenFactory` uses `Any` casts that could be improved with a custom KSP processor. The excerpt also mentions event channels or callbacks as alternatives for breaking the cycle, and says `Lazy` is possible but offers no significant improvement over `Provider`.

### 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...

## Bringing GitHub Actions to GitHub Mobile

DevFeed: [Bringing GitHub Actions to GitHub Mobile](<https://devfeed.tech/articles/bringing-github-actions-to-github-mobile-68114.md>)

Original publisher: [Read original article](<https://github.blog/news-insights/product-news/bringing-github-actions-to-github-mobile/>)

Author: Maximilian Sachs

Published: 2023-01-20T17:00:41Z

Content type: release

Language: en

Sources: [GitHub Blog](<https://devfeed.tech/sources/github-engineering.md>)

Topics: [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [Android Auto](<https://devfeed.tech/topics/android-auto.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [github-mobile](<https://devfeed.tech/tags/github-mobile.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [news-insights](<https://devfeed.tech/tags/news-insights.md>), [product](<https://devfeed.tech/tags/product.md>)

### AI overview

GitHub Mobile adds ways to inspect and manage GitHub Actions workflows from a phone. Users can view pull request checks, workflow summaries and job logs, receive push notifications when runs finish, and cancel or retrigger runs.

### Source excerpt

How to tap into the power of GitHub Actions from anywhere with GitHub Mobile!

## Interpreting voice results for Android media apps in cars

DevFeed: [Interpreting voice results for Android media apps in cars](<https://devfeed.tech/articles/interpreting-voice-results-for-android-media-apps-in-cars-25891.md>)

Original publisher: [Read original article](<https://proandroiddev.com/interpreting-voice-results-for-android-media-apps-in-cars-f36d7bdb26e1?source=rss-1331e67af4e1------2>)

Author: Danny Preussler

Published: 2022-01-10T21:33:42Z

Content type: tutorial

Language: en

Sources: [Danny Preussler](<https://devfeed.tech/sources/stories-by-danny-preussler-on-medium.md>)

Topics: [Android Auto](<https://devfeed.tech/topics/android-auto.md>), [Android](<https://devfeed.tech/topics/android.md>), [media3](<https://devfeed.tech/topics/media3.md>), [Android Testing](<https://devfeed.tech/topics/android-testing.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [android-auto](<https://devfeed.tech/tags/android-auto.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [cars](<https://devfeed.tech/tags/cars.md>), [google-assistant](<https://devfeed.tech/tags/google-assistant.md>), [integration](<https://devfeed.tech/tags/integration.md>), [media](<https://devfeed.tech/tags/media.md>), [voice](<https://devfeed.tech/tags/voice.md>)

### AI overview

For Android Auto media searches, the excerpt reports that Assistant calls `MediaSessionCompat.Callback.onPlayFromSearch()` with the remaining query, but the documented `MediaStore.EXTRA_MEDIA_FOCUS` check does not distinguish artist, album, or track: it says the received focus is always `vnd.android.cursor.item/*`. The suggested workaround is to read the non-null `EXTRA_MEDIA_ARTIST`, `EXTRA_MEDIA_ALBUM`, and `EXTRA_MEDIA_TITLE` values from the callback bundle to identify the requested entities. The author notes the cause is unclear and recommends testing the implementation, since documented behavior may not match reality.

### 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: "<Play> <Moderat> <on SoundCloud>" 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