I’m curious how software can be created and evolve over time. I’m afraid that at some point, we’ll realize there are issues with the software we’re using that can only be remedied by massive changes or a complete rewrite.
Are there any instances of this happening? Where something is designed with a flaw that doesn’t get realized until much later, necessitating scrapping the whole thing and starting from scratch?
I dont know if this even makes sense but damn if bluetooth/ audio could get to a point of “It just works”.
What’s your latest disfavor?
Mine is the priorisation of devices. If someone turns on the flatshare BT box and I’m listening to Death Metal over my headphones, suddenly everyone except me is listening to Death Metal.
It’s been a while (few years actually) since I even tried, but bluetooth headsets just won’t play nicely. You either get the audio quality from a bottom of the barrel or somewhat decent quality without microphone. And the different protocol/whatever isn’t selected automatically, headset randomly disconnects and nothing really works like it does with my cellphone/windows-machines.
YMMV, but that’s been my experience with my headsets. I’ve understood that there’s some propietary stuff going on with audio codecs, but it’s just so frustrating.
Just being… crappy?
Not connecting automatically. Bad quality. Some glitchy artifacts. It gets horrible The only work around I’ve found is stupid but running
apt reinstall --purge bluez gnome-bluetoothand it works fine. So annoying but I have to do this almost every day.Reinstalling should change nothing. If its getting corrupted check your drive and Ram.
I don’t know why this works, but if im having issues, i do this, and it fixes all of them across the board. Even just restarting the service is not as effective as this. That some times works, sometimes doesn’t.
I’m confident its not a drive or ram issue. Its a blue tooth issue/ audio. But I also can’t explain why it is so consistent.
That really sounds like shitty firmware at one end or the other
Have you checked the logs?
Yep. Nothing sus. I also don’t have the time to do a deep dive. I need to work. It might be this chip. It might be my bluetooth headset (but I have issues with my mouse and keyboard too). I don’t have time to figure it out, so I just keep this on a copy paste ready terminal and if I have issue, I run the command and I’m good to go.
Not to mention bluez aggressive conne ts to devices. It would be nice if my laptop in the other room didn’t interrupt my phones connection to my earbuds.
Then again, we also have wired for a reason. Hate all you want but it works and is predicable
It does for me. What issue are you having?
My most recent issue with Bluez is that it’s been very inconsistent about letting me disable auto-switching to HSP/HFP (headset mode) when joining any sort of call.
It’s working now, but it feels like every few months I need to try a different solution.
deleted by creator
We have clearly had different experiences. If you are a developer maybe troubleshoot and file an issue.
Bluetooth in general is just a mess and it’s sad that there’s no cross-platform sdk written in C for using it.