Skip to contentSkip to conversation

Samsung WEP210 Bluetooth Headset

Bluez-users Jelle de Jong 2 participants 7 messages Apr 18, 2008 – Apr 21, 2008 Bluetooth drivers

lore
Share & tools
lore
#0 lore raw

This message contains the following attachment(s):
Samsung WEP210 Bluetooth Headset.txt simple-agent

Hello everybody,

I bought a new headset and am trying to get it working under debian sid 3.30-2 bluez-utils

However i cant connect to the device when it is in pairing mode.

I have attached my working files with a lot of background information.

Can somebody help me to get the device working.

Kind regards,

Jelle

#!/bin/bash

http://gentoo-wiki.com/HOWTO_use_a_bluetooth_headset
http://www.wahlau.org/failed_getting_bluetooth_headset_to_work_with_ubuntu_edgy_eft
http://www.think-future.de/wiki/index.php?title=Bluetooth

sudo cp /etc/bluetooth/audio.conf /etc/bluetooth/audio.conf.backup sudo mv /etc/bluetooth/audio.conf.backup /etc/bluetooth/audio.conf

cp $HOME/.asoundrc $HOME/.asoundrc.backup

# step 1: install bluetooth alsa software
sudo apt-get install bluetooth-alsa bluez-utils
# step 2: enable bluetooth alsa service

echo '[Bluetooth Service]
Identifier=audio
Name=Audio service
Description=Bluetooth Audio service Autostart=true' | sudo tee /etc/bluetooth/audio.conf

echo '[Bluetooth Service]
Identifier=audio
Name=Audio service
Description=Bluetooth Audio service Autostart=true' | sudo tee /etc/bluetooth/audio.service

cat /etc/bluetooth/audio.service

cat /etc/bluetooth/audio.conf

hcitool scan
20:07:09:15:A9:5A
sudo sdptool browse 20:07:09:15:A9:5A

sudo sdptool search HS
Inquiring ...
Searching for HS on 20:07:09:15:A9:5A ...
Service Name: Headset
Service RecHandle: 0x10001
Service Class ID List:
"Headset" (0x1108)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 2
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Headset" (0x1108)

    Version: 0x0100

echo 'pcm.bluetooth {
type bluetooth
device 20:07:09:15:A9:5A
profile "auto"
}' | tee --append $HOME/.asoundrc

sudo hcitool cc 20:07:09:15:A9:5A

cat $HOME/.asoundrc

sudo /etc/init.d/bluetooth restart
sudo /etc/init.d/alsa-utils restart

sudo apt-get install mplayer

mplayer -ao alsa:device=bluetooth test.mp3
arecord -D bluetooth -f S16_LE | aplay -D bluetooth -f S16_LE

sudo modprobe snd-bt-sco
dbus-send --system --dest=org.bluez /org/bluez/hci0 org.bluez.Adapter.SetMode string:discoverable btsco -v 20:07:09:15:A9:5A
sudo a2dpd

pcm.bluetooth {
    type plug
    slave {
       pcm "bluetooth_hw"
    }
}
pcm.bluetooth_hw {
    type bluetooth
    device 00:0B:2E:5B:30:E6
}

sudo hidd --connect 20:07:09:15:A9:5A
sudo l2ping 20:07:09:15:A9:5A

passkey-agent 0000 20:07:09:15:A9:5A

echo 0000 | sudo tee /etc/bluetooth/pin

sdptool search 20:07:09:15:A9:5A
hcitool cc 20:07:09:15:A9:5A
sudo /etc/init.d/syslog restart

sudo /etc/init.d/sysklogd start
sudo /etc/init.d/klogd start

sudo cat /var/log/syslog

sudo vim /etc/bluetooth/hcid.conf
pin_helper /etc/bluetooth/feed-pin.sh;

echo '#!/bin/sh
echo "PIN:0000"' | sudo tee /etc/bluetooth/feed-pin.sh

Apr 19 00:56:29 debian-eeepc hcid[5705]: Audio API: received BT_GETCAPABILITIES_REQ
Apr 19 00:56:29 debian-eeepc hcid[5705]: Audio API: sending BT_GETCAPABILITIES_RSP
Apr 19 00:56:29 debian-eeepc hcid[5705]: Audio API: received BT_SETCONFIGURATION_REQ
Apr 19 00:56:29 debian-eeepc hcid[5705]: config sco - device = 20:07:09:15:A9:5A access_mode = 2
Apr 19 00:56:32 debian-eeepc hcid[5705]: pin_code_request (sba=00:1B:DC:00:32:71, dba=20:07:09:15:A9:5A)
Apr 19 00:56:32 debian-eeepc hcid[5705]: connect(): Connection refused (111)
Apr 19 00:56:32 debian-eeepc hcid[5705]: config failed
Apr 19 00:56:32 debian-eeepc hcid[5705]: Audio API: sending BT_SETCONFIGURATION_RSP

Package: bluez-utils
Version: 3.30-2

dbus-send --system --type=method_call --print-reply --dest=":1.20" \
/org/bluez/audio org.bluez.audio.Manager.CreateDevice string:20:07:09:15:A9:5A

dbus-send --system --type=method_call --print-reply --dest=":1.20" \
"/org/bluez/audio/device0" org.bluez.audio.Sink.Connect

sudo python simple-agent
Agent registered
RequestPasskey (/hci0/dev_20_07_09_15_A9_5A)

Apr 19 01:24:29 debian-eeepc hcid[2353]: Audio API: received BT_GETCAPABILITIES_REQ
Apr 19 01:24:29 debian-eeepc hcid[2353]: Audio API: sending BT_GETCAPABILITIES_RSP
Apr 19 01:24:29 debian-eeepc hcid[2353]: Audio API: received BT_SETCONFIGURATION_REQ
Apr 19 01:24:29 debian-eeepc hcid[2353]: config sco - device = 20:07:09:15:A9:5A access_mode = 2
Apr 19 01:24:33 debian-eeepc hcid[2353]: link_key_request (sba=00:1B:DC:00:32:71, dba=20:07:09:15:A9:5A)
Apr 19 01:24:36 debian-eeepc kernel: usb 1-2: USB disconnect, address 4
Apr 19 01:24:36 debian-eeepc hcid[2353]: HCI dev 0 down
Apr 19 01:24:36 debian-eeepc hcid[2353]: Stopping security manager 0
Apr 19 01:24:36 debian-eeepc hcid[2353]: Device hci0 has been disabled
Apr 19 01:24:36 debian-eeepc hcid[2353]: connect(): Software caused connection abort (103)
Apr 19 01:24:36 debian-eeepc hcid[2353]: config failed
Apr 19 01:24:36 debian-eeepc hcid[2353]: Audio API: sending BT_SETCONFIGURATION_RSP
Apr 19 01:24:37 debian-eeepc hcid[2353]: HCI dev 0 unregistered
Apr 19 01:24:37 debian-eeepc hcid[2353]: Unregister path: /org/bluez/hci0
Apr 19 01:24:37 debian-eeepc hcid[2353]: Device hci0 has been removed
Apr 19 01:24:37 debian-eeepc kernel: usb 1-2: new full speed USB device using uhci_hcd and address 5
Apr 19 01:24:37 debian-eeepc kernel: usb 1-2: configuration #1 chosen from 1 choice

#!/usr/bin/python

import gobject

import dbus
import dbus.service
import dbus.mainloop.glib

class Agent(dbus.service.Object):

	@dbus.service.method("org.bluez.Agent",
					in_signature="", out_signature="")
	def Release(self):
		print "Release"
		mainloop.quit()

	@dbus.service.method("org.bluez.Agent",
					in_signature="os", out_signature="")
	def Authorize(self, device, uuid):
		print "Authorize (" + device + ", " + uuid + ")"
		return

	@dbus.service.method("org.bluez.Agent",
					in_signature="o", out_signature="s")
	def RequestPasskey(self, device):
		print "RequestPasskey (" + device + ")"
		return "0000"

	@dbus.service.method("org.bluez.Agent",
					in_signature="s", out_signature="")
	def ConfirmModeChange(self, mode):
		print "ConfirmModeChange (" + mode + ")"
		return

	@dbus.service.method("org.bluez.Agent",
					in_signature="", out_signature="")
	def Cancel(self):
		print "Cancel"
		return

if __name__ == '__main__':
dbus.mainloop.glib.DBusGMainLoop(set_as_default=True)

bus = dbus.SystemBus()
manager = dbus.Interface(bus.get_object("org.bluez", "/"),
"org.bluez.Manager")

path = manager.DefaultAdapter()
adapter = dbus.Interface(bus.get_object("org.bluez", path),
"org.bluez.Adapter")

path = "/test/agent"
object = Agent(bus, path)

adapter.RegisterAgent(path)
print "Agent registered"

mainloop = gobject.MainLoop()
mainloop.run()

#adapter.UnregisterAgent(path)
#print "Agent unregistered"

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

#1 lore raw
Quoted 6 lines · Jelle de Jong

This message contains the following attachment(s):
Samsung WEP210 Bluetooth Headset.txt simple-agent

Hello everybody,

Quoted 8 lines

I bought a new headset and am trying to get it working under debian sid 3.30-2 bluez-utils

However i cant connect to the device when it is in pairing mode.

I have attached my working files with a lot of background information.

Can somebody help me to get the device working.

Some updated information with a full hcidump

Kind regards,

Jelle

