bluetooth mouse does not reconnect on wake from suspend

This same behavior also occurs whenever computer is restarted: cannot reconnect, and must delete and re-pair mouse.

Does your adapter require being toggled from hid into hci modes? What bluetooth adapter are you using? Perhaps is the adapter just missing a reset quirk in that case?

Please retry on the latest bluez upload, as it may cover your case:

bluez (4.12-0ubuntu4) intrepid; urgency=low

  * Add hid2hci.patch to enable hid2hci to be ran after
    suspending a machine. (LP: #268877)
  * debian/rules:
    - Install new script from above patch.
  * Add logitech_5500_ids.patch for enabling hid2hci on
    more logitech devices. (LP: #272352)

 -- Mario Limonciello < <email address hidden>> Wed, 22 Oct 2008 16:01:59 -0500

Hi Mario,

Unfortunately, re-connect to mouse after suspend/reboot still does not work. Note that it works perfectly with the bluez 3.x series in Hardy, and was working well with KBluetooth4 tools before the breakage.

matt@darwin:~$ apt-cache policy bluez
bluez:
  Installed: 4.12-0ubuntu5
  Candidate: 4.12-0ubuntu5
  Version table:
 *** 4.12-0ubuntu5 0

matt@darwin:~$ hciconfig -a
hci0: Type: USB
        BD Address: 00:0E:9B:DC:BC:98 ACL MTU: 377:10 SCO MTU: 64:8
        UP RUNNING
        RX bytes:24635 acl:1447 sco:0 events:52 errors:0
        TX bytes:800 acl:17 sco:0 commands:39 errors:0
        Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy:
        Link mode: SLAVE ACCEPT
        Name: 'darwin-0'
        Class: 0x0a010c
        Service Classes: Networking, Capturing
        Device Class: Computer, Laptop
        HCI Ver: 1.2 (0x2) HCI Rev: 0x9 LMP Ver: 1.2 (0x2) LMP Subver: 0x6963
        Manufacturer: Broadcom Corporation (15)

matt@darwin:~$ lsusb | grep -i bluetooth
Bus 004 Device 002: ID 0a5c:201e Broadcom Corp. IBM Integrated Bluetooth IV

Any other information you would like?

The same problem here with my Bluetooth mouse. My adapter information is:
Bus 003 Device 004: ID 0a5c:201e Broadcom Corp. IBM Integrated Bluetooth IV

A weird behavior observed: when the mouse can not reconnect, toggle the "Visibility setting" in "Bluetooth Preferences" dialog from "Hidden" to "Always visible" will help the bluetooth mouse get re-discovered.

For me, the visibility setting is already listed as "always visible", and this does not allow mouse to re-connect.

changing status to confirmed with Peng's confirmation

Adding mouse details:

matt@darwin:~$ hcitool name 00:07:61:9A:79:53
Bluetooth Laser Travel Mouse

Actually it's not the setting of "Visible" that brings back the
bluetooth connection, but the action of changing from "Hidden" to
"Visible" that does the trick for me.

Same problem here - using a Dell Travel Mouse and the Dell Mini 9 running vanilla Ubuntu 8.10. The mini loses the connection with the Mouse upon waking from suspend.

This also affects me with a a Microsoft Wireless Presenter Mouse 8000 on Intrepid, turning off the mouse, restarting, suspending, or a long period of inactivity will disconnect the mouse. Only removing the pairing and adding again or running hidd --search (with mouse in pairing mode) will reconnect the mouse.

my adapter:

Bus 004 Device 004: ID 0a5c:2101 Broadcom Corp. A-Link BlueUsbA2 Bluetooth

Features: 0xff 0xff 0x8d 0xfe 0x9b 0xf9 0x00 0x80
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Class: 0x0a010c
Service Classes: Networking, Capturing
Device Class: Computer, Laptop
HCI Ver: 2.0 (0x3) HCI Rev: 0x4000 LMP Ver: 2.0 (0x3) LMP Subver: 0x430e
Manufacturer: Broadcom Corporation (15)

i'm seeing this also in 8.10 running on a lenovo s10. still seeing it in 9.04 alpha4, which was supposed to have later versions of bluez

I haven't been using hidd since it was a compatibility package.

in jaunty, i actually haven't seen the mouse function correctly, although the applet reports it is connected. would an hcidump help?

note that jaunty doesn't show any bluez problems, as far as I could see. should I open something in the jaunty bug area?

forgot to say that the mouse is a microsoft bluetooth mouse 5000

also referencing a discussion in the forums:

http://ubuntuforums.org/showthread.php?p=6438656#post6438656

My Microsoft Bluetooth Notebook 5000 mouse also exhibited the same reconnect issues until I added "sudo hciconfig hci0 pscan" to my /etc/rc.local file (before the "exit 0" line) - now the mouse reconnects quite happily whenever I switch it on and off, but doesn't always work from suspend and never works from reboot, however generally all I have to do is switch off the mouse and turn it back on, and it reconnects without needing to delete and redo the pairing.

In the case of those times where it doesn't work from suspend, I notice that the Bluetooth adapter has switched out of PSCAN mode. If I re-issue the "sudo hciconfig hci0 pscan" command and wait a couple of seconds, the mouse will suddenly start working again.

I should add that my Bluetooth Preferences are set to "Hidden".

just tested the lenovo s10 and bluetooth mouse with an 8.04 system running kernel 2.6.27-7 booted
from a live dvd from linux pro magazine.

mouse syncs and works with no changes or command line. just using the applet.

note that a graphic of a connector show after using the connect button.

never have seen this with either the 8.10 or 9.04 applet usage

argh, brain fog, make that a 8.10 live dvd . synced while not running pscan.

bluez 4.12-0ubuntu5

hmm

If you let the mouse go to sleep, you will should find it won't reconnect in Intrepid until you configure the BT adapter to run pscan.

using suspend from the shutdown menu after using the pscan command . mouse working.

dmesg shows

restarting tasks ... done.
input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/pci0000:00/ld.1/usb2/2-2/2-2:1.0/bluetooth/hci0:11/input16

can't really test rc.local use of pscan on a live cd

todays jaunty upgrade list included bluez 4.29-0ubnuntu-1 upgrade.

now I can sync my microsoft mouse with the lenovo s10 and it works

dmesg shows

<block>
[ 552.092270] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 552.094777] input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2:1.0/bluetooth/hci0/hci0:11/input10
[ 552.108268] generic-bluetooth 0005:045E:0700.0001: input,hidraw0: BLUETOOTH HID v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on 00:14:A4:FD:57:75
[ 580.191625] input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2:1.0/bluetooth/hci0/hci0:11/input11
[ 580.212552] generic-bluetooth 0005:045E:0700.0002: input,hidraw1: BLUETOOTH HID v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on 00:14:A4:FD:57:75
[ 593.107392] input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2:1.0/bluetooth/hci0/hci0:11/input12
[ 593.124264] generic-bluetooth 0005:045E:0700.0003: input,hidraw2: BLUETOOTH HID v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on 00:14:A4:FD:57:75

</block>

there was also an upgrade to kernel 2.6.28-7

(now glitches with video, workaround with recovery kernel to test bluez)

now to test hibernate

btw, there is no directory /devices (???) strange message in dmesg above

interesting,

the mouse did not appear to sync when awakening from hibernate, and
the device did not show in the applet device list, but turning the
mouse on and off caused an authorization request to pop up.

when the the subsequent window popped up, checking ok made the mouse
respond.

now the mouse shows in the preferences device list.

now i'm wondering about getting it automatically authorized?

this is still with pscan enabled

there is a checkbox on the authorization confirmation window. but it does
not seem to eliminate the dialogue.

small chance that booting recovery mode interacts with this, but right now
that's what i have, because of problems with x and video.

b

no joy

back to not seeing the mouse sync,

but maybe I see something in the dmesg dump

[block]
3.989874] uhci_hcd: USB Universal Host Controller Interface driver
[ 3.990084] uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
[ 3.990178] uhci_hcd 0000:00:1d.0: setting latency timer to 64
[ 3.990189] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[ 3.990485] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
[ 3.990651] uhci_hcd 0000:00:1d.0: irq 23, io base 0x00001820
[ 3.990990] usb usb1: configuration #1 chosen from 1 choice
[ 4.028657] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 4.028735] Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd, not after
[ 4.052681] hub 1-0:1.0: USB hub found
[ 4.052781] hub 1-0:1.0: 2 ports detected
[ 4.053272] ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
[ 4.053411] ehci_hcd 0000:00:1d.7: setting latency timer to 64
[ 4.053420] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[ 4.053635] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
[ 4.057656] ehci_hcd 0000:00:1d.7: debug port 1
[ 4.057728] ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
[ 4.057749] ehci_hcd 0000:00:1d.7: irq 23, io mem 0xf0844000
[ 4.073053] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
[ 4.073347] usb usb2: configuration #1 chosen from 1 choice
[ 4.073500] hub 2-0:1.0: USB hub found
[ 4.073580] hub 2-0:1.0: 8 ports detected
[ 4.076001] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[ 4.076124] uhci_hcd 0000:00:1d.1: setting latency timer to 64
[ 4.076134] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[ 4.076374] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
[ 4.076505] uhci_hcd 0000:00:1d.1: irq 19, io base 0x00001840
[ 4.076791] usb usb3: configuration #1 chosen from 1 choice
[ 4.076931] hub 3-0:1.0: USB hub found
[ 4.077009] hub 3-0:1.0: 2 ports detected
[ 4.077374] uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[ 4.077455] uhci_hcd 0000:00:1d.2: setting latency timer to 64
[ 4.077464] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[ 4.077673] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
[ 4.077815] uhci_hcd 0000:00:1d.2: irq 18, io base 0x00001860
[ 4.078113] usb usb4: configuration #1 chosen from 1 choice
[ 4.078817] hub 4-0:1.0: USB hub found
[ 4.078911] hub 4-0:1.0: 2 ports detected
[ 4.079273] uhci_hcd 0000:00:1d.3: PCI INT D -> GSI 16 (level, low) -> IRQ 16
[ 4.079358] uhci_hcd 0000:00:1d.3: setting latency timer to 64
[ 4.079368] uhci_hcd 0000:00:1d.3: UHCI Host Controller
[ 4.079566] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
[ 4.079711] uhci_hcd 0000:00:1d.3: irq 16, io base 0x00001880
[ 4.080074] usb usb5: configuration #1 chosen from 1 choice
[ 4.080220] hub 5-0:1.0: USB hub found
[ 4.080299] hub 5-0:1.0: 2 ports detected
[ 4.299307] eth0: Tigon3 [partno(BCM95906) rev c002 PHY(5906)] (PCI Express) 10/100Base-TX Ethernet 00:23:8b:08:4f:c9
[ 4.299409] eth0: RXcsu...

