Unfortunately the problem isn't with Linux (or other OSs), it's the Bluetooth spec.

There are so many different optional parts layered on top of other optional parts that the whole thing is unstable.

Here's an audio article which doesn't answer your problem directly, but gives some background on where the root of the problem is

https://www.soundguys.com/why-is-bluetooth-unreliable-55016/

Huh, I didn't realize Bluetooth was still such a problem for some people. I've been using Ubuntu and cheap chinese Bluetooth earbuds with a Intel wireless/Bluetooth chip, and they've been fine. Haven't really had many disconnect or connection issues.

Now the 10 year old integrated nvidia gpu on my alienware steam machine, on the other hand.. Sleep just broke again when I did an apt upgrade yesterday, time to diagnose that, again. On 24.04 LTS if anyone was interested.

What's funny is that all those same Bluetooth issues are also still very common on Windows, Mac, iOS, Android...

Distro makes a difference , or rather the packages installed that come with the distro. My Bluetooth worked great for my devices, until I tried my 20 year old BT mouse and it would fail to reconnect after boot. But it was fixed by changine or adding other Bluetooth packages. I forget which right now but something like bluewave vs blueman or somthing, then it was fine.

Mostly depends on your blurtooth card. If the one on your mobo isn't behaving, grab a $10 generic usb one off amazon that claims it works with linux. Mine's been solid for years, it's what I had to do.

But how you FIX it is you dig into the code and fix it so everyone else with your card gets the positive experience.

I had tonnes of problems when I used Mint which went away when I switched to Arch. I switched from Arch to EndeavourOS and didn't get the problems coming back. I think EndeavourOS is about on par with Mint in terms of difficulty and set up time, but seems more stable and capable. I use KDE and the associated Bluetooth management stack and it works well.

That said, in the rare case I do have an issue I just restart Bluetooth through systemctl and it starts working again. The most recent time I had this was when I had my left earbud working on my phone and my right on my computer. It worked fine until I stepped away for a second, it dropped from my phone but not my computer, but then the left earbud tried to join up with the right connecting to the PC and everything broke. A quick restart of Bluetooth and boom, all good.

I wish I knew.

I have two Linux systems: a laptop with Fedora and home media PC with Ubuntu. Bluetooth works great on the laptop, no issues whatsoever.

Completely different story with the media PC. I've never been able to get it working properly, and I've spent hours googling things to throw into the terminal hoping to get it fixed. I'm no IT guy but I know the basics, and it's not an old PC or anything (Asus NUC 14 Pro I think), but I can't get the stupid thing to stay connected with my Xbox controllers for the life of me. My wife wants to play games god damnit!

My Windows box, while rife with other problems (even though I'm on 10 LTSC) also never has Bluetooth issues, and it isn't the first time I've had said problems with Linux distros (had Mint installed on a box at one point but I managed to fix the issue by changing drivers). There must be a better way!

My motherboards always have the shittest no range garbo bluetooth chips, so I've been using generic bluetooth USB dongles instead. Work fine under Linux so far.

Learn how to develop kernel drivers for Bluetooth chipsets and debug them. That's really the big issue, the huge number of buggy chipsets that don't quite follow the standard and have to be worked around.

Not to mention that Bluetooth is a hell of a protocol anyway. The spec is huge and complex.

Been using Bazzite for over a year now and Bluetooth has always just worked.

I've been using Pop!_OS as my main system (Lenovo X1 Extreme) since just before the COVID lockdown and I've never had an issue with my Bluetooth devices.

I am going to guess that maybe the issue is that some computers use a Bluetooth device that has less than optimal Linux support. Maybe the way to address the issue is by having a more detailed hardware support list so that consumers can choose the hardware that is the most stable with Linux.