I have a HP mouse. Recently, I have been practicing implementing the device driver. Instead of using the hid-generic driver, I would like to use my customized driver for the Bluetooth device. I don't have any ideas about how to implement it in another way for this character device. My idea is kind of similar to my previous implementation on the USB driver by using the USB API instead of the hid-usb static driver. I am wondering if there is any API or subsystem category related to Bluetooth that I can use to implement a driver for the mouse. Or I am wondering if there are any better ideas or designs about this.

I'm using an ASUS ZenBook 14 (UX3405CA) with an Intel WiFi 7 card. A couple weeks ago, I was running Arch and bluetoothctl worked, but graphical controls like blueman would show that bluetooth was disabled. Recently, I migrated to the PopOS 24.04 alpha since I wanted to test out COSMIC and also have a bit more stable OS. Now, regardless of whether I use COSMIC or a stable session like Gnome, bluetooth is completely borked. GUI bluetooth managers are actually worse now (blueman crashes when I try to enable Bluetooth), and bluetoothctl doesn't work anymore. bluetoothctl list yields no output. lsusb does not list any Bluetooth adapters. inxi -bE:

Bluetooth:
  Device-1: Intel driver: btusb type: USB
  Report: hciconfig ID: hci0 rfk-id: 4 state: down
    bt-service: enabled,running rfk-block: hardware: no software: no
    address: 00:00:00:00:00:00

hciconfig:

hci0:	Type: Primary  Bus: USB
	BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
	DOWN
	RX bytes:221 acl:0 sco:0 events:6 errors:0
	TX bytes:28 acl:0 sco:0 commands:6 errors:0

Errors from journalctl -b:

Aug 04 23:59:24 arkel-mars kernel: Bluetooth: hci0: DSM reset method type: 0x00
Aug 04 23:59:24 arkel-mars kernel: Bluetooth: hci0: Reading Intel device address failed (-16)
Aug 04 23:59:24 arkel-mars kernel: Bluetooth: hci0: Found device firmware: intel/ibt-0093-0291.sfi
Aug 04 23:59:24 arkel-mars kernel: Bluetooth: hci0: Boot Address: 0x100800
Aug 04 23:59:24 arkel-mars kernel: Bluetooth: hci0: Firmware Version: 149-7.25
Aug 04 23:59:24 arkel-mars kernel: Bluetooth: hci0: Firmware already loaded
Aug 04 23:59:24 arkel-mars kernel: Bluetooth: hci0: Setting Intel event mask failed (-16)
Aug 04 23:59:24 arkel-mars kernel: Bluetooth: hci0: Reading supported features failed (-16)
Aug 04 23:59:24 arkel-mars kernel: Bluetooth: hci0: Error reading debug features
Aug 04 23:59:24 arkel-mars kernel: Bluetooth: hci0: Fseq status: Success (0x00)
Aug 04 23:59:24 arkel-mars kernel: Bluetooth: hci0: Fseq executed: 00.00.04.196
Aug 04 23:59:24 arkel-mars kernel: Bluetooth: hci0: Fseq BT Top: 00.00.04.195
Aug 04 23:59:24 arkel-mars kernel: Bluetooth: hci0: Opcode 0x0c03 failed: -16

Bluetooth Signal Jamming in Linux Mint 22.1: Mouse Interference Blocks Audio Device Detection On Linux Mint 22.1 with PipeWire, I ran into an odd issue with Avantree Bluetooth headphones. They paired successfully (bluetoothctl showed them as connected), but no audio sink appeared in pavucontrol, pactl list sinks, or Mint’s sound settings—no sound output at all. After a lot of trial and error, I traced the problem to Bluetooth interference from a wireless mouse. It was paired, energized, and idle. Once I disconnected the mouse, the headphones instantly appeared as an audio device and started working as expected. Summary: PipeWire was set up correctly, PulseAudio removed Headphones paired successfully but weren't usable Disconnecting an unused Bluetooth mouse allowed audio routing to work This appears to be low-level Bluetooth bandwidth interference, where idle devices can block others from establishing full functionality—even if they’re not actively being used. If you’re troubleshooting missing Bluetooth audio sinks, try disconnecting unused peripherals first. It may save hours of frustration.

