OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
audio-input medium common DISPUTE

Fix Bluetooth music stuttering, skipping or sounding low-bitrate

omarchyarchendeavouroscachyosmanjarohyprlandwaylandpipewirebluetoothlaptopdesktop
AUDITED Audited against its sources and confirmed accurate.

Symptom

Bluetooth music stutters, skips, or sounds "muddy" and low-bitrate, especially when you walk a few metres away or when a Bluetooth mouse is also connected. systemctl --user status pipewire shows lines like pipewire[249297]: (bluez_input.18:54:CF:04:00:56.a2dp-sink-60) client too slow! rate:512/48000 pos:370688 status:triggered.

Cause

The negotiated A2DP codec/bitrate is too aggressive for the link quality, or 2.4 GHz congestion (Wi-Fi, BT mouse/keyboard sharing the radio) is starving the stream. client too slow! means PipeWire could not fill the Bluetooth transport buffer in time.

Fix

Check which codec is in use:


pactl list sinks | grep -i codec

Pin a more robust codec set. SBC-XQ gives noticeably better quality than plain SBC at similar robustness:


mkdir -p ~/.config/wireplumber/wireplumber.conf.d

# ~/.config/wireplumber/wireplumber.conf.d/bluez-config.conf
monitor.bluez.properties = {
  bluez5.enable-sbc-xq = true
  bluez5.enable-msbc = true
  bluez5.codecs = [ sbc sbc_xq ]
}

systemctl --user restart pipewire.service wireplumber.service

Reconnect the headphones. Valid values for bluez5.codecs are sbc sbc_xq aac ldac aptx aptx_hd. If you have LDAC hardware and the link is strong, try [ ldac aac sbc_xq sbc ] instead. If it still stutters, fall back to [ sbc_xq sbc ].

Also disable node suspension for Bluetooth (see the pop/crack record) and move your 2.4 GHz Wi-Fi to 5 GHz if you can.

Verify

pactl list sinks | grep -i codec shows the codec you selected, and journalctl --user -u pipewire -f stays free of client too slow! during a full song.

Sources

bluetooth-audio-stutters-codec