Bluetooth Microsoft Sculpt Comfort Mouse repeatedly needs repairing

[jawz101]

I've tried this mouse on Antergos using MATE desktop on the same computer and it's reliable.
Every time I pair this on Ubuntu Mate 16.01 x64 the device will lose connection and need re-pairing after ever reboot or resume.

Controller HP-EliteBook-2570p

----------

A)

as I wiggle the mouse bluetoothctl will see it briefly but there's no mouse movement.

user@HP-EliteBook-2570p:~$ bluetoothctl
[NEW] Controller 08:3E:8E:xx:xx:xx HP-EliteBook-2570p [default]
[NEW] Device C0:33:5E:xx:xx:xx Microsoft Sculpt Comfort Mouse
[CHG] Device C0:33:5E:xx:xx:xx Connected: no
[CHG] Device C0:33:5E:xx:xx:xx Class: 0x000580
[CHG] Device C0:33:5E:xx:xx:xx Icon: input-mouse
[CHG] Device C0:33:5E:xx:xx:xx Connected: yes
[CHG] Device C0:33:5E:xx:xx:xx Connected: no
[CHG] Device C0:33:5E:xx:xx:xx Connected: yes
[CHG] Device C0:33:5E:xx:xx:xx Connected: no... and repeats these last 2 lines continuously as I move the mouse

B)

if I try to connect in the blueman appliet I get this error
Connection Failed: blueman.bluez.errors.DBusFailedError: Input/output error...

C) dmesg output:

[ 55.607088] hidraw: raw HID events driver (C) Jiri Kosina
[ 55.609255] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 55.609260] Bluetooth: HIDP socket layer initialized
[ 55.631331] hid-generic 0005:045E:07A2.0001: unknown main item tag 0x0
[ 55.631620] input: Microsoft Sculpt Comfort Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/bluetooth/hci0/hci0:12/0005:045E:07A2.0001/input/input23
[ 55.632113] hid-generic 0005:045E:07A2.0001: input,hidraw0: BLUETOOTH HID v1.29 Mouse [Microsoft Sculpt Comfort Mouse] on 08:3e:8e:9e:xx:xx

----------

I've Googled and similar problems have been reported on the Ubuntu launchpad many times over the years but it refers to editing a pin code database file the doesn't exist on MATE since it uses a different bluetooth manager. Since this isn't
/usr/share/gnome-bluetooth/pin-code-database.xml

https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1094744

[jawz101 (jawz101-deactivatedaccount-deactivatedaccount)]

It's not a duplicate. I'm on Ubuntu MATE and the fix in your referenced tickt 10947444 refers to a fix involving editing a file /usr/share/gnome-bluetooth/pin-code-database.xml
and adding a device OUI for this mouse. Ubuntu MATE doesn't use gnome-bluetooth. That file doesn't even exist on Ubuntu MATE.