## Context I'm having difficulty getting the kernel to load the necessary Bluetooth firmware for my XPS 9310. My model has the AX500 connectivity chip, which uses the QCA6390. Users of both [Ubuntu](https://github.com/NixOS/nixos-hardware/pull/207#issuecomment-727668837) and [Arch](https://wiki.archlinux.org/index.php/Dell_XPS_13_(9310)) have reported Bluetooth working with this model, however, I'm having difficulty finding the right kernel configuration necessary to get this working on NixOS. ## My Configuration I have enabled the following kernel configuration params with the following patch added to boot.kernelPatches in my nix configuration:

# Extra config required for Bluetooth.
    {
      name = "enable-qca6390-bluetooth";
      patch = null;
      extraConfig = ''
        BT_QCA m
        BT_HCIBTUSB m
        BT_HCIBTUSB_AUTOSUSPEND y
        BT_HCIUART m
        BT_HCIUART_QCA y
      '';
    }

I'm loading the related modules like so:

boot.kernelModules = [ "bluetooth" "btqca" "btusb" "hci_qca" "hci_uart" ];

It should go without saying that I have:

hardware.bluetooth.enable = true;

I also have:

hardware.enableRedistributableFirmware = true;

which, enables the [firmwareLinuxNonfree](https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/hardware/all-firmware.nix#L46) package, which in turn adds the firmware from the [linux-firmware](https://github.com/NixOS/nixpkgs/blob/a1ea95ba042964875bdb985d70934aca19ba0c6e/pkgs/os-specific/linux/firmware/firmware-linux-nonfree/default.nix#L8) repo, which in turn includes the [necessary QCA firmware](https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/qca) . ## The Problem This firmware can be observed being loaded in the dmesg output of two separate Ubuntu users [here](https://github.com/NixOS/nixos-hardware/pull/207#issuecomment-727860836) and [here](https://askubuntu.com/questions/1299154/dell-xps-13-9310-bluetooth-wont-find-anything) , both of which report working Bluetooth. However, I am unable to observe it being loaded in mine. For reference, here is the dmesg output from a user with working Bluetooth:

[ 2.349008] Bluetooth: Core ver 2.22
[ 2.349019] Bluetooth: HCI device and connection manager initialized
[ 2.349023] Bluetooth: HCI socket layer initialized
[ 2.349024] Bluetooth: L2CAP socket layer initialized
[ 2.349028] Bluetooth: SCO socket layer initialized
[ 2.394642] Bluetooth: HCI UART driver ver 2.3
[ 2.394644] Bluetooth: HCI UART protocol H4 registered
[ 2.394645] Bluetooth: HCI UART protocol BCSP registered
[ 2.394654] Bluetooth: HCI UART protocol LL registered
[ 2.394655] Bluetooth: HCI UART protocol ATH3K registered
[ 2.394660] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 2.394702] Bluetooth: HCI UART protocol Intel registered
[ 2.394734] Bluetooth: HCI UART protocol Broadcom registered
[ 2.394742] Bluetooth: HCI UART protocol QCA registered
[ 2.394743] Bluetooth: HCI UART protocol AG6XX registered
[ 2.394748] Bluetooth: HCI UART protocol Marvell registered
[ 2.416321] Bluetooth: hci0: setting up ROME/QCA6390
[ 2.420348] Bluetooth: hci0: Frame reassembly failed (-84)
[ 2.444937] Modules linked in: snd_pcm qrtr ns snd_seq_midi snd_seq_midi_event ath11k_pci(+) mhi snd_rawmidi ath11k hci_uart qmi_helpers btqca i915(+) snd_seq btrtl uvcvideo mac80211 snd_seq_device btbcm btintel snd_timer videobuf2_vmalloc dell_wmi drm_kms_helper input_leds videobuf2_memops dell_smbios videobuf2_v4l2 cec dcdbas snd efi_pstore serio_raw rc_core videobuf2_common hid_sensor_als i2c_algo_bit hid_sensor_trigger ucsi_acpi(+) cfg80211 fb_sys_fops industrialio_triggered_buffer processor_thermal_device typec_ucsi dell_wmi_descriptor kfifo_buf hid_sensor_iio_common intel_rapl_common soundcore industrialio wmi_bmof videodev mei_me libarc4 syscopyarea cros_ec_ishtp 8250_dw mc hid_multitouch sysfillrect mei cros_ec sysimgblt intel_soc_dts_iosf typec mac_hid bluetooth ecdh_generic ecc int3403_thermal int340x_thermal_zone acpi_pad intel_hid acpi_tad int3400_thermal acpi_thermal_rel sparse_keymap sch_fq_codel parport_pc ppdev drm lp parport ip_tables x_tables autofs4 hid_sensor_hub
[ 2.756645] Bluetooth: hci0: QCA Product ID :0x00000010
[ 2.756647] Bluetooth: hci0: QCA SOC Version :0x400a0200
[ 2.756647] Bluetooth: hci0: QCA ROM Version :0x00000200
[ 2.756648] Bluetooth: hci0: QCA Patch Version:0x00000d2b
[ 2.756650] Bluetooth: hci0: QCA controller version 0x02000200
[ 2.756651] Bluetooth: hci0: QCA Downloading qca/htbtfw20.tlv
[ 3.584055] Bluetooth: hci0: QCA Downloading qca/htnv20.bin
[ 3.777754] Bluetooth: hci0: QCA setup on UART is completed
[ 3.998318] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 3.998319] Bluetooth: BNEP filters: protocol multicast
[ 3.998321] Bluetooth: BNEP socket layer initialized
[ 14.108234] Bluetooth: RFCOMM TTY layer initialized
[ 14.108238] Bluetooth: RFCOMM socket layer initialized
[ 14.108242] Bluetooth: RFCOMM ver 1.11

