Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Linux parts requires exclusive hci access. #107

Closed
dezi opened this issue Aug 12, 2023 · 2 comments
Closed

Linux parts requires exclusive hci access. #107

dezi opened this issue Aug 12, 2023 · 2 comments

Comments

@dezi
Copy link

dezi commented Aug 12, 2023

Hi

as I learned in the middle of developing, this package
requires exclusive access of the HCI interface under linux.

Means: You cannot use any other bluetooth device at the
same time while using Your go-application.

Means: No mouse, no keyboard, no speakers, no headsets.

This renders the linux part for me virtually useless.

Solution: Migrate linux funktionality using

github.com/muka/go-bluetooth

which is using non-exclusive dBus access.

Regards,
dezi

@huguesb
Copy link

huguesb commented Dec 30, 2023

arguably a feature, not a bug: a dbus-based approach has many more dependencies and many more points of failure (as I painfully learned trying to figure out why all bluez-based apps were miserably failing on some of my machines in inconsistent ways, despite bluetoothctl and btmgmt seemingly working fine...

@estutzenberger
Copy link

Exclusive HCI access is a design choice of this library. It is meant for having full access control of the radio for embedded and edge applications that do not require additional connected bluetooth devices.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants