Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@ViRaS I found one other person on the internet who complained about the same issue on Reddit a couple months before it emerged for me with a different but similar type of Sony headphones.
-
@lorentz Were they still under warranty when the issue emerged ?
-
@ViRaS No, they were working correctly for a couple years.
-
I traced the issue to this file, I'm clueless because I don't engage often with Bluetooth, C or the Linux kernel, but I'm pretty sure that the type of message it fails on starts as disallowed and is never explicitly set to allowed.
https://github.com/torvalds/linux/... -
@hjk101 Yes, it never solved the problem, not even temporarily.
-
Bluetoothd locks up whenever I attempt to connect to my headset. Today the controller went down and wouldn't come back when I restarted bluetoothd, I had to cycle the antenna with rfkill. Even if the headset is broken, a faulty peer should NOT cause this much trouble to a safe Bluetooth implementation.
Stackoverflow.
I'm the git master in my group for a uni project as I am the only one with some experience.
This is what I ha...
Such a relief
For the past 5 odd years my Bluetooth headphones wouldn't connect to my laptop properly and I had to issue a second Connect command while the first was pending to get it working. I even wrote a script to automate this: https://github.com/lbfalvy/...
Today Bluez finally released a patch for this. That's right, after many years, today the issue got fixed; Connect now returns an error if a call is already pending.
My headphones still don't work, but my workaround is now correctly recognized as invalid input.
rant
pain
bluetooth
bugs
fix the bug not the workaround
bluez