here's the whole dmesg dump

now it's working, again, on jaunty alpha 4 bluez 4.29

trying different combinations of hibernate, restart, mouse on/off

bluez asks to authenticate, then repeats with an (object id) even though
I have earlier marked the box to always authenticate.

Confirming newore's comment of "bluez asks to authenticate, then repeats with an (object id) even though
I have earlier marked the box to always authenticate." on jaunty alpha 4. I have a Logitech v470 bluetooth mouse ("Bluetooth Laser Travel Mouse") connecting to my laptop using "Bus 002 Device 002: ID 0b05:1712 ASUSTek Computer, Inc. BT-183 Bluetooth 2.0+EDR". I also have this issue, and must 'authenticate' on each resume or reboot, despite having selected the box each time to 'always authenticate'.

bluez 4.30 appears to improve the recognition of my microsoft bluetooth 5000 mouse. on startup the mouse is available before the login prompt.

on hibernate, however, there are still problems. during the first return from hibernate, I saw the mouse work, briefly, but the cursor would
not move. upon a second hibernate cycle the mouse did not move the cursor before or after. upon a full reboot, the mouse worked, again before the login prompt.

I had been using the blueman applet, so I checked against bluez-gnome, by installing bluez-gnome with synaptic. the problem with bluetooth mouse recognition after resuming from hibernation persists, while using bluez-gnome. the bluetooth preferences page of bluez-gnome shows the mouse. the mouse shows in the list of devices as connected. if I power the mouse down, the connected icon is removed; if I power the mouse the connected icon appears.

