From: "Florian Schaefer" <listbox@netego.de>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] aplay freezes with headsetd
Date: Sun, 28 Jan 2007 15:30:55 +0100 [thread overview]
Message-ID: <E1HBB3Y-0000YF-QI@washu.netego.de> (raw)
In-Reply-To: <E1HAsSn-0000V7-5M@washu.netego.de>
[-- Attachment #1.1: Type: text/plain, Size: 1901 bytes --]
OK, so I'll start and reply to myself a bit...
On Sat, 27 Jan 2007 19:39:37 +0100, Florian Schaefer said:
> 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)
Reading the bluetooth-alsa website once again, this USB-adapter seems to
be responsible:
root@washu:~ # hciconfig hci0 revision
hci0: Type: USB
BD Address: 00:02:78:3D:18:DD ACL MTU: 1017:8 SCO MTU: 64:0
Firmware 220.65 / 92
I already tried to load hci_usb via "modprobe hci_usb force_scofix" as
advised by the contact website but that didn't change anything. I'm using
linux kernel 2.6.19 with the "plugz/patches/sco-flowcontrol-v3.0.diff"
patches here.
Does anyone have positive or negative experiences with this Broadcom
adapter?
Anything else I might try?
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 prev parent reply other threads:[~2007-01-28 14:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-27 18:39 [Bluez-devel] aplay freezes with headsetd Florian Schaefer
2007-01-28 14:30 ` Florian Schaefer [this message]
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=E1HBB3Y-0000YF-QI@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