hciconfig -a
hci0: Type: USB
BD Address: 00:1B:DC:00:32:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN
RX bytes:3311300 acl:6850 sco:62541 events:778 errors:0
TX bytes:7160 acl:289 sco:0 commands:177 errors:0
Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'debian-eeepc-0'
Class: 0x080100
Service Classes: Capturing
Device Class: Computer, Uncategorized
HCI Ver: 2.0 (0x3) HCI Rev: 0xc5c LMP Ver: 2.0 (0x3) LMP Subver: 0xc5c
Manufacturer: Cambridge Silicon Radio (10)

HCI sniffer - Bluetooth packet analyzer ver 1.41
device: hci0 snap_len: 1028 filter: 0xffffffff

Quoted 1 line

HCI Event: Connect Request (0x04) plen 10

0000: 5a a9 15 09 07 20 04 04 20 01 Z.... .. .
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
0000: 5a a9 15 09 07 20 00 Z.... .

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

0000: 00 01 09 04 ....

Quoted 1 line

HCI Event: Role Change (0x12) plen 8

0000: 00 5a a9 15 09 07 20 00 .Z.... .

Quoted 1 line

HCI Event: Connect Complete (0x03) plen 11

0000: 00 2b 00 5a a9 15 09 07 20 01 00 .+.Z.... ..
< ACL data: handle 43 flags 0x02 dlen 10
L2CAP(s): Info req: type 2
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
0000: 2b 00 +.

Quoted 1 line

HCI Event: Page Scan Repetition Mode Change (0x20) plen 7

0000: 5a a9 15 09 07 20 01 Z.... .

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

0000: 00 01 1b 04 ....
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
0000: 2b 00 0f 00 +...

Quoted 1 line

HCI Event: Command Complete (0x0e) plen 6

0000: 01 0d 08 00 2b 00 ....+.
< HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4
0000: 2b 00 18 cc +...

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

0000: 00 01 0f 04 ....
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
0000: 5a a9 15 09 07 20 02 00 00 00 Z.... ....

Quoted 1 line

HCI Event: Connection Packet Type Changed (0x1d) plen 5

0000: 00 2b 00 1e 33 .+..3

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

0000: 00 01 19 04 ....

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 2b 00 01 00 .+...

Quoted 1 line

ACL data: handle 43 flags 0x02 dlen 16

L2CAP(s): Info rsp: type 2 result 0
Extended feature mask 0x0000

Quoted 1 line

HCI Event: Read Remote Supported Features (0x0b) plen 11

0000: 00 2b 00 fc fe 0f 00 08 08 00 00 .+.........

Quoted 1 line

HCI Event: Remote Name Req Complete (0x07) plen 255

  0000: 00 5a a9 15 09 07 20 53  61 6d 73 75 6e 67 20 57  .Z.... Samsung W
  0010: 45 50 32 31 30 00 00 00  00 00 00 00 00 00 00 00  EP210...........
  0020: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  0030: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  0040: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  0050: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  0060: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  0070: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  0080: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  0090: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  00a0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  00b0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  00c0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  00d0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  00e0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  00f0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00     ...............
Quoted 1 line

HCI Event: Link Key Request (0x17) plen 6

0000: 5a a9 15 09 07 20 Z....
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
0000: 5a a9 15 09 07 20 10 ed c2 db ba 8d bf 44 9a de Z.... .......D..
0010: 67 50 10 5a 46 d9 gP.ZF.

Quoted 1 line

HCI Event: Command Complete (0x0e) plen 10

0000: 01 0b 04 00 5a a9 15 09 07 20 ....Z....

Quoted 1 line

ACL data: handle 43 flags 0x02 dlen 12

    L2CAP(s): Connect req: psm 1 scid 0x004a
< ACL data: handle 43 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x004a result 0 status 0
      Connection successful
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 2b 00 01 00 .+...

Quoted 1 line

ACL data: handle 43 flags 0x02 dlen 16

    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
      MTU 48 
< ACL data: handle 43 flags 0x02 dlen 18
    L2CAP(s): Config rsp: scid 0x004a flags 0x00 result 0 clen 4
      MTU 48 
< ACL data: handle 43 flags 0x02 dlen 12
    L2CAP(s): Config req: dcid 0x004a flags 0x00 clen 0
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 2b 00 01 00 .+...

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 2b 00 01 00 .+...

Quoted 1 line

ACL data: handle 43 flags 0x02 dlen 14

    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
      Success
Quoted 1 line

ACL data: handle 43 flags 0x02 dlen 24

    L2CAP(d): cid 0x0040 len 20 [psm 1]
        SDP SSA Req: tid 0x1 len 0xf
          pat uuid-32 0x111f (Handsfree AG)
          max 38
          aid(s) 0x0004 (ProtocolDescList)
          cont 00
< ACL data: handle 43 flags 0x02 dlen 14
    L2CAP(d): cid 0x004a len 10 [psm 1]
        SDP SSA Rsp: tid 0x1 len 0x5
          count 2
          cont 00
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 2b 00 01 00 .+...

Quoted 1 line

ACL data: handle 43 flags 0x02 dlen 12

    L2CAP(s): Disconn req: dcid 0x0040 scid 0x004a
< ACL data: handle 43 flags 0x02 dlen 12
    L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x004a
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 2b 00 01 00 .+...

Quoted 1 line

HCI Event: Disconn Complete (0x05) plen 4

0000: 00 2b 00 13 .+..

Quoted 1 line

HCI Event: Connect Request (0x04) plen 10

0000: 5a a9 15 09 07 20 04 04 20 01 Z.... .. .
< HCI Command: Accept Connection Request (0x01|0x0009) plen 7
0000: 5a a9 15 09 07 20 00 Z.... .

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

0000: 00 01 09 04 ....

Quoted 1 line

HCI Event: Role Change (0x12) plen 8

0000: 00 5a a9 15 09 07 20 00 .Z.... .

Quoted 1 line

HCI Event: Connect Complete (0x03) plen 11

0000: 00 2a 00 5a a9 15 09 07 20 01 00 .*.Z.... ..
< ACL data: handle 42 flags 0x02 dlen 10
L2CAP(s): Info req: type 2
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
0000: 2a 00 *.

Quoted 1 line

HCI Event: Page Scan Repetition Mode Change (0x20) plen 7

0000: 5a a9 15 09 07 20 01 Z.... .

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

0000: 00 01 1b 04 ....
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
0000: 2a 00 0f 00 *...

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 2a 00 01 00 .*...

Quoted 1 line

HCI Event: Command Complete (0x0e) plen 6

0000: 01 0d 08 00 2a 00 ....*.
< HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4
0000: 2a 00 18 cc *...

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

0000: 00 01 0f 04 ....
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
0000: 5a a9 15 09 07 20 02 00 00 00 Z.... ....

Quoted 1 line

HCI Event: Connection Packet Type Changed (0x1d) plen 5

0000: 00 2a 00 1e 33 .*..3

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

0000: 00 01 19 04 ....

Quoted 1 line

ACL data: handle 42 flags 0x02 dlen 16

L2CAP(s): Info rsp: type 2 result 0
Extended feature mask 0x0000

Quoted 1 line

HCI Event: Read Remote Supported Features (0x0b) plen 11

0000: 00 2a 00 fc fe 0f 00 08 08 00 00 .*.........

Quoted 1 line

HCI Event: Remote Name Req Complete (0x07) plen 255

  0000: 00 5a a9 15 09 07 20 53  61 6d 73 75 6e 67 20 57  .Z.... Samsung W
  0010: 45 50 32 31 30 00 00 00  00 00 00 00 00 00 00 00  EP210...........
  0020: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  0030: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  0040: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  0050: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  0060: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  0070: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  0080: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  0090: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  00a0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  00b0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  00c0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  00d0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  00e0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  00f0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00     ...............
Quoted 1 line

HCI Event: Link Key Request (0x17) plen 6

0000: 5a a9 15 09 07 20 Z....
< HCI Command: Link Key Request Reply (0x01|0x000b) plen 22
0000: 5a a9 15 09 07 20 10 ed c2 db ba 8d bf 44 9a de Z.... .......D..
0010: 67 50 10 5a 46 d9 gP.ZF.

Quoted 1 line

HCI Event: Command Complete (0x0e) plen 10

0000: 01 0b 04 00 5a a9 15 09 07 20 ....Z....

Quoted 1 line

ACL data: handle 42 flags 0x02 dlen 12

    L2CAP(s): Connect req: psm 1 scid 0x004b
< ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x004b result 0 status 0
      Connection successful
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 2a 00 01 00 .*...

Quoted 1 line

ACL data: handle 42 flags 0x02 dlen 16

    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
      MTU 48 
< ACL data: handle 42 flags 0x02 dlen 18
    L2CAP(s): Config rsp: scid 0x004b flags 0x00 result 0 clen 4
      MTU 48 
< ACL data: handle 42 flags 0x02 dlen 12
    L2CAP(s): Config req: dcid 0x004b flags 0x00 clen 0
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 2a 00 01 00 .*...

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 2a 00 01 00 .*...

Quoted 1 line

ACL data: handle 42 flags 0x02 dlen 14

    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
      Success
Quoted 1 line

ACL data: handle 42 flags 0x02 dlen 24

    L2CAP(d): cid 0x0040 len 20 [psm 1]
        SDP SSA Req: tid 0x1 len 0xf
          pat uuid-32 0x1112 (Headset AG)
          max 38
          aid(s) 0x0004 (ProtocolDescList)
          cont 00
< ACL data: handle 42 flags 0x02 dlen 33
    L2CAP(d): cid 0x004b len 29 [psm 1]
        SDP SSA Rsp: tid 0x1 len 0x18
          count 21
          record #0
              aid 0x0004 (ProtocolDescList)
                 < < uuid-16 0x0100 (L2CAP) > <
                 uuid-16 0x0003 (RFCOMM) uint 0xc > >
          cont 00
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 2a 00 01 00 .*...

Quoted 1 line

ACL data: handle 42 flags 0x02 dlen 12

    L2CAP(s): Disconn req: dcid 0x0040 scid 0x004b
< ACL data: handle 42 flags 0x02 dlen 12
    L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x004b
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 2a 00 01 00 .*...

Quoted 1 line

ACL data: handle 42 flags 0x02 dlen 12

    L2CAP(s): Connect req: psm 3 scid 0x004c
< ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x004c result 0 status 0
      Connection successful
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 2a 00 01 00 .*...

Quoted 1 line

ACL data: handle 42 flags 0x02 dlen 16

    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
      MTU 132 
< ACL data: handle 42 flags 0x02 dlen 18
    L2CAP(s): Config rsp: scid 0x004c flags 0x00 result 0 clen 4
      MTU 132 
< ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x004c flags 0x00 clen 4
      MTU 1013 
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 2a 00 01 00 .*...

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 2a 00 01 00 .*...

Quoted 1 line

ACL data: handle 42 flags 0x02 dlen 18

    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
      MTU 1013 
Quoted 1 line

ACL data: handle 42 flags 0x02 dlen 8

    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c 
< ACL data: handle 42 flags 0x02 dlen 8
    L2CAP(d): cid 0x004c len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7 
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 2a 00 01 00 .*...

Quoted 1 line

ACL data: handle 42 flags 0x02 dlen 18

L2CAP(d): cid 0x0040 len 14 [psm 3]
RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8 dlci 24 frame_type 0 credit_flow 15 pri 0 ack_timer 0 frame_size 126 max_retrans 0 credits 0
< ACL data: handle 42 flags 0x02 dlen 18
L2CAP(d): cid 0x004c len 14 [psm 3]
RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8 dlci 24 frame_type 0 credit_flow 14 pri 0 ack_timer 0 frame_size 126 max_retrans 0 credits 7

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 2a 00 01 00 .*...

Quoted 1 line

ACL data: handle 42 flags 0x02 dlen 8

    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): SABM: cr 1 dlci 24 pf 1 ilen 0 fcs 0xa2 

< HCI Command: Authentication Requested (0x01|0x0011) plen 2
0000: 2a 00 *.

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

0000: 00 01 11 04 ....

Quoted 1 line

HCI Event: Auth Complete (0x06) plen 3

0000: 00 2a 00 .*.
< HCI Command: Set Connection Encryption (0x01|0x0013) plen 3
0000: 2a 00 01 *..

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

0000: 00 01 13 04 ....

Quoted 1 line

HCI Event: Encrypt Change (0x08) plen 4

0000: 00 2a 00 01 .*..
< ACL data: handle 42 flags 0x02 dlen 8

    L2CAP(d): cid 0x004c len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 24 pf 1 ilen 0 fcs 0x69 
< ACL data: handle 42 flags 0x02 dlen 12
    L2CAP(d): cid 0x004c len 8 [psm 3]
      RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
      dlci 24 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 1 b3 0 len 0
< HCI Command: Change Connection Link Key (0x01|0x0015) plen 2
  0000: 2a 00                                             *.
< ACL data: handle 42 flags 0x02 dlen 8
    L2CAP(d): cid 0x004c len 4 [psm 3]
      RFCOMM(s): DISC: cr 0 dlci 24 pf 1 ilen 0 fcs 0x22 
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 2a 00 01 00 .*...

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 2a 00 01 00 .*...

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 2a 00 01 00 .*...

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

0000: 00 01 15 04 ....

Quoted 1 line

ACL data: handle 42 flags 0x02 dlen 12

    L2CAP(d): cid 0x0040 len 8 [psm 3]
      RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
      dlci 24 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 1 b3 0 len 0
Quoted 1 line

HCI Event: Link Key Notification (0x18) plen 23

0000: 5a a9 15 09 07 20 4d 00 fa df 23 f9 5e 49 93 93 Z.... M...#.^I..
0010: 30 3d e8 c4 0b 55 00 0=...U.

Quoted 1 line

HCI Event: Change Connection Link Key Complete (0x09) plen 3

0000: 00 2a 00 .*.

Quoted 1 line

ACL data: handle 42 flags 0x02 dlen 12

    L2CAP(d): cid 0x0040 len 8 [psm 3]
      RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2
      dlci 24 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 1 len 14
< ACL data: handle 42 flags 0x02 dlen 12
    L2CAP(d): cid 0x004c len 8 [psm 3]
      RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2
      dlci 24 fc 0 rtc 1 rtr 1 ic 0 dv 0 b1 0 b2 0 b3 1 len 14
< ACL data: handle 42 flags 0x02 dlen 9
    L2CAP(d): cid 0x004c len 5 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 24 pf 1 ilen 0 fcs 0xc8 credits 33
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 2a 00 01 00 .*...

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 2a 00 01 00 .*...

Quoted 1 line

ACL data: handle 42 flags 0x02 dlen 9

    L2CAP(d): cid 0x0040 len 5 [psm 3]
      RFCOMM(d): UIH: cr 1 dlci 24 pf 1 ilen 0 fcs 0x12 credits 15
Quoted 1 line

ACL data: handle 42 flags 0x02 dlen 8

    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): UA: cr 0 dlci 24 pf 1 ilen 0 fcs 0x8 
< ACL data: handle 42 flags 0x02 dlen 8
    L2CAP(d): cid 0x004c len 4 [psm 3]
      RFCOMM(s): DISC: cr 0 dlci 0 pf 1 ilen 0 fcs 0x9c 
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 2a 00 01 00 .*...

Quoted 1 line

ACL data: handle 42 flags 0x02 dlen 8

    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): DM: cr 0 dlci 24 pf 1 ilen 0 fcs 0xe9 
Quoted 1 line

ACL data: handle 42 flags 0x02 dlen 8

    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): DM: cr 0 dlci 24 pf 1 ilen 0 fcs 0xe9 
Quoted 1 line

ACL data: handle 42 flags 0x02 dlen 8

    L2CAP(d): cid 0x0040 len 4 [psm 3]
      RFCOMM(s): UA: cr 0 dlci 0 pf 1 ilen 0 fcs 0xb6 
< ACL data: handle 42 flags 0x02 dlen 12
    L2CAP(s): Disconn req: dcid 0x004c scid 0x0040
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 2a 00 01 00 .*...

Quoted 1 line

ACL data: handle 42 flags 0x02 dlen 12

    L2CAP(s): Disconn rsp: dcid 0x004c scid 0x0040

< HCI Command: Disconnect (0x01|0x0006) plen 3
0000: 2a 00 13 *..

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

0000: 00 01 06 04 ....

Quoted 1 line

HCI Event: Disconn Complete (0x05) plen 4

0000: 00 2a 00 16 .*..
< HCI Command: Create Connection (0x01|0x0005) plen 13
0000: 5a a9 15 09 07 20 18 cc 02 00 00 00 01 Z.... .......

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

0000: 00 01 05 04 ....

Quoted 1 line

HCI Event: Connect Complete (0x03) plen 11

0000: 00 2c 00 5a a9 15 09 07 20 01 00 .,.Z.... ..
< ACL data: handle 44 flags 0x02 dlen 10
L2CAP(s): Info req: type 2
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
0000: 2c 00 ,.

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 2c 00 01 00 .,...

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

0000: 00 01 1b 04 ....
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
0000: 2c 00 0f 00 ,...

Quoted 1 line

HCI Event: Page Scan Repetition Mode Change (0x20) plen 7

0000: 5a a9 15 09 07 20 01 Z.... .

Quoted 1 line

HCI Event: Command Complete (0x0e) plen 6

0000: 01 0d 08 00 2c 00 ....,.
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
0000: 5a a9 15 09 07 20 02 00 00 00 Z.... ....

Quoted 1 line

HCI Event: Read Remote Supported Features (0x0b) plen 11

0000: 00 2c 00 fc fe 0f 00 08 08 00 00 .,.........

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

0000: 00 01 19 04 ....

Quoted 1 line

ACL data: handle 44 flags 0x02 dlen 16

L2CAP(s): Info rsp: type 2 result 0
Extended feature mask 0x0000
< ACL data: handle 44 flags 0x02 dlen 12

    L2CAP(s): Connect req: psm 1 scid 0x0040
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 2c 00 01 00 .,...

Quoted 1 line

ACL data: handle 44 flags 0x02 dlen 16

L2CAP(s): Connect rsp: dcid 0x004d scid 0x0040 result 1 status 2
Connection pending - Authorization pending

Quoted 1 line

ACL data: handle 44 flags 0x02 dlen 16

    L2CAP(s): Connect rsp: dcid 0x004d scid 0x0040 result 0 status 0
      Connection successful
< ACL data: handle 44 flags 0x02 dlen 12
    L2CAP(s): Config req: dcid 0x004d flags 0x00 clen 0
Quoted 1 line

