- Decision
- ADR-172
- Date
- 2026-10-16
- Status
- ProposedProposed
- Part
- AirPods
- Mentions
- ADR-125
1Decision
With no pod in an ear the app removes the AirPods from the active audio slots again each time the A2DP or hands-free profile makes them the active device (EarDetectionPolicy.onAudioActive, a receiver for BluetoothA2dp/BluetoothHeadset ACTION_ACTIVE_DEVICE_CHANGED in EarDetectionController). Amends the route-away of ADR-125, which ran once per change of the ear count.
2Why and evidence
Owner report 2026-10-16: pods taken out of the case and left out of the ears were connected and played the music. Measured on stallion (image 2026101405, user build): the session started at 00:31:33.048, the first frame came 537 ms later, A2DP connected at 00:31:33.805 and became active at 00:31:33.807, HFP at 00:31:33.853; no setA2dpActiveDevice(null) followed.
The same pods taken out of the ears after being worn at 00:32:51 gave pause keys, setHfpActiveDevice(null) and setA2dpActiveDevice(null) within 0.45 s and the playback stopped, so the change-of-count path works.
[assumption] The first ear report arrived before the profiles were active, so the route-away of the baseline found nothing to remove (AirPodsRouteTracker.away records nothing then) and EarDetectionPolicy kept routedAway true, which blocked every later route-away until a pod went in an ear; no app-side log shows the arrival order on a user build, AIR-201 measures it.
3Consequences
A pod the owner selects by hand as audio output while both are out of the ears is removed again. A repeat call is harmless: the stack removes only the slots where the device is active. The Bluetooth module is unchanged, so this is an app-only image.
4Review when
AIR-201 fails; the owner wants to select the pods by hand while they are out of the ears.
Read from docs/governance/decision-log.md, entry ADR-172.