Public bug reported:
A bluetooth usb device is failing to work consistently. The device is a
no-name brand, and the output of lsusb -v is attached.
Trying to pair a Nokia 6310 mobile phone, "hcitool scan" generally fails
to detect the phone entirely, but intermittently returns its correct
bdaddr without its device name. An example, with the bdaddr replaced by
xxs, is:
hcitool scan --class
Scanning ...
BD Address: xx:xx:xx:xx:xx:xx [mode 1, clkoffset 0x4094]
Device name: n/a
Device class: Phone, Cellular (0x500204)
The same hardware works ok and connects properly under windows xp, using
bluesoleil. The phone also pairs and connects properly using ubuntu
8.10 on a macbook pro with built-in bluetooth.
It looks to me like the btusb or bluez software does not fully handle
this bluetooth device, and maybe has some intermittent timing problems.
ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
MachineType: System manufacturer System Product Name
Package: linux-image-2.6.28-10-generic 2.6.28-10.33
ProcCmdLine: root=UUID=06da8c6c-d07d-46e8-becf-5a4f4e3a31b1 ro quiet splash
ProcEnviron:
LANG=en_AU.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-10.33-generic
SourcePackage: linux
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: amd64 apport-bug
--
btusb hcitool scan failing
https://bugs.launchpad.net/bugs/344655
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
