How to Route Bluetooth Audio with pavucontrol

Before you start

Open pavucontrol on the same Linux machine where the Bluetooth device is paired and connected. The procedure is local: pavucontrol controls the PulseAudio or PipeWire session running for your desktop user. You do not need a separate service or admin access just to change audio routing.

Check that a Bluetooth audio profile is active for the device. If it is connected only as a headset, it may use a low-quality profile for microphone support. For music or system audio, a high-fidelity playback profile is usually preferable.

Step-by-step instructions

• 1. Start pavucontrol from the application menu or run pavucontrol in a terminal.
• 2. Open the Playback tab.
• 3. Start the application that should play Bluetooth audio.
• 4. In the application row, open the output device dropdown.
• 5. Select the Bluetooth device as the output device.
• 6. If the application does not appear, return to the Playback tab while it is actively producing sound.
• 7. Use the volume slider in the same row to adjust the application level.

The Output Devices tab shows Bluetooth devices available to PulseAudio or PipeWire. For a selected device, use the volume slider and the mute button to adjust system-wide playback level. The advanced menu may show a port or profile label that changes how the device is exposed.

On the Configuration tab, choose the Bluetooth profile that matches the task. A2DP is suitable when you only need playback. A hands-free profile may be needed when the Bluetooth microphone must work at the same time. Profile names can vary between versions, so compare the visible options before switching.

For microphone routing, open the Recording tab while the recording or calling application is active. Select the Bluetooth device as the input device in the application row. Then adjust input level in the Input Devices tab. Keep changes reversible by noting the previous profile or device selection before switching.

Check the output

Play a familiar test sound and verify that the moving level bar in the Playback tab belongs to the expected application and Bluetooth device. Confirm that sound is audible through the Bluetooth output and not through the computer speaker.

For a Bluetooth input device, speak or make a controlled noise and watch the level bar in the Recording or Input Devices tab. A rising bar shows that the session is receiving audio, but it does not confirm that the application saved a usable recording or that the microphone quality is suitable for the intended use.

Remember that codec and profile choice can affect latency and frequency range. The session may display a chosen sample rate, but the audible result also depends on the Bluetooth profile and the application's own processing.

Common problems and next steps

If no Bluetooth device appears in pavucontrol, check whether the system's Bluetooth settings show the device as connected. Disconnecting and reconnecting the device, or toggling the Bluetooth radio off and on, can restore visibility. Avoid repeatedly changing multiple settings at once so you can identify which action helps.

When sound remains silent after routing, compare the mute state and volume of the application, the output device, and the Bluetooth speaker or headphones themselves. Some Bluetooth devices have independent volume controls.

When the Bluetooth microphone and playback cannot be used simultaneously with acceptable quality, switch between the high-fidelity playback profile and the hands-free profile as needed. For calls, background noise may be more noticeable through the hands-free profile; position the microphone consistently and test in the actual calling app.

If the device appears but the sound comes from the wrong route, close the application, set the intended default in the Output Devices or Input Devices tab, and then reopen the application. Many applications select a device only at startup.