Broadcom BCM2045B3 bluetooth adapter detected as mouse and keyboard

[Rishi]

Binary package hint: bluez

I recently bought Insignia bluetooth headset (Best Buy brand) which came with a bluetooth adapter. When I plug in the adapter it is not recognized as bluetooth adapter. It is recognized as Keyboard and mouse instead. I am attaching a file which contains the snippets you might need to narrow down the bug. I am using Ubuntu Intrepid release with all the updates till Dec 17th 2008, 8AM.

[Ambricka (petter-ambricka)]

Have you tried "sudo hid2hci"?

[Rishi (rishikes)]

Thanks for your reply. I will trying this.

Rishi

On Fri, Mar 6, 2009 at 3:06 PM, Ambricka <email address hidden> wrote:
> Have you tried "sudo hid2hci"?
>
> --
> Broadcom BCM2045B3 bluetooth adapter detected as mouse and keyboard
> https://bugs.launchpad.net/bugs/308962
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “bluez” source package in Ubuntu: New
>
> Bug description:
> Binary package hint: bluez
>
> I recently bought Insignia bluetooth headset (Best Buy brand) which came with a bluetooth adapter. When I plug in the adapter it is not recognized as bluetooth adapter. It is recognized as Keyboard and mouse instead. I am attaching a file which contains the snippets you might need to narrow down the bug. I am using Ubuntu Intrepid release with all the updates till Dec 17th 2008, 8AM.
>

[Ryan E (wyild1)]

Morning

I have encountered the same issue, but using a RocketFish USB Dongle (Same chipset BCM2045B3) for a Rocketfish Mouse

Output of sudo hid2hci:

yild1@EXXXX:~$ sudo hid2hci
No devices in HID mode found

I cannot get this device to connect properly. dmesg states its a mouse:

[ 285.536331] hub 2-2:1.0: USB hub found
[ 285.538194] hub 2-2:1.0: 3 ports detected
[ 285.829166] usb 2-2.2: new full speed USB device using uhci_hcd and address 14
[ 285.967577] usb 2-2.2: configuration #1 chosen from 1 choice
[ 285.974705] input: Broadcom Corp BCM2045B3 ROM as /devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2.2/2-2.2:1.0/input/input17
[ 286.033397] input,hidraw2: USB HID v1.11 Keyboard [Broadcom Corp BCM2045B3 ROM] on usb-0000:00:1d.1-2.2
[ 286.110134] usb 2-2.3: new full speed USB device using uhci_hcd and address 15
[ 286.260287] usb 2-2.3: configuration #1 chosen from 1 choice
[ 286.268453] input: Broadcom Corp BCM2045B3 ROM as /devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2.3/2-2.3:1.0/input/input18
[ 286.332380] input,hidraw3: USB HID v1.11 Mouse [Broadcom Corp BCM2045B3 ROM] on usb-0000:00:1d.1-2.3

If you need more info please ask!

Cheers!

[Ryan E (wyild1)]

btw i have already tried update-usbids and rebooted (ya dumb windows habit) and still not luck

Cheers!

[Bill Westrup (billwestrup)]

I have the same problem as well. (Insignia Bluetooth adapter) After many hours of googling for answers it appears that the problem with bluetooth adapters being recognized as keyboard, usb hub and mouse is quite common. As far as I can tell, no solution to this issue has ever been found. Most users appear to be giving up and simply buying a better supported adapter. This is unfortunate since this headset was the best deal available when I purchased it...other bluetooth headsets cost twice as much.

[Mario Limonciello (superm1)]

I'm suspecting this isn't going to work OOTB currently on karmic, but using a karmic A2 disk, you should be able to do a test that might work to switch the modes.

So follow these steps:
1) Bootup a karmic alpha2 disk. You don't have to install it, just boot up it.
2) Look at the output of lsusb
# lsusb
Bus 002 Device 002: ID 05ca:18a1 Ricoh Co., Ltd
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 a) The column that shows the two 4 digit pairs is what we are looking at. Take note of BOTH of the pairs that are there
     for the keyboard and mouse

3) Run this command with those pairs inserted. The first of 4 digit pair is the VENDOR. The second is the PRODUCT:

$ sudo hid2hci --method dell -v VENDOR -p PRODUCT --mode hci

So if I was trying to run the command on my Ricoh device (which wouldn't do anything), i'd run:

$ sudo hid2hci --method dell -v 05ca -p 18a1 --mode hci

4) To check if that command works, run lsusb again and check for a new bluetooth radio device. If it exists please post it in this bug and this can be fixed OOTB for you in a later karmic alpha.

5) If that command doesn't work, try the other pair and repeat step 4.

[papukaija (papukaija)]

Thank you for reporting this bug to Ubuntu. Intrepid reached EOL on April 30 2010. Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

Please either a) upgrade and test again or b) increase the verbosity of the steps to recreate it so we can try again.

Please feel free to report any other bugs you may find.

[papukaija (papukaija)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Rishi (rishikes)]

Unfortunately I do not have the hardware anymore: neither the computer nor the bluetooth dongle. Please close this ticket.

[papukaija (papukaija)]

Thank you for taking the time to make Ubuntu better. I'm leaving this bug open since one of the 4 (excluding Rishi and me) subscribers might still have this bluetooth adapter and therefore would be able to test this bug in a newer release of Ubuntu. Please submit any future bugs you may find.

[papukaija (papukaija)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[Bill Westrup (billwestrup)]

Hey, I found my Insignia blue-tooth adapter the other day and when I
plugged it into my Linux desktop at work it came up and was recognized
as a blue-tooth adapter immediately! So far performance has been great.
Thanks so much for fixing this. I had filed this bug report because the
device was originally recognized as a keyboard and mouse. I believe I
was running Linux Mint 5 at the time I filed the report. I'm running
Linux Mint Version 9 32bit currently

Thanks,
Bill

On 9/30/2010 5:14 PM, papukaija wrote:
> We are closing this bug report because it lacks the information we need
> to investigate the problem, as described in the previous comments.
> Please reopen it if you can give us the missing information, and don't
> hesitate to submit bug reports in the future. To reopen the bug report
> you can click on the current status, under the Status column, and change
> the Status back to "New". Thanks again!
>
> ** Changed in: bluez (Ubuntu)
> Status: Incomplete => Invalid
>
>

[papukaija (papukaija)]

Thank you for your report. However, this bug stays as invalid as the exact version number fixing this bug is unknown. Feel free to report any other bugs you may find in Ubuntu.