kernel-packages team mailing list archive

[Yung Shen <1510570@xxxxxxxxxxxxxxxxxx>]

found a workaround to this:

if you happened to upgrade from vivid(15.04) or you know how to get vivid kernel install properly,
you can boot the system with 3.19 kernel and pairing up the mouse using bluetoothctl manually
then reboot with 4.2, the mouse will still paired and working.

$ bluetoothctl (entering interactive mode)
$ agent on
$ default-agent
$ pairable on
$ scan on
$ devices (to see the device mac that you want to pair)
$ pair <dev mac>
$ trust <dev mac>
$ connect <dev mac>

verified versions(stable while posted):
bluez 5.35-0ubuntu2
linux-image-3.19.0-43-generic 3.19.0-43.49
linux-image-4.2.0-23-generic 4.2.0-23.28

-- 
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