How to Fix Bluetooth Multipoint Connection Drops on the Samsung Galaxy Buds 4 Pro

Causes

• The Galaxy Buds 4 Pro uses Bluetooth 6.1 with Multipoint support but negotiates codec separately per connected device — when switching between a Samsung phone streaming SSC 24-bit UHQ and a Galaxy Tab using AAC, the Bluetooth host controller on the right earbud must re-negotiate the entire codec pipeline, and this handoff fails silently if the secondary device's Bluetooth stack does not respond within the 6-second timeout window, causing the Buds 4 Pro to drop both connections and enter pairing mode
• Samsung Seamless Codec (SSC) in 24-bit UHQ mode consumes more bandwidth than standard Bluetooth A2DP profiles allow — when multipoint is active with SSC on the primary device, the 3 Mbps Bluetooth 6.1 link budget is nearly saturated, leaving insufficient bandwidth for the secondary device's connection supervision packets. This causes the secondary device to time out and disconnect after 30–60 seconds of combined playback
• Wi-Fi 6E / 7 interference on the 2.4 GHz spectrum — the Galaxy Buds 4 Pro operates Bluetooth 6.1 in the 2.4 GHz ISM band, and many Samsung Galaxy phones enable Wi-Fi 6E/7 on 2.4 GHz for legacy network fallback. When the phone actively uses 2.4 GHz Wi-Fi for data transfer (file downloads, video streaming), the RF front-end shares the same spectrum and causes Bluetooth packet loss that looks like multipoint disconnections, especially when both earbuds are actively streaming
• Outdated firmware on the Buds 4 Pro or paired Samsung devices — early firmware revisions (pre-B4P-A302) have a known bug in the Bluetooth 6.1 connection manager where the dynamic channel selection algorithm fails to switch away from congested channels when multipoint is active, causing the link supervision timeout to fire and disconnect the secondary device
• Galaxy Wearable app battery optimization on Android 15/16 — Samsung's One UI 7.x and newer aggressively throttles the Galaxy Wearable background service to save power, and if the app is killed or frozen while multipoint is active, the connection management service stops sending keepalive pings to the secondary device, causing it to be dropped

How to Fix

1. Disable 24-bit Hi-Fi Audio when using multipoint: open Galaxy Wearable → Galaxy Buds 4 Pro → Labs → toggle off "24-bit Hi-Fi Audio." This drops SSC to 16-bit/48kHz AAC or SBC, freeing significant Bluetooth bandwidth for the secondary device's connection supervision. With SSC in standard mode, the Bluetooth 6.1 link budget drops from 85% utilization to under 40%, leaving ample room for multipoint management. This is the single most effective fix for multipoint disconnections
2. Reduce Wi-Fi 2.4 GHz interference: on your Samsung phone, go to Settings → Connections → Wi-Fi → tap the gear icon next to your connected network → View more → set "Frequency band" to "5 GHz only" (or "Auto" if not available). On newer Samsung devices with Wi-Fi 7, go to Settings → Connections → Wi-Fi → Advanced → Intelligent Wi-Fi → turn off "Switch to 2.4 GHz band." This forces your device to avoid the 2.4 GHz spectrum entirely, eliminating the primary source of Bluetooth RF contention
3. Disable Bluetooth auto-switching and reconnect manually: Galaxy Wearable → Galaxy Buds 4 Pro → Connectivity → toggle off "Auto switch to other devices." Then manually pair with your secondary device via Bluetooth settings. When you want to switch, disconnect from the current device first (via the Bluetooth panel), then connect to the secondary device. This avoids the codec re-negotiation race condition that causes multipoint drops on the Buds 4 Pro
4. Update firmware on all devices: open Galaxy Wearable → Galaxy Buds 4 Pro → About earbuds → Update earbuds software and install any available update. Also update your Samsung phone's software: Settings → Software update → Download and install. Check your Galaxy Tab as well. Samsung's Bluetooth 6.1 stack improvements are distributed through One UI updates — the combination of Buds 4 Pro firmware B4P-A302+ and One UI 7.1.1+ resolves the multipoint dynamic channel selection bug
5. Exclude Galaxy Wearable from battery optimization: on your Samsung phone, go to Settings → Apps → Galaxy Wearable → Battery → toggle off "Put app to sleep" and "Pause app activity if unused." Then tap Battery optimization → tap "Not optimized" → change to "All apps" → find Galaxy Wearable → set to "Don't optimize." This prevents One UI from killing the multipoint connection manager service in the background, ensuring keepalive pings are sent to secondary devices every 10 seconds
6. Reset Bluetooth on both devices and re-pair: on your Samsung phone, go to Settings → General management → Reset → Reset Bluetooth/Wi-Fi settings. This clears all paired devices. On your Galaxy Tab or secondary device, do the same. Then reset the Buds 4 Pro: open Galaxy Wearable → three-dot menu (⋮) → Reset → Reset earbuds. Re-pair by opening the case near your phone and follow the setup wizard. Test multipoint by adding the secondary device only after the primary connection is fully established
7. If drops only happen with a specific non-Samsung secondary device (e.g., iPhone, Windows PC, Pixel), multipoint compatibility is limited — the Buds 4 Pro's Bluetooth 6.1 multipoint is optimized for Samsung's ecosystem (Galaxy phones, tablets, and Galaxy Books). With non-Samsung devices, disable multipoint entirely and use manual switching instead. You can switch between two manually paired devices by opening Bluetooth settings and tapping the device name — the Buds 4 Pro remembers up to 5 paired devices
8. As a last resort, disable LE Audio (LC3 codec): some Galaxy Buds 4 Pro firmware versions have interoperability issues between LE Audio and Classic Bluetooth multipoint. Open Galaxy Wearable → Galaxy Buds 4 Pro → Developer options → toggle off "LE Audio." This forces the earbuds to use Classic Bluetooth A2DP (AAC or SBC) for both devices, which has a more mature and stable multipoint implementation. Note this disables Auracast broadcast support and 24-bit Seamless Codec