Another interesting discovery: when bluetoothd is stopped and bluez
version is 4.60, hciconfig can show all info and i can scan for
another devices:
$ sudo hciconfig -a
hci0: Type: USB
BD Address: 00:1A:7D:0A:C8:8A ACL MTU: 377:10 SCO MTU: 16:0
UP RUNNING
RX bytes:1012 acl:0 sco:0 events:29 errors:0
TX bytes:114 acl:0 sco:0 commands:31 errors:0
Features: 0xff 0xff 0x0d 0x38 0x08 0x08 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy:
Link mode: SLAVE ACCEPT
Name: 'Broadcom BCM2035'
Class: 0x000000
Service Classes: Unspecified
Device Class: Miscellaneous,
HCI Ver: 1.1 (0x1) HCI Rev: 0x3 LMP Ver: 1.1 (0x1) LMP Subver: 0x800
Manufacturer: Broadcom Corporation (15)
$ hcitool scan
Scanning ...
00:1E:DC:9B:FF:C4 HBH-DS205
but afer bluetoothd start problem reappears, hciconfig doesn't show
all info and hcitool scan fails
--
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
