> Hi Artem, > > please do not top post on this mailing list. It does break the reading thread. > >> Here is hcitool info: >> >> BD Address: 10:B7:F6:01:31:ED >> Device Name: Monster Clarity >> LMP Version: 2.1 (0x4) LMP Subversion: 0x189c >> Manufacturer: Cambridge Silicon Radio (10) >> Features page 0: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00 >> <3-slot packets> >> Features page 1: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x59 0x83 >> >> Label also says Precision Micro Bluetooth Speaker 100. > > normally all CSR based solutions should just work. Maybe this is just a bad firmware. Are you sure that Connection Pending is really causing the observed problem. It sounds strange to hit that on a CSR based speaker. > > Regards > > Marcel > I compared the logs from avtest and bluetoothd (attached earlier in this thread). I think the only difference that could matter is this Authorization Pending response. Thanks, Artem -- 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
