Hi Gustavo, On Wed, Apr 25, 2012 at 10:48 PM, Gustavo Padovan <gustavo@xxxxxxxxxxx> wrote: > Can you also send the output of hciconfig -a? Sure. Here it is (with my bluetooth address hidden): ----------------------------------------------- hci0: Type: BR/EDR Bus: USB BD Address: 02:03:05:07:11:13 ACL MTU: 384:8 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:978 acl:0 sco:0 events:27 errors:0 TX bytes:355 acl:0 sco:0 commands:26 errors:0 Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'localhost-0' Class: 0x420100 Service Classes: Networking, Telephony Device Class: Computer, Uncategorized HCI Version: 1.1 (0x1) Revision: 0x7a6 LMP Version: 1.1 (0x1) Subversion: 0x7a6 Manufacturer: Cambridge Silicon Radio (10) ------------------------------------------------------- Perhaps the following is the correct patch (works with my device): ----------------------------------------------------------------- --- bluez-4.99/plugins/hciops.c.orig 2012-03-05 11:03:57.000000000 +0200 +++ bluez-4.99/plugins/hciops.c 2012-04-26 06:38:53.105166053 +0300 @@ -565,7 +565,7 @@ static void set_event_mask(int index) } if (dev->features[3] & LMP_RSSI_INQ) - events[4] |= 0x04; /* Inquiry Result with RSSI */ + events[4] |= 0x02; /* Inquiry Result with RSSI */ if (dev->features[5] & LMP_SNIFF_SUBR) events[5] |= 0x20; /* Sniff Subrating */ ------------------------------------------------------------------- Above the code that I quoted there's another "event[4] |= 0x02" with the comment "Inquiry Result with RSSI". Surely it cannot be both 0x02 and 0x04? The bluetooth spec 1.2 suggests 0x02 is correct. Regards, Colin -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
