Ubuntu
bluez package

  1. Bug #424215
  2. Comment #23

Comment 23 for bug 424215

Revision history for this message
Jens Janssen (jayjay) wrote :

The problem is not bluez but the settings bluez uses. You can use hciconfig to put your device into the correct mode.

hciconfig hci0 lm ACCEPT,MASTER
hciconfig hci0 lp HOLD,SNIFF,PARK

should be enough where hci0 is your bluetooth device.

I put this in a udev rule so that these changes are applied every startup.

For that you can copy following text:

# put this file in /etc/udev/rules.d
# choose a higher rule number than the existing file at /lib/udev/rules.d/XX-bluetooth.rules
ACTION=="add", SUBSYSTEM=="bluetooth", KERNELS=="hci0", RUN+="/usr/sbin/hciconfig hci0 lm ACCEPT,MASTER", RUN+="/usr/sbin/hciconfig hci0 lp HOLD,SNIFF,PARK"

You can name the file 100-bluetooth.rules. Hope this helps.