kernel-packages team mailing list archive

[Keith McClelland <1510570@xxxxxxxxxxxxxxxxxx>]

I have been working with a Microsoft Designer Mouse (also a BLA device).
I went to AskUbuntu to try to find out why I could not use it with
Ubuntu 15.10. [I have a Microsoft Surface Pro3 and am using a home-built
kernel but the kernel does not seem to affect this problem.] I have
followed the instructions in comment #9 and find that the mouse
works...for 10 minutes. Apparently each use of the mouse resets a
10-minute watchdog timer and the mouse is disconnected if ever this
timer expires.

It won't come back on its own. To reconnect it, you must "remove" the
mouse using Blueman or the Gnome Bluetooth Manager (I use the former),
search it out again, and set it up again. Usually this works the first
time but sometimes you have to go through it again. Despite the fact
that the mouse works it is reported as of type "unknown" or "All types."

I have attached a chunk of syslog showing the full cycle.  I removed the
old and reconnected it at 19:19. I used the mouse for about 4 minutes
and then turned it upside down at 19:23. It disconnected 10 minutes
later at 19:33. This sequence is repeatable and invariant.

Is this the right bug for this our should another be started?

Thanks,
Keith

** Attachment added: "syslog"
   https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1510570/+attachment/4523863/+files/syslog

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  BLE pairing fail

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.

  But this pairing doesn't work very well. Mouse is seen but pairing fail.
  More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

  This is due to udev rule that use "hcitool" to power on device.
  Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules.

  here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138
  And a ppa to test it: https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1510570/+subscriptions