From: Gunter Ohrner <G.Ohrner@post.rwth-aachen.de>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: btsco and Jabra Headset
Date: Thu, 16 Jun 2005 00:45:45 +0200 [thread overview]
Message-ID: <d8qap1$vp7$2@sea.gmane.org> (raw)
In-Reply-To: d7uvkf$jm$1@sea.gmane.org
Gunter Ohrner wrote:
> I've had a hard time trying to get my headset working but had no success
> so far. :-(
Mh, noone has any idea? So it's probably a hardware defect rather than a
configuration or software problem? Unfortunately I have no replacement
hardware to verify, I'll need to buy some if it's the likely cause...
Greetings,
Gunter
--
"The thing is that Mr. Dibbler can even sell sausages to people who
have bought them off him *before*." -- (Terry Pratchett, Moving
Pictures)
*** PGP-Verschlüsselung bei eMails erwünscht :-) *** PGP: 0x1128F25F ***
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-06-15 22:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-05 13:48 [Bluez-devel] btsco and Jabra Headset Gunter Ohrner
2005-06-15 22:43 ` [Bluez-devel] " Gunter Ohrner
2005-06-15 22:43 ` Gunter Ohrner
2005-06-15 22:44 ` Gunter Ohrner
2005-06-15 22:52 ` Brad Midgley
2005-06-17 18:02 ` [Bluez-devel] " Gunter Ohrner
2005-06-15 22:53 ` [Bluez-devel] " Gunter Ohrner
2005-06-15 22:45 ` Gunter Ohrner
2005-06-15 22:45 ` Gunter Ohrner [this message]
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='d8qap1$vp7$2@sea.gmane.org' \
--to=g.ohrner@post.rwth-aachen.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