Phones and Auracast

Reading the results

Here, phone reception means decoding broadcast audio in the handset. In the assistant route described by Bluetooth SIG, the phone selects a broadcast for another receiver, which receives that broadcast directly. A compatibility listing alone does not establish phone-local playback or relay to older headphones. Read the route, receiving device, OS and limitations together; empty values remain unresolved. Manufacturer app and phone statements retain their specific device conditions. (Bluetooth SIG Market Development 2025; Ray 2025; Oticon n.d.; Samsung Electronics 2025)

Codebook

phone_family

Named phone family, explicitly grouped models, or labelled platform class. Slashes join enumerated models, not every variant sharing a name. Generic platform rows overlap model rows and must not be counted as additional phone models.

platform

Android, iOS, or the SIG's platform-neutral architecture class. A manufacturer interface name is included when relevant.

auracast_reception

Native reception and decoding in the handset: yes if explicitly supported, no if explicitly unavailable in the stated class/date, partial for a documented restricted handset-reception mode, or empty when unresolved. This is separate from assistant support.

reception_note

Explains the reception value or missing evidence and identifies external-receiver paths.

native_assistant

yes for documented built-in or phone-maker-provided assistant support; partial for a general assistant listing without a specified interface or a family supported by a native example for only one member; no for an explicit negative in the stated class/date; empty when unresolved. Hearing-device manufacturer apps are recorded separately in assistant_route. This field does not assert which device performs radio scanning internally.

hearing_aid_assistant

yes for an explicit hearing-aid route within the stated app/device conditions; partial for general assistant support without a full hearing-aid/model match, a family supported only by an example member, or a conditional legacy-app route; no only for an explicit negative; empty where no hearing-aid route is established. yes never means all hearing aids.

assistant_route

Phone controls or app and receiving device described by the sources. Manufacturer descriptions are attributed.

os_version

Source-specific OS/interface requirements, preserving earbud versus hearing-aid conditions and historical beta status. Not reported is missing evidence, not unrestricted support.

statement_dates

Semicolon-separated source-id=date pairs for every source used in the row. Values are YYYY-MM-DD, YYYY-MM, or undated. The Pro Audito month is its Q&A heading, not a verified revision date for every phone entry.

reception_source_ids

Semicolon-separated library ids supporting the reception value or the limited role described in reception_note. A citation beside an empty value identifies the material checked, not proof of absence.

assistant_source_ids

Library ids supporting the two assistant fields, route and family membership.

os_source_ids

Library ids giving OS conditions or checked for a missing minimum.

source_locator

Original page, section, table or model entry supporting the row; source names identify locations when several originals are used.

funding_detail

Funding and producer context retained from the earlier compilation; the funding column carries the current source-record labels.

limitations

Row-specific interpretation limits and source-record reading limits. Missing information is not reported, never an inferred zero.

reviewed

Date this compilation read the evidence, 2026-10-13. It is not the date a feature shipped or a source was published.

source_id

Library source identifiers supporting the row, separated by semicolons. Feature-specific and supporting-source columns retain their more precise roles.

funding

Source-record funding labels. With multiple primary sources, each label is followed by its source id in brackets. Funding detail remains in funding_detail where supplied by the earlier compilation.

Compilation and interpretation

phone-support.csv was compiled on 2026-10-13 from ten sources: six existing library records and four new records, checked against their private archived originals. Its 29 rows cover iPhone and Android app routes, a legacy-phone architecture class, Pixel, Galaxy, Xiaomi and POCO families. This is a dated research dataset for editorial review, not a complete inventory of phones sold on the compilation date.

Reception means the phone itself receiving and decoding broadcast audio. An assistant selects a stream for another receiver; that receiver receives the broadcast directly. The SIG explicitly separates these roles. Consequently, a phone's entry on an Auracast compatibility list does not establish phone-local audio playback, relay to older Bluetooth headphones, or output through wired earphones. Unresolved reception cells stay empty rather than becoming a positive or a negative. No retained source establishes a phone-local yes or partial reception result. (Bluetooth SIG Market Development 2025; Ray 2025; Samsung Electronics 2025)

The file is UTF-8, comma-delimited, with a header, quoted fields and LF line endings. Import every column as text to preserve empty categorical values, partial dates and OS strings. Source ids resolve to content/sources/<id>.md; they are unbracketed in the CSV and use source identifiers in prose. There are no formulas, rankings or inferred market-share values. Rows are grouped by platform and family rather than performance.

The iPhone reception and native-assistant negatives are attributed to Pro Audito's dated guidance, not an Apple announcement. Oticon documents an app assistant on iOS 15.2+ and Android 10+, so absence of native phone support does not exclude hearing-aid reception. The legacy row is explicitly restricted to phones without an LE Audio host stack; the SIG's architecture and the Starkey/Phonak app descriptions do not establish support on every old phone. (Pro Audito Schweiz 2026; Oticon n.d.; Bluetooth SIG Market Development 2025; Starkey 2026; Roh 2026)

Pro Audito lists assistants without identifying the interface on each phone. The S20, Fold7 and Xiaomi rows therefore use partial for native support. The broad Pixel family's native support is also partial: manufacturer Google describes Pixel 9 controls and manufacturer Oticon uses Pixel 9 screenshots, while the wider lists do not document the native interface on every family member. These qualifications preserve the positive assistant listings without treating them as tests of built-in controls across all listed phones. (Pro Audito Schweiz 2026; Balaji Ganesan 2025; Ray 2025; Oticon n.d.)

Keep the date and route distinctions during reuse. Samsung's 2024 One UI 5.1.1 minimum concerns Galaxy Buds listening; its 2025 general assistant list says One UI 6.1+, while Google's hearing-aid announcement says One UI 7/Android 15 and Pixel 9 on Android 16 beta. The table does not collapse these into one universal OS minimum. Google's September 2025 Pixel wording is broader than Pro Audito's explicit Pixel 8a/9a exclusions; those two models remain unresolved, because exclusion from a combined transmission-and-assistant list does not establish absence of every assistant route. POCO's general compatibility listing likewise does not settle a hearing-aid assistant role. (Samsung Electronics 2024; Samsung Electronics 2025; Balaji Ganesan 2025; Ray 2025; Pro Audito Schweiz 2026)

The q36 research report lists searches, archive provenance, exclusions and record concerns. Updating this table requires checking the original for the exact model, role, receiving device and OS. Do not turn a newer reading date into a newer support statement or fill an empty reception cell from a Bluetooth version number.

Change log

• 2026-10-13: Migrated 29 rows with codebook and source provenance into the data section.