Bluetooth audio paired but not connect?

jameschyn · 2013-07-14 11:02:32

Hi, guys. I've got a SONY BTN-40 handsfree set. It works very well under Windows XP and Windows 7. Now I've tried several times to make it working under Archlinux. Here is my step:

$ bluetoothctl

Now I get into bluetooth control interface:

[bluetooth]# help
Available commands:
  list                       List available controllers
  show [ctrl]                Controller information
  select <ctrl>              Select default controller
  devices                    List available devices
  power <on/off>             Set controller power
  pairable <on/off>          Set controller pairable mode
  discoverable <on/off>      Set controller discoverable mode
  agent <on/off/capability>  Enable/disable agent with given capability
  default-agent              Set agent as the default one
  scan <on/off>              Scan for devices
  info <dev>                 Device information
  pair <dev>                 Pair with device
  trust <dev>                Trust device
  remove <dev>               Remove device
  connect <dev>              Connect device
  disconnect <dev>           Disconnect device
  version                    Display version
  quit                       Quit program

[bluetooth]# list
Controller 00:09:DD:40:2D:05 SANDOVAL-ARCH [default]

[bluetooth]# show
Controller 00:09:DD:40:2D:05
        Name: SANDOVAL-ARCH
        Alias: SANDOVAL-ARCH
        Class: 0x000000
        Powered: no
        Discoverable: no
        Pairable: no
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        Modalias: usb:v1D6Bp0246d0507
        Discovering: no

Now I set the controller:

[bluetooth]# power on
Changing power on succeeded
[CHG] Controller 00:09:DD:40:2D:05 Powered: yes
[CHG] Controller 00:09:DD:40:2D:05 Class: 0x000104

[bluetooth]# pairable on
Changing pairable on succeeded
[CHG] Controller 00:09:DD:40:2D:05 Pairable: yes
[CHG] Controller 00:09:DD:40:2D:05 PairableTimeout: 0x000000

I scan my handfree set and paring:

[bluetooth]# scan on
[NEW] Device 57:D3:98:08:AE:7D DRC-BTN40
[CHG] Device 57:D3:98:08:AE:7D UUIDs has unsupported type

[bluetooth]# pair 57:D3:98:08:AE:7D
Attempting to pair with 57:D3:98:08:AE:7D
[CHG] Device 57:D3:98:08:AE:7D Connected: yes
Pairing successful
[CHG] Device 57:D3:98:08:AE:7D UUIDs has unsupported type
[CHG] Device 57:D3:98:08:AE:7D Paired: yes
[CHG] Device 57:D3:98:08:AE:7D Connected: no

See last info: "Connected no"? I am wondering why my device has connected but a short time after, it disconnected automatically.
If I manually connect my device:

[bluetooth]# connect 57:D3:98:08:AE:7D
Attempting to connect to 57:D3:98:08:AE:7D
[CHG] Device 57:D3:98:08:AE:7D Connected: yes
Connection successful
[CHG] Device 57:D3:98:08:AE:7D Connected: no

Again failed here.

I think use only this "bluetoothctl" can solve this problem. Any guys know how to solve this ?

Thanks.

Last edited by jameschyn (2013-07-15 00:25:19)

ewaller · 2013-07-14 17:34:51

Moderator: Please use BBCode Tags code tags when posting program output.
Thanks

gsf747 · 2013-07-16 17:12:05

I ran into the exact same issue today with a HomeSpot NFC-enabled Bluetooth Audio Receiver. I'm able to pair and connect, but then it disconnects immediately. Here's my bluetoothctl session:

# bluetoothctl 
[NEW] Controller 00:02:72:DE:16:59 manheim [default]
[NEW] Device 00:10:61:00:01:92 GT BT-Receiver
[bluetooth]# devices
Device 00:10:61:00:01:92 GT BT-Receiver
[bluetooth]# info 00:10:61:00:01:92
Device 00:10:61:00:01:92
        Name: GT BT-Receiver
        Alias: GT BT-Receiver
        Class: 0x240404
        Icon: audio-card
        Paired: yes
        Trusted: yes
        Blocked: no
        Connected: no
        LegacyPairing: no
        UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
