Hi everybody,
i’m a long time Debian user and, while i’ve always loved the Linux experience, the bluetooth side of things was always a little bit… painful.
Lately, i’ve been digging on how bluetooth on Linux works (i knew about BlueZ, but i didn’t know about HCI sockets, standard protocols for bluetooth controllers, …). Seeing how Android manages to work fine with bluetooth (yes, i know, money and company support, blah blah blah), i was thinking about re-writing the bluetooth daemon, in order to be modern, modular, safe (written in Rust), stable and retro-compatible (exposes the same D-Bus APIs as BlueZ) I already found some documents about HCI socket in Linux, HCI communication with bluetooth controllers, HID standards for Bluetooth, etc…
My questions are:
- is this a good idea?
- does somebody want to collaborate?
Thanks for reading.
EDIT: The repository is https://github.com/djtech-dev/reblued but at the moment is pretty much empty, just the project’s skeleton, license, README and disussions for collaborators.
I think it can be good attempt to reimplement it and make it work stable and normal.My hesdphones sometimes randomly dropping connection and need to restart bluez to make them connect again.Also have to say about audio profiles for bluetooth headphones. While A2DP can deliver can good high quality sound but cannot work in duplex mode and can noy record ur headphones microphone and it would be nice if u share link for ur git :)
The repository is https://github.com/djtech-dev/reblued but at the moment is pretty much empty, just the project’s skeleton, license, README and disussions for collaborators.