ObliviOS Developer portal Project site

Home / Decisions / ADR-135

The Name row changes the phone's alias through a new narrow platform call BluetoothDevice#setAirPodsAlias(String).

Proposed, recorded 4 October 2026.

Decision
ADR-135
Date
2026-10-04
Status
ProposedProposed
Part
AirPods
Mentions
ADR-117, ADR-119, ADR-129
Mentioned by
ADR-134

1Decision

The Name row changes the phone's alias through a new narrow platform call BluetoothDevice#setAirPodsAlias(String) (patch 0012, Bluetooth module): a @SystemApi behind the signature or privileged permission MANAGE_AIRPODS_IDENTITY, only for a device that is bonded and registered through setAirPodsIdentity, only for a name of 1 to 32 UTF-8 bytes of visible text (the same rule as AapCodec.isValidName), on the registry lock setAirPodsMetadata already uses. The app does not get BLUETOOTH_PRIVILEGED and does not use a companion-device association.

2Why and evidence

AIR-170: BluetoothDevice#setAlias needs BLUETOOTH_PRIVILEGED or a companion-device association, the app caught the SecurityException, the pair was renamed and the phone's alias and the Name row kept the old value. The owner chose a narrow call in the pattern of ADR-117 and ADR-119 over an association.

3Consequences

Supersedes the sentence of ADR-129 that the phone's alias follows the rename. Patch 0012 must be landed on the server branch, built and proven on the device (AIR-170, AIR-191) before this entry is Accepted.

4Review when

A second app that needs the call; a change of the alias rules of the Bluetooth module.

Read from docs/governance/decision-log.md, entry ADR-135.