[bluetooth]# connect 00:10:61:00:01:92
Attempting to connect to 00:10:61:00:01:92
[CHG] Device 00:10:61:00:01:92 Connected: yes
Failed to connect: org.bluez.Error.Failed
[CHG] Device 00:10:61:00:01:92 Connected: no
[bluetooth]#

And here's the relevant hcidump:

> ACL data: handle 21 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0064 scid 0x0041 result 1 status 2
      Connection pending - Authorization pending
> ACL data: handle 21 flags 0x02 dlen 8
    L2CAP(d): cid 0x0040 len 4 [psm 25]
      AVDTP(s): Discover rsp: transaction 14 nsp 0x00
        ACP SEID 1 - Audio Sink
< ACL data: handle 21 flags 0x00 dlen 7
    L2CAP(d): cid 0x0063 len 3 [psm 25]
      AVDTP(s): Capabilities cmd: transaction 15 nsp 0x00
        ACP SEID 1
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 21 packets 1
> ACL data: handle 21 flags 0x02 dlen 20
    L2CAP(d): cid 0x0040 len 16 [psm 25]
      AVDTP(s): Capabilities rsp: transaction 15 nsp 0x00
        Media Transport
        Media Codec - SBC
          16kHz 32kHz 44.1kHz 48kHz 
          Mono DualChannel Stereo JointStereo 
          4 8 12 16 Blocks
          4 8 Subbands
          SNR Loudness 
          Bitpool Range 2-53
        Content Protection
          02 00 
> ACL data: handle 21 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0064 scid 0x0041 result 0 status 0
      Connection successful
< ACL data: handle 21 flags 0x00 dlen 12
    L2CAP(s): Config req: dcid 0x0064 flags 0x00 clen 0
> ACL data: handle 21 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 4
      MTU 895 
< ACL data: handle 21 flags 0x00 dlen 18
    L2CAP(s): Config rsp: scid 0x0064 flags 0x00 result 0 clen 4
      MTU 895 
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 21 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 21 packets 1
> ACL data: handle 21 flags 0x02 dlen 14
    L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 0
      Success
< ACL data: handle 21 flags 0x00 dlen 12
    L2CAP(s): Disconn req: dcid 0x0064 scid 0x0041
< ACL data: handle 21 flags 0x00 dlen 12
    L2CAP(s): Disconn req: dcid 0x0063 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 21 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 21 packets 1
> ACL data: handle 21 flags 0x02 dlen 12
    L2CAP(s): Disconn rsp: dcid 0x0064 scid 0x0041
> ACL data: handle 21 flags 0x02 dlen 12
    L2CAP(s): Disconn rsp: dcid 0x0063 scid 0x0040
< HCI Command: Disconnect (0x01|0x0006) plen 3
    handle 21 reason 0x13
    Reason: Remote User Terminated Connection
> HCI Event: Command Status (0x0f) plen 4
    Disconnect (0x01|0x0006) status 0x00 ncmd 1
> HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 21 reason 0x16
    Reason: Connection Terminated by Local Host

jameschyn · 2013-07-20 04:09:01

No one use bluetooth handfree set under linux ?
Or every one use wired or 2.4G?

progandy · 2013-07-20 10:32:40

The stable pulseaudio (v4.0) does not support the new bluez 5 API. The git version should support it since june.
PS: heftig has a precompiled pulseaudio-git in his private repository, it is listed here: https://wiki.archlinux.org/index.php/Un … positories

Last edited by progandy (2013-07-20 10:42:07)

ttll · 2013-10-08 11:51:45

Using pulseaudio-git also fixed my Bluetooth Headphone issue with Gnome3.10 requiring bluez5.

vlsd · 2013-10-08 23:00:19

Why would having pulseaudio installed or not interfere with the ability to connect or to pair with one's device?

When using bluez4 I used to connect through ALSA and didn't even have pulseaudio installed. Did bluez5 introduce pulseaudio as a dependency or an optional dependency, but forgot to list it as such? Also, I want to note that I just tried installing pulseaudio-git from AUR and I still cannot connect to my headset using bluez5.

[Edit] It seems indeed that pulseaudio-git is needed to get headsets working with bluez5. As for getting my headset paired and connected everything seems to work fine as of today through bluetoothctl as long as I don't forget to turn the power to the controller on and enable the agent before pairing.

