Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
My Bluetooth devices constantly drop in and out of connection. And that's once they're paired, pairing in the first place is a PITA and always takes multiple tries, and very often things unpair overnight so I have to re-pair frequently. I have three computers running Mint and they all do this with all Bluetooth connections.
My Mac had no such issues, you pair something one and it's stuck like glue till you unpair it, and even automatically re-pairs after a reboot no problem.
I don't have the connection drop in/out problem(s), but something like nine times out of ten I, too, need to
bluetoothctl connect <MAC address>twice for my headphones to actually connect. It's all the more frustrating because bluetoothctl's prompt will adjust after the first connection (*attempt) - if it weren't for the headphones themselves not acknowledging the connection I'd have no idea why no sound would be coming from them.I had that problem with my Sony XM5's, too, for a while. But it got fixed with either a kernel or software update a few months ago (running the latest Fedora here).
Huh. I have XM3s but am running latest Arch, so maybe it's something weird with my headphones?
Had this happen with both, the Qualcomm and the MediaTek wifi7 chips when they came out. Took years for a fix in the driver. Vendor support for linux drivers is sadly still bad.