Bluetooth Not working (works in windows though)

hi, i have a USP Bluetooth stick that works okay on windows but doesn't work at all in Linux
I've tried multiple Linux distributions and nothing changes.
here are the outputs of multiple commands that I've encountered while trying to solve this issue :

note: i can see my usp blueetooth from my phone but i can't connect to it .

~ >>> inxi -Fx                                                                                                                                                                               
System:    Host: ziad-ms7a38 Kernel: 5.6.16-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.1.0 Desktop: Gnome 3.36.3 
           Distro: Manjaro Linux 
Machine:   Type: Desktop Mobo: Micro-Star model: B450M PRO-VDH PLUS (MS-7A38) v: 7.0 serial: <root required> 
           UEFI: American Megatrends v: 9.40 date: 07/04/2019 
CPU:       Topology: 6-Core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen L2 cache: 3072 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 86435 
           Speed: 3600 MHz min/max: 2200/3600 MHz Core speeds (MHz): 1: 3600 2: 2055 3: 2199 4: 2200 5: 2057 6: 2199 7: 2200 
           8: 2201 9: 4060 10: 2060 11: 2060 12: 2200 
Graphics:  Device-1: NVIDIA TU117 [GeForce GTX 1650] vendor: Micro-Star MSI driver: nvidia v: 440.82 bus ID: 29:00.0 
           Display: x11 server: X.org 1.20.8 driver: nvidia resolution: <xdpyinfo missing> 
           OpenGL: renderer: GeForce GTX 1650/PCIe/SSE2 v: 4.6.0 NVIDIA 440.82 direct render: Yes 
Audio:     Device-1: NVIDIA vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus ID: 29:00.1 
           Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio vendor: Micro-Star MSI driver: snd_hda_intel 
           v: kernel bus ID: 2b:00.4 
           Sound Server: ALSA v: k5.6.16-1-MANJARO 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI driver: r8169 v: kernel 
           port: f000 bus ID: 25:00.0 
           IF: enp37s0 state: up speed: 100 Mbps duplex: full mac: 00:d8:61:9d:55:7e 
           Device-2: TP-Link TL-WN722N v2 type: USB driver: r8188eu bus ID: 3-4:2 
           IF: wlp43s0f3u4 state: down mac: d0:37:45:70:75:36 
Drives:    Local Storage: total: 1.02 TiB used: 12.43 GiB (1.2%) 
           ID-1: /dev/sda vendor: Kingston model: SA400S37120G size: 111.79 GiB 
           ID-2: /dev/sdb vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB 
Partition: ID-1: / size: 237.10 GiB used: 12.34 GiB (5.2%) fs: ext4 dev: /dev/sdb2 
Sensors:   System Temperatures: cpu: 57.4 C mobo: N/A gpu: nvidia temp: 36 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 35% 
Info:      Processes: 326 Uptime: 9h 23m Memory: 15.65 GiB used: 8.93 GiB (57.1%) Init: systemd Compilers: gcc: 10.1.0 
           Shell: zsh v: 5.8 inxi: 3.0.37 

~ >>> sudo systemctl status bluetooth -l                                                                                                                                                     
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
     Active: active (running) since Wed 2020-07-08 10:06:52 EET; 9h ago
       Docs: man:bluetoothd(8)
   Main PID: 783 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 19132)
     Memory: 2.7M
     CGroup: /system.slice/bluetooth.service
             └─783 /usr/lib/bluetooth/bluetoothd

Jul 08 16:55:33 ziad-ms7a38 bluetoothd[783]: Endpoint unregistered: sender=:1.29 path=/MediaEndpoint/A2DPSink/sbc
Jul 08 16:55:33 ziad-ms7a38 bluetoothd[783]: Endpoint unregistered: sender=:1.29 path=/MediaEndpoint/A2DPSource/sbc
Jul 08 16:55:33 ziad-ms7a38 bluetoothd[783]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSink/sbc
Jul 08 16:55:33 ziad-ms7a38 bluetoothd[783]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSource/sbc
Jul 08 16:55:34 ziad-ms7a38 bluetoothd[783]: Failed to set mode: Blocked through rfkill (0x12)
Jul 08 19:07:54 ziad-ms7a38 bluetoothd[783]: Endpoint unregistered: sender=:1.29 path=/MediaEndpoint/A2DPSink/sbc
Jul 08 19:07:54 ziad-ms7a38 bluetoothd[783]: Endpoint unregistered: sender=:1.29 path=/MediaEndpoint/A2DPSource/sbc
Jul 08 19:07:54 ziad-ms7a38 bluetoothd[783]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSink/sbc
Jul 08 19:07:54 ziad-ms7a38 bluetoothd[783]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSource/sbc
Jul 08 19:07:55 ziad-ms7a38 bluetoothd[783]: Failed to set mode: Blocked through rfkill (0x12)
~ >>> rfkill list                                                                                                                                                                            
3: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no

~ >>> sudo bluetoothctl                                                                                                                                                                      
Agent registered
[bluetooth]# list
Controller 00:1A:7D:DA:71:10 ziad-ms7a38 [default]
[bluetooth]# 

apparently https://wiki.archlinux.org/index.php/Bluetooth has a section on Bluetooth USB Dongle so here is some outputs related to that :slight_smile:
my bluetooth device doesn't show up in journalctl -f

 journalctl -f                                                                                                                                                                          