And here is the output of dmesg | grep -i blue on my machine:

[    4.363188] Bluetooth: Core ver 2.22
[    4.363199] Bluetooth: HCI device and connection manager initialized
[    4.363201] Bluetooth: HCI socket layer initialized
[    4.363203] Bluetooth: L2CAP socket layer initialized
[    4.363205] Bluetooth: SCO socket layer initialized
[    4.379230] Bluetooth: HCI UART driver ver 2.3
[    4.379231] Bluetooth: HCI UART protocol H4 registered
[    4.379232] Bluetooth: HCI UART protocol BCSP registered
[    4.379238] Bluetooth: HCI UART protocol LL registered
[    4.379256] Bluetooth: HCI UART protocol Intel registered
[    4.379260] Bluetooth: HCI UART protocol QCA registered
[   20.090546] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   20.090553] Bluetooth: BNEP socket layer initialized

As you can see, my Bluetooth setup never performs this step or any of the following hci0 steps:

[ 2.416321] Bluetooth: hci0: setting up ROME/QCA6390

Unsurprisingly, as a result, I'm unable to enable Bluetooth in my GNOME settings GUI, and bluetoothctl shows nothing:

$ bluetoothctl list

$ bluetoothctl devices
No default controller available

## Questions From my understanding, the firmware should be automatically loaded in the case that BT_QCA is enabled and the firmware exists, both of which should be happening as a result of my aforementioned nix configuration. Is this assumption correct? Am I missing a necessary step required to trigger the hci0 lines shown above? Any advice or ideas on how to progress would be greatly appreciated! ## System info

$ nix-shell -p nix-info --run "nix-info -m"
 - system: "x86_64-linux"
 - host os: Linux 5.10.2, NixOS, 21.03pre259798.84917aa00bf (Okapi)
 - multi-user?: yes
 - sandbox: yes
 - version: nix-env (Nix) 2.3.10
 - channels(root): "nixos-21.03pre259798.84917aa00bf, home-manager-20.09"
 - nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

$ lsmod | grep -i bt
btusb                  57344  0
btrtl                  24576  1 btusb
btbcm                  20480  1 btusb
btintel                28672  2 hci_uart,btusb
btqca                  20480  1 hci_uart
bluetooth             589824  13 btrtl,btqca,btintel,hci_uart,btbcm,bnep,btusb
usbcore               270336  5 xhci_hcd,usbhid,uvcvideo,btusb,xhci_pci

