Hi, Am 26.01.2012 13:29, schrieb Luiz Augusto von Dentz: > do you have any logs when Socket is disabled? Jan 26 14:28:10 localhost bluetoothd[813]: Discovery session 0x7f5a22e73c50 with :1.41 activated Jan 26 14:28:13 localhost bluetoothd[813]: Stopping discovery Jan 26 14:28:24 localhost kernel: [ 349.752870] input: 00:16:94:0B:XX:XX as /devices/virtual/input/input17 Jan 26 14:28:24 localhost pulseaudio[1072]: [pulseaudio] module-bluetooth-device.c: Bluetooth audio service not available Jan 26 14:28:24 localhost pulseaudio[1072]: [pulseaudio] module-bluetooth-device.c: Service not connected Jan 26 14:28:24 localhost pulseaudio[1072]: [pulseaudio] module.c: Failed to load module "module-bluetooth-device" (argument: "address="00:16:94:0B:XX:XX" path="/org/bluez/813/hci0/dev_00_16_94_0B_XX_XX""): initialization failed. So you were right, it seems that PulseAudio is the culprit here. However it works with bluez-4.96, although sockets are not enabled explicitly? So the question stays whether bluez 4.96 uses sockets implicitly, or whether PulseAudio doesn't work with bluez-4.98. Best regards, Karol Babioch
Attachment:
signature.asc
Description: OpenPGP digital signature
