How do I get Logitech MX Anywhere 2 to work in 16.04 (Bluetooth smart)

New question following post
Logitech MX Anywhere 2 mouse pairs but doesn't do anything

Pairing and connecting via built-in bluetooth manager and blueman works.
also via commandline:

bluetoothctl

Output see below.

[MX Anywhere 2]# info DE:CE:68:71:F9:97
Device DE:CE:68:71:F9:97
    Name: MX Anywhere 2
    Alias: MX Anywhere 2
    Appearance: 0x03c2
    Icon: input-mouse
    Paired: yes
    Trusted: yes
    Blocked: no
    Connected: yes
    LegacyPairing: no
    UUID:                           (1800)
    UUID:                           (1801)
    UUID:                           (180a)
    UUID:                           (180f)
    UUID:                           (1812)
    UUID: Vendor specific           (00010000-0000-1000-8000-011f2000046d)
    Modalias: usb:v046DpB013d0007
[MX Anywhere 2]# paired-devices 
Device DE:CE:68:71:F9:97 MX Anywhere 2

What does not work is input, as in “the mouse doesn’t move the cursor”

Here is Solutions:

We have many solutions to this problem, But we recommend you to use the first solution because it is tested & true solution that will 100% work for you.

Solution 1

My device is a Surface Edition Bluetooth LE Arc Touch Mouse made by Microsoft.

I couldn’t get it to connect with any distro I’ve tried over the past year, until OpenSuse Leap. Then I knew it was possible! But I like Ubuntu (I know I know)

Came across this thread and had everything looking exactly like your read out shows:

Name: Arc Touch Mouse SE
Alias: Arc Touch Mouse SE
Appearance: 0x03c2
 Icon: input-mouse
 Paired: yes  
 Trusted: yes
 Blocked: no
Connected: yes
LegacyPairing: no 

And Still NOTHING! No movement even though its clearly listed as paired, trusted, unblocked, and connected! I was about to give up for good but decided to try one last thing..

I deleted the device using “remove” and issued the following commands in this exact order which resulted in my device working! After a year of trying to find a way.

[bluetooth]# power off
[bluetooth]# power on
[bluetooth]# scan on
[bluetooth]# connect XX:XX:XX:XX:XX:XX
[Arc Touch Mouse SE]# trust
[Arc Touch Mouse SE]# connect XX:XX:XX:XX:XX:XX
[Arc Touch Mouse SE]# pair
[Arc Touch Mouse SE]# unblock
[Arc Touch Mouse SE]# power off
[bluetooth]# power on

So I can confirm that Ubuntu 16.04 does indeed support Bluetooth LE devices

Solution 2

I managed to get my Anywhere MX2 to work on Ubuntu 16.04 thanks to this post.

After connecting the mouse in the “Bluetooth” configuration – it was still not working.
Running bluetoothctl and “info ” gave me this:

➜  ~ bluetoothctl 
[NEW] Controller 5C:51:4F:DC:FB:D0 ChromeLinux_CBDE [default]
[NEW] Device FB:59:51:BF:60:XX MX Anywhere 2
[bluetooth]# info FB:59:51:BF:60:XX
Device FB:59:51:BF:60:XX
    Name: MX Anywhere 2
    Alias: MX Anywhere 2
    Appearance: 0x03c2
    Icon: input-mouse
    Paired: yes
    Trusted: yes
    Blocked: no
    Connected: no
    LegacyPairing: no
    UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
    UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
    Modalias: usb:v046DpB013d0007

As you can see – my device was somehow not connected. And thus not responsive. What I did to make it work was only call ‘connect’:

[bluetooth]# connect FB:59:51:BF:60:XX
Attempting to connect to FB:59:51:BF:60:XX
[CHG] Device FB:59:51:BF:60:XX Connected: yes
Connection successful
[CHG] Device FB:59:51:BF:60:XX UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[..snip..]
[CHG] Device FB:59:51:BF:60:XX Paired: yes

And after that everything “just works(TM)”. Thanks for the useful additional information to this post.

Solution 3

In my case the issue that you can find here for 15.10 and the provided solution helped me:

hciconfig hci0 sspmode 1
hciconfig hci0 down
hciconfig hci0 up

Note: Use and implement solution 1 because this method fully tested our system.
Thank you 🙂

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply