What to know
- Android 17 QPR2 Beta 2 adds Settings text for a “Manage assistant audio” control that lets you allow or deny it per app.
- The permission behind it is not new — the Google app has declared it for at least a month. What is new is a place for you to manage it.
- Its built-in search keywords are “assistant, llm,” which is the clearest hint of what it is meant for.
- The control is written as special access, the same category Android uses for powers it does not grant casually.
Android keeps a set of powerful abilities out of the normal permission list and files them under special access — things like drawing over other apps or changing system settings. Code in the latest Pixel beta shows a new entry being prepared for that list, covering an app’s ability to manage assistant audio.
The permission already exists — the Settings screen does not
This is the part worth being precise about. The underlying permission is already in the wild: the Google app has declared MANAGE_ASSISTANT_AUDIO in its manifest for at least a month, well before this beta. Nothing about the capability itself is a debut.
What the beta adds is the user-facing half. Until now the permission existed with no screen where you could see who held it or take it away. The strings appearing in Settings are that missing screen — a title, a toggle, an explanation, and search keywords so it can be found.
What the new Settings text says
The control is titled “Manage assistant audio.” Its toggle reads “Allow managing assistant audio,” and the description spells out the grant plainly: allow this app to manage assistant audio on this device.
Two details stand out. The wording is scoped specifically to assistant audio rather than to the microphone in general — a distinct permission, not the standard mic prompt. And the search keywords attached to it are “assistant, llm,” which is an unusually direct signal that this exists to serve large-language-model features rather than the older voice assistant.
Why a special access entry matters
Special access is where Android puts abilities it does not hand out through a normal prompt. Putting assistant audio management there suggests Google expects a small number of apps to request it, and wants you able to audit and withdraw it afterwards.
The screen is not reachable in this build yet, and work-in-progress code can change or be dropped before release. But a permission gaining a management surface usually means it is about to be used by more than the app that defined it.
Leave a Reply