How to Fix Bluetooth Not Working After Suspend or Sleep in Ubuntu

A widespread inconvenience encountered by laptop and desktop users on Ubuntu Linux is the sudden disappearance of Bluetooth functionality after the system resumes from sleep or suspend mode. Upon opening the laptop lid or pressing the power button, Bluetooth devices (such as wireless mice, keyboards, or headphones) fail to reconnect, and the Bluetooth settings panel often shows “No Bluetooth Adapter Found.”

This malfunction occurs when the Linux kernel power management system suspends the USB controller hosting the internal Bluetooth chipset, but fails to cleanly re-initialise the device firmware upon system resume. The Bluetooth kernel module (btusb) becomes unresponsive, leaving the device locked in an unpowered state. The following instructions provide permanent solutions to restore reliable Bluetooth operation.

Manually Reload the Bluetooth Kernel Driver

To confirm that a stalled kernel driver is the culprit without restarting your entire workstation, you can unload and reload the Bluetooth kernel module dynamically.

  1. Open the Terminal application (Ctrl + Alt + T).
  2. Stop the active Bluetooth system service:
    sudo systemctl stop bluetooth.service
  3. Unload the Bluetooth USB kernel module from memory:
    sudo modprobe -r btusb
  4. Wait five seconds, then reload the module cleanly:
    sudo modprobe btusb
  5. Start the Bluetooth service again:
    sudo systemctl start bluetooth.service
  6. Check the status of your adapter:
    rfkill list bluetooth
  7. If the output reports Soft blocked: yes, unblock it by running:
    sudo rfkill unblock bluetooth

Create an Automated Systemd Sleep Hook to Restart Bluetooth

Rather than manually typing commands each time your computer wakes up, you can configure an automated systemd suspend hook that transparently resets the Bluetooth subsystem upon resume.

  • Open a new systemd suspend script in a text editor with administrative privileges:
    sudo nano /lib/systemd/system-sleep/bluetooth-restart
  • Paste the following shell script into the file:
    #!/bin/sh
    case "$1" in
      post)
        modprobe -r btusb
        sleep 1
        modprobe btusb
        systemctl restart bluetooth
        ;;
    esac
  • Save the file by pressing Ctrl + O, press Enter, and exit nano with Ctrl + X.
  • Make the script executable:
    sudo chmod +x /lib/systemd/system-sleep/bluetooth-restart

Disable Kernel USB Autosuspend for Bluetooth Interfaces

The Linux kernel applies aggressive runtime power autosuspend to USB devices by default. Disabling autosuspend for your internal Bluetooth controller prevents the hardware from entering unrecoverable deep sleep states.

  1. Identify your Bluetooth adapter’s USB vendor and product ID:
    lsusb | grep -i bluetooth
  2. Note the alphanumeric ID displayed in the format ID xxxx:yyyy.
  3. Create a new Udev rule to keep the device powered:
    sudo nano /etc/udev/rules.d/50-bluetooth-power.rules
  4. Add the following line (replace xxxx and yyyy with your actual vendor and product IDs, or apply globally):
    ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="xxxx", ATTR{idProduct}=="yyyy", ATTR{power/autosuspend}="-1"
  5. Alternatively, disable general USB autosuspend in GRUB: open /etc/default/grub, find GRUB_CMDLINE_LINUX_DEFAULT, append usbcore.autosuspend=-1 to the quotes, save, and run sudo update-grub.

Update Proprietary Firmware Packages

Many modern Intel, Realtek, and Qualcomm Atheros Wi-Fi/Bluetooth combination cards require updated binary firmware blobs to handle advanced power states properly.

  • Update your system package index and upgrade available firmware:
    sudo apt update && sudo apt install --reinstall linux-firmware
  • If using an Intel wireless adapter, verify that the active firmware loaded cleanly into the kernel ring buffer:
    dmesg | grep -i bluetooth
  • Look for error messages such as “failed to load firmware” or “firmware patch failed”, which indicate missing hardware binaries in /lib/firmware/.

Test Suspend and Resume Behaviour

After implementing the systemd sleep hook and configuring power management rules, test the configuration.

  1. Close all sensitive work and suspend the computer via the system menu or by running systemctl suspend.
  2. Wait thirty seconds and wake the machine.
  3. Confirm that the Bluetooth status icon in the top system bar remains active and your wireless devices reconnect automatically within seconds.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.