Skip to main content
added /lib/udev/hid2hci info
Source Link

I do not have a definitive answer, but for me the output of lsusb is:

Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

and hcitool scan works for me, listing the visible devices.

Maybe your device is not in "HCI Mode"? Try:

/lib/udev/hid2hci

I also find that I need to use sudo to use some commands like hcitool info

sudo hcitool info

else I get the error: Can't create connection: Operation not permitted

I do not have a definitive answer, but for me the output of lsusb is:

Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

and hcitool scan works for me, listing the visible devices.

Maybe your device is not in "HCI Mode"?

I also find that I need to use sudo to use some commands like hcitool info

sudo hcitool info

else I get the error: Can't create connection: Operation not permitted

I do not have a definitive answer, but for me the output of lsusb is:

Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

and hcitool scan works for me, listing the visible devices.

Maybe your device is not in "HCI Mode"? Try:

/lib/udev/hid2hci

I also find that I need to use sudo to use some commands like hcitool info

sudo hcitool info

else I get the error: Can't create connection: Operation not permitted

added sudo info
Source Link

I do not have a definitive answer, but for me the output of lsusb is:

Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

and hcitool scan works for me, listing the visible devices.

Maybe your device is not in "HCI Mode"?

I also find that I need to use sudo to use some commands like hcitool info

sudo hcitool info

else I get the error: Can't create connection: Operation not permitted

I do not have a definitive answer, but for me the output of lsusb is:

Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

and hcitool scan works for me, listing the visible devices.

Maybe your device is not in "HCI Mode"?

I do not have a definitive answer, but for me the output of lsusb is:

Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

and hcitool scan works for me, listing the visible devices.

Maybe your device is not in "HCI Mode"?

I also find that I need to use sudo to use some commands like hcitool info

sudo hcitool info

else I get the error: Can't create connection: Operation not permitted

Source Link

I do not have a definitive answer, but for me the output of lsusb is:

Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

and hcitool scan works for me, listing the visible devices.

Maybe your device is not in "HCI Mode"?