Difference between revisions of "Bluetooth mouse"

From ArchWiki
Jump to: navigation, search
(Configuring through bluetoothctl: please don't write in 1st person, see Help:Style)
(Troubleshooting: options and not option)
 
(41 intermediate revisions by 14 users not shown)
Line 1: Line 1:
 
[[Category:Mice]]
 
[[Category:Mice]]
 
[[Category:Bluetooth]]
 
[[Category:Bluetooth]]
[[cs:Bluetooth Mouse]]
+
[[cs:Bluetooth mouse]]
[[ru:Bluetooth Mouse]]
+
[[ja:Bluetooth マウス]]
This article describes how to set up a [[Bluetooth]] mouse manually with no desktop assistance for Bluetooth. For example, a minimalist XFCE installation.  
+
[[ru:Bluetooth mouse]]
 +
{{Related articles start}}
 +
{{Related|Bluetooth}}
 +
{{Related|Bluez4}}
 +
{{Related|Mouse polling rate}}
 +
{{Related articles end}}
 +
 
 +
This article describes how to set up a [[Bluetooth]] mouse through the command line without relying upon a graphical application.
  
 
== Installation ==
 
== Installation ==
  
You need the {{Pkg|bluez}} package and optionally the {{Pkg|bluez-utils}} package from the extra repository.
+
Install the {{Pkg|bluez}} package which contains the current Linux bluetooth stack (Bluez5). You may also want to install {{Pkg|bluez-utils}} which provides the ''bluetoothctl'' utility. See [[Bluetooth]] for more information.
 +
 
 +
== Bluez5 instructions ==
 +
 
 +
{{Tip|Ensure that the bluetooth daemon is started before continuing.}}
 +
 
 +
The ''bluetoothctl'' utility provides a simple interface for configuring bluetooth devices. The text below is an example of how you can connect a bluetooth mouse using ''bluetoothctl'':
  
Note: The following instructions only work for the {{Pkg|bluez4}} package. For Bluez 5(Current version) please see the bluetoothctl section.
+
# bluetoothctl
 +
[bluetooth]# list
 +
Controller <controller mac> BlueZ 5.5 [default]
 +
[bluetooth]# select <controller mac>
 +
[bluetooth]# power on
 +
[bluetooth]# scan on
 +
[bluetooth]# agent on
 +
[bluetooth]# devices
 +
Device <mouse mac> Name: Bluetooth Mouse
 +
[bluetooth]# pair <mouse mac>
 +
[bluetooth]# trust <mouse mac>
 +
[bluetooth]# connect <mouse mac>
  
== Start Bluetooth service ==
+
In order for the device to start on boot you may have to create a [[udev]] rule. Please see [[Bluetooth#Bluetoothctl]] for more information.
  
The pertinent options in /etc/conf.d/bluetooth are
+
{{Tip|In case you were using USB Bluetooth dongle and moved it to another USB port, you may need to remove the mouse's MAC address in ''bluetoothctl'' with ''remove <mouse mac>'' command and repeat the entire procedure again.}}
HIDD_ENABLE=true
 
  
after that, start bluetooth services with
+
== Troubleshooting ==
# systemctl enable bluetooth.service
 
# systemctl start bluetooth.service
 
  
=== kernel modules ===
+
=== Mouse lag ===
No additional actions are necessary if the bluetooth service is started using systemd. If it does not work try following.
 
  
The command
+
If you experience mouse lag you can try to increase the polling rate. See [[Mouse polling rate]] for more information.
# modprobe -v btusb bluetooth hidp l2cap
 
loads the kernel modules you need, if they were not loaded automatically.
 
  
=== Test ===
+
=== Problems with the USB dongle ===
The following command should show your bluetooth adapter:
 
  
{{hc|# hciconfig|
+
If you have trouble with your USB dongle, you may also want to try:
hci0:  Type: BR/EDR  Bus: USB
 
      BD Address: 00:22:43:E1:82:E0  ACL MTU: 1021:8  SCO MTU: 64:1
 
      UP RUNNING PSCAN
 
      RX bytes:1062273 acl:62061 sco:0 events:778 errors:0
 
      TX bytes:1825 acl:11 sco:0 commands:39 errors:0
 
}}
 
  
== Configure Bluetooth Mouse ==
+
# modprobe -v rfcomm
The method described here is based in three steps, in this order:
 
  
# Make the PC learn about the bluetooth mouse.
+
At this point, you should get an hci0 device with:
# Grant the mouse permissions to connect.
 
# Make the mouse learn about the PC.
 
  
=== Search your mouse ===
+
# hcitool dev
First make your mouse discoverable. For example some mouse need to press a button. Then issue the following command as root:
 
  
{{hc|# hcitool scan|
+
Sometimes the device is not active right away. Try starting the interface with:
Scanning ...
 
        00:07:61:F5:5C:3D      Logitech Bluetooth Mouse M555b
 
}}
 
  
Your mouse bluetooth address will be similar to {{ic|12:34:56:78:9A:BC}}. You may also find it in the documentation or on the mouse itself.
+
# hciconfig hci0 up
  
== Connecting the mouse ==
+
and searching for devices as shown above.
hidd --search
 
hcitool inq
 
are good for device scanning (I needed to use sudo for 'hidd --search' to automatically connect mouse, searching worked even without sudo).
 
hidd --connect <bdaddr>
 
to actually connect.
 
hidd --show
 
will show your currently connected devices. The mouse should show up in this list. If it does not, press the reset button to make it discoverable.
 
  
Note: If you have the ipw3945 module loaded (wifi on HP computer) the bluetooth wont work.
+
=== Mouse always disconnect ===
  
== Connecting the mouse at startup ==
+
If the mouse stops working but works again after restarting bluetooth, you may need to [[Power_management#USB_autosuspend|disable USB autosuspend]] for the selected device.
Edit /etc/conf.d/bluetooth:
 
# Arguments to hidd
 
HIDD_OPTIONS="--connect <enter here your bluetooth mouse address>"
 
  
and test the new settings:
+
=== Failed to set power on: org.bluez.Error.Blocked ===
/etc/rc.d/bluetooth stop
 
hidd --killall (drop mouse connection)
 
/etc/rc.d/bluetooth start
 
  
Note: The above instructions to start the mouse at startup do not work with the now outdated 3.11 bluetooth packages. New versions such as the current (3.32) packages are not affected. If you are using an older version, then to start the mouse at startup, add:
+
Check rfkill block list and unblock if necessary:
hidd --connect <enter here your bluetooth mouse address (No capitals!!!)>
 
to your /etc/rc.local file.
 
  
Note #2: You can connect any bluetooth mouse and/or keyboard without any further configuration and without knowing the device address. You can do it by adding the --master and/or --server option in HIDD_OPTIONS depending on your device.
+
$ rfkill list
 +
$ rfkill unblock #
  
== Configuring through bluetoothctl ==
+
=== Apple Magic Mouse scroll speed ===
Since `bluez>=5` there is bluetoothctl util, that provide simple interface to configuring bluetooth devices.
 
  
For example, configuring autoconnect bluetooth mouse can be done as described above:
+
If the scroll speed is too slow, you can try
  # bluetoothctl
+
# rmmod hid_magicmouse
  [bluetooth]# list
+
# modprobe hid_magicmouse croll_acceleration=1 scroll_speed=55
  Controller <cmac> BlueZ 5.5 [default]
 
  [bluetooth]# select <cmac>
 
  [bluetooth]# power on
 
  [bluetooth]# scan on
 
  /// enable scanning mode on your mouse
 
  [bluetooth]# devices
 
  Device <mmac> Name: Bluetooth Mouse
 
  [bluetooth]# trust <mmac>
 
  [bluetooth]# pairable on
 
  [bluetooth]# pair <mmac>
 
  [bluetooth]# connect <mmac>
 
  
In order for the device to start on boot you may have to create a [[udev]] rule as discussed in [https://bbs.archlinux.org/viewtopic.php?id=166362].
+
Scroll speed can be set from 0 to 63.
  
== Troubleshooting tips ==
+
If the speed suits you, you can make the change permanent in {{ic|/etc/modprobe.d/}}
=== Mouse lag ===
+
{{hc | /etc/modprobe.d/hid_magicmouse.conf |<nowiki>
If you experience mouse lag you can try to increase the polling rate. There is a wiki article describing the procedure: [[Mouse Polling Rate]].
+
options hid_magicmouse croll_acceleration=1 scroll_speed=55</nowiki>}}
  
=== Problems with the USB dongle ===
+
=== Apple Magic Mouse middle click ===
If you have trouble with your USB dongle, you may also want to try
 
# modprobe -v rfcomm
 
  
At this point, you should get an hci0 device with
+
If you find the middle click to be too finicky, you can disable it
  # hcitool dev
+
# rmmod hid_magicmouse
 +
  # modprobe hid_magicmouse emulate_3button=0
  
Sometimes the device is not active right away - try starting the interface with
+
If this setting suits you, you can make the change permantent in {{ic|/etc/modprobe.d/}}
# hciconfig hci0 up
+
{{hc | /etc/modprobe.d/hid_magicmouse.conf |<nowiki>
and searching for devices as shown above.
+
options hid_magicmouse emulate_3button=0</nowiki>}}

Latest revision as of 03:15, 24 July 2017

This article describes how to set up a Bluetooth mouse through the command line without relying upon a graphical application.

Installation

Install the bluez package which contains the current Linux bluetooth stack (Bluez5). You may also want to install bluez-utils which provides the bluetoothctl utility. See Bluetooth for more information.

Bluez5 instructions

Tip: Ensure that the bluetooth daemon is started before continuing.

The bluetoothctl utility provides a simple interface for configuring bluetooth devices. The text below is an example of how you can connect a bluetooth mouse using bluetoothctl:

# bluetoothctl
[bluetooth]# list
Controller <controller mac> BlueZ 5.5 [default]
[bluetooth]# select <controller mac>
[bluetooth]# power on
[bluetooth]# scan on
[bluetooth]# agent on
[bluetooth]# devices
Device <mouse mac> Name: Bluetooth Mouse
[bluetooth]# pair <mouse mac>
[bluetooth]# trust <mouse mac>
[bluetooth]# connect <mouse mac>

In order for the device to start on boot you may have to create a udev rule. Please see Bluetooth#Bluetoothctl for more information.

Tip: In case you were using USB Bluetooth dongle and moved it to another USB port, you may need to remove the mouse's MAC address in bluetoothctl with remove <mouse mac> command and repeat the entire procedure again.

Troubleshooting

Mouse lag

If you experience mouse lag you can try to increase the polling rate. See Mouse polling rate for more information.

Problems with the USB dongle

If you have trouble with your USB dongle, you may also want to try:

# modprobe -v rfcomm

At this point, you should get an hci0 device with:

# hcitool dev

Sometimes the device is not active right away. Try starting the interface with:

# hciconfig hci0 up

and searching for devices as shown above.

Mouse always disconnect

If the mouse stops working but works again after restarting bluetooth, you may need to disable USB autosuspend for the selected device.

Failed to set power on: org.bluez.Error.Blocked

Check rfkill block list and unblock if necessary:

$ rfkill list
$ rfkill unblock #

Apple Magic Mouse scroll speed

If the scroll speed is too slow, you can try

# rmmod hid_magicmouse
# modprobe hid_magicmouse croll_acceleration=1 scroll_speed=55

Scroll speed can be set from 0 to 63.

If the speed suits you, you can make the change permanent in /etc/modprobe.d/

 /etc/modprobe.d/hid_magicmouse.conf 
options hid_magicmouse croll_acceleration=1 scroll_speed=55

Apple Magic Mouse middle click

If you find the middle click to be too finicky, you can disable it

# rmmod hid_magicmouse
# modprobe hid_magicmouse emulate_3button=0

If this setting suits you, you can make the change permantent in /etc/modprobe.d/

 /etc/modprobe.d/hid_magicmouse.conf 
options hid_magicmouse emulate_3button=0