-- Logs begin at Thu 2020-07-02 11:20:42 EET. --
Jul 08 20:00:52 ziad-ms7a38 kernel: audit: type=1334 audit(1594231252.096:339): prog-id=46 op=UNLOAD
Jul 08 20:02:57 ziad-ms7a38 NetworkManager[661]: <warn>  [1594231377.6593] device (wlp43s0f3u4): set-hw-addr: new MAC address F6:70:59:91:D7:BD not successfully set (scanning)
Jul 08 20:02:57 ziad-ms7a38 NetworkManager[661]: <info>  [1594231377.6604] device (wlp43s0f3u4): supplicant interface state: inactive -> interface_disabled
Jul 08 20:02:57 ziad-ms7a38 NetworkManager[661]: <info>  [1594231377.7141] device (wlp43s0f3u4): supplicant interface state: interface_disabled -> inactive
Jul 08 20:02:59 ziad-ms7a38 wpa_supplicant[1122]: wlp43s0f3u4: Reject scan trigger since one is already pending
Jul 08 20:03:55 ziad-ms7a38 sudo[32950]: pam_unix(sudo:session): session closed for user root
Jul 08 20:03:55 ziad-ms7a38 audit[32950]: USER_END pid=32950 uid=0 auid=1000 ses=2 subj==unconfined msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Jul 08 20:03:55 ziad-ms7a38 audit[32950]: CRED_DISP pid=32950 uid=0 auid=1000 ses=2 subj==unconfined msg='op=PAM:setcred grantors=pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Jul 08 20:03:55 ziad-ms7a38 kernel: audit: type=1106 audit(1594231435.856:340): pid=32950 uid=0 auid=1000 ses=2 subj==unconfined msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'
Jul 08 20:03:55 ziad-ms7a38 kernel: audit: type=1104 audit(1594231435.856:341): pid=32950 uid=0 auid=1000 ses=2 subj==unconfined msg='op=PAM:setcred grantors=pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2 res=success'

output from btmgmt

[mgmt]# info
Index list with 1 item
hci0:   Primary controller
        addr 00:1A:7D:DA:71:10 version 6 manufacturer 10 class 0x000000
        supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr hs debug-keys 
        current settings: connectable discoverable bondable ssp br/edr 
        name ziad-ms7a38
        short name 
[mgmt]# select hci0
Selected index 0
[hci0]# power up
Set Powered for hci0 failed with status 0x14 (Permission Denied)
[hci0]# info
hci0:   Primary controller
        addr 00:1A:7D:DA:71:10 version 6 manufacturer 10 class 0x000000
        supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr hs debug-keys 
        current settings: connectable discoverable bondable ssp br/edr 
        name ziad-ms7a38
        short name 
[hci0]# 

~ >>> hciconfig -a hci0                                                                                                                                                                      
hci0:   Type: Primary  Bus: USB
        BD Address: 00:1A:7D:DA:71:10  ACL MTU: 640:4  SCO MTU: 64:8
        DOWN 
        RX bytes:1829 acl:0 sco:0 events:103 errors:0
        TX bytes:1575 acl:0 sco:0 commands:102 errors:20
        Features: 0xff 0xff 0x8f 0xfa 0x9b 0xff 0x59 0x87
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
        Link policy: RSWITCH HOLD SNIFF PARK 
        Link mode: SLAVE ACCEPT 

https://wiki.archlinux.org/index.php/Bluetooth
scroll down where examples are like power on, scan on etc..
or install blueman

1 Like

still not working i have tried this before. here is some useful output from bluetoothctl

bluetoothctl tells me it is powered on successfully put doesn't list it as powered in the show output.

~ >>> sudo bluetoothctl                                                                                                                                                                      
[sudo] password for ziad: 
Agent registered
[bluetooth]# list
Controller 00:1A:7D:DA:71:10 ziad-ms7a38 [default]
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# show
Controller 00:1A:7D:DA:71:10 (public)
        Name: ziad-ms7a38
        Alias: ziad-ms7a38
        Class: 0x00000000
        Powered: no
        Discoverable: yes
        DiscoverableTimeout: 0x00000000
        Pairable: yes
        UUID: Headset AG                (00001112-0000-1000-8000-00805f9b34fb)
        UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
        UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
        UUID: Message Access Server     (00001132-0000-1000-8000-00805f9b34fb)
        UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
        UUID: OBEX File Transfer        (00001106-0000-1000-8000-00805f9b34fb)
        UUID: IrMC Sync                 (00001104-0000-1000-8000-00805f9b34fb)
        UUID: OBEX Object Push          (00001105-0000-1000-8000-00805f9b34fb)
        UUID: Vendor specific           (00005005-0000-1000-8000-0002ee000001)
        Modalias: usb:v1D6Bp0246d0536
        Discovering: no
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.NotReady
[bluetooth]# 

all the guides on the internet say that this is caused by rfkill but my Bluetooth device is not blocked by rfkill

turns out my device is of type CSR Dongle 0a12:0001 which has a regression bug and is only works with kernel version ≤ 3.9.11 , there appears to be a patch though

i also found this article explaining how to solve this issue the problem is this article works with the arch kernel but my kernel ends with manjaro .. are they the same thing ? does manjaro introduce changes to the kernel ?

Bluetooth Not working (works in windows though)

I find bluetooth a flawed technology that never even worked properly for me in Windoze. One of the first things I do in Manjaro is permanently disable Bluetooth.

I bet if you bought an Apple Computer Bluetooth would work spectacularly well there though, because most Apple cult members swear Apple is the shiznit.

1 Like

i need Bluetooth because i won't buy another pair of headphones for 70$ . i searched for another type of Bluetooth adapter but i haven't found any in my local market, i also tried to find a PCI Express to Mini PCI Express Card Adapter but found none so I'm stuck with this adapter.
but i actually agree with you thought. i hate Bluetooth.

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by