microsoft mouse BluetoothMouse3600 is not work

Status changed to 'Confirmed' because the bug affects multiple users.

Seems also to affect "Microsoft IntelliMouse Explorer for Bluetooth" and "Microsoft Wireless Notebook Presenter Mouse 8000"

Brand/Model: Microsoft Bluetooth Mobile 3600 (uses BLE).
I bought it last week and it was tested in the shop (Win8, no pin required). I knew Microsoft does NOT have support for Linux (exception for Android). System requirements are Win/Mac/Android. But I want this experience (Does BLE work in Ubuntu?).

I don't have experince with posting bugs or dealing with BT tools. But here is the output of some bluetoothctl commands. I just manually set trust (!?).

[BluetoothMouse3600]# info D7:E6:A4:2C:85:F3
Device D7:E6:A4:2C:85:F3
 Name: BluetoothMouse3600
 Alias: BluetoothMouse3600
 Appearance: 0x03c2
 Icon: input-mouse
 Paired: no
 Trusted: yes
 Blocked: no
 Connected: yes
 LegacyPairing: no
 UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
 UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
 UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
 UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb)
 UUID: Human Interface Device (00001812-0000-1000-8000-00805f9b34fb)
[BluetoothMouse3600]# pair D7:E6:A4:2C:85:F3
Attempting to pair with D7:E6:A4:2C:85:F3
Failed to pair: org.bluez.Error.Failed

It seems to be some issue with pairing step. Also bellow dmesg shows some error (no devices). I tested a BT headphone (do not know protocol ver) with success. So don't know if it's the controller.

> dmesg
[ 17.566030] usb 2-6: device descriptor read/64, error -110
[ 22.799520] usb 2-6: New USB device found, idVendor=0cf3, idProduct=e005
[ 22.799524] usb 2-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 22.918579] Bluetooth: RFCOMM TTY layer initialized
[ 22.918590] Bluetooth: RFCOMM socket layer initialized
[ 22.918597] Bluetooth: RFCOMM ver 1.11

> lsusb -t
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
    |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/11p, 480M
    |__ Port 5: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M
    |__ Port 5: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M
    |__ Port 6: Dev 6, If 0, Class=Wireless, Driver=btusb, 12M
    |__ Port 6: Dev 6, If 1, Class=Wireless, Driver=btusb, 12M
    |__ Port 8: Dev 5, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M

Tested with xenial in 2016-12-03.

This bug seems to be included (duplicate?) in #1510570.

The following seems to solve my problem:

1) remove /lib/udev/rules.d/50-bluetooth-hci-auto-poweron.rules

2) change /etc/bluetooth/main.conf: uncomment [Policy] and uncomment/set AutoEnable=true

The dmesg error also desappeared:
[ 17.566030] usb 2-6: device descriptor read/64, error -110

------------------------------------------

#1510570 is much more actively commented and there are other "solutions" I did not tried. Maybe the above one is not the correct one, so stay tuned with #1510570. But after many reboots, connects and disconnects I am just happy with the result. M$ mouse 3600 works on xenial.