From: "Brad Midgley" <bmidgley@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] audio bluetooth connectivity in gutsy
Date: Mon, 21 Jan 2008 11:19:07 -0700 [thread overview]
Message-ID: <d89ddf300801211019h6591383asa0239dccede535d5@mail.gmail.com> (raw)
In-Reply-To: <20080121135052.GB20816@juIljoat8>
Benito
> Nevertheless I can go one step further than Gunnar: the audio player
> starts up, the headset-speaker beeps,
>
> To my uneducated eyes this looks like the audio stream somehow can't be
> transmitted while the "signalling" works.
Yes, you're correct that signaling works but not audio. The beep you
hear is the headset letting you know the connection was negotiated...
it's not a sound sent by the computer.
It's unlikely the problem is in the headset. What usually is happening
in this situation is the computer opens the sco connection and tries
to push data over it but the adapter is not picking up the data and
transmitting it.
--
Brad
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2008-01-21 18:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-19 23:22 [Bluez-users] audio bluetooth connectivity in gutsy Gunnar Thielebein
2008-01-20 3:13 ` Eugene
2008-01-20 4:41 ` Brad Midgley
2008-01-20 12:54 ` Christophe-Marie Duquesne
2008-01-20 13:04 ` Gunnar Thielebein
2008-01-20 14:39 ` Brad Midgley
2008-01-21 13:50 ` Benito Torres
2008-01-21 18:19 ` Brad Midgley [this message]
2008-01-22 5:16 ` Johan Brannlund
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=d89ddf300801211019h6591383asa0239dccede535d5@mail.gmail.com \
--to=bmidgley@gmail.com \
--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