From: John McCorquodale <random-spam@viz.cacr.caltech.edu>
To: John McCorquodale <random-spam@viz.cacr.caltech.edu>
Cc: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: btsco/headset problems
Date: Mon, 24 Jan 2005 20:05:26 -0800 [thread overview]
Message-ID: <20050125040526.GA2080@viz.cacr.caltech.edu> (raw)
In-Reply-To: <20050125015049.GA1520@viz.cacr.caltech.edu>
> stracing btsco shows that no data ever comes in on the BT file descriptor;
> the poll just sits in its little one-second loop never rx'ing anything from
> anybody, even when I bang on the headset button like an undersexed chihuahua
> on speed.
I done figured it out, Martha. Turns out there were two problems:
1. The Debian bluez-utils package comes with this great little pin helper
that's a Python script and pops up a little window with PyGtk to ask
for the headset's PIN. But it seems MyGtk had evolved and the little
script hadn't and it got stuck or bombed or something. The thread of
control was hanging in that pin handler and thus btsco was unable to
print out "recieve AT+CKPD=200" and go forward. Switching my pin
helper to "#!/bin/sh \n echo PIN:0000" suddenly caused btsco to act
like it's supposed to and quiet static to eminate from an full-loud
headset. But aplay/arecord still hung forever.
2. Switching away from the Socket CF G card to the D-Link DBT-120 USB
fob solved the aplay/arecord problem and now I have a fully working
ALSA headset!
3. (aside) I also switched up to 2.6.10-mh2 in the process here and
from Debian's 2.10 libs/utils to the current 2.14 libs/utils. I
don't know if that made any difference; I suspect not.
Since I answered the hard question and the list didn't have to, I have an
easy one for you guys:
What is a CF card BT adapter that has _no_ protruding antenna, like the Socket
CF, that _works_? I really want my Zaurus to talk to my headset and the little
antenna doodah will break off in my pocket, and Zaurus has no USB host.
Thanks, y'all,
-mcq
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-01-25 4:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 1:50 [Bluez-devel] btsco/headset problems John McCorquodale
2005-01-25 4:05 ` John McCorquodale [this message]
2005-01-26 16:06 ` Brad Midgley
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=20050125040526.GA2080@viz.cacr.caltech.edu \
--to=random-spam@viz.cacr.caltech.edu \
--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