linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jelle de Jong <jelledejong@powercraft.nl>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Samsung WEP210 Bluetooth Headset
Date: Sat, 19 Apr 2008 22:39:19 +0200	[thread overview]
Message-ID: <480A5877.4080201@powercraft.nl> (raw)
In-Reply-To: <alpine.LNX.1.00.0804190011000.27696@nge2.ngu.pk>

[-- Attachment #1: Type: text/plain, Size: 5386 bytes --]

jayjwa wrote:
> 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.
> 
>

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



[-- Attachment #2: Samsung WEP210 Bluetooth Headset.txt --]
[-- Type: text/plain, Size: 3198 bytes --]

#!/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


[-- Attachment #3: debug-bluez.tar.bz2 --]
[-- Type: application/x-bzip, Size: 14985 bytes --]

[-- Attachment #4: Type: text/plain, Size: 320 bytes --]

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

[-- Attachment #5: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2008-04-19 20:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-18 23:29 [Bluez-users] Samsung WEP210 Bluetooth Headset Jelle de Jong
2008-04-18 23:47 ` Jelle de Jong
2008-04-19  4:27   ` jayjwa
2008-04-19 20:39     ` Jelle de Jong [this message]
2008-04-21  1:06       ` jayjwa
2008-04-21  9:25         ` Jelle de Jong
2008-04-21  9:58           ` Jelle de Jong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=480A5877.4080201@powercraft.nl \
    --to=jelledejong@powercraft.nl \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).