Android expands LE Audio Auracast support and multi-user audio sharing.
Google announced expanded Android support for LE Audio Auracast across more Pixel, Samsung, Xiaomi devices, and Sony headphones, adding audio sharing through QR codes, Fast Pair, and multiple headsets. Bluetooth audio is moving from single-device pairing toward public broadcasts, private sharing, and assistive listening.
In its September 2025 Android post, Google described LE Audio as the next-generation Bluetooth audio capability that offers higher-quality sound and richer features, including broadcasting to multiple devices at the same time. The update expanded Android’s Auracast support and moved headphone sharing and public listening closer to real user scenarios.
Google said users can join an audio share by scanning a QR code or connect quickly through Fast Pair. In private scenarios, one phone can connect two LE Audio headsets so two people can listen to music, movies, or podcasts in sync. In group scenarios, users can create a private broadcast.
Public venues are another important direction for Auracast. Airports, museums, gyms, classrooms, and stations can broadcast TV, guide, or announcement audio to users’ own headphones or hearing devices. For audio products, user experience is no longer only about sound quality, noise cancellation, and battery life, but also broadcast discovery, connection flow, and multi-platform compatibility.
Bluetooth audio solution development needs joint validation across phone systems, headset chips, firmware, acoustics, batteries, antennas, and PCBA layout. Products targeting overseas markets should also cover combinations such as Pixel, Samsung, and Xiaomi devices, and validate switching between LE Audio, Auracast, and legacy Bluetooth modes early.
Although this news focuses on audio, it also matters for keyboard and mouse peripherals. Android and mainstream terminals are making Bluetooth experiences more system-level, so users increasingly expect smoother discovery, quick pairing, multi-device management, and state indication. Bluetooth keyboards and mice that only provide basic pairing can feel fragmented across tablets, phones, TV boxes, and handheld consoles.
For wireless peripheral development, Bluetooth mode should not be treated as a lower-end substitute for 2.4 GHz mode. Bluetooth keyboards need attention to multi-OS key mapping, input-method switching, media-key compatibility, and multi-host memory. Bluetooth mice need validation of wheel behavior, side buttons, DPI switching, and sleep/wake behavior across systems. This keeps the product experience complete in mobile scenarios without a dongle.