$ lspci
00:00.0 Host bridge: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers (rev 01)
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 01)
00:04.0 Signal processing controller: Intel Corporation Device 9a03 (rev 01)
00:06.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller (rev 01)
00:07.0 PCI bridge: Intel Corporation Tiger Lake-LP Thunderbolt PCI Express Root Port #0 (rev 01)
00:07.2 PCI bridge: Intel Corporation Tiger Lake-LP Thunderbolt PCI Express Root Port #2 (rev 01)
00:0a.0 Signal processing controller: Intel Corporation Device 9a0d (rev 01)
00:0d.0 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt USB Controller (rev 01)
00:0d.2 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt NHI #0 (rev 01)
00:0d.3 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt NHI #1 (rev 01)
00:12.0 Serial controller: Intel Corporation Tiger Lake-LP Integrated Sensor Hub (rev 20)
00:14.0 USB controller: Intel Corporation Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller (rev 20)
00:14.2 RAM memory: Intel Corporation Tiger Lake-LP Shared SRAM (rev 20)
00:15.0 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #0 (rev 20)
00:15.1 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #1 (rev 20)
00:16.0 Communication controller: Intel Corporation Tiger Lake-LP Management Engine Interface (rev 20)
00:19.0 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #4 (rev 20)
00:19.1 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #5 (rev 20)
00:1c.0 PCI bridge: Intel Corporation Device a0b8 (rev 20)
00:1d.0 PCI bridge: Intel Corporation Device a0b3 (rev 20)
00:1e.0 Communication controller: Intel Corporation Tiger Lake-LP Serial IO UART Controller #0 (rev 20)
00:1f.0 ISA bridge: Intel Corporation Tiger Lake-LP LPC Controller (rev 20)
00:1f.3 Multimedia audio controller: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller (rev 20)
00:1f.4 SMBus: Intel Corporation Tiger Lake-LP SMBus Controller (rev 20)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP SPI Controller (rev 20)
01:00.0 Non-Volatile memory controller: Toshiba Corporation Device 011a
56:00.0 Unassigned class [ff00]: Qualcomm Device 1101
57:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5260 PCI Express Card Reader (rev 01)

$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 0c45:672a Microdia Integrated_Webcam_HD
Bus 003 Device 002: ID 27c6:533c Shenzhen Goodix Technology Co.,Ltd. FingerPrint
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

## Further Reference In case they help as a reference, here are the links to the default kernel configurations for [NixOS](https://github.com/NixOS/nixpkgs/blob/master/pkgs/os-specific/linux/kernel/common-config.nix) , [Debian](https://salsa.debian.org/kernel-team/linux/blob/master/debian/config/config) and [Arch](https://git.archlinux.org/svntogit/packages.git/tree/trunk/config?h=packages/linux) . Here is my WIP [PR](https://github.com/NixOS/nixos-hardware/pull/207) aimed at adding support for the XPS 9310 to NixOS that will include this work. Here is [my previous post](https://discourse.nixos.org/t/how-to-include-and-use-external-firmware-in-nixos-config-bluetooth-for-qca6390/10471/3) to the NixOS discourse forum asking for help with this issue, yet to receive a response as of writing this.

Trying to connect some wireless headphones to my laptop. They worked a couple days ago then stopped and I cant figure out why. Before that it would work for a few days then stop until I rebooted or just tried again after a few hours. Now it hasn't worked for almost 2 weeks. ``` $ neofetch OS: Arch Linux x86_64 Host: 20BU000AUS ThinkPad T450 Kernel: 5.17.7-zen1-2-zen # Installed bluez 5.64-2 bluez-firmware 1.2-9 bluez-hid2hci 5.64-2 bluez-libs 5.64-2 bluez-utils 5.64-2 hidapi 0.11.2-1 libldac 2.0.2.3-1 pulseaudio-bluetooth 15.0-4 sbc 1.5-2 $ bluetoothctl show Powered: yes Discoverable: no Pairable: yes $ bluetoothctl info 8D:40:4C:C6:73:A4 Device 8D:40:4C:C6:73:A4 (public) Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no $ bluetoothctl connect 8D:40:4C:C6:73:A4 Attempting to connect to 8D:40:4C:C6:73:A4 Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable $ journalctl -u bluetooth bluetoothd: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 8D:40:4C:C6:73:A4: Protocol not available $ systemctl list-unit-files | grep blue UNIT FILE STATE VENDOR PRESET bluetooth-mesh.service enabled disabled bluetooth.service enabled disabled dbus-org.bluez.mesh.service alias - dbus-org.bluez.service alias - bluetooth.target static - $ lsmod | grep bluetooth bluetooth 925696 31 btrtl,btmtk,btintel,btbcm,bnep,btusb crc16 16384 1 bluetooth rfkill 36864 6 iwlmvm,bluetooth,thinkpad_acpi,cfg80211 ecdh_generic 16384 2 bluetooth

