How Linux Handles Bluetooth Audio via BlueZ

This article explains how the Linux operating system routes, manages, and plays sound through wireless devices using the official Linux Bluetooth stack, BlueZ. In Linux, Bluetooth audio processing is a cooperative effort between the Linux kernel, the BlueZ user-space daemon, inter-process communication systems like D-Bus, and modern sound servers such as PipeWire or PulseAudio. Together, these layers handle everything from device discovery and cryptographic pairing to profile negotiation and real-time audio stream encoding.

The Core Architecture: Kernel to User Space

Bluetooth handling in Linux begins at the kernel level. The Linux kernel contains the low-level drivers necessary to communicate with Bluetooth hardware transceivers via the Host Controller Interface (HCI). The kernel provides the network socket layer (such as L2CAP and RFCOMM protocols) used for raw packet transport.

Directly above the kernel sits BlueZ, the official Linux Bluetooth stack. The primary component of BlueZ is bluetoothd, a background daemon running in user space. The bluetoothd daemon is responsible for:

• Scanning for and discovering nearby Bluetooth devices.
• Managing pairing, authentication, and key storage.
• Maintaining connection states and link keys.
• Exposing device states, interfaces, and controls to the rest of the system using D-Bus (Desktop Bus).

The Handshake Between BlueZ and Sound Servers

BlueZ does not process, decode, or mix audio directly. Instead, it delegates audio streaming to specialized sound servers—historically PulseAudio, and increasingly PipeWire on modern Linux distributions.

When a Bluetooth audio device connects:

1. Detection: The kernel notifies bluetoothd of the physical link.
2. Registration: bluetoothd communicates over D-Bus to advertise that an audio-capable device is available.
3. Session Management: Audio session managers (such as WirePlumber for PipeWire, or the module-bluez5 plugins in PulseAudio) detect the device via D-Bus and negotiate an audio connection.
4. Transport Endpoint Creation: BlueZ and the sound server establish an audio transport object. BlueZ hands off a raw file descriptor (socket) for the audio connection to the sound server.

Bluetooth Audio Profiles

Bluetooth audio relies on standard profiles defined by the Bluetooth Special Interest Group (SIG). BlueZ and sound servers negotiate these profiles depending on the device’s capabilities and the user’s use case:

• A2DP (Advanced Audio Distribution Profile): Designed for one-way, high-quality stereo sound output (e.g., listening to music). It supports codecs like standard SBC, AAC, aptX, and LDAC.
• HFP / HSP (Hands-Free Profile / Headset Profile): Designed for two-way, low-latency audio suitable for phone calls and voice chat. While this mode enables the headset's microphone, it switches the playback stream to lower-quality mono (using codecs like mSBC or CVSD).

In older architectures, an auxiliary daemon called oFono was often required to manage HFP telephony profiles alongside BlueZ. Modern configurations with PipeWire can manage native HFP/HSP profiles directly, simplifying hands-free audio handling.

The Real-Time Audio Pipeline

Once the connection is established and the profile is negotiated, the audio streaming pipeline functions as follows:

1. Application Output: An application sends an uncompressed PCM audio stream to the audio server (PipeWire or PulseAudio).
2. Encoding: The audio server encodes the PCM data into the negotiated Bluetooth codec (such as LDAC, AAC, or SBC).
3. Transmission: The audio server writes the encoded packets directly into the socket file descriptor provided by BlueZ.
4. Kernel Dispatch: The Linux kernel's L2CAP layer encapsulates the audio frames and passes them to the HCI driver.
5. Wireless Output: The Bluetooth hardware transmits the radio frequency packets over the air to the receiver.

By offloading the media encoding and stream synchronization to the sound server while keeping connection logic inside bluetoothd, the Linux operating system maintains low-latency, modular, and codec-flexible Bluetooth audio reproduction.