Last edited by vlsd (2013-11-18 20:31:47)

netskink · 2013-12-02 01:03:44

Hello

I have pulseaudio-git and bluez5 installed, and I have similar problem. I can pair my headset but I can not connect.

[bluetooth]# scan on
Discovery started
[CHG] Controller 00:1E:4C:F4:98:5B Discovering: yes
[CHG] Device 00:1A:7D:12:36:B9 LegacyPairing: yes
[CHG] Device 00:1A:7D:12:36:B9 RSSI: -70
[CHG] Device 00:1A:7D:12:36:B9 RSSI: -56
[CHG] Device 00:1A:7D:12:36:B9 RSSI: -64
[CHG] Device 00:1A:7D:12:36:B9 RSSI: -55
[CHG] Device 00:1A:7D:12:36:B9 RSSI: -69
[CHG] Device 00:1A:7D:12:36:B9 RSSI: -55
[bluetooth]# pair 00:1A:7D:12:36:B9
Attempting to pair with 00:1A:7D:12:36:B9
Failed to pair: org.bluez.Error.AlreadyExists
[CHG] Device 00:1A:7D:12:36:B9 RSSI: -68
[CHG] Device 00:1A:7D:12:36:B9 RSSI: -58
[bluetooth]# remove 00:1A:7D:12:36:B9
[DEL] Device 00:1A:7D:12:36:B9 SoundBot SB220
Device has been removed
[bluetooth]# pair 00:1A:7D:12:36:B9
Device 00:1A:7D:12:36:B9 not available
[NEW] Device 00:1A:7D:12:36:B9 SoundBot SB220
[CHG] Device 00:1A:7D:12:36:B9 RSSI: -64
[CHG] Device 00:1A:7D:12:36:B9 RSSI: -79
[CHG] Device 00:1A:7D:12:36:B9 RSSI: -55
[CHG] Device 00:1A:7D:12:36:B9 RSSI: -75
[CHG] Device 00:1A:7D:12:36:B9 RSSI: -55
[CHG] Device 00:1A:7D:12:36:B9 RSSI: -72
[CHG] Device 00:1A:7D:12:36:B9 RSSI: -54
[CHG] Device 00:1A:7D:12:36:B9 RSSI: -74
[bluetooth]# pair 00:1A:7D:12:36:B9
Attempting to pair with 00:1A:7D:12:36:B9
[CHG] Device 00:1A:7D:12:36:B9 Connected: yes
[CHG] Device 00:1A:7D:12:36:B9 UUIDs has unsupported type
[CHG] Device 00:1A:7D:12:36:B9 Paired: yes
Pairing successful
[CHG] Device 00:1A:7D:12:36:B9 Paired: no
[CHG] Device 00:1A:7D:12:36:B9 Connected: no
[CHG] Device 00:1A:7D:12:36:B9 RSSI: -54
[CHG] Device 00:1A:7D:12:36:B9 RSSI: -62
[CHG] Device 00:1A:7D:12:36:B9 RSSI: -54
[bluetooth]# agent on
Agent registered
[bluetooth]# pair 00:1A:7D:12:36:B9
Attempting to pair with 00:1A:7D:12:36:B9
[CHG] Device 00:1A:7D:12:36:B9 Connected: yes
[CHG] Device 00:1A:7D:12:36:B9 Paired: yes
Pairing successful
[CHG] Device 00:1A:7D:12:36:B9 Connected: no
[bluetooth]# trust 00:1A:7D:12:36:B9
[CHG] Device 00:1A:7D:12:36:B9 Trusted: yes
Changing 00:1A:7D:12:36:B9 trust succeeded
[bluetooth]# pair 00:1A:7D:12:36:B9
Attempting to pair with 00:1A:7D:12:36:B9
Failed to pair: org.bluez.Error.AlreadyExists
[bluetooth]# remove 00:1A:7D:12:36:B9
[DEL] Device 00:1A:7D:12:36:B9 SoundBot SB220
Device has been removed
[NEW] Device 00:1A:7D:12:36:B9 SoundBot SB220
[bluetooth]# pair 00:1A:7D:12:36:B9
Attempting to pair with 00:1A:7D:12:36:B9
[CHG] Device 00:1A:7D:12:36:B9 Connected: yes
[CHG] Device 00:1A:7D:12:36:B9 UUIDs has unsupported type
[CHG] Device 00:1A:7D:12:36:B9 Paired: yes
Pairing successful
[CHG] Device 00:1A:7D:12:36:B9 Connected: no
[bluetooth]# connect 00:1A:7D:12:36:B9
Attempting to connect to 00:1A:7D:12:36:B9
Failed to connect: org.bluez.Error.Failed

daspostloch · 2013-12-05 23:34:57

I have the exact same problem - it connects shortly, never having asked for a password, and then disconnects after two seconds. Also updated to pulseaudio-git.. any further hints or troubleshooting questions anyone? Thanks..

netskink · 2013-12-07 20:20:48

I had these same problems. It would pair, but not connect. I updated the archwiki page on my setup. here

lahwaacz · 2013-12-27 12:50:58

pulseaudio from [extra] pulls from a git snapshot to support bluez5 - see this and this commit. Can somebody test if it works with the package from [extra]? Otherwise it might be worth filing a bug report.

whatshisname · 2014-01-18 20:18:21

Chiming in with the paired but can't connect problem. I've uninstalled everything alsa and pulseaudio 4 or 5 times during the past month or so trying to get this thing to work but it never does. The wiki, which I have "followed to a t", suggests using pulseaudio-git from AUR but that package has been broken for over a month, failing with:

/tmp/yaourt-tmp-USERNAME/aur-pulseaudio-git/src/pulseaudio/configure: line 9478: syntax error near unexpected token `2.4'
/tmp/yaourt-tmp-USRNAME/aur-pulseaudio-git/src/pulseaudio/configure: line 9478: `LT_PREREQ(2.4)'
==> ERROR: A failure occurred in build().
    Aborting...
==> ERROR: Makepkg was unable to build pulseaudio-git.

Is there anyone out there who has a bluetooth headset set up working on a 64 bit machine in the current sad state of affairs in the bluetooth4 not quite bluetooth5 world?

I'm on a Dell Latitude D630.

Edit: For some reason libtool wasn't installed on my system and was causing install of pulseaudio-git to fail. Past that hurdle now but still can't connect my bluetooth headset. Sigh.

Last edited by whatshisname (2014-01-19 17:43:25)

fdservices · 2014-01-21 12:27:17

pulseaudio-git makes no difference to me.

Please let me know if anyone finds the answer - most frustrating!

Andrew

fdservices · 2014-01-21 16:36:39

OK, this seems to be a bluez5 problem. Downgrading to bluez-fedora, bluez-tools and bluez-utils (bluez4), all still in AUR, and then connecting the headset with 'bt-audio -c' works.

'course, this will probably break other things, especially bluedevil which only works with bluez5

Andrew

whatshisname · 2014-01-21 16:47:18

Glad you got it working. After my post, I too tried downgrading -- again -- but it still didn't work.

Did you use pulseaudio-git with your bluez4 installation or do you fall back to pulseaudio from the main repositories? I think I stayed with pulseaudio-git.

fdservices · 2014-01-21 16:56:17

No I did not use pulseaudio-git

I used bluez-fedora, which includes bluez-utils, and bluez-tools (change the dependency in PKGBUILD to bluez-fedora) all from AUR

bluez-tools includes bt-audio, among others, which connects the headset.

Andrew

AndyRTR · 2014-01-21 18:21:14

There's currently no bluez5 media api compatible alsa implementation. So either use pulseaudio and bluez5 or some outdated bluez4 AUR stuff.

whatshisname · 2014-01-21 19:03:00

Are you saying that if you use pulseaudio and bluez5, then you should remove all things alsa from your system?

AndyRTR · 2014-01-21 19:09:11

no. I once could confirm my BT headphones working in Gnome with PA and kept alsa stuff installed but removed all BT v4 packages.

vlsd · 2014-01-21 19:16:07

fdservices wrote:

pulseaudio-git makes no difference to me.

It didn't use to work for me either, I think something changed in a semi-recent version to support my hardware ( I have a D-Link DBT-120 adapter and a Sony DR-BT50 headset).

whatshisname wrote:

Are you saying that if you use pulseaudio and bluez5, then you should remove all things alsa from your system?

You don't need to remove alsa, just reroute its output through pulseaudio in asound.conf. This is what my /etc/asound.conf looks like, for reference:

# Use PulseAudio by default
pcm.!default {
  type pulse
  fallback "sysdefault"
  hint {
    show on
    description "Default ALSA Output (currently PulseAudio Sound Server)"
  }
}

ctl.!default {
  type pulse
  fallback "sysdefault"
}

vlsd · 2014-01-21 19:22:10

Also just did a bluez upgrade today (from the official repos) and while my headset still works, it took about five tries to connect to it, with messages like this:

[bluetooth]# connect 00:1D:BA:29:50:D3 
Attempting to connect to 00:1D:BA:29:50:D3
Failed to connect: org.bluez.Error.Failed
[CHG] Device 00:1D:BA:29:50:D3 Connected: yes
[CHG] Device 00:1D:BA:29:50:D3 Connected: no
[bluetooth]# connect 00:1D:BA:29:50:D3 
Attempting to connect to 00:1D:BA:29:50:D3
[CHG] Device 00:1D:BA:29:50:D3 Connected: yes
Connection successful

So something is here is certainly fucky.

Daimusou · 2014-01-21 23:21:53

Often with simple 'failed' messages like that there can be clues as to what really went wrong in the system journal.
To see the last 20 lines of the journal:

sudo journalctl -n 20

I have audio through pulseaudio to bluetooth headset working on my x86_64 desktop Arch box, but not yet
on my headless Arch ARM box. The problem is not ARM, but that there are quite a few things that just
"come along" with the desktop environment (I use xfce4) that have to be done manually on a headless system.
Starting the per-session dbus daemon and the pulseaudio server (which runs as the user,
not as root) are a couple; there may be more.

As was noted above, ALSA wlll not work with the latest bluez. The story I heard is that nobody stepped forward
to update ALSA, so this might change in the future. But for now, pulseaudio is it. The wiki has several
obsolete bluez4 references so beware of any Google searches on these problems that date from more than
a year ago.

bluez 5.13-1
pulseaudio 4.0-6

fdservices · 2014-01-22 08:12:48

For me, there is nothing reported in the journal, and my headset does not work with bluez5. I also have x86_64 arch, bluez 5-14-1 and pulseaudio 4.0.6

I confirm that it works with bluez4, so I guess it must depend on the type of hardware.

Requesting information ...
BD Address: 00:0C:55:1C:CD:DA
OUI Company: Microlink Communications Inc. (00-0C-55)
Device Name: Motorola H500
LMP Version: 1.2 (0x2) LMP Subversion: 0x886
Manufacturer: Cambridge Silicon Radio (10)
Features: 0xfc 0xfe 0x0f 0x00 0x08 0x08 0x00 0x00
<encryption> <slot offset> <timing accuracy> <role switch>
<hold mode> <sniff mode> <RSSI> <channel quality> <SCO link>
<HV2 packets> <HV3 packets> <u-law log> <A-law log> <CVSD>
<paging scheme> <power control> <transparent SCO>
<AFH cap. slave> <AFH cap. master>

Andrew

whatshisname · 2014-01-28 01:33:54

I'm chiming in in agreement with fdservices. It's all in the hardware!

I have spent *days* trying to get the 2 or 3 headsets around my house (the latest being a Plantronics 330) working with my laptop, trying both Bluez4 and Bluez5 to no avail.

The wiki for Bluetooth Headsets, https://wiki.archlinux.org/index.php/Bl … dio_method, mentioned success with the SoundBot SB220. So I broke down and bought a pair. They arrived today. (Nice headsets, BTW!)

My last attempt at this madness had me trying bluez4 so I started there this evening.

I began with the wiki: https://wiki.archlinux.org/index.php/Bluez4 paying particular attention to https://wiki.archlinux.org/index.php/Bl … SA_devices and editing the /etc/asound.conf file per the wiki.

The command sequence was:

systemctl start bluetooth
hcitool scan # To get the Mac address of my new headset
bluez-simple-agent # Ctrl-C to exit after the agent is registered. Ignore the error messages.
bluez-simple-agent hci0 FC:58:FA:C6:49:B3 # pairing the SoundBot
(Enter 0000 passkey)
bt-audio -c FC:58:FA:C6:49:B3 # as normal user to connect

