Microphone device detection and permissions reference

A microphone is a capture path

The physical microphone produces an input signal, while the host represents a controller, codec, USB or Bluetooth interface, capture endpoint, and stream. “Microphone detected” can refer to different layers, so the subject of a status statement matters.

Detection and publication differ

A bus or device layer can enumerate an interface before the audio subsystem publishes a capture endpoint. Endpoint publication can then depend on topology, package metadata, policy, and device state. These stages are related but not interchangeable.

Permissions belong to the application boundary

A host audio stack can represent a capture endpoint while separately applying privacy or application-access policy. Permission state is not a hardware identifier, package version, or driver state. It is a policy relationship between an application or user context and a capture capability.

Streams add another boundary

A capture stream has a format, channels, timing, and lifecycle independent of endpoint publication and permission records. A reference keeps device, endpoint, policy, and stream observations separate so a label is not mistaken for a cause.

Questions and answers