From: "Florian Schaefer" <listbox@netego.de>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] aplay freezes with headsetd
Date: Sat, 27 Jan 2007 19:39:37 +0100 [thread overview]
Message-ID: <E1HAsSn-0000V7-5M@washu.netego.de> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 4212 bytes --]
Hi,
I'm currently trying to get my "Logitech Mobile Pro II" headset connected
to my Debian box using the new and shiny headsetd. It seems that I get a
connection between my notebook and the headset when starting a test run
of aplay (the speaker of the headset is activated and emits some quiet
static sounds) but that's all that happens. Aplay will just kind of
freezes and that's it.
But now the information in more order (my CVS checkouts are from today):
root@washu:~ # hciconfig -a
hci0: Type: USB
BD Address: 00:02:78:3D:18:DD ACL MTU: 1017:8 SCO MTU: 64:0
UP RUNNING PSCAN
RX bytes:397591 acl:21 sco:7760 events:50 errors:0
TX bytes:806 acl:21 sco:0 commands:30 errors:0
Features: 0xff 0xff 0x8d 0xfe 0x9b 0xfd 0x00 0x80
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'washu'
Class: 0x3e0100
Service Classes: Networking, Rendering, Capturing, Object
Transfer, Audio
Device Class: Computer, Uncategorized
HCI Ver: 2.0 (0x3) HCI Rev: 0x20dc LMP Ver: 2.0 (0x3) LMP Subver:
0x415c
Manufacturer: Broadcom Corporation (15)
florian@washu:~ # /opt/bluetooth-alsa/bin/headsetd -n
headsetd[1808]: Bluetooth headset daemon version 0.5
[*** headset switched on ***]
headsetd[1808]: Incoming RFCOMM hs connection from 00:0D:44:5C:A7:69
accepted
headsetd[1808]: Changing state: Idle-->Connected
[*** aplay started ***]
headsetd[1808]: Changing state: Connected-->Ready
headsetd[1808]: Changing state: Ready-->Opening
headsetd[1808]: SCO channel opened handle=0x0001 mtu=64
headsetd[1808]: Changing state: Opening-->Streaming
[*** this is where aplay hangs ***]
florian@washu:~ # aplay -B 1000000 -Dheadset
/usr/share/sounds/alsa/Front_Left.wav
DEBUG(pid=1897): _snd_pcm_sco_open: Starting pcm_sco_headset plugin.
DEBUG(pid=1897): _snd_pcm_sco_open: Open mode is for Playback.
DEBUG(pid=1897): _snd_pcm_sco_open: opened as ioplug=0x805c778,
pcm=0x805c8b0, i
oplug->callback = 0xb7acc7e0
Playing WAVE '/usr/share/sounds/alsa/Noise.wav' : Signed 16 bit Little
Endian, R
ate 48000 Hz, Mono
Warning: rate is not accurate (requested = 48000Hz, got = 8000Hz)
please, try the plug plugin (-Dplug:headset)
DEBUG(pid=1897): sco_headset_hw_params: period_count = 200
DEBUG(pid=1897): sco_headset_prepare: Preparing with io->period_size =
24, io->b
uffer_size = 4800
DEBUG(pid=1897): sco_headset_pointer: returning bt_headset->hw_ptr=0
DEBUG(pid=1897): sco_headset_write: areas->step=16, areas->first=0,
offset=0, si
ze=24, io->nonblock=0
DEBUG(pid=1897): sco_headset_write: returning 24
DEBUG(pid=1897): sco_headset_pointer: returning bt_headset->hw_ptr=24
DEBUG(pid=1897): sco_headset_write: areas->step=16, areas->first=0,
offset=0, si
ze=24, io->nonblock=0
DEBUG(pid=1897): sco_headset_write: returning 24
DEBUG(pid=1897): sco_headset_pointer: returning bt_headset->hw_ptr=48
DEBUG(pid=1897): sco_headset_write: areas->step=16, areas->first=0,
offset=0, si
ze=24, io->nonblock=0
[*** many more of those lines ***]
DEBUG(pid=1897): sco_headset_write: returning 24
DEBUG(pid=1897): sco_headset_pointer: returning bt_headset->hw_ptr=4776
DEBUG(pid=1897): sco_headset_write: areas->step=16, areas->first=0,
offset=0, si
ze=24, io->nonblock=0
DEBUG(pid=1897): sco_headset_write: returning 24
DEBUG(pid=1897): sco_headset_pointer: returning bt_headset->hw_ptr=0
DEBUG(pid=1897): sco_headset_write: areas->step=16, areas->first=0,
offset=0, si
ze=24, io->nonblock=0
[*** this is where aplay hangs ***]
Here I here, that the speaker has been switched on, but all I hear is
static.
root@washu:~ # hcidump -X -V
[*** shows a lot of stuff all the time similar to: ***]
> SCO data: handle 1 dlen 48
0000: f1 ff 57 ff 39 ff bb ff bb ff 28 ff 0d ff 83 ff
..W.9.....(.....
0010: c0 ff 72 ff 4d ff b3 ff 1b 00 0e 00 cc ff 13 00
..r.M...........
0020: 7e 00 37 01 3d 01 30 01 46 01 59 01 37 02 00 02
~.7.=.0.F.Y.7...
The output of hcidump continued even after aplay didn't do anything
anymore.
I already tried to use the btsco method: Slightly different debug output,
but the same net result.
Any ideas?
Ciao
Florian
[-- Attachment #1.2: Type: application/pgp-signature, Size: 253 bytes --]
[-- Attachment #2: Type: text/plain, Size: 347 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2007-01-27 18:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-27 18:39 Florian Schaefer [this message]
2007-01-28 14:30 ` [Bluez-devel] aplay freezes with headsetd Florian Schaefer
2007-01-28 14:53 ` Brad Midgley
2007-01-28 16:04 ` Florian Schaefer
2007-01-28 17:12 ` Brad Midgley
2007-01-28 18:44 ` Florian Schaefer
2007-02-04 13:13 ` Florian Schaefer
2007-01-28 19:40 ` Fabien Chevalier
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=E1HAsSn-0000V7-5M@washu.netego.de \
--to=listbox@netego.de \
--cc=bluez-devel@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