Dell WL5024 / HR024 Dongle — Severe Audio Issues on Linux (Ubuntu/Mint)
## Summary
The Dell Pro Plus Wireless ANC Headset WL5024 has multiple critical issues when used with Linux (Ubuntu 24.04 / Linux Mint 22, Kernel 6.17.0-20-generic). Both direct Bluetooth connection and the HR024 USB dongle have significant problems that make the headset unreliable for professional use in video conferences (Microsoft Teams, Zoom).
## Hardware Setup
- **Headset:** Dell Pro Plus Wireless ANC Headset WL5024 (Firmware 0.2.8.8) - **Dongle:** Dell HR024 Audio Receiver (Firmware 0.3.6, MediaTek chip) - **Lapmargin: 0;">## Issue 1: Direct Bluetooth — Corrupted SCO Packets (Intel AX210)
### Description
When connecting the WL5024 directly via Bluetooth to the laptop, the microphone (HFP/SCO profile) is severely broken. The kernel log is flooded with corrupted SCO packet errors:
This results in: - Microphone audio not reaching the laptop at all - Crackling/noise instead of voice in recordings - Microphone randomly stops working and cannot be recovered without reconnecting
### Additional Bluetooth Problems
- **Profile issues after reconnect:** After disconnecting and reconnecting, the Bluetooth profiles (A2DP / HFP) are not properly re-negotiated. Sometimes only HFP appears, sometimes only A2DP. Both profiles need to be available for proper operation (A2DP for media playback, HFP for calls with microphone). - **Microphone mute gets stuck:** When flipping the boom arm up (mute) and down (unmute), PipeWire sometimes does not process the unmute HID event. The microphone remains software-muted even though the headset reports "mic on". The only workaround is switching the audio profile back and forth in the sound settings. - **USB resets of the Bluetooth adapter:** The Intel AX210 occasionally performs USB disconnects/reconnects, causing the entire Bluetooth stack to reinitialize. This breaks all active audio connections. - **Default audio source not set:** After reconnecting, PipeWire sometimes fails to set the Bluetooth microphone as the default source, resulting in no microphone input despite the headset being connected.
### Root Cause
This is a known issue with Intel AX210 Bluetooth chips under Linux. The SCO (Synchronous Connection-Oriented) protocol used for HFP telephony audio is unreliable with the Intel btusb driver. The problem persists even after updating the Intel Bluetooth firmware to the latest version (2026.5, build 82122) from the linux-firmware git repository.
### Workaround Attempted
Updated Intel Bluetooth firmware manually from the linux-firmware git repository: ``` sudo zstd -f /path/to/linux-firmware/intel/ibt-0041-0041.sfi -o /lib/firmware/intel/ibt-0041-0041.sfi.zst sudo zstd -f /path/to/linux-firmware/intel/ibt-0041-0041.ddc -o /lib/firmware/intel/ibt-0041-0041.ddc.zst ``` This reduced the frequency of corrupted SCO packets but did not eliminate them.
## Issue 2: HR024 USB Dongle — Audio Pulsing/Pulsating in Duplex Mode
### Description
Due to the Bluetooth issues described above, I switched to using the HR024 USB dongle. The dongle is recognized by Linux as a USB audio device (via `snd_usb_audio` driver) and generally works. However, there is a severe audio quality issue:
**When the microphone is active (duplex mode), the incoming audio (other people's voices) develops a rhythmic pulsing/pulsating in volume.** The voices of other participants fluctuate in loudness periodically, making conversation very difficult.
### Characteristics of the Pulsing
- **Only occurs when the microphone has been activated.** Pure playback (music, YouTube, system sounds) works perfectly. - **Affects all audio output**, not just the application using the microphone. Once the pulsing starts, it is audible in all browsers and applications simultaneously. - **Persists after the microphone is deactivated.** Once triggered, the pulsing continues even if the microphone is no longer in use. - **Occurs in all browsers:** Tested with Chromium and Firefox — same behavior in both. - **Occurs outside of browsers:** Reproducible with plain ALSA commands: ``` arecord -f S16_LE -r 48000 -d 5 /tmp/test.wav && aplay /tmp/test.wav ``` After running this command, subsequent `aplay` playback may exhibit pulsing. - **Not related to any specific application:** Happens in Microsoft Teams, Zoom, Jitsi, and even raw ALSA playback. - **Immediately fixed by physically disconnecting and reconnecting the dongle** - **Switching the audio profile in pavucontrol also sometimes fixes it** (e.g., switching from "Analog Stereo Duplex" to "Analog Stereo Output" and back). - **Does not occur when the dongle is set to output-only mode** (profile "Analog Stereo Output" without microphone input). - **Does not occur on Android** when the headset is connected via Bluetooth directly. - **Sporadically occurs** — sometimes it starts immediately when the microphone is activated, sometimes it takes several minutes, and sometimes it doesn't occur at all. - **Balance test:** When shifting the audio balance fully to one channel (left only or right only), the pulsing is not perceived. It only manifests when both stereo channels are active simultaneously, suggesting a possible phase issue between the left and right channels in duplex mode.
### PipeWire/ALSA Analysis
The dongle reports identical parameters before and after the pulsing starts: - Sample format: s16le 2ch 48000Hz - Channel map: front-left, front-right - Volume: 100% on both channels - Profile: analog-stereo (output) + mono-fallback (input) - No changes in sample rate, channel count, or format
The only parameters that appear after Teams opens the audio stream are: ``` node.max-latency = "16384/48000" api.alsa.period-size = "256" ``` These remain constant regardless of whether pulsing occurs.
### Suspected Root Cause
The pulsing appears to be caused by **internal audio processing in the HR024 dongle's firmware** when it enters duplex mode (simultaneous microphone capture and audio playback). The dongle likely activates echo cancellation or some other DSP processing that introduces a phase shift or amplitude modulation between the left and right stereo channels.
Evidence: 1. The problem only occurs in duplex mode (microphone + speakers active) 2. It does not occur in output-only mode 3. It is immediately resolved by a dongle reset (USB reconnect) 4. PipeWire/ALSA parameters do not change — the issue is below the USB audio layer 5. The balance test suggests inter-channel interference
### Dongle Firmware History
The dongle was updated to firmware v0.3.6 (with LE Audio support). It is unclear whether this issue existed with earlier firmware versions, as there was no prolonged Linux testing before the update. Dell does not provide older firmware versions for downgrade.
When the headset's Wear Detection feature is enabled, removing the headset from the head triggers a mute event. This mute event is sent via HID to Linux, which in turn writes back a LED_MUTE status via the HID output channel. This creates a feedback loop where the headset and Linux continuously toggle the mute state back and forth, hundreds of times per second.
### Impact
- The system becomes nearly unusable — keyboard input is blocked due to USB bus saturation - Audio cuts in and out rapidly - The only fix is physically removing the dongle
The `event19` device has both `KEY_MICMUTE` input and `LED_MUTE` output capabilities. Linux writes back the mute status via `LED_MUTE`, which the dongle interprets as a new mute command, creating the loop.
### Workaround
Disabling Wear Detection via the Dell Audio mobile app (Android/iOS) resolves this specific issue. However, this setting is not accessible from Linux — it requires the Dell Peripheral Manager (Windows only) or the Dell Audio mobile app.
The boom arm flip (mute/unmute) can also sporadically trigger the same loop, though less frequently than Wear Detection.
## Environment Details
``` $ uname -r 6.17.0-20-generic
$ pactl info | grep "Server Name" Server Name: PulseAudio (on PipeWire 1.x)
$ lsusb | grep -i "413c\|8087" Bus 003 Device 0xx: ID 8087:0032 Intel Corp. AX210 Bluetooth Bus 003 Device 0xx: ID 413c:a527 Dell Computer Corp. Dell HR024 Audio Receiver
$ pactl list sinks short | grep HR024 xxx alsa_output.usb-MediaTek_Inc_Dell_HR024_Audio_Receiver_0000000000000000-00.analog-stereo PipeWire s16le 2ch 48000Hz RUNNING ```
I would appreciate any feedback from Dell engineering, especially regarding: 1. Whether the audio pulsing in duplex mode is a known issue with the HR024 dongle firmware v0.3.6 2. Whether a firmware fix is planned 3. Whether earlier dongle firmware versions (e.g., v0.2.2) are available for downgrade testing
The specifications for this product does not indicate Linux as a supported OS. The supported OS would be Win11/10 64 Bit and Mac OS. Unfortunately, it would be unlikely for any fix to be provided as Linux is out of the scope of support for this headset.
DELL-Daniel V #IWork4Dell Digital Support Forum Liaison
Great to hear how interested you are in improving and correcting your product. Linux is by the way a main operating system and also Android is a Linux operating system. Also I think drivers for HID devices should be operating system independent.
I could solve the issue #2 with the pulsing sound by downgrading the headset firmware from v3.0.3_0722 to v2.8.8_Y9XJ2.
Tried this after reading https://www.dell.com/community/en/conversations/storage-drives-media/wireless-headset-mutes-audio-when-only-right-channel-plays-audio-wl5024-over-hr024-dongle/695b661104bdbe7915e15f07?keyword=wl5024 comment "3.0.x is buggy as".
Since downgrade pulsing sound never appeard, so it does not seem to be dependent on the operating system but something inbetween headset and dongle.
DELL-Daniel V
Community Manager
•
922 Posts
•
5303 Points
3
0
Posted April 15th, 2026 14:31
The specifications for this product does not indicate Linux as a supported OS. The supported OS would be Win11/10 64 Bit and Mac OS. Unfortunately, it would be unlikely for any fix to be provided as Linux is out of the scope of support for this headset.
DELL-Daniel V
#IWork4Dell
Digital Support Forum Liaison
New to Community? Check our FAQ!