Bluetooth issue - apply kernel patch?

Hi guys,

I am running the latest OSMC on a raspberry pi 2 and am now trying to get a bluetooth mouse (Microsoft Designer Mouse) to work.
All info that I can find through the OSMC menu, bluetoothctl and hciconfig looks fine as far as I can tell. I can scan/pair/trust/connect, and the menu also shows a nice blue check symbol - but no matter what I did so far, the mouse won’t actually start moving. The pi has no energy problems, which seems to be a common case for such problems.

This is the output of bluetoothctl info after scan/pair/trust/connect:

[Designer Mouse]# info C1:FB:16:B2:96:59
Device C1:FB:16:B2:96:59
    Name: Designer Mouse
    Alias: Designer Mouse
    Appearance: 0x03c2
    Icon: input-mouse
    Paired: yes
    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)
    Modalias: usb:v045Ep0805d0100
    RSSI: -42

dmesg shows this issue:

[60005.417152] Bluetooth: SMP security requested but not available

I looked around extensively and it seems likely that this is connected to 104011 – SMP Security check breaks formerly working bluetooth mouse connection . There’s a kernel patch in the latest git repository, and even though it is not quite clear that it solves the issue, I’d like to give it a try. I have never run a manually compiled kernel, so would like to get some advice on how to best do this, maybe there’s an easier way of applying a patch (it’s only a 3-line change)?

Other ideas on how to solve the problem would be most welcome, too, of course :).

As a side issue, the connection can never be re-established after I power down either the pi or the mouse, I always have to do the whole configuration in bluetoothctl or the osmc menu again. This seems to be a common thing, though, and I’ll look into it once the mouse worked at least one time :).