Bluetooth mouse timeout

jo-shva · 2016-01-22 21:40:09

I have a new bluetooth mouse, it works well under every condition except when it times out. When I try and wake it from its time out all I get is an invisible mouse cursor. I can't turn the mouse on and off to restart it. It simply won't become visible. Now I am speaking of the mouse itself timing out(or bluetooth putting it to sleep). It works fine anytime I am required to log-in; and it works fine after suspend. I have googled my fingers to the bone trying to find a way to stop the mouse from timing out(bluetooth putting it to sleep), but nothing I have tried including a udev rule has been effective.
Please if anyone knows of a way to stop the time out(bluetooth sleep) let me know. Your help is greatly appreciated.

TheSaint · 2016-01-23 01:11:59

Like this is hard to guess. Perhaps any information from the logs ?

$ lsusb
$ journalctl -b -u bluetooth

Is an internal bluetooth device or plugged to USB ?
There could be problem related with power saving, either from the computer or the mouse itself.

jo-shva · 2016-01-23 02:07:27

It is an internal bluetooth device. They recommend on Win to turn off power-saving in the bluetooth controls.

-- Logs begin at Wed 2015-11-25 17:00:48 CST, end at Fri 2016-01-22 20:05:40 CST. --
Jan 22 14:27:02 rooster systemd[1]: Starting Bluetooth service...
Jan 22 14:27:02 rooster bluetoothd[530]: Bluetooth daemon 5.37
Jan 22 14:27:03 rooster bluetoothd[530]: Unknown key FastConnectable in main.conf
Jan 22 14:27:03 rooster systemd[1]: Started Bluetooth service.
Jan 22 14:27:03 rooster bluetoothd[530]: Starting SDP server
Jan 22 14:27:03 rooster bluetoothd[530]: Bluetooth management interface 1.10 initialized
Jan 22 14:27:03 rooster bluetoothd[530]: Failed to obtain handles for "Service Changed" characteristic
Jan 22 14:27:03 rooster bluetoothd[530]: Not enough free handles to register service
Jan 22 14:27:03 rooster bluetoothd[530]: Error adding Link Loss service
Jan 22 14:27:03 rooster bluetoothd[530]: Not enough free handles to register service
Jan 22 14:27:03 rooster bluetoothd[530]: Not enough free handles to register service
Jan 22 14:27:03 rooster bluetoothd[530]: Not enough free handles to register service
Jan 22 14:27:03 rooster bluetoothd[530]: Current Time Service could not be registered
Jan 22 14:27:03 rooster bluetoothd[530]: gatt-time-server: Input/output error (5)
Jan 22 14:27:03 rooster bluetoothd[530]: Not enough free handles to register service
Jan 22 14:27:03 rooster bluetoothd[530]: Not enough free handles to register service
Jan 22 14:27:03 rooster bluetoothd[530]: Sap driver initialization failed.
Jan 22 14:27:03 rooster bluetoothd[530]: sap-server: Operation not permitted (1)
Jan 22 14:27:42 rooster bluetoothd[530]: Endpoint registered: sender=:1.47 path=/MediaEndpoint/A2DPSource
Jan 22 14:27:42 rooster bluetoothd[530]: Endpoint registered: sender=:1.47 path=/MediaEndpoint/A2DPSink

Also I am using Gnome Desktop with Gnome-Bluetooth

Last edited by jo-shva (2016-01-23 02:10:04)

TheSaint · 2016-01-23 09:28:53

Maybe it would need to keep dmesg tail while the time is going to end.
What's the brand and model of the mouse ?

jo-shva · 2016-01-23 12:00:23

I am sorry I don't know what you mean by keep dmesg tail?
The brand is Goldtouch (GT Bluetooth Mouse).
Here is the udev rule I tried:

ACTION=="add", SUBSYSTEM=="bluetooth", ATTR{idVendor}=="1131", ATTR{idProduct}=="5035", ATTR{product}=="GT Bluetooth Mouse", TEST=="power/control", ATTR{power/control}="on"

