Bluetooth Controllers connect, then go unresponsive for about 15 seconds then connect again and stay connected

Help
1 
Operating System: CachyOS Linux 
KDE Plasma Version: 6.7.4
KDE Frameworks Version: 6.29.0
Qt Version: 6.11.2
Kernel Version: 7.2.0-1-cachyos (64-bit)
Graphics Platform: Wayland

I’m somewhat crossposting this (between CachyOS forums and here). I do provide a link to that post at the end of this post.

I’ve tried many things but have come to realize the issue is not particular to CachyOS. This Bluetooth issue also affects Manjaro and Kubuntu (tested on their live CDs). It could be a KDE Plasma issue (all test had it in common) OR it could be my particular hardware on Linux.

Bluetooth Issues

  • First connection after boot up will never respond (must restart the device).
  • Subsequent connections will at some point go unresponsive for 15 or more seconds then stay connected.

Things I’ve Tried

  • Disabled builtin BT and tried an ASUS dongle.
  • Wiped out /var/lib/bluetooth contents and tried again.
  • Connected completely different brand of controller (Amazon Fire Controllers)
  • Created /etc/modprobe.d/bluetooth.conf with contents options btusb enable_autosuspend=0
  • Tried 6.18.42-1-cachyos-lts (on host machine)

Same Issues Across CachyOS, Kubuntu and Manjaro Live CDs

  • Tried live ISO cachyos-desktop-linux-260809.iso
  • Tried live ISO kubuntu-25.10-desktop-amd64.iso
  • Tried live ISO manjaro-kde-26.1.0-260812-linux71.iso

Windows 11 (Confirms No HW Problems)

I have an installation of Windows 11 on this same machine and I can confirm, the bluetooth itself and controllers do not exhibit any of the issues I’m currently experiencing.

My CachyOS Post Has More Info

I do provide more info with this post Bluetooth Controllers connect, then go unresponsive for about 15 seconds then connect again and stay connected - Issues & Assistance - CachyOS Forum but when I realized this issue also exist on Manjaro and Kubuntu I thought I’d crosspost here.

Where should I post these issues if it isn’t a KDE Plasma issue?