the mouse does not move the cursor.

this behavior is cleared by a full reboot.

adding to the previous, a clarification: when I saw the mouse move the cursor on the first resume from hibernation, the mouse stopped
moving before finishing the password answer, and did not move after fully resuming.

system is a lenovo s10 now running

bp@bp-ssdjacky:~$ uname -a
Linux bp-ssdjacky 2.6.28-8-generic #22-Ubuntu SMP Fri Feb 13 21:40:17 UTC 2009 i686 GNU/Linux

Ubuntu Jaunty Alpha 5
Microsoft Bluetooth 5000 mouse

The BlueTooth Device Wizard detects the mouse and even reports that it connected successfully however the mouse never leaves beacon mode... and does not move the cursor.

uname -a gives
Linux joedirt 2.6.28-8-generic #26-Ubuntu SMP Wed Feb 25 04:28:54 UTC 2009 i686 GNU/Linux

here are all the messages from dmesg containing "Bluetooth"
[ 0.532009] Bluetooth: Core ver 2.13
[ 0.532020] Bluetooth: HCI device and connection manager initialized
[ 0.532020] Bluetooth: HCI socket layer initialized
[ 2.626683] Bluetooth: L2CAP ver 2.11
[ 2.626685] Bluetooth: L2CAP socket layer initialized
[ 2.626687] Bluetooth: SCO (Voice Link) ver 0.6
[ 2.626689] Bluetooth: SCO socket layer initialized
[ 2.626705] Bluetooth: RFCOMM socket layer initialized
[ 2.626710] Bluetooth: RFCOMM TTY layer initialized
[ 2.626712] Bluetooth: RFCOMM ver 1.10
[ 9.627472] Bluetooth: Generic Bluetooth USB driver ver 0.3
[ 17.798999] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 17.799006] Bluetooth: BNEP filters: protocol multicast
[ 103.038057] Bluetooth: HIDP (Human Interface Emulation) ver 1.2