I read in the Ubuntu forums to add a input.conf to /etc/bluetooth to stop the time out(didn't work)

# Configuration file for the input service

# This section contains options which are not specific to any
# particular interface
[General]

# Set idle timeout (in minutes) before the connection will
# be disconnect (defaults to 0 for no timeout)
IdleTimeout=0

And lastly here is my bluetooth configuration /etc/bluetooth/main.conf

[General]

# Default adaper name
# Defaults to 'BlueZ X.YZ'
#Name = BlueZ

# Default device class. Only the major and minor device class bits are
# considered. Defaults to '0x000000'.
#Class = 0x000100

# How long to stay in discoverable mode before going back to non-discoverable
# The value is in seconds. Default is 180, i.e. 3 minutes.
# 0 = disable timer, i.e. stay discoverable forever
DiscoverableTimeout = 0

# How long to stay in pairable mode before going back to non-discoverable
# The value is in seconds. Default is 0.
# 0 = disable timer, i.e. stay pairable forever
PairableTimeout = 0

# Automatic connection for bonded devices driven by platform/user events.
# If a platform plugin uses this mechanism, automatic connections will be
# enabled during the interval defined below. Initially, this feature
# intends to be used to establish connections to ATT channels. Default is 60.
AutoConnectTimeout = 0

# Use vendor id source (assigner), vendor, product and version information for
# DID profile support. The values are separated by ":" and assigner, VID, PID
# and version.
# Possible vendor id source values: bluetooth, usb (defaults to usb)
#DeviceID = bluetooth:1234:5678:abcd

# Do reverse service discovery for previously unknown devices that connect to
# us. This option is really only needed for qualification since the BITE tester
# doesn't like us doing reverse SDP for some test cases (though there could in
# theory be other useful purposes for this too). Defaults to 'true'.
#ReverseServiceDiscovery = true

# Enable name resolving after inquiry. Set it to 'false' if you don't need
# remote devices name and want shorter discovery cycle. Defaults to 'true'.
#NameResolving = true

# Enable runtime persistency of debug link keys. Default is false which
# makes debug link keys valid only for the duration of the connection
# that they were created for.
#DebugKeys = false

# Restricts all controllers to the specified transport. Default value
# is "dual", i.e. both BR/EDR and LE enabled (when supported by the HW).
# Possible values: "dual", "bredr", "le"
#ControllerMode = dual

# Enables Multi Profile Specification support. This allows to specify if
# system supports only Multiple Profiles Single Device (MPSD) configuration
# or both Multiple Profiles Single Device (MPSD) and Multiple Profiles Multiple
# Devices (MPMD) configurations.
# Possible values: "off", "single", "multiple"
#MultiProfile = off

# Permanently enables the Fast Connectable setting for adapters that
# support it. When enabled other devices can connect faster to us,
# however the tradeoff is increased power consumptions. This feature
# will fully work only on kernel version 4.1 and newer. Defaults to
# 'false'.
FastConnectable = true

#[Policy]
#
# The ReconnectUUIDs defines the set of remote services that should try
# to be reconnected to in case of a link loss (link supervision
# timeout). The policy plugin should contain a sane set of values by
# default, but this list can be overridden here. By setting the list to
# empty the reconnection feature gets disabled.
#ReconnectUUIDs=00001112-0000-1000-8000-00805f9b34fb, 0000111f-0000-1000-8000-00805f9b34fb, 0000110a-0000-1000-8000-00805f9b34fb

# ReconnectAttempts define the number of attempts to reconnect after a link
# lost. Setting the value to 0 disables reconnecting feature.
#ReconnectAttempts=7

# ReconnectIntervals define the set of intervals in seconds to use in between
# attempts.
# If the number of attempts defined in ReconnectAttempts is bigger than the
# set of intervals the last interval is repeated until the last attempt.
#ReconnectIntervals=1, 2, 4, 8, 16, 32, 64

# AutoEnable defines option to enable all controllers when they are found.
# This includes adapters present on start as well as adapters that are plugged
# in later on. Defaults to 'false'.
#AutoEnable=false

I don't know if any of this may be usefull, but here it is. Maybe the input.conf should be added to the main.conf under [GENERAL]? I tried it, it didn't work. I fixed the error in the udev rule and will test it. Fingers crossed. No dice. The udev rule didn't fix it.
The problem is I can live with the time out if the cursor would come back after it; instead of being invisible and unusable. It wont even pair again(a new). I have to plug another mouse in to get the cursor back, and then it works again.

Last edited by jo-shva (2016-01-23 14:21:38)

TheSaint · 2016-01-23 17:12:51

To see the latest event, as per wiki, you may use

# journalctl -f

That's the meaning of dmseg tail.
Though, the problem isn't the mouse itself, but the DE that doesn't reconnect the pointers icon to the mouse. So if it is a laptop, mostly there are conflicts with the touchpad. Probably it will need some particular setting in xorg.conf.

Last edited by TheSaint (2016-01-23 17:16:19)

jo-shva · 2016-01-23 17:32:31

Yes it a laptop. I have had another bluetooth mouse and it didn't have this issue.
I would have know idea what to put in xorg for a lost pointer.

TheSaint · 2016-01-23 17:45:06

Probably, to have a look into Xorg.o.log.
If you start xev, with the invisible pointer, what do you can see ?

jo-shva · 2016-01-23 18:26:02

xev:

 ButtonPress event, serial 36, synthetic NO, window 0x1400001,
    root 0xd5, subw 0x0, time 16188052, (9,128), root:(233,691),
    state 0x10, button 1, same_screen YES

ButtonRelease event, serial 36, synthetic NO, window 0x1400001,
    root 0xd5, subw 0x0, time 16188158, (9,128), root:(233,691),
    state 0x110, button 1, same_screen YES

MotionNotify event, serial 36, synthetic NO, window 0x1400001,
    root 0xd5, subw 0x0, time 16197163, (10,125), root:(234,688),
    state 0x10, is_hint 0, same_screen YES

MotionNotify event, serial 36, synthetic NO, window 0x1400001,
    root 0xd5, subw 0x0, time 16197171, (13,120), root:(237,683),
    state 0x10, is_hint 0, same_screen YES

Xorg.o.log doesn't even mention the bluetooth mouse.

Last edited by jo-shva (2016-01-23 18:31:41)

jo-shva · 2016-01-23 23:56:33

I'm just going to return this mouse and try another. Hopefully I wont run into the same problem. Thanks for your help.

TheSaint · 2016-01-24 01:44:36

I'm using a Genius Navigator 905BT Mouse.

jo-shva · 2016-01-24 11:17:45

No, Goldtouch Bluetooth Mouse

jo-shva · 2016-01-24 23:22:42

Upon further inspection, I tried the mouse in Ubuntu. And guess what? No problems at all. When the mouse times out the cursor is still visible, and a small amount of movement of the mouse brings it back to life. KDE is the same, no problems. This is a Gnome bug. bug 761067
WHAT GIVES!

Last edited by jo-shva (2016-01-25 00:46:13)

TheSaint · 2016-01-25 05:11:58

Is it you to report it ?
So you may have to change DE, until they'll get fix it

jo-shva · 2016-01-25 10:24:24

Yes I reported it. In the mean time I will use KDE and/or connect a second mouse in Gnome so I don't loose the cursor.

Arch Linux

#1 2016-01-22 21:40:09

Bluetooth mouse timeout

#2 2016-01-23 01:11:59

Re: Bluetooth mouse timeout

#3 2016-01-23 02:07:27

Re: Bluetooth mouse timeout

#4 2016-01-23 09:28:53

Re: Bluetooth mouse timeout

#5 2016-01-23 12:00:23

Re: Bluetooth mouse timeout

#6 2016-01-23 17:12:51

Re: Bluetooth mouse timeout

#7 2016-01-23 17:32:31

Re: Bluetooth mouse timeout

#8 2016-01-23 17:45:06

Re: Bluetooth mouse timeout

#9 2016-01-23 18:26:02

Re: Bluetooth mouse timeout

#10 2016-01-23 23:56:33

Re: Bluetooth mouse timeout

#11 2016-01-24 01:44:36

Re: Bluetooth mouse timeout

#12 2016-01-24 11:17:45

Re: Bluetooth mouse timeout

#13 2016-01-24 23:22:42

Re: Bluetooth mouse timeout

#14 2016-01-25 05:11:58

Re: Bluetooth mouse timeout

#15 2016-01-25 10:24:24

Re: Bluetooth mouse timeout

Board footer