Skip to content

Feature Request: Automatically disable conversational awareness when only one single AirPod is inserted #616

@tabjy

Description

@tabjy

Scope

Android

Problem or use case

Currently, conversational awareness (CA) activates whenever the AirPods detect speech, regardless of one or both AirPods are worn. This issue propose adding an option to only enable CA when both AirPods are in, preventing unwanted volume reduction when listening with a single bud. The idea is that when wearing a single AirPod, the user is already in a natural "conversational aware" posture. Lowering volume feels unnatural and often distracts me.

I don't believe this is an existing feature on Apple devices. However, I personally would like this feature and I'm often bothered with unwanted volume reduction. Similarly, the same idea could also apply to disabling pausing media playback instead of just lowering volume.

Proposed solution

From what I understand, there are two approaches:

  1. Firmware-side toggle: send CONVERSATION_DETECT_CONFIG (0x28) to disable CA on the AirPods when ear detection 0x06 reports one bud out.
  2. App-side suppression: ignore incoming 0x4B CA packets when earDetectionNotification.status doesn't show both AirPods are in.

I would suggest the app-side suppression approach for the following reasons:

  1. Easier implementation: an extra if-condition in onConversationAwarenessReceived() vs bi-directional protocol coordination
  2. No reliance on firmware/protocol: Apple doesn't seem to have this feature, and everything could change. Implement on app-side is more likely to be compatible with future devices/firmware.

Also, a new UI toggle "Only when both AirPods are worn" should be added to the CA config section. It should default to off to preserve current behaviour.

Please let you know what you think. Thanks!

Alternatives considered

(See above)

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions