Re: Samsung WEP210 Bluetooth Headset

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).