hciconfig -a gives
hci0: Type: USB
 BD Address: 00:1C:26:F1:F5:8E ACL MTU: 1017:8 SCO MTU: 64:8
 UP RUNNING PSCAN ISCAN
 RX bytes:17135 acl:693 sco:0 events:338 errors:0
 TX bytes:7024 acl:210 sco:0 commands:121 errors:0
 Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80
 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
 Link policy: RSWITCH HOLD SNIFF PARK
 Link mode: SLAVE ACCEPT
 Name: 'joedirt-0'
 Class: 0x0a210c
 Service Classes: Networking, Capturing
 Device Class: Computer, Laptop
 HCI Ver: 2.0 (0x3) HCI Rev: 0x216f LMP Ver: 2.0 (0x3) LMP Subver: 0x41d8
 Manufacturer: Broadcom Corporation (15)

I just got Microsoft 5000 mouse working with restart/resume. I have followed http://blog.chinthaka.org/2008/09/getting-microsoft-bluetooth-mouse.html

However, additionally I had to change security from user to auto in order to reconnection at startup/resume works.

So I changed at /etc/bluetooth/hcid.conf

# Security Manager mode
# none - Security manager disabled
# auto - Use local PIN for incoming connections
# user - Always ask user for a PIN
#
security auto;

Instead of last step sudo hidd --seacrh, I cleaned all devices, reboot and added mouse again from applet.
After that everything works with resume/restart!

The last post worked for me:

security auto;

Ubuntu 10.10, i386

I observe the same problem. My Bluetooth mouse cannot reconnect after wake up or power on (on mouse). I even observe that menu created for Bluetooth mouse in indicator GNOME applet is messed after several tries to force mouse connection; like menu items are at wrong position, sometimes connect item is twice, etc.

