Comment 12 for bug 781556

Simply performing bccmd in the bluetooth init script might not be a good idea, as it's not applicable to other bluetooth modules. One reliable way is to keep it in the udev rules. I used the rules below which is working for me:

SUBSYSTEM=="bluetooth", SUBSYSTEMS="usb", ATTRS{idVendor}=="148f", ATTRS{idProduct}=="2000", RUN+="/usr/sbin/bccmd -d $kernel psset -r 0x028c 0x0001"

This is not the optimal fix as it's going to set the key anyway to 1 upon the hci device is added, but could be less intrusive.