From: billy leung <vientito1@pppoe.ca>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] continue: error 22
Date: Thu, 1 Nov 2007 00:13:41 -0400 [thread overview]
Message-ID: <20071101001341.0c2a9fd2.vientito1@pppoe.ca> (raw)
when you talk about my device, which one are you talking about - the cellular headset or my USB bluetooth adaptor? i glance past the manual and it seems to indicate both have headset service (obvious for the headset, otherwise what's its use? ). or does it have something to do with SCO mapping? if so, would we expect resolution in the future versions?
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2007-11-01 4:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 4:13 billy leung [this message]
2007-11-01 5:02 ` [Bluez-users] continue: error 22 Marcel Holtmann
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=20071101001341.0c2a9fd2.vientito1@pppoe.ca \
--to=vientito1@pppoe.ca \
--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