There is no file /etc/bluetooth/hcid.conf at my notebook with U10.10.

The BT mouse works fine WinXP, it can wake up, reconnect, etc.

This is what I see when I run command "hcidump -X" and I try to reconnect mouse (doubleclick a mouse button)

> HCI Event: Connect Request (0x04) plen 10
  0000: f7 18 01 d1 60 00 80 25 00 01 ....`..%..
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
  0000: f7 18 01 d1 60 00 00 ....`..
> HCI Event: Command Status (0x0f) plen 4
  0000: 00 01 09 04 ....
> HCI Event: Role Change (0x12) plen 8
  0000: 00 f7 18 01 d1 60 00 00 .....`..
> HCI Event: Connect Complete (0x03) plen 11
  0000: 00 07 00 f7 18 01 d1 60 00 01 00 .......`...
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
  0000: 07 00 ..
> HCI Event: Command Status (0x0f) plen 4
  0000: 00 01 1b 04 ....
< HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4
  0000: 07 00 18 cc ....
> HCI Event: Command Status (0x0f) plen 4
  0000: 0c 01 0f 04 ....
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
  0000: f7 18 01 d1 60 00 02 00 00 00 ....`.....
> HCI Event: Command Status (0x0f) plen 4
  0000: 00 01 19 04 ....
> ACL data: handle 7 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 17 scid 0x0058
< ACL data: handle 7 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0058 result 1 status 0
      Connection pending - No futher information available
< ACL data: handle 7 flags 0x02 dlen 10
    L2CAP(s): Info req: type 2
> HCI Event: Max Slots Change (0x1b) plen 3
  0000: 07 00 05 ...
> HCI Event: Number of Completed Packets (0x13) plen 5
  0000: 01 07 00 02 00 .....
> ACL data: handle 7 flags 0x02 dlen 12

    L2CAP(s): Info rsp: type 2 result 1
      Not supported
< ACL data: handle 7 flags 0x02 dlen 10
    L2CAP(s): Info req: type 3
> HCI Event: Read Remote Supported Features (0x0b) plen 11
  0000: 00 07 00 af fe 29 38 18 00 00 00 .....)8....
> ACL data: handle 7 flags 0x02 dlen 12
    L2CAP(s): Info rsp: type 3 result 1
      Not supported
< ACL data: handle 7 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0058 result 0 status 0
      Connection successful
> ACL data: handle 7 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
      MTU 48
< ACL data: handle 7 flags 0x02 dlen 18
    L2CAP(s): Config rsp: scid 0x0058 flags 0x00 result 0 clen 4
      MTU 48
< ACL data: handle 7 flags 0x02 dlen...

I solved it! It was HW problem.
Notebook Comapaq NC6000 has bluetooth module that was designed for bluetooth 1.1. Mouse was compatible with 2.0 or 2.1.
I replaced module version 1.1 with newer module that is 2.1; you can get such module at eBay, it is small module with BCM92046 chip; easy to replace. With new bluetooth module, mouse works as expected.

To check your bluettooth module, use CLI command hciconfig:

# hcicinfig -a

hci0: Type: BR/EDR Bus: USB
 BD Address: 00:25:56:E7:XX:XX ACL MTU: 1021:8 SCO MTU: 64:1
 UP RUNNING PSCAN
 RX bytes:137386 acl:9055 sco:0 events:69 errors:0
 TX bytes:1451 acl:12 sco:0 commands:55 errors:0
 Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x83
 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
 Link policy: RSWITCH HOLD SNIFF PARK
 Link mode: SLAVE ACCEPT
 Name: 'nc6000-0'
 Class: 0x5a0100
 Service Classes: Networking, Capturing, Object Transfer, Telephony
 Device Class: Computer, Uncategorized
 HCI Version: 2.1 (0x4) Revision: 0x51d3
 LMP Version: 2.1 (0x4) Subversion: 0x424c
 Manufacturer: Broadcom Corporation (15)