🔍 Problem

Bluetooth audio (boAt Rockerz 512 ANC) is unstable under Windows:

• A2DP stream starts fine → degrades into stutter / crackle / packet drops
• Often triggered after sleep/resume or after some runtime
• Not usable for continuous playback

🧪 Repro + tests

• Headphones work perfectly with phone → sink is fine
• Same behavior across reconnects → not a pairing issue
• Clean driver reinstall → temporarily resolves (state reset)
• Disable/enable BT → sometimes recovers
• Toggling WiFi OFF→ON immediately restores clean audio (most consistent recovery)

Strong repro condition:

• Using 5 GHz phone hotspot → issue reproducible
• Switching hotspot to 2.4 GHz → no stutter observed

⚠️ Key observations

• With WiFi disabled, Bluetooth A2DP is completely stable
• With WiFi enabled, audio eventually degrades
• Behavior suggests coexistence arbitration / scheduling issue, not RF-only interference

🧠 Hypothesis

Likely a WiFi/BT coexistence bug on the internal combo module (Realtek/MediaTek?):

• Faulty PTA (Packet Traffic Arbitration) / coexistence algorithm
• Improper timeslot scheduling under concurrent WiFi load (even on 5 GHz)
• Driver/firmware enters a bad state after sleep → stateful degradation
• WiFi toggle forces a firmware/radio reset, restoring correct arbitration

❌ What didn’t help

• Latest drivers from Lenovo support page
• Lenovo Vantage (no newer updates)
• Power management changes (both WiFi + BT)
• Re-pairing devices

📍 Environment notes

• More frequent in dense RF environments (library)
• Still reproducible at home on 5 GHz hotspot
• 2.4 GHz hotspot = stable (counterintuitive if this were pure interference)

❓ Questions

• Is this a known issue with IdeaPad Slim 5 AMD variants / specific WLAN cards?
• Which exact modules are shipping here (Realtek vs MediaTek SKUs)?
• Has anyone resolved this via:
  • WLAN/BT module replacement?
  • Firmware/BIOS update?
• Does swapping to an Intel AX200/AX210 eliminate this (better coexistence/PTA)?

At ~₹85k, consistent A2DP playback shouldn’t be failing under normal usage. This looks like a platform-level issue (driver/firmware/hardware) rather than user configuration.

If anyone has logs, module IDs, or a confirmed fix path, would appreciate it.