HCI Event: Remote Name Req Complete (0x07) plen 255

  0000: 00 5a a9 15 09 07 20 53  61 6d 73 75 6e 67 20 57  .Z.... Samsung W
  0010: 45 50 32 31 30 00 00 00  00 00 00 00 00 00 00 00  EP210...........
  0020: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  0030: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  0040: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  0050: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  0060: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  0070: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  0080: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  0090: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  00a0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  00b0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  00c0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  00d0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  00e0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
  00f0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00     ...............
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 2c 00 01 00 .,...

Quoted 1 line

ACL data: handle 44 flags 0x02 dlen 14

    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
      Success
Quoted 1 line

ACL data: handle 44 flags 0x02 dlen 16

    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
      MTU 48 
< ACL data: handle 44 flags 0x02 dlen 18
    L2CAP(s): Config rsp: scid 0x004d flags 0x00 result 0 clen 4
      MTU 48 
< ACL data: handle 44 flags 0x02 dlen 17
    L2CAP(d): cid 0x004d len 13 [psm 1]
        SDP SS Req: tid 0x0 len 0x8
          pat uuid-16 0x1108 (Headset)
          max 64
          cont 00
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 2c 00 01 00 .,...

Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 2c 00 01 00 .,...

Quoted 1 line

ACL data: handle 44 flags 0x02 dlen 14

    L2CAP(d): cid 0x0040 len 10 [psm 1]
        SDP SS Rsp: tid 0x0 len 0x5
          count 0
          cont 00
< ACL data: handle 44 flags 0x02 dlen 12
    L2CAP(s): Disconn req: dcid 0x004d scid 0x0040
Quoted 1 line

HCI Event: Number of Completed Packets (0x13) plen 5

0000: 01 2c 00 01 00 .,...

Quoted 1 line

ACL data: handle 44 flags 0x02 dlen 12

    L2CAP(s): Disconn rsp: dcid 0x004d scid 0x0040

< HCI Command: Disconnect (0x01|0x0006) plen 3
0000: 2c 00 13 ,..

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

0000: 00 01 06 04 ....

Quoted 1 line

HCI Event: Disconn Complete (0x05) plen 4

0000: 00 2c 00 16 .,..

#!/bin/bash

http://gentoo-wiki.com/HOWTO_use_a_bluetooth_headset
http://www.wahlau.org/failed_getting_bluetooth_headset_to_work_with_ubuntu_edgy_eft
http://www.think-future.de/wiki/index.php?title=Bluetooth

sudo cp /etc/bluetooth/audio.conf /etc/bluetooth/audio.conf.backup sudo mv /etc/bluetooth/audio.conf.backup /etc/bluetooth/audio.conf

cp $HOME/.asoundrc $HOME/.asoundrc.backup

# step 1: install bluetooth alsa software
sudo apt-get install bluetooth-alsa bluez-utils
# step 2: enable bluetooth alsa service

echo '[Bluetooth Service]
Identifier=audio
Name=Audio service
Description=Bluetooth Audio service Autostart=true' | sudo tee /etc/bluetooth/audio.conf

echo '[Bluetooth Service]
Identifier=audio
Name=Audio service
Description=Bluetooth Audio service Autostart=true' | sudo tee /etc/bluetooth/audio.service

cat /etc/bluetooth/audio.service

cat /etc/bluetooth/audio.conf

hcitool scan
20:07:09:15:A9:5A
sudo sdptool browse 20:07:09:15:A9:5A

sudo sdptool search HS
Inquiring ...
Searching for HS on 20:07:09:15:A9:5A ...
Service Name: Headset
Service RecHandle: 0x10001
Service Class ID List:
"Headset" (0x1108)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 2
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Headset" (0x1108)

    Version: 0x0100

echo 'pcm.bluetooth {
type bluetooth
device 20:07:09:15:A9:5A
profile "auto"
}' | tee --append $HOME/.asoundrc

sudo hcitool cc 20:07:09:15:A9:5A

cat $HOME/.asoundrc

sudo /etc/init.d/bluetooth restart
sudo /etc/init.d/alsa-utils restart

sudo apt-get install mplayer

mplayer -ao alsa:device=bluetooth test.mp3
arecord -D bluetooth -f S16_LE | aplay -D bluetooth -f S16_LE

sudo modprobe snd-bt-sco
dbus-send --system --dest=org.bluez /org/bluez/hci0 org.bluez.Adapter.SetMode string:discoverable btsco -v 20:07:09:15:A9:5A
sudo a2dpd

pcm.bluetooth {
    type plug
    slave {
       pcm "bluetooth_hw"
    }
}
pcm.bluetooth_hw {
    type bluetooth
    device 00:0B:2E:5B:30:E6
}

sudo hidd --connect 20:07:09:15:A9:5A
sudo l2ping 20:07:09:15:A9:5A

passkey-agent 0000 20:07:09:15:A9:5A

echo 0000 | sudo tee /etc/bluetooth/pin

sdptool search 20:07:09:15:A9:5A
hcitool cc 20:07:09:15:A9:5A
sudo /etc/init.d/syslog restart

sudo /etc/init.d/sysklogd start
sudo /etc/init.d/klogd start

sudo cat /var/log/syslog

sudo vim /etc/bluetooth/hcid.conf
pin_helper /etc/bluetooth/feed-pin.sh;

echo '#!/bin/sh
echo "PIN:0000"' | sudo tee /etc/bluetooth/feed-pin.sh

Apr 19 00:56:29 debian-eeepc hcid[5705]: Audio API: received BT_GETCAPABILITIES_REQ
Apr 19 00:56:29 debian-eeepc hcid[5705]: Audio API: sending BT_GETCAPABILITIES_RSP
Apr 19 00:56:29 debian-eeepc hcid[5705]: Audio API: received BT_SETCONFIGURATION_REQ
Apr 19 00:56:29 debian-eeepc hcid[5705]: config sco - device = 20:07:09:15:A9:5A access_mode = 2
Apr 19 00:56:32 debian-eeepc hcid[5705]: pin_code_request (sba=00:1B:DC:00:32:71, dba=20:07:09:15:A9:5A)
Apr 19 00:56:32 debian-eeepc hcid[5705]: connect(): Connection refused (111)
Apr 19 00:56:32 debian-eeepc hcid[5705]: config failed
Apr 19 00:56:32 debian-eeepc hcid[5705]: Audio API: sending BT_SETCONFIGURATION_RSP

Package: bluez-utils
Version: 3.30-2

dbus-send --system --type=method_call --print-reply --dest=":1.20" \
/org/bluez/audio org.bluez.audio.Manager.CreateDevice string:20:07:09:15:A9:5A

dbus-send --system --type=method_call --print-reply --dest=":1.20" \
"/org/bluez/audio/device0" org.bluez.audio.Sink.Connect

sudo python simple-agent
Agent registered
RequestPasskey (/hci0/dev_20_07_09_15_A9_5A)

Apr 19 01:24:29 debian-eeepc hcid[2353]: Audio API: received BT_GETCAPABILITIES_REQ
Apr 19 01:24:29 debian-eeepc hcid[2353]: Audio API: sending BT_GETCAPABILITIES_RSP
Apr 19 01:24:29 debian-eeepc hcid[2353]: Audio API: received BT_SETCONFIGURATION_REQ
Apr 19 01:24:29 debian-eeepc hcid[2353]: config sco - device = 20:07:09:15:A9:5A access_mode = 2
Apr 19 01:24:33 debian-eeepc hcid[2353]: link_key_request (sba=00:1B:DC:00:32:71, dba=20:07:09:15:A9:5A)
Apr 19 01:24:36 debian-eeepc kernel: usb 1-2: USB disconnect, address 4
Apr 19 01:24:36 debian-eeepc hcid[2353]: HCI dev 0 down
Apr 19 01:24:36 debian-eeepc hcid[2353]: Stopping security manager 0
Apr 19 01:24:36 debian-eeepc hcid[2353]: Device hci0 has been disabled
Apr 19 01:24:36 debian-eeepc hcid[2353]: connect(): Software caused connection abort (103)
Apr 19 01:24:36 debian-eeepc hcid[2353]: config failed
Apr 19 01:24:36 debian-eeepc hcid[2353]: Audio API: sending BT_SETCONFIGURATION_RSP
Apr 19 01:24:37 debian-eeepc hcid[2353]: HCI dev 0 unregistered
Apr 19 01:24:37 debian-eeepc hcid[2353]: Unregister path: /org/bluez/hci0
Apr 19 01:24:37 debian-eeepc hcid[2353]: Device hci0 has been removed
Apr 19 01:24:37 debian-eeepc kernel: usb 1-2: new full speed USB device using uhci_hcd and address 5
Apr 19 01:24:37 debian-eeepc kernel: usb 1-2: configuration #1 chosen from 1 choice

#!/usr/bin/python

import gobject

import dbus
import dbus.service
import dbus.mainloop.glib

class Agent(dbus.service.Object):

	@dbus.service.method("org.bluez.Agent",
					in_signature="", out_signature="")
	def Release(self):
		print "Release"
		mainloop.quit()

	@dbus.service.method("org.bluez.Agent",
					in_signature="os", out_signature="")
	def Authorize(self, device, uuid):
		print "Authorize (" + device + ", " + uuid + ")"
		return

	@dbus.service.method("org.bluez.Agent",
					in_signature="o", out_signature="s")
	def RequestPasskey(self, device):
		print "RequestPasskey (" + device + ")"
		return "0000"

	@dbus.service.method("org.bluez.Agent",
					in_signature="s", out_signature="")
	def ConfirmModeChange(self, mode):
		print "ConfirmModeChange (" + mode + ")"
		return

	@dbus.service.method("org.bluez.Agent",
					in_signature="", out_signature="")
	def Cancel(self):
		print "Cancel"
		return