It connected!!!

Then a quick trip to alsamixer to make sure there weren't any muted outputs. (This is a big gotcha. For some reason, probably due to all the tinkering around, some of the outputs continually get muted even though I have unmuted them numerous times before. Also, beware of outputs that have their volume set to max or 80%, etc. but are nonetheless muted as evidenced by the "MM" in the box below the volume scale. Click "m" to unmute them.)

This proved to be sufficient to get the new headset working with Google Talk, the primary reason for my messing with bluetooth in the first place. Happily, the SB220 was one of the options in both the "Microphone" and "Speakers" drop down boxes in "Chat" settings. Selected the SB220 in both boxes, successfully tested the mike and and headset and I'm finally back to making long distance phone calls with my laptop. Yay!

Back to my laptop only to discover that music played with mplayer wasn't streaming to the headset

So another trip to the wiki and this section: https://wiki.archlinux.org/index.php/Bl … om_the_AUR

I installed bluez-tools which changed the /etc/asound.conf file but happily got my headset listed in pavucontrol. In the "Output devices" tab I had to click the green check mark to activate the headset whereupon "mplayer some.mp3" streamed music to my headset!!

I *might* get around to testing this with bluez5 but having gotten this far, I'm not inclined to fix something that isn't broken.

The moral of this story is the choice of bluetooth headset/hardware makes all the difference. At least it did for me.

Perhaps we should start a list of compatible bluetooth headsets in the wiki? There is clearly a big interest in this topic considering the well over 4,400 views of this thread alone.

Hope this helps someone.

vlsd · 2014-01-28 20:10:04

whatshisname wrote:

Perhaps we should start a list of compatible bluetooth headsets in the wiki? There is clearly a big interest in this topic considering the well over 4,400 views of this thread alone.

I second this. Do you think the bluetooth adapter makes a big difference or is it mostly in the headset?

Arch Linux

#1 2013-07-14 11:02:32

Bluetooth audio paired but not connect?

#2 2013-07-14 17:34:51

Re: Bluetooth audio paired but not connect?

#3 2013-07-16 17:12:05

Re: Bluetooth audio paired but not connect?

#4 2013-07-20 04:09:01

Re: Bluetooth audio paired but not connect?

#5 2013-07-20 10:32:40

Re: Bluetooth audio paired but not connect?

#6 2013-10-08 11:51:45

Re: Bluetooth audio paired but not connect?

#7 2013-10-08 23:00:19

Re: Bluetooth audio paired but not connect?

#8 2013-12-02 01:03:44

Re: Bluetooth audio paired but not connect?

#9 2013-12-05 23:34:57

Re: Bluetooth audio paired but not connect?

#10 2013-12-07 20:20:48

Re: Bluetooth audio paired but not connect?

#11 2013-12-27 12:50:58

Re: Bluetooth audio paired but not connect?

#12 2014-01-18 20:18:21

Re: Bluetooth audio paired but not connect?

#13 2014-01-21 12:27:17

Re: Bluetooth audio paired but not connect?

#14 2014-01-21 16:36:39

Re: Bluetooth audio paired but not connect?

#15 2014-01-21 16:47:18

Re: Bluetooth audio paired but not connect?

#16 2014-01-21 16:56:17

Re: Bluetooth audio paired but not connect?

#17 2014-01-21 18:21:14

Re: Bluetooth audio paired but not connect?

#18 2014-01-21 19:03:00

Re: Bluetooth audio paired but not connect?

#19 2014-01-21 19:09:11

Re: Bluetooth audio paired but not connect?

#20 2014-01-21 19:16:07

Re: Bluetooth audio paired but not connect?

#21 2014-01-21 19:22:10

Re: Bluetooth audio paired but not connect?

#22 2014-01-21 23:21:53

Re: Bluetooth audio paired but not connect?

#23 2014-01-22 08:12:48

Re: Bluetooth audio paired but not connect?

#24 2014-01-28 01:33:54

Re: Bluetooth audio paired but not connect?

#25 2014-01-28 20:10:04

Re: Bluetooth audio paired but not connect?

Board footer