Announcement

Collapse
No announcement yet.

Bluetooth not working -- mostly -- no idea why

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Bluetooth not working -- mostly -- no idea why

    So this has been a problem since I first installed Kubuntu (my first Linux install) about two months ago. I had other issues to resolve that were more pressing. Now that I have the other stuff solved, I want to come back to this.

    I'm on an ASUS Q501LA laptop running 13.10. Built-in bluetooth. The bluetooth icon does appear in the system tray. When I select and congfigure it, there is a yellow bar warning that "your default bluetooth adapter is not visible for remote devices." If I click "fix it," then select "adapters" the same warning comes on. I can select "fix it" again, but the "visibility" radio button remains clicked. If I change to "temporarily visible," and hit "apply," it reverts back to "hidden" and the "fix it" bar returns.

    Under any configuration, here are the outputs of various bluetooth troubleshooting commands that I've perused in my attempts to resolve this via google:

    Code:
    hcitool scan
    Device is not available: No such device
    Code:
    hciconfig -a
    hci0:   Type: BR/EDR  Bus: USB
            BD Address: 0C:8B:FD:6A:20:01  ACL MTU: 1021:5  SCO MTU: 96:5
            DOWN 
            RX bytes:1016 acl:0 sco:0 events:104 errors:0
            TX bytes:16335 acl:0 sco:0 commands:103 errors:0
            Features: 0xff 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
            Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
            Link policy: RSWITCH HOLD SNIFF 
            Link mode: SLAVE ACCEPT
    Code:
    hciconfig hci0 reset
    Can't down device hci0: Operation not permitted (1)
    Code:
    hciconfig hci0 piscan 
    Can't set scan mode on hci0: Operation not permitted (1)
    Code:
    sudo rfkill list
    0: asus-wlan: Wireless LAN
            Soft blocked: no
            Hard blocked: no
    1: asus-bluetooth: Bluetooth
            Soft blocked: no
            Hard blocked: no
    2: phy0: Wireless LAN
            Soft blocked: no
            Hard blocked: no
    3: hci0: Bluetooth
            Soft blocked: no
            Hard blocked: no
    Code:
    lsusb | grep -i blue
    *NADA*
    Code:
    dmesg | grep blue
    *NADA*
    Any help is greatly appreciated. I am going to try Trusty Tahr under a VM to see if it recognizes bluetooth.

    Thoughts?

    #2
    I'm no Bluetooth expert. But putting that aside, heh...

    hcitool scan looks for remote devices. To find local devices like Bluetooth adapters, run hcitool dev.

    Your hciconfig -a output shows the device in the down state. To actually perform actions with hciconfig, you need to run it with sudo.
    Last edited by SteveRiley; Feb 08, 2014, 12:19 AM. Reason: fix "perform actions..." sentence

    Comment


      #3
      Thanks for the knowledge re: hcitool scan. I was definitely looking at some threads that dealt with external devices; I didn't realize that the commands were different for internal. Here is hcitool dev:

      Code:
      sudo hcitool dev
      Devices:
      (i.e., NADA).

      Any ideas how to get this running?

      Comment


        #4
        Eh, I mistyped the "perform actions..." sentence previously. You don't need sudo with hcitool, but you do need it with hciconfig when making changes.

        Let's start with the basics. Open a console window and run
        Code:
        tail -f /var/log/syslog
        This will print the most recent 10 lines of your system log and then wait for more log entries. I'm having you do this because we want to see what happens next.

        Open another console window and run
        Code:
        sudo hciconfig hci0 up
        What do you see in this console window? What do you see in other one, tailing on the syslog -- did anything appear? If so, what?

        Finally, in the "tailing syslog" console, press Ctrl+C to stop.

        Comment


          #5
          Thanks again for the help!

          The sudo hciconfig hci0 up command seems to have worked (thanks!!) -- well, somewhat. I highlighted the output from tail -f /var/log/syslog that is when I entered the hciconfig. It made my bluetooth device accessible, and I was even able to connect to a bluetooth dongle that I use to play music through external speakers!

          Code:
          ~$ tail -f /var/log/syslog
          Feb  8 07:45:17 mbwd-Q501LA bluetoothd[855]: Endpoint registered: sender=:1.162 path=/MediaEndpoint/HFPAG
          Feb  8 07:45:17 mbwd-Q501LA bluetoothd[855]: Endpoint registered: sender=:1.162 path=/MediaEndpoint/HFPHS
          Feb  8 07:45:17 mbwd-Q501LA bluetoothd[855]: Endpoint registered: sender=:1.162 path=/MediaEndpoint/A2DPSource
          Feb  8 07:45:17 mbwd-Q501LA bluetoothd[855]: Endpoint registered: sender=:1.162 path=/MediaEndpoint/A2DPSink
          Feb  8 07:45:17 mbwd-Q501LA rtkit-daemon[2106]: Recovering from system lockup, not allowing further RT threads.
          Feb  8 07:45:17  rtkit-daemon[2106]: last message repeated 10 times
          Feb  8 07:45:17 mbwd-Q501LA pulseaudio[11547]: [pulseaudio] pid.c: Daemon already running.
          Feb  8 07:45:17 mbwd-Q501LA rtkit-daemon[2106]: Recovering from system lockup, not allowing further RT threads.
          Feb  8 07:45:17  rtkit-daemon[2106]: last message repeated 10 times
          Feb  8 07:45:17 mbwd-Q501LA pulseaudio[11549]: [pulseaudio] pid.c: Daemon already running.
          [HL]Feb  8 07:49:37 mbwd-Q501LA bluetoothd[855]: Adapter /org/bluez/855/hci0 has been enabled[/HL]
          Feb  8 07:50:41 mbwd-Q501LA bluetoothd[855]: Discovery session 0x7f27da5f8b90 with :1.33 activated
          Feb  8 07:50:44 mbwd-Q501LA bluetoothd[855]: Stopping discovery
          Feb  8 07:51:27 mbwd-Q501LA bluetoothd[855]: Discovery session 0x7f27da608b20 with :1.168 activated
          Feb  8 07:51:32 mbwd-Q501LA bluetoothd[855]: Unknown command complete for opcode 37
          Feb  8 07:51:33 mbwd-Q501LA bluetoothd[855]: Unknown command complete for opcode 37
          Feb  8 07:51:33 mbwd-Q501LA NetworkManager[1069]: bluez_manager_bdaddr_removed_cb: assertion 'bdaddr != NULL' failed
          Feb  8 07:51:33 mbwd-Q501LA pulseaudio[11542]: [pulseaudio] bluetooth-util.c: Received GetProperties() reply from unknown device: /org/bluez/855/hci0/dev_00_18_AF_1B_93_DE (device removed?)
          Feb  8 07:51:50 mbwd-Q501LA bluetoothd[855]: Stopping discovery
          Feb  8 07:51:58 mbwd-Q501LA bluetoothd[855]: Badly formated or unrecognized command: AT+CSRSF=0,0,0,0,0,7
          Feb  8 07:52:00 mbwd-Q501LA kernel: [56702.759502] input: 00:18:91:4F:3C:6A as /devices/virtual/input/input15
          Feb  8 07:52:00 mbwd-Q501LA bluetoothd[855]: Operation not supported (95)
          Feb  8 07:52:00 mbwd-Q501LA pulseaudio[11542]: [pulseaudio] module-bluetooth-device.c: Failed to acquire transport /org/bluez/855/hci0/dev_00_18_91_4F_3C_6A/fd0

          But then, as you can see below, I ran into some problems actually playing music out of the bluetooth. I can connect to the dongle. But I can't get any sound to play out of it. What I did, after it was connected, was go to KDE Mixer and try to select it. I could only find the dongle under Audio and Video Settings > Audio Hardware Setup > Sound Card > BT_Device. Selecting it did not shift the output from the built-in speakers to the bluetooth.

          I then tried restarting the BT dongle. It actually auto-connected to the dongle. But then it died immediately. I got this in the syslog:

          Code:
          Feb  8 08:19:34 mbwd-Q501LA bluetoothd[855]: Unable to get service record: Host is down (112)
          Feb  8 08:24:28 mbwd-Q501LA bluetoothd[855]: Badly formated or unrecognized command: AT+CSRSF=0,0,0,0,0,7
          Feb  8 08:24:31 mbwd-Q501LA kernel: [58653.520636] input: 00:18:91:4F:3C:6A as /devices/virtual/input/input17
          Feb  8 08:24:56 mbwd-Q501LA pulseaudio[11542]: [pulseaudio] module-bluetooth-device.c: Failed to acquire transport /org/bluez/855/hci0/dev_00_18_91_4F_3C_6A/fd3
          Feb  8 08:25:11 mbwd-Q501LA bluetoothd[855]: HUP or ERR on socket
          I also tried to use the bluetooh to browse my phone. I paired them fine, and I could browse the phone for a short period. But it keeps disconnecting. Here is the output:

          Code:
          Feb  8 08:52:20 mbwd-Q501LA bluetoothd[855]: Handsfree Agent not registered
          Feb  8 08:52:27 mbwd-Q501LA bluetoothd[855]: Handsfree Agent not registered
          Feb  8 09:01:19 mbwd-Q501LA bluetoothd[855]: hci0: Remove UUID (0x0011) failed: Busy (0x0a)
          Feb  8 09:02:11 mbwd-Q501LA bluetoothd[855]: Discovery session 0x7f27da606870 with :1.204 activated
          Feb  8 09:02:17 mbwd-Q501LA bluetoothd[855]: Unknown command complete for opcode 37
          Feb  8 09:02:34 mbwd-Q501LA bluetoothd[855]: Handsfree Agent not registered
          Feb  8 09:02:38 mbwd-Q501LA kernel: [60939.495111] input: BC:F5:AC:71:A0:D8 as /devices/virtual/input/input22
          Feb  8 09:02:41 mbwd-Q501LA bluetoothd[855]: Handsfree Agent not registered
          Feb  8 09:02:43 mbwd-Q501LA bluetoothd[855]: Discovery session 0x7f27da613b40 with :1.33 activated
          Feb  8 09:02:47 mbwd-Q501LA bluetoothd[855]: Handsfree Agent not registered
          Feb  8 09:02:48 mbwd-Q501LA bluetoothd[855]: Unknown command complete for opcode 37
          Feb  8 09:02:54 mbwd-Q501LA bluetoothd[855]: Handsfree Agent not registered
          Feb  8 09:03:03 mbwd-Q501LA bluetoothd[855]: Stopping discovery
          Feb  8 09:03:19 mbwd-Q501LA bluetoothd[855]: Handsfree Agent not registered
          Feb  8 09:03:23 mbwd-Q501LA kernel: [60984.283948] input: BC:F5:AC:71:A0:D8 as /devices/virtual/input/input23
          Feb  8 09:03:26 mbwd-Q501LA bluetoothd[855]: Handsfree Agent not registered
          I feel like I must be close. Do you have any suggestions for getting this to work?
          Last edited by mbwd1; Feb 08, 2014, 11:05 AM.

          Comment


            #6
            I have noticed similar error messages when connecting my sound bar to Bluetooth on my laptop. Whenever that happens, I just remove and re-add the device in the Bluetooth control module. I don't know why, but this fixes the problem -- Bluetooth devices no longer disppear. Well, until I reboot, that is. After rebooting, their flakiness returns. So I remove and re-add the device yet again. Annoying, and I've seen a fair number of bug reports about this already, so adding more noise won't help I think. I read recently that BlueZ is being worked on, hopefully some stability will arrive soon.

            Comment

            Working...
            X