if __name__ == '__main__':
dbus.mainloop.glib.DBusGMainLoop(set_as_default=True)

bus = dbus.SystemBus()
manager = dbus.Interface(bus.get_object("org.bluez", "/"),
"org.bluez.Manager")

path = manager.DefaultAdapter()
adapter = dbus.Interface(bus.get_object("org.bluez", path),
"org.bluez.Adapter")

path = "/test/agent"
object = Agent(bus, path)

adapter.RegisterAgent(path)
print "Agent registered"

mainloop = gobject.MainLoop()
mainloop.run()

#adapter.UnregisterAgent(path)
#print "Agent unregistered"

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

#2 lore raw

On Sat, 19 Apr 2008, Jelle de Jong wrote:

-> > This message contains the following attachment(s):
-> > Samsung WEP210 Bluetooth Headset.txt
-> > simple-agent

Looks like you have alot of obsolete and unneeded steps in there.

-> > I bought a new headset and am trying to get it working under debian sid -> > 3.30-2 bluez-utils
-> >
-> > However i cant connect to the device when it is in pairing mode.

I can't connect to mine either without it disconnecting, but it connects to the computer when a sound is to be played. I'm guessing this is just how they work.

-> > I have attached my working files with a lot of background information. -> >
-> > Can somebody help me to get the device working.

Getting headsets going is a frequent topic on this list, so you might try looking at a past solution first, to see if it helps, before starting from the beginning trying to solve this problem. Here's one I posted when I was first using mine:

http://sourceforge.net/mailarchive/forum.php?thread_name=alpine.LNX.1.00.0802052112140.20192%40nge2.ngu.pk&forum_name=bluez-users

There's alot of headset-talk, particularly in the Feb. 2008 part of the archive.

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

#3 lore raw
Quoted 20 lines · jayjwa

On Sat, 19 Apr 2008, Jelle de Jong wrote:

-> > This message contains the following attachment(s):
-> > Samsung WEP210 Bluetooth Headset.txt
-> > simple-agent

Looks like you have alot of obsolete and unneeded steps in there.

-> > I bought a new headset and am trying to get it working under debian sid -> > 3.30-2 bluez-utils
-> >
-> > However i cant connect to the device when it is in pairing mode.

I can't connect to mine either without it disconnecting, but it connects to the computer when a sound is to be played. I'm guessing this is just how they work.

-> > I have attached my working files with a lot of background information. -> >
-> > Can somebody help me to get the device working.

Quoted 7 lines

Getting headsets going is a frequent topic on this list, so you might try looking at a past solution first, to see if it helps, before starting from the beginning trying to solve this problem. Here's one I posted when I was first using mine:

http://sourceforge.net/mailarchive/forum.php?thread_name=alpine.LNX.1.00.0802052112140.20192%40nge2.ngu.pk&forum_name=bluez-users

There's alot of headset-talk, particularly in the Feb. 2008 part of the archive.

Thank you,

So, I tried to get it working for a other 4 hours, but I can't get it to work. Please help me, how can I get the device fully working, what am I doing wrong here?

Please take a look at the logs i attached in the mail, i hope this gives enough information for a advanced bluez users to tell me what is wrong.

Kind regards,

Jelle

snapshot of my syslog >>

Apr 19 21:55:55 debian-eeepc hcid[2330]: Bluetooth HCI daemon
Apr 19 21:55:55 debian-eeepc hcid[2330]: HCI dev 0 registered
Apr 19 21:55:55 debian-eeepc hcid[2330]: Starting SDP server
Apr 19 21:55:55 debian-eeepc hcid[2330]: Unix socket created: 12
Apr 19 21:55:55 debian-eeepc hidd[2333]: Bluetooth HID daemon
Apr 19 21:55:55 debian-eeepc hcid[2330]: Registered manager
path:/org/bluez/audio
Apr 19 21:55:55 debian-eeepc hcid[2330]: Registering service
Apr 19 21:55:55 debian-eeepc hcid[2330]: Unable to execute
/usr/lib/bluetooth/bluetoothd-service-audio
Apr 19 21:55:55 debian-eeepc hcid[2330]: HCI dev 0 up
Apr 19 21:55:55 debian-eeepc hcid[2330]: Device hci0 has been added
Apr 19 21:55:55 debian-eeepc hcid[2330]: Starting security manager 0
Apr 19 21:55:55 debian-eeepc hcid[2330]: Device hci0 has been activated
Apr 19 21:56:53 debian-eeepc hcid[2330]: link_key_request
(sba=00:1B:DC:00:32:71, dba=20:07:09:15:A9:5A)
Apr 19 21:56:55 debian-eeepc hcid[2330]: pin_code_request
(sba=00:1B:DC:00:32:71, dba=20:07:09:15:A9:5A)
Apr 19 21:56:55 debian-eeepc hcid[2330]: link_key_notify
(sba=00:1B:DC:00:32:71, dba=20:07:09:15:A9:5A)
Apr 19 21:56:57 debian-eeepc hcid[2330]: link_key_request
(sba=00:1B:DC:00:32:71, dba=20:07:09:15:A9:5A)
Apr 19 21:56:58 debian-eeepc hcid[2330]: Access denied: Not authorized
Apr 19 21:56:59 debian-eeepc hcid[2330]: link_key_notify
(sba=00:1B:DC:00:32:71, dba=20:07:09:15:A9:5A)
Apr 19 21:57:18 debian-eeepc hcid[2330]: Audio API: received
BT_GETCAPABILITIES_REQ
Apr 19 21:57:18 debian-eeepc hcid[2330]: Audio API: sending
BT_GETCAPABILITIES_RSP
Apr 19 21:57:18 debian-eeepc hcid[2330]: Audio API: received
BT_SETCONFIGURATION_REQ
Apr 19 21:57:18 debian-eeepc hcid[2330]: config sco - device =
20:07:09:15:A9:5A access_mode = 2
Apr 19 21:57:20 debian-eeepc hcid[2330]: link_key_request
(sba=00:1B:DC:00:32:71, dba=20:07:09:15:A9:5A)
Apr 19 21:57:22 debian-eeepc kernel: Bluetooth: SCO (Voice Link) ver 0.5
Apr 19 21:57:22 debian-eeepc kernel: Bluetooth: SCO socket layer initialized
Apr 19 21:57:24 debian-eeepc kernel: hci_scodata_packet: hci0 SCO packet
for unknown connection handle 43
Apr 19 21:57:55 debian-eeepc last message repeated 10158 times
Apr 19 21:58:02 debian-eeepc last message repeated 2576 times
Apr 19 21:58:02 debian-eeepc hcid[2330]: connect(): Connection timed out
(110)
Apr 19 21:58:02 debian-eeepc hcid[2330]: config failed
Apr 19 21:58:02 debian-eeepc hcid[2330]: Audio API: sending
BT_SETCONFIGURATION_RSP
Apr 19 21:58:02 debian-eeepc kernel: hci_scodata_packet: hci0 SCO packet
for unknown connection handle 43
Apr 19 21:58:33 debian-eeepc last message repeated 10090 times
Apr 19 21:59:23 debian-eeepc last message repeated 16726 times
Apr 19 21:59:23 debian-eeepc hcid[2330]: Audio API: received
BT_GETCAPABILITIES_REQ
Apr 19 21:59:23 debian-eeepc hcid[2330]: Audio API: sending
BT_GETCAPABILITIES_RSP
Apr 19 21:59:23 debian-eeepc kernel: hci_scodata_packet: hci0 SCO packet
for unknown connection handle 43
Apr 19 21:59:23 debian-eeepc last message repeated 2 times
Apr 19 21:59:23 debian-eeepc hcid[2330]: Audio API: received
BT_SETCONFIGURATION_REQ
Apr 19 21:59:23 debian-eeepc hcid[2330]: config sco - device =
20:07:09:15:A9:5A access_mode = 2
Apr 19 21:59:23 debian-eeepc kernel: hci_scodata_packet: hci0 SCO packet
for unknown connection handle 43
Apr 19 21:59:54 debian-eeepc last message repeated 10270 times
Apr 19 22:00:03 debian-eeepc last message repeated 3062 times
Apr 19 22:00:03 debian-eeepc hcid[2330]: connect(): Connection timed out
(110)
Apr 19 22:00:03 debian-eeepc hcid[2330]: config failed
Apr 19 22:00:03 debian-eeepc hcid[2330]: Audio API: sending
BT_SETCONFIGURATION_RSP
Apr 19 22:00:03 debian-eeepc kernel: hci_scodata_packet: hci0 SCO packet

for unknown connection handle 43

#!/bin/bash

# background information:
http://gentoo-wiki.com/HOWTO_use_a_bluetooth_headset
http://www.wahlau.org/failed_getting_bluetooth_headset_to_work_with_ubuntu_edgy_eft
http://www.think-future.de/wiki/index.php?title=Bluetooth
http://sourceforge.net/mailarchive/forum.php?thread_name=alpine.LNX.1.00.0802052112140.20192%40nge2.ngu.pk&forum_name=bluez-users
# step 1: install bluetooth alsa software
sudo apt-get install bluetooth-alsa bluez-utils

