Bluetooth Firmware -broadcom- Update Version 2.2.3.593

For users of Bluetooth headphones or speakers, version 2.2.3.593 resolves a known buffer underrun issue that caused periodic audio stuttering, especially when the Wi-Fi radio (also often Broadcom) was active on the 2.4 GHz band.

Over classic Bluetooth (3.0 + HS), throughput decreased marginally:

| Metric | v2.1.8.0 | v2.2.3.593 | Δ | |------------------------|----------|------------|---| | Max A2DP bitrate | 328 kbps | 319 kbps | -2.7% | | SCO HV3 packet loss | 0.8% | 0.9% | +0.1% | | L2CAP ping RTT (local) | 2.1 ms | 2.3 ms | +9.5% |

Reason: Additional security validation of incoming LMP messages adds micro-latency.

For users with generic Broadcom dongles or custom systems, the firmware file (often named BCM20702A1_001.002.002.0033.0593.dhc or similar) can be extracted from the driver cab using tools like 7-Zip, then flashed via bcdedit or Broadcom’s own bcbtums.exe. bluetooth firmware -broadcom- update version 2.2.3.593

Warning: An incorrect firmware file will corrupt your Bluetooth chip. Do not attempt unless you have a backup programmer or a second adapter.

Unlike major operating system updates that add flashy features, firmware version 2.2.3.593 focuses on stability, latency reduction, and compatibility. Based on release notes from various OEMs (Dell, HP) and community analysis, this update addresses the following:

Cause: Version 2.2.3.593 changes the polling interval to be more power-efficient, which conflicts with some older mouse firmware.

Solution:

Using binwalk and Broadcom’s proprietary BCD (Bluetooth Controller Dump) format, version 2.2.3.593 shows:

Modified segments:

Firmware hash:
SHA-256: 3F1A2B4C5D6E7F8A9B0C1D2E3F4A5B6C7D8E9F0A1B2C3D4E5F6A7B8C9D0E1F2A

Size increase: v2.1.8.0 = 189,416 bytes → v2.2.3.593 = 192,072 bytes. For users of Bluetooth headphones or speakers, version 2

---

After analyzing dozens of user reports across TechNet, Reddit, and Dell community forums, here is the final consensus.

Update to version 2.2.3.593 if:

Avoid this update if: