Hello.
Almost every distribution gets it wrong and enables hid2hci by default
(besides Fedora where I already intervened twice).
This is a real problem, because it disables Bluetooth keyboards and/or
mice which aren't paired with bluez, thus many Live-CDs and default
installs aren't usable when only a Bluetooth keyboard is connect.
An easy solution to disable that behaviour would be to install an empty
rule in /etc/udev/rules.d named the same as the one in
/lib/udev/rules.d. It could just contain a comment like
# Delete this file in order to activate hid2hci.
#
# You might need to pair your Bluetooth keyboard and/or mouse
# in order to still use it when hid2hci is enabled.
This (empty) rule would then be used by udev instead of the one in
/lib/udev/rules.d and thus would be an easy to use configuration switch.
I would appreciate it, if the default bluez install would install such
an empty rule too, if configure was called with --enable-hid2hci.
I think otherwise that problem will never go away. It's really
unbelievable how many distributions got this wrong and thus how many
Live-CDs and default installations are unusable when only a Bluetooth
keyboard is used with a hid-aware Bluetooth dongle.
Regards,
Alexander Holler
Am 01.12.2013 18:26, schrieb Alexander Holler:
> Hello.
>
> Almost every distribution gets it wrong and enables hid2hci by default
> (besides Fedora where I already intervened twice).
>
> This is a real problem, because it disables Bluetooth keyboards and/or
> mice which aren't paired with bluez, thus many Live-CDs and default
> installs aren't usable when only a Bluetooth keyboard is connect.
>
> An easy solution to disable that behaviour would be to install an empty
> rule in /etc/udev/rules.d named the same as the one in
> /lib/udev/rules.d. It could just contain a comment like
(...)
Unfortunately that isn't a very practical idea, as the rule(-file) would
likely become installed again with every upgrade or reinstall. :(
> I think otherwise that problem will never go away. It's really
> unbelievable how many distributions got this wrong and thus how many
> Live-CDs and default installations are unusable when only a Bluetooth
> keyboard is used with a hid-aware Bluetooth dongle.
So another idea seems to be necessary to either educate distributions
(or their package maintainers) that they should build a distinct package
for hid2hci and don't install that package by default, or some mechanism
which enables the user to enable/disable hid2hci (as it was the case
before the udev-rule went to /lib),
Regards,
Alexander Holler