sudo /etc/init.d/bluetooth stop
sudo /etc/init.d/alsa-utils stop
echo | sudo tee /var/log/syslog
sudo rm --recursive /var/lib/bluetooth/*

sudo modprobe --remove hci_usb
sudo modprobe hci_usb force_scofix=1

# system information:
cd $HOME
apt-cache show bluez-utils > bluez-utils-version-log.txt
lsmod > $HOME/lsmod-log.txt
# step 2: enable bluetooth audio service
sudo cp /etc/bluetooth/audio.service /etc/bluetooth/audio.service.backup
#~ sudo mv /etc/bluetooth/audio.service.backup /etc/bluetooth/audio.service

echo '[Bluetooth Service]
Identifier=audio
Name=Audio service
Description=Bluetooth Audio service Autostart=true' | sudo tee /etc/bluetooth/audio.service

sudo cat /etc/bluetooth/audio.service
sudo cp /etc/bluetooth/audio.service $HOME/audio.service

# step 3:
sudo cp /etc/bluetooth/audio.conf /etc/bluetooth/audio.conf.backup
#~ sudo mv /etc/bluetooth/audio.conf.backup /etc/bluetooth/audio.conf

echo '[General]
SCORouting=HCI
[Headset]
DisableHFP=false' | sudo tee /etc/bluetooth/audio.conf

sudo cat /etc/bluetooth/audio.conf
sudo cp /etc/bluetooth/audio.conf $HOME/audio.conf

# step 4:
cp $HOME/.asoundrc $HOME/.asoundrc.backup
echo 'pcm.bluetooth {
    type plug
    slave {
       pcm "bluetooth_hardware"
    }
}

pcm.bluetooth_hardware {
type bluetooth
device 20:07:09:15:A9:5A
# profile "auto"
}' | tee $HOME/.asoundrc

sudo cp $HOME/.asoundrc $HOME/asoundrc

# step 5:
sudo cp /etc/bluetooth/hcid.conf /etc/bluetooth/hcid.conf.backup
echo 'options {
    autoinit yes;
    security user;
    pairing multi;
    passkey "0000";
}
device {
    name "[%h] / BT Device %d";
    class 0x020108;
    pkt_type DH1,DM1,HV1;
    iscan enable; pscan enable;
    lm accept;
    lp rswitch,hold,sniff,park;
}' | sudo tee /etc/bluetooth/hcid.conf

cat /etc/bluetooth/hcid.conf
sudo cp /etc/bluetooth/hcid.conf $HOME/hcid.conf

echo 0000 | sudo tee /etc/bluetooth/pin
sudo cp /etc/bluetooth/pin $HOME/pin

sudo hcidump -X > $HOME/hcidump.txt

sudo /etc/init.d/sysklogd start
sudo /etc/init.d/klogd start
sudo /etc/init.d/bluetooth restart
sudo /etc/init.d/alsa-utils restart
sudo python simple-agent 2> $HOME/simple-agent-log.txt

sudo tail --lines=100 --follow /var/log/syslog

sudo cp /var/log/syslog $HOME/syslog

sudo apt-get install mplayer
mplayer -ao alsa:device=bluetooth test.mp3
arecord -D bluetooth -f S16_LE | aplay -D bluetooth -f S16_LE

hcitool scan
20:07:09:15:A9:5A
sudo sdptool browse 20:07:09:15:A9:5A
sudo sdptool search HS > sptool-search-hs-log.txt
hcitool con > hcitool-con-log.txt
sudo hcitool cc 20:07:09:15:A9:5A
sdptool search 20:07:09:15:A9:5A
hcitool cc 20:07:09:15:A9:5A
ls -hal /var/lib/bluetooth/

# note: why is this not avalible in debian sid
passkey-agent 0000 20:07:09:15:A9:5A

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

#4 lore raw

On Sat, 19 Apr 2008, Jelle de Jong wrote:

-> So, I tried to get it working for a other 4 hours, but I can't get it to -> work. Please help me, how can I get the device fully working, what am I -> doing wrong here?
-> -> Please take a look at the logs i attached in the mail, i hope this gives -> enough information for a advanced bluez users to tell me what is wrong.

Several things stand out.

1.)

First is your kernel version. Seems to be a 2.5.24.x. If you are using an SCO-only headset, the 2.6.24.x kernels will not work with it. You must either patch the kernel, or upgrade to an ESCO-able headset. This is the issue with mine. I use the patch that was on this list to patch my 2.6.24.4. The device's features should mention eSCO.

-> snapshot of my syslog >>
-> Apr 19 21:55:55 debian-eeepc hcid[2330]: Bluetooth HCI daemon -> Apr 19 21:55:55 debian-eeepc hcid[2330]: HCI dev 0 registered -> Apr 19 21:55:55 debian-eeepc hcid[2330]: Starting SDP server -> Apr 19 21:55:55 debian-eeepc hcid[2330]: Unix socket created: 12 -> Apr 19 21:55:55 debian-eeepc hidd[2333]: Bluetooth HID daemon -> Apr 19 21:55:55 debian-eeepc hcid[2330]: Registered manager -> path:/org/bluez/audio
-> Apr 19 21:55:55 debian-eeepc hcid[2330]: Registering service -> Apr 19 21:55:55 debian-eeepc hcid[2330]: Unable to execute -> /usr/lib/bluetooth/bluetoothd-service-audio

2). The file, and format of those files above is not used anymore. Now, the audio service is a plugin: /usr/lib/bluetooth/plugins/libaudio.so There are no more *.service files in /etc/bluetooth like audio.service.

-> Apr 19 21:55:55 debian-eeepc hcid[2330]: HCI dev 0 up
-> Apr 19 21:55:55 debian-eeepc hcid[2330]: Device hci0 has been added -> Apr 19 21:55:55 debian-eeepc hcid[2330]: Starting security manager 0 -> Apr 19 21:55:55 debian-eeepc hcid[2330]: Device hci0 has been activated -> Apr 19 21:56:53 debian-eeepc hcid[2330]: link_key_request -> (sba=00:1B:DC:00:32:71, dba=20:07:09:15:A9:5A)
-> Apr 19 21:56:55 debian-eeepc hcid[2330]: pin_code_request -> (sba=00:1B:DC:00:32:71, dba=20:07:09:15:A9:5A)
-> Apr 19 21:56:55 debian-eeepc hcid[2330]: link_key_notify
-> (sba=00:1B:DC:00:32:71, dba=20:07:09:15:A9:5A)
-> Apr 19 21:56:57 debian-eeepc hcid[2330]: link_key_request -> (sba=00:1B:DC:00:32:71, dba=20:07:09:15:A9:5A)
-> Apr 19 21:56:58 debian-eeepc hcid[2330]: Access denied: Not authorized

3.) The pin setup you used I think is old, too. The users on this list seem to use some graphical utility, but myself I've always just used auth-agent and passkey-agent from the bluez-utils src tarball.

passkey-agent --default (pin number) (remote device address) & auth-agent &

-> Apr 19 21:56:59 debian-eeepc hcid[2330]: link_key_notify
-> (sba=00:1B:DC:00:32:71, dba=20:07:09:15:A9:5A)
-> Apr 19 21:57:18 debian-eeepc hcid[2330]: Audio API: received
-> BT_GETCAPABILITIES_REQ
-> Apr 19 21:57:18 debian-eeepc hcid[2330]: Audio API: sending
-> BT_GETCAPABILITIES_RSP
-> Apr 19 21:57:18 debian-eeepc hcid[2330]: Audio API: received
-> BT_SETCONFIGURATION_REQ
-> Apr 19 21:57:18 debian-eeepc hcid[2330]: config sco - device = -> 20:07:09:15:A9:5A access_mode = 2
-> Apr 19 21:57:20 debian-eeepc hcid[2330]: link_key_request
-> (sba=00:1B:DC:00:32:71, dba=20:07:09:15:A9:5A)
-> Apr 19 21:57:22 debian-eeepc kernel: Bluetooth: SCO (Voice Link) ver 0.5 -> Apr 19 21:57:22 debian-eeepc kernel: Bluetooth: SCO socket layer initialized -> Apr 19 21:57:24 debian-eeepc kernel: hci_scodata_packet: hci0 SCO packet -> for unknown connection handle 43
-> Apr 19 21:57:55 debian-eeepc last message repeated 10158 times -> Apr 19 21:58:02 debian-eeepc last message repeated 2576 times -> Apr 19 21:58:02 debian-eeepc hcid[2330]: connect(): Connection timed out

Here...

-> Apr 19 21:58:02 debian-eeepc hcid[2330]: config failed
-> Apr 19 21:58:02 debian-eeepc hcid[2330]: Audio API: sending -> BT_SETCONFIGURATION_RSP
-> Apr 19 21:58:02 debian-eeepc kernel: hci_scodata_packet: hci0 SCO packet -> for unknown connection handle 43
-> Apr 19 21:58:33 debian-eeepc last message repeated 10090 times -> Apr 19 21:59:23 debian-eeepc last message repeated 16726 times

...and here, look like the message I used to get about the SCO/eSCO problem with 2.6.24 kernels. I'm not 100% sure that's what this is, but it looks similar.

I'll attach setup info and the previously posted esco patch, if you find you do need it. Other than these things mentioned here, I'm not sure what the problem could be.

bluez-firmware-1.2
bluez-hcidump-1.41
bluez-libs-3.30
bluez-utils-3.30

# tree -a /usr/lib/bluetooth                               
/usr/lib/bluetooth
`-- plugins
    |-- libaudio.so
    |-- libinput.so
    |-- libnetwork.so
    `-- libserial.so

1 directory, 4 files

# tree -a /etc/bluetooth                                   
/etc/bluetooth
|-- audio.conf
|-- hcid.conf
|-- ifdown-pan0
|-- ifup-pan0
|-- init-pan0
|-- network.conf
|-- panu-client
`-- rfcomm.conf

0 directories, 8 files

## Alsa Sound Config
##
## Extra configurations for Alsa
## (/etc/asound.conf)
##

pcm.oss {
type oss
device /dev/dsp
}

pcm.bluetooth {
        type bluetooth
        device "00:1A:45:01:F9:42"
}
pcm.bt_slave {
        type plug
        slave {
                pcm "bluetooth"
        }
}
# /etc/bluetooth/hcid.conf                         
#
# HCI daemon configuration file.
#

# HCId options
options {
# Automatically initialize new devices
autoinit yes;

# Security Manager mode
# none - Security manager disabled
# auto - Use local PIN for incoming connections
# user - Always ask user for a PIN
#
security user;

# Pairing mode
# none - Pairing disabled
# multi - Allow pairing with already paired devices
# once - Pair once and deny successive attempts
pairing multi;
}

# Default settings for HCI devices
device {
# Local device name
# %d - device id
# %h - host name
name "[%h] / BT Device %d";

# Local device class (see hcid.conf manpage) # 0x000100 = Computer, unspec.
# 0x020100 = Networking Computer, unspec. class 0x020108;

# Default packet type
pkt_type DH1,DM1,HV1;

# Inquiry and Page scan
iscan enable; pscan enable;

# Default link mode
# none - no specific policy
# accept - always accept incoming connections
# master - become master on incoming connections,
# deny role switch on outgoing connections
lm accept;

# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
lp rswitch,hold,sniff,park;

}

# hcitool scan

Scanning ...

        00:1A:45:01:F9:42       Jabra BT135
# passkey-agent --default 0000 00:1A:45:01:F9:42 &

[1] 4569
# auth-agent&

[2] 4570

# hcitool info 00:1A:45:01:F9:42

Requesting information ...
BD Address: 00:1A:45:01:F9:42
LMP Version: 2.0 (0x3) LMP Subversion: 0xbfa
Manufacturer: Cambridge Silicon Radio (10)
Features: 0xfc 0xfe 0x0b 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> <transparent SCO> <AFH cap. slave> <AFH cap. master>

(No eSCO mentioned above, only <SCO link> and <transparent SCO> )

Apr 20 16:40:12 atr2 kernel: usb 1-1: new full speed USB device using
uhci_hcd and address 3
Apr 20 16:40:12 atr2 kernel: usb 1-1: configuration #1 chosen from 1 choice
Apr 20 16:40:19 atr2 hcid[4524]: Bluetooth HCI daemon
Apr 20 16:40:20 atr2 hcid[4524]: HCI dev 0 registered
Apr 20 16:40:20 atr2 hcid[4524]: Starting SDP server
Apr 20 16:40:20 atr2 hcid[4524]: Creation of inotify context failed
Apr 20 16:40:20 atr2 kernel: pan0: Dropping NETIF_F_UFO since no
NETIF_F_HW_CSUM feature.
Apr 20 16:40:20 atr2 hcid[4524]: Registered manager path:/org/bluez/network
Apr 20 16:40:20 atr2 hcid[4524]: Registered server
path:/org/bluez/network/nap
Apr 20 16:40:20 atr2 hcid[4524]: Registered server
path:/org/bluez/network/gn
Apr 20 16:40:20 atr2 hcid[4524]: Registered server
path:/org/bluez/network/panu
Apr 20 16:40:20 atr2 hcid[4524]: Registering service
Apr 20 16:40:20 atr2 hcid[4524]: Registered manager path:/org/bluez/serial
Apr 20 16:40:20 atr2 hcid[4524]: Registering service
Apr 20 16:40:20 atr2 hcid[4524]: Registered input manager
path:/org/bluez/input
Apr 20 16:40:20 atr2 hcid[4524]: Registering service
Apr 20 16:40:20 atr2 hcid[4524]: Unix socket created: 17
Apr 20 16:40:20 atr2 hcid[4524]: Registered manager path:/org/bluez/audio
Apr 20 16:40:20 atr2 hcid[4524]: Registering service
Apr 20 16:40:20 atr2 hcid[4524]: HCI dev 0 up
Apr 20 16:40:20 atr2 hcid[4524]: Device hci0 has been added
Apr 20 16:40:20 atr2 hcid[4524]: Starting security manager 0
Apr 20 16:40:20 atr2 hcid[4524]: Device hci0 has been activated
Apr 20 19:35:17 atr2 hcid[4524]: Default passkey agent (:1.1,/org/bluez/passkey_agent_4569) registered
Apr 20 19:35:22 atr2 hcid[4524]: Default authorization agent (:1.2,//org/bluez/auth_agent_4570) registered

(Maybe depress the headset button, listen for the beep
that says it's connected to the computer, if your headset works like this.)

sox -t mp3 /some/file.mp3 -t alsa pcm.bluetooth

I noticed on my no-soundcard system this wouldn't work. Both systems have the same setup, but only the one with the soundcard works for bluetooth audio. Seems like it would work for both, as they both have Alsa. On the no-soundcard machine I used the dummy card driver but it didn't make any difference for bluetooth. Regular sound output did work to the dummy driver (looks like sound is playing, but no sound due to no real card).

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

#5 lore raw
Quoted 91 lines · jayjwa

On Sat, 19 Apr 2008, Jelle de Jong wrote:

-> So, I tried to get it working for a other 4 hours, but I can't get it to -> work. Please help me, how can I get the device fully working, what am I -> doing wrong here?
-> -> Please take a look at the logs i attached in the mail, i hope this gives
-> enough information for a advanced bluez users to tell me what is wrong.

Several things stand out.

1.)

First is your kernel version. Seems to be a 2.5.24.x. If you are using an SCO-only headset, the 2.6.24.x kernels will not work with it. You must either patch the kernel, or upgrade to an ESCO-able headset. This is the issue with mine. I use the patch that was on this list to patch my 2.6.24.4. The device's features should mention eSCO.

-> snapshot of my syslog >>
-> Apr 19 21:55:55 debian-eeepc hcid[2330]: Bluetooth HCI daemon -> Apr 19 21:55:55 debian-eeepc hcid[2330]: HCI dev 0 registered -> Apr 19 21:55:55 debian-eeepc hcid[2330]: Starting SDP server -> Apr 19 21:55:55 debian-eeepc hcid[2330]: Unix socket created: 12 -> Apr 19 21:55:55 debian-eeepc hidd[2333]: Bluetooth HID daemon -> Apr 19 21:55:55 debian-eeepc hcid[2330]: Registered manager -> path:/org/bluez/audio
-> Apr 19 21:55:55 debian-eeepc hcid[2330]: Registering service -> Apr 19 21:55:55 debian-eeepc hcid[2330]: Unable to execute -> /usr/lib/bluetooth/bluetoothd-service-audio

2). The file, and format of those files above is not used anymore. Now, the audio service is a plugin: /usr/lib/bluetooth/plugins/libaudio.so There are no more *.service files in /etc/bluetooth like audio.service.

-> Apr 19 21:55:55 debian-eeepc hcid[2330]: HCI dev 0 up
-> Apr 19 21:55:55 debian-eeepc hcid[2330]: Device hci0 has been added -> Apr 19 21:55:55 debian-eeepc hcid[2330]: Starting security manager 0 -> Apr 19 21:55:55 debian-eeepc hcid[2330]: Device hci0 has been activated -> Apr 19 21:56:53 debian-eeepc hcid[2330]: link_key_request -> (sba=00:1B:DC:00:32:71, dba=20:07:09:15:A9:5A)
-> Apr 19 21:56:55 debian-eeepc hcid[2330]: pin_code_request -> (sba=00:1B:DC:00:32:71, dba=20:07:09:15:A9:5A)
-> Apr 19 21:56:55 debian-eeepc hcid[2330]: link_key_notify
-> (sba=00:1B:DC:00:32:71, dba=20:07:09:15:A9:5A)
-> Apr 19 21:56:57 debian-eeepc hcid[2330]: link_key_request -> (sba=00:1B:DC:00:32:71, dba=20:07:09:15:A9:5A)
-> Apr 19 21:56:58 debian-eeepc hcid[2330]: Access denied: Not authorized

3.) The pin setup you used I think is old, too. The users on this list seem to use some graphical utility, but myself I've always just used auth-agent and passkey-agent from the bluez-utils src tarball.

passkey-agent --default (pin number) (remote device address) & auth-agent &

-> Apr 19 21:56:59 debian-eeepc hcid[2330]: link_key_notify
-> (sba=00:1B:DC:00:32:71, dba=20:07:09:15:A9:5A)
-> Apr 19 21:57:18 debian-eeepc hcid[2330]: Audio API: received -> BT_GETCAPABILITIES_REQ
-> Apr 19 21:57:18 debian-eeepc hcid[2330]: Audio API: sending -> BT_GETCAPABILITIES_RSP
-> Apr 19 21:57:18 debian-eeepc hcid[2330]: Audio API: received -> BT_SETCONFIGURATION_REQ
-> Apr 19 21:57:18 debian-eeepc hcid[2330]: config sco - device = -> 20:07:09:15:A9:5A access_mode = 2
-> Apr 19 21:57:20 debian-eeepc hcid[2330]: link_key_request
-> (sba=00:1B:DC:00:32:71, dba=20:07:09:15:A9:5A)
-> Apr 19 21:57:22 debian-eeepc kernel: Bluetooth: SCO (Voice Link) ver 0.5 -> Apr 19 21:57:22 debian-eeepc kernel: Bluetooth: SCO socket layer initialized
-> Apr 19 21:57:24 debian-eeepc kernel: hci_scodata_packet: hci0 SCO packet -> for unknown connection handle 43
-> Apr 19 21:57:55 debian-eeepc last message repeated 10158 times -> Apr 19 21:58:02 debian-eeepc last message repeated 2576 times -> Apr 19 21:58:02 debian-eeepc hcid[2330]: connect(): Connection timed out

Here...

-> Apr 19 21:58:02 debian-eeepc hcid[2330]: config failed
-> Apr 19 21:58:02 debian-eeepc hcid[2330]: Audio API: sending -> BT_SETCONFIGURATION_RSP
-> Apr 19 21:58:02 debian-eeepc kernel: hci_scodata_packet: hci0 SCO packet -> for unknown connection handle 43
-> Apr 19 21:58:33 debian-eeepc last message repeated 10090 times -> Apr 19 21:59:23 debian-eeepc last message repeated 16726 times

Quoted 8 lines

...and here, look like the message I used to get about the SCO/eSCO problem with 2.6.24 kernels. I'm not 100% sure that's what this is, but it looks similar.

I'll attach setup info and the previously posted esco patch, if you find you do need it. Other than these things mentioned here, I'm not sure what the problem could be.

Thank you so much for the quality information:

I setup my system again and followed your steps i only used my own simple -agent because the passkey-agent is not available in debian sid.

The device nicely connects goes to voice mode and than crashes because it's a SCO only device.

sudo hcitool info 20:07:09:15:A9:5A
Requesting information ...
BD Address: 20:07:09:15:A9:5A
Device Name: Samsung WEP210
LMP Version: 2.0 (0x3) LMP Subversion: 0xbf9
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>

If i understand correctly i have to recompile my kernel to get the device working. This is not a sustainable solution for me, so i want to go with a better solution.

Where can I find a list of eSCO capable headsets so that i get "out of the box support"

Will the SCO only capable device be supported again? They worked in the past but the community has decided to remove the support? How and why did this happen?

Kind regards,

Jelle

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

#6 lore raw
Quoted 125 lines · Jelle de Jong
Quoted 90 lines · jayjwa

On Sat, 19 Apr 2008, Jelle de Jong wrote:

-> So, I tried to get it working for a other 4 hours, but I can't get it to -> work. Please help me, how can I get the device fully working, what am I -> doing wrong here?
-> -> Please take a look at the logs i attached in the mail, i hope this gives
-> enough information for a advanced bluez users to tell me what is wrong.

Several things stand out.

1.)

First is your kernel version. Seems to be a 2.5.24.x. If you are using an SCO-only headset, the 2.6.24.x kernels will not work with it. You must either patch the kernel, or upgrade to an ESCO-able headset. This is the issue with mine. I use the patch that was on this list to patch my 2.6.24.4. The device's features should mention eSCO.

-> snapshot of my syslog >>
-> Apr 19 21:55:55 debian-eeepc hcid[2330]: Bluetooth HCI daemon -> Apr 19 21:55:55 debian-eeepc hcid[2330]: HCI dev 0 registered -> Apr 19 21:55:55 debian-eeepc hcid[2330]: Starting SDP server -> Apr 19 21:55:55 debian-eeepc hcid[2330]: Unix socket created: 12 -> Apr 19 21:55:55 debian-eeepc hidd[2333]: Bluetooth HID daemon -> Apr 19 21:55:55 debian-eeepc hcid[2330]: Registered manager -> path:/org/bluez/audio
-> Apr 19 21:55:55 debian-eeepc hcid[2330]: Registering service -> Apr 19 21:55:55 debian-eeepc hcid[2330]: Unable to execute -> /usr/lib/bluetooth/bluetoothd-service-audio

2). The file, and format of those files above is not used anymore. Now, the audio service is a plugin: /usr/lib/bluetooth/plugins/libaudio.so There are no more *.service files in /etc/bluetooth like audio.service.

-> Apr 19 21:55:55 debian-eeepc hcid[2330]: HCI dev 0 up
-> Apr 19 21:55:55 debian-eeepc hcid[2330]: Device hci0 has been added -> Apr 19 21:55:55 debian-eeepc hcid[2330]: Starting security manager 0 -> Apr 19 21:55:55 debian-eeepc hcid[2330]: Device hci0 has been activated -> Apr 19 21:56:53 debian-eeepc hcid[2330]: link_key_request -> (sba=00:1B:DC:00:32:71, dba=20:07:09:15:A9:5A)
-> Apr 19 21:56:55 debian-eeepc hcid[2330]: pin_code_request -> (sba=00:1B:DC:00:32:71, dba=20:07:09:15:A9:5A)
-> Apr 19 21:56:55 debian-eeepc hcid[2330]: link_key_notify
-> (sba=00:1B:DC:00:32:71, dba=20:07:09:15:A9:5A)
-> Apr 19 21:56:57 debian-eeepc hcid[2330]: link_key_request -> (sba=00:1B:DC:00:32:71, dba=20:07:09:15:A9:5A)
-> Apr 19 21:56:58 debian-eeepc hcid[2330]: Access denied: Not authorized

3.) The pin setup you used I think is old, too. The users on this list seem to use some graphical utility, but myself I've always just used auth-agent and passkey-agent from the bluez-utils src tarball.

passkey-agent --default (pin number) (remote device address) & auth-agent &

-> Apr 19 21:56:59 debian-eeepc hcid[2330]: link_key_notify
-> (sba=00:1B:DC:00:32:71, dba=20:07:09:15:A9:5A)
-> Apr 19 21:57:18 debian-eeepc hcid[2330]: Audio API: received -> BT_GETCAPABILITIES_REQ
-> Apr 19 21:57:18 debian-eeepc hcid[2330]: Audio API: sending -> BT_GETCAPABILITIES_RSP
-> Apr 19 21:57:18 debian-eeepc hcid[2330]: Audio API: received -> BT_SETCONFIGURATION_REQ
-> Apr 19 21:57:18 debian-eeepc hcid[2330]: config sco - device = -> 20:07:09:15:A9:5A access_mode = 2
-> Apr 19 21:57:20 debian-eeepc hcid[2330]: link_key_request
-> (sba=00:1B:DC:00:32:71, dba=20:07:09:15:A9:5A)
-> Apr 19 21:57:22 debian-eeepc kernel: Bluetooth: SCO (Voice Link) ver 0.5 -> Apr 19 21:57:22 debian-eeepc kernel: Bluetooth: SCO socket layer initialized
-> Apr 19 21:57:24 debian-eeepc kernel: hci_scodata_packet: hci0 SCO packet -> for unknown connection handle 43
-> Apr 19 21:57:55 debian-eeepc last message repeated 10158 times -> Apr 19 21:58:02 debian-eeepc last message repeated 2576 times -> Apr 19 21:58:02 debian-eeepc hcid[2330]: connect(): Connection timed out

Here...

-> Apr 19 21:58:02 debian-eeepc hcid[2330]: config failed
-> Apr 19 21:58:02 debian-eeepc hcid[2330]: Audio API: sending -> BT_SETCONFIGURATION_RSP
-> Apr 19 21:58:02 debian-eeepc kernel: hci_scodata_packet: hci0 SCO packet -> for unknown connection handle 43
-> Apr 19 21:58:33 debian-eeepc last message repeated 10090 times -> Apr 19 21:59:23 debian-eeepc last message repeated 16726 times

Quoted 8 lines

...and here, look like the message I used to get about the SCO/eSCO problem with 2.6.24 kernels. I'm not 100% sure that's what this is, but it looks similar.

I'll attach setup info and the previously posted esco patch, if you find you do need it. Other than these things mentioned here, I'm not sure what the problem could be.

Thank you so much for the quality information:

I setup my system again and followed your steps i only used my own simple -agent because the passkey-agent is not available in debian sid.

The device nicely connects goes to voice mode and than crashes because it's a SCO only device.

sudo hcitool info 20:07:09:15:A9:5A
Requesting information ...
BD Address: 20:07:09:15:A9:5A
Device Name: Samsung WEP210
LMP Version: 2.0 (0x3) LMP Subversion: 0xbf9
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>

If i understand correctly i have to recompile my kernel to get the device working. This is not a sustainable solution for me, so i want to go with a better solution.

Quoted 7 lines

Where can I find a list of eSCO capable headsets so that i get "out of the box support"

Will the SCO only capable device be supported again? They worked in the past but the community has decided to remove the support? How and why did this happen?

Just to be sure:

http://en.wikipedia.org/wiki/Bluetooth

So if a headset follows the Bluetooth 1.0 and 1.0B and 1.01 specs is uses SCO Links and is not native supported.

If the headset follows Bluetooth 1.2 and above it should have eSCO link capabilities.

The description of the seller of my Samsung WEP210 described my headset as Bluetooth specification: Ver 2.0. However I can't find specification on the Samsung website about the headset. I can only assume that the description of the seller is wrong.

Kind regards,

Jelle

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users