I'm using a Raspberry Pi with BlueZ 5.66 and Linux 6.6. I want to use the Pi as a Bluetooth audio sink (A2DP) and AVRCP controller so I can stream audio from an iPhone and control playback (play/pause/next/etc) via D-Bus using the org.bluez.MediaPlayer1 interface. This works correctly when the iPhone initiates the Bluetooth connection to the Pi. I can see the MediaPlayer1 interface under the device path on D-Bus, and playback control works. However, if I initiate the connection from the Pi using:

bluetoothctl connect XX:XX:XX:XX:XX:XX

…the connection succeeds, but org.bluez.MediaPlayer1 never appears. Even if I start playback on the iPhone afterward, the interface is still missing. I'm using BlueZ as the Bluetooth stack and BlueALSA for audio. I'm not using PulseAudio and would prefer to avoid it due to its complexity. From what I understand, MediaPlayer1 is exposed by BlueZ when acting as an AVRCP controller and detecting a remote media player. Is there a way to force or trigger org.bluez.MediaPlayer1 to appear when the Pi initiates the Bluetooth connection to the iPhone? Are there any known limitations, timing issues, or configuration-based workarounds that would allow this to work more reliably (ideally without switching to PulseAudio)? **Steps to reproduce:** 1. Pair and trust the iPhone:

bluetoothctl
   power on
   agent on
   default-agent
   pair XX:XX:XX:XX:XX:XX
   trust XX:XX:XX:XX:XX:XX
   connect XX:XX:XX:XX:XX:XX

2. Start music playback on the iPhone. 3. Check D-Bus for /player0:

busctl tree org.bluez

**Expected:** A /org/bluez/hci0/dev_XX_XX_XX_XX_XX_XX/player0 path should appear, with org.bluez.MediaPlayer1 exposed. **Actual:** That path and interface only appear if the iPhone initiates the Bluetooth connection to the Pi. They never appear if the Pi initiates the connection.

### Context I bought a CM749 UGREEN Bluetooth 5.4 USB adapter for my Nixos machine. It is recognized by lsusb as ID 33fa:0010 USB2.0-BT, but is not detected by KDE/Plasma's bluetooth daemon. I dug deeper and found an Ubuntu bug report with the exact same problem and diagnosis as me. As of today, the last post links to an AskUbuntu post with a vexingly vague answer: > I patch my kernel source to cancel command hci_read_local_ext_features in the hci_init2[] and hci_init3[] in file hci_sync.c. It worked. So, I downloaded and unpacked the 6.15.7 kernel source from cdn.kernel.org , opened the corresponding file in Keta... and was lost like a lamb. Question: What does it mean to "cancel" a command in the linux kernel and how can one do so? Please, do tell me if my question is too vague or whether more information should be provided.

For a specific task, **I am failing to scan BLE / BlueZ (hcitool, gatttool, btdevice-l) in Docker under non-privileged and Non-Host network mode.** These are my results (in Debian-Jessie-8.8.0 Host and debian:jessie docker image): root1@73ab53a9268e:/# hciconfig -a Can't open HCI socket.: Operation not permitted root1@73ab53a9268e:/# bt-device -l Couldn't connect to DBus system bus: Could not connect: Connection refused On another image: root2@0d208802d44a:/# hciconfig -a Can't open HCI socket.: Address family not supported by protocol I even gave ALL-CAP permissions for Docker on Host but still could not make it. docker run --name container-ID --cap-add=ALL -d -v /var/run/docker.sock:/host/var/run/docker.sock -v /dev:/host/dev -v /proc:/host/proc:ro -v /lib/modules:/host/lib/modules:ro -v /usr:/host/usr:ro Image-ID So, is it possible by any chance to scan BLE / BlueZ in docker under Non-Privileged & Non-Host network mode?

I've tried everything mentioned on the answers mentioned in the following post: https://unix.stackexchange.com/questions/255509/bluetooth-pairing-on-dual-boot-of-windows-linux-mint-ubuntu-stop-having-to-p But I've made no progress. A few details about my system: Keyboard: Logitech K380 (Bluetooth) Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal Windows 10 (Latest edition as of writing this post) After changing my keys in linux to the ones from windows, the keyboard connects for a fraction of a second, before disconnecting, and I'm unable to understand why. My keyboard has 3 profiles that I can switch from and I tried all combinations of profile choice in windows and linux. I've spent quite a few hours on this and any help would be appreciated. Please let me know if I am missing any details that might help.

I have a JBL Bluetooth speaker. And usually it doesn't have a problem until my recent question earlier about [Bluetooth](https://unix.stackexchange.com/questions/676403/connecting-to-bluetooth-but-connection-failed-no-audio-endpoints-registered) :) And today's problem is my device is connected, but the device is not showing up in volume control. I try to reinstall blueman but it still not working. By the way, I'm dual booted my Linux with Win11. Please help me to resolve this issue, thank you :D  

I use notify-send and dunst for my notification system on my desktop. After a research, I found out that there are a few commercial solutions for sending push notifications to iOS devices, and I even wrote a script using Pushover. However, I did not find any way to get notifications from the iPhone displayed on my desktop. (Preferably using a unified notification system, for example using notify-send). I know that OSX has very good support for this, so I guess it's not impossible, but I did not find any working solution. Of course, the best solution would be to get full sync, including removing a notification from both places if it has been read in one place. A lot of this is already solved, of course. E-mail, Facebook, etc. notifications gets "synced" out-of-the-box basically. I'm ok with having to write scripts, including having to write customized filters, etc. If there's no full solutions, I'm satisfied with getting the building blocks only, especially something that sends the iOS notifications to my desktop somehow. EDIT: I added the tag Bluetooth because I learned that OSX does this using Bluetooth LE. Looking up Bluetooth LE support still did not help me, though.

I recently installed ubuntu 20.04 and bluetooth seemed to work out-of-the-box. Yesterday, it stopped working with no known reason. I can turn it ON but the settings still show it to be OFF. I tried the following:

$ sudo -i
$ rfkill list
0: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
3: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no

and on running bluetoothctl,

Agent registered
[bluetooth]# power off
No default controller available
[bluetooth]# power on
No default controller available
[bluetooth]# exit

What could be the problem and how to tackle it ?

I (a linux noob) have installed linux mint 20.3 (Una) on an older fujitsu laptop and recently did some updates. Since then, I get an error message on boot: > Bluetooth: hci0: unexpected event for opcode 0x0000 The system then asks for login/password and continues after successful login to the console window. The graphical interface, which is usually started, does not show up. What do I have to do to get to the graphical interface? I tried the "startx" command. A black screens opens up with a mouse cursor, but nothing else happens. **EDIT**
It seems I could overcome the error by using the command "sudo systemctl enable bluetooth". So the remaining question is how to get back to the graphical interface, because this is still not launched.

I want to test and debug linux kernel internals within the bluetooth stack, i.e. /net/bluetooth. I have a (rather minimal) kernel, manually built, with debug symbols, and a busybox at the moment, running in qemu. Now I want to investigate specific bluetooth functions from the kernel. I thought, a virtual device would be easiest but it seems harder than expected. I found there is btvirt from bluez for dealing with virtual bluetooth devices. I have tried manually building bluez statically. Doesn't work, btvirt is still (at least partly) dynamically linked (and hence doesn't work in my vm):

# in bluez repo
autoreconf -vfi
./configure --enable-static --enable-debug --enable-test --enable-testing --enable-deprecated --enable-experimental --enable-logger CFLAGS=-static LDFLAGS=-static
make
ldd emulator/btvirt  # output below
	linux-vdso.so.1 (0x00007f7225f23000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f7225cf5000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f7225f25000)

Also, I tried clang instead of gcc, without success. musl-gcc yielded some error about readline when trying to ./configure I have not followed further yet. What options do I have/which route would be the easiest? 1. Should I abandon my minimal kernel and use a full debian/ubuntu instead? I need debugging symbols and might want to pin to specific versions, so I guess, I would have to manually build the debian/ubuntu kernel (i.e. in accordance with some minimum build flags these distros need/expect), right? 2. How much work is it/should I try to expand my custom small setup with libc, linker etc? 3. Am I on the right track at all? I assume(d) that kernel bluetooth developers might use virtual devices. (Am I correct on that one? If people have experience here, I'd be curious.) Or is this rather hopeless and should I try to pass-through a USB bluetooth device instead? Thanks in advance, I'll be happy to provide further info if needed.

My logitech M590 mouse isn't recognized by blueman. My current distro is Debian 9.9. The mouse worked fine in Ubuntu 18.04.

I have Debian 11 operating system LXQt version, and my computer is HP 15-n220ca I'm trying to install Bluetooth on my computer but it doesn't work. I don't know what USB Bluetooth dongle to buy here in Ecuador. I am close to Coca, Orellana. The Bluetooth internal adapter currently on my laptop is Ralink Corp RT3290. Any help would be appreciated. Thank you. --- I tried what you recommended above and it says my Bluetooth doesn't have the firmware for my operating system. Searching, I found this website and I'm just wondering if this works for any USB Bluetooth 5.0 or 4.0 dongle? https://medium.com/nerd-for-tech/how-to-install-unsupported-bluetooth-5-0-dongle-on-linux-4bf34aa99fed I am stuck. I need help. Thank you.

I need help to solve this dilemma, I recently brought an Acer Aspire 15, I decided to install Debian 12 onto it to replace Windows. I installed KDE as the DE. I attempted to set up my Bluetooth Headphones to my laptop using the GUI. A button to enable bluetooth can be seen, when I press it nothing happens. I then decided to attempt to set it up via bluetoothctl since I believed at the time it was just a problem with the GUI and not the bluetooth connection itelf. bluetoothctl Agent registered [bluetooth]# scan on No default controller available After attempting to scan for devices, an error message appears stating that there is no default controller available. I have attempted to reinstall the Debian operating system, removed and readded btusb, attempted to restart bluetooth.service and none of these worked. **Some more important data:** *Code after running dmesg* sudo dmesg | grep -i bluetooth [ 4.539228] Bluetooth: Core ver 2.22 [ 4.539250] NET: Registered PF_BLUETOOTH protocol family [ 4.539252] Bluetooth: HCI device and connection manager initialized [ 4.539255] Bluetooth: HCI socket layer initialized [ 4.539258] Bluetooth: L2CAP socket layer initialized [ 4.539263] Bluetooth: SCO socket layer initialized [ 5.337009] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 5.337011] Bluetooth: BNEP filters: protocol multicast [ 5.337015] Bluetooth: BNEP socket layer initialized [ 6.564253] Bluetooth: hci0: Opcode 0x0c03 failed: -110 [ 1355.554640] Bluetooth: hci0: Opcode 0x0c03 failed: -110 *Code after running rfkill to ensure that nothing was blocked* sudo rfkill ID TYPE DEVICE SOFT HARD 0 wlan acer-wireless unblocked unblocked 1 bluetooth acer-bluetooth unblocked unblocked 3 wlan phy0 unblocked unblocked 4 bluetooth hci0 unblocked unblocked *Running lsusb to check the driver of the Bluetooth. Which has been identified as IMC Networks Wireless_Device* lsusb Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 30fa:0400 USB Optical Mouse Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3606 IMC Networks Wireless_Device Bus 001 Device 002: ID 04f2:b773 Chicony Electronics Co., Ltd ACER HD User Facing Bus 001 Device 004: ID 0480:0907 Toshiba America Inc EXTERNAL_USB Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I'm unsure how to solve the problem and I need some help. Thank you for reading.

I am struggling to get my **bluetooth adapter** work on my Linux desktop. **I see it when I plug it in, but basically, nothing else works correctly**: $ lsusb Bus 002 Device 006: ID 0a12:0002 Cambridge Silicon Radio, Ltd Fontline Test Equipment Bluetooth Device I can't put it up: $ sudo hciconfig hci0 up Can't init device hci0: Cannot assign requested address (99) Bluetooth service is not working properly and can't be started: $ sudo service bluetooth status bluetooth stop/waiting $ sudo service bluetooth start start: Job failed to start The logs say : "init: Failed to spawn bluetooth main process: unable to execute: No such file or directory". There are also plenty of : [ 5485.753603] init: bluetooth main process ended, respawning [ 5485.776272] init: bluetooth main process (24531) terminated with status 1 I tried to re-install bluetooth, blueman etc. They depends on the bluez package, and one of the issues(?) seems to be that **I fail to install bluez**. $ sudo apt-get install blueman Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: bluez Suggested packages: bluez-hcidump The following NEW packages will be installed: blueman bluez ... Setting up bluez (4.101-0ubuntu13.1) ... reload: Job is not running: dbus invoke-rc.d: initscript dbus, action "force-reload" failed. start: Job failed to start invoke-rc.d: initscript bluetooth, action "start" failed. dpkg: error processing package bluez (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of blueman: blueman depends on bluez (>= 4.61); however: Package bluez is not configured yet. dpkg: error processing package blueman (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. Errors were encountered while processing: bluez blueman Bluetooth is not blocked: $ sudo rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Bluetooth kernel modules are present: $ lsmod | grep -E "blue|bt|rfco" rfcomm 69160 0 btusb 32412 0 bluetooth 391136 4 btusb,rfcomm Those are the packages I have related to bluetooth: $ dpkg -l | grep -i blue iU blueman 1.23-git201403102151-1ubuntu1 amd64 Graphical bluetooth manager iF bluez 4.101-0ubuntu13.1 amd64 Bluetooth tools and daemons ii bluez-compat 4.101-0ubuntu13.1 amd64 BlueZ 3.x compatibility binaries ii gir1.2-gnomebluetooth-1.0 3.8.2.1-0ubuntu4.2 amd64 Introspection data for GnomeBluetooth rc gnome-bluetooth 3.8.2.1-0ubuntu4.1 amd64 GNOME Bluetooth tools rc indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu2 amd64 System bluetooth indicator. ii libbluetooth-dev 4.101-0ubuntu13.1 amd64 Development files for using the BlueZ Linux Bluetooth library ii libbluetooth3:amd64 4.101-0ubuntu13.1 amd64 Library to use the BlueZ Linux Bluetooth stack ii libgnome-bluetooth11 3.8.2.1-0ubuntu4.2 amd64 GNOME Bluetooth tools - support library ii libgnome-bluetooth8 3.2.2-0ubuntu5.1 amd64 GNOME Bluetooth tools - support library ii libmatebluetooth 1.2.1-2+precise amd64 MATE Bluetooth tools (library) rc mate-bluetooth 1.2.1-2+precise amd64 MATE Bluetooth tools In this question , I saw mention of bluez-firmware, but couldn't find that yet. $ sudo apt-get install bluez-firmware ... E: Unable to locate package bluez-firmware In attempts to solve the issue, I upgraded my system to the latest **Linux Mate 17.3 Rosa + upgraded the kernel to 4.4**, however this does not solve the issue. I have been reading tons of more or less similar issue, but could not find the answer :( Thanks for your help!

I don't want to run sudo systemctl start bluetooth command after every restart to turn on my bluetooth service in kali linux; how to keep it running? I tried googling but couldn't find; also can you explain me why bluetooth service is turning off after shutdown in linux but why not in windows?

I connected a device (a joystick) using bluetoothctl and trusted it. So far so good, everything works. But if I quit bluetoothctl power the joystick off and power it on again, it won't reconnect... Here step-by-step what I do in the bluetoothctl cli: [bluetooth]# agent on [bluetooth]# default-agent [bluetooth]# power on [bluetooth]# discoverable on [bluetooth]# pairable on [bluetooth]# scan on [bluetooth]# connect [bluetooth]# trust Funny thing is that I noticied this when I quit : [bluetooth]# quit Agent unregistered And in the journal I am seeing this message : # journalctl -u bluetooth -n50 [...] Mar 05 12:27:30 hostname bluetoothd: No agent available for request type 0 Mar 05 12:27:30 hostname bluetoothd: device_request_pin: Operation not permitted So as far as I understand my device tries to connect but it cannot find an agent to connect. Am I missing something? What am I supposed to do to be able to reconnect automagically without pairing through the CLI everytime I want to play? Thanks!