• Bluetooth mouse keeps reconnecting


    Hey!

    I’m having a problem with my bluetooth mouse. When I first pair it, everything works fine, but after it is turned off and then on again, the system seems to detect it however as soon as it is connected, it automatically disconnects. The only way to establish a connection is by removing the mouse from the saved devices list and manually pairing it with the computer again.

    I’m running GNOME with all software up-to-date.

    Any help would be appreciated. 🙂

  • @hfel I would avoid to use bluetooth connection for mouse and keyboard 😉

    RF connection needs no setup and are less power hungry.

    I just find a section on “Mouse always disconnect” INSIDE archwiki: https://wiki.archlinux.org/index.php/Bluetooth_mouse#Mouse_always_disconnect
    But it links to this: https://wiki.archlinux.org/index.php/Power_management#USB_autosuspend

    Where it says “The Linux kernel can automatically suspend USB devices when they are not in use.”

    And gives instructions on how to ENABLE autosuspend for usb devices… tjhis is kind of unlogcal mto what i understand so far, as i want to disable it. And a bluetooth device is not an usb device… so they may talk about the bluetooth device… what CAN BE a usb device (bluetooth-dongle)

    Archwiki is very unclear sometimes… So if they talk about the bluetooth device then it is may the call that it siuspend by default, and you can solve this by adding the bluetooth device (when it shows up as a usb device) to the usb-suspend-blacklist.

    lsusb

    will give you something like this:

    Bus 001 Device 006: ID 050d:065a Belkin Components F8T065BF Mini Bluetooth 4.0 Adapter
    

    You need this: 050d:065a Vendor ID (before the colon) and each device has a Product ID (after the colon)

    Then create this file:

    sudo nano /etc/udev/rules.d/50-usb_power_save.rules
    

    paste this inside:

    # blacklist for usb autosuspend
    ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="050d", ATTR{idProduct}=="065a", GOTO="power_usb_rules_end"
    

    replace VendorID 050d and ProductID 065a with what you get for your BT device.
    And do not follow what the Archwiki says about blaclisting the one you have the problem, and enable autosuspend for all others… this will make all other usb devices unusable…

    Save the file with [Ctrl+X] and reboot.

    [updates once a week] = [90% less problems]
    antergos:_rescue
    how to add system logs:
    wget http://bit.ly/2GCG9k2 && sh 2GCG9k2
    :handshake: donate antergos

  • Hey @joekamprad , thank you very much for the quick and thorough reply!!

    Unfortunately, when I run lsusb, it doesn’t seem to detect the mouse at all… 😞

    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 004: ID 04f2:b59a Chicony Electronics Co., Ltd 
    Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
    Bus 001 Device 002: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    

    I was running Solus Budgie before and didn’t have the problem there, so I’m thinking it should be fixable here on Antergos/Arch too…

  • It should be the bluetooth device what needs to be blacklisten for autosuspend… but that is also not an usb device… in your case…

    [updates once a week] = [90% less problems]
    antergos:_rescue
    how to add system logs:
    wget http://bit.ly/2GCG9k2 && sh 2GCG9k2
    :handshake: donate antergos

  • can you give also the ouput of lspci?

    [updates once a week] = [90% less problems]
    antergos:_rescue
    how to add system logs:
    wget http://bit.ly/2GCG9k2 && sh 2GCG9k2
    :handshake: donate antergos

  • I’m actually starting to think that perhaps the problem isn’t with the bluetooth adapter autosuspending… because it seems to be working when I go to the bluetooth menu, it displays all the nearby devices and even remains connected to my bluetooth speakers. The problem is just that it doesn’t seem to be able to reconnect to the mouse.

    Now that I think about it, I actually had the same problem with my bluetooth speakers on Solus, but not with the mouse! I think the speakers were then the first device I ever paired on that, and they could also never autoreconnect. In Antergos, I first paired my mouse, and I noticed now that it successfully autoconnects to the speakers whenever I turn them on, just like it did with my mouse on Solus but not with the speakers!

    Perhaps I should take it up with GNOME, as Budgie relies on GNOME’s bluetooth manager as well?

  • Back then I just assumed it was just a problem with the speakers, which I got very cheaply. So at least it doesn’t seem to be a hardware problem.

  • i do pülay arpound with different BT chipsets and it is also afact that they are all different on stability and some needs firmware to nwork fully…and if you do dualbooting, BT devices that need a firmware, get problematic if you do not unload the firmware inserted by win dows… (by power off complete)…

    [updates once a week] = [90% less problems]
    antergos:_rescue
    how to add system logs:
    wget http://bit.ly/2GCG9k2 && sh 2GCG9k2
    :handshake: donate antergos

  • Yeah, it could be a problematic BT chipset though. So here is the output of lspci:

    00:00.0 Host bridge: Intel Corporation Device 590c (rev 02)
    00:02.0 VGA compatible controller: Intel Corporation Device 591e (rev 02)
    00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 02)
    00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model
    00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
    00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21)
    00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
    00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21)
    00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1)
    00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
    00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
    00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
    00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
    01:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
    
  • @hfel But it is integrated, not a usb dongle? i can not see any device information on your BT-Device …

    [updates once a week] = [90% less problems]
    antergos:_rescue
    how to add system logs:
    wget http://bit.ly/2GCG9k2 && sh 2GCG9k2
    :handshake: donate antergos

  • It’s integrated yes

  • can be a dualchipset together with wireless… do you have a exact model specification of your system it is a notebook as far as i can see?

    [updates once a week] = [90% less problems]
    antergos:_rescue
    how to add system logs:
    wget http://bit.ly/2GCG9k2 && sh 2GCG9k2
    :handshake: donate antergos

  • If it’s any help, this is my computer: https://www.gearbest.com/laptops/pp_625263.html

    I couldn’t find anything about the bluetooth device per se though…

  • seems to be integrated together with wifi chipset… as download page shows intel driver for bluetooth…

    [updates once a week] = [90% less problems]
    antergos:_rescue
    how to add system logs:
    wget http://bit.ly/2GCG9k2 && sh 2GCG9k2
    :handshake: donate antergos

  • So do you have any ideas on how to go about fixing this, or should I report it GNOME?

  • do you have dualboot or Linux only?

    [updates once a week] = [90% less problems]
    antergos:_rescue
    how to add system logs:
    wget http://bit.ly/2GCG9k2 && sh 2GCG9k2
    :handshake: donate antergos

  • i would ask to get device info about bluetooth, at producer or seller… but gnome has nothing to do with it…

    [updates once a week] = [90% less problems]
    antergos:_rescue
    how to add system logs:
    wget http://bit.ly/2GCG9k2 && sh 2GCG9k2
    :handshake: donate antergos

  • I’m just curious, but wouldn’t the fix involve changes in the bluetooth software, which would be an upstream issue? If not GNOME, then techincally what’s the level where it should be handled?

    Anyway, I’m running just Antergos, and running lspci gave the following network controller:

    01:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
    

    … which seems to incorporate both WiFi and Bluetooth, the Intel page is here.

  • I tried 2 BT mice with my laptop, and they were a source of endless frustration, regardless of the OS and/or DE in use. Finally I started using wireless devices with a receiver in the usb port.

    Take a look at my portfolio

  • @hfel said in Bluetooth mouse keeps reconnecting:

    I’m just curious, but wouldn’t the fix involve changes in the bluetooth software, which would be an upstream issue? If not GNOME, then techincally what’s the level where it should be handled?

    Anyway, I’m running just Antergos, and running lspci gave the following network controller:

    01:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
    

    … which seems to incorporate both WiFi and Bluetooth, the Intel page is here.

    https://bugzilla.kernel.org/buglist.cgi?quicksearch=bluez

    [updates once a week] = [90% less problems]
    antergos:_rescue
    how to add system logs:
    wget http://bit.ly/2GCG9k2 && sh 2GCG9k2
    :handshake: donate antergos

mouse61 bluetooth44 keeps15 reconnecting1 Posts 23Views 618
Log in to reply
Bloom Email Optin Plugin

Looks like your connection to Antergos Community Forum was lost, please wait while we try to reconnect.