public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Robinson <pbrobinson@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] btsco under FC3
Date: Sat, 8 Jan 2005 09:42:42 +0800	[thread overview]
Message-ID: <5256d0b05010717425be7834d@mail.gmail.com> (raw)
In-Reply-To: <20050107120154.424e0927.henryk@ploetzli.ch>

> > As seen below it detects the device, the voice settings and connects
> > with a RFCOMM channel but then it just sits there. I end up just
> > putting it into the background and try running the varoius examples.
> > Output of all included below. I get no sound at all. any ideas or
> > suggestions?
> 
> You did press the connect button on the headset, did you?

Yes. You put this headset into a Pairing mode, run btsco, it asks for
a pin for the headset and away you go.
 
> > [root@trinity btsco]# btsco 00:07:A4:0E:69:3D
> ...
> > [1]+ btsco 00:07:A4:0E:69:3D &
> > [root@trinity btsco]# mpg123 --au -
> > /home/audio/mp3/green_day/american_idiot/green_day-boulevard_of_broke
> > n_dreams.mp3
> > | sbc/sbcenc - | ./a2play 00:07:A4:0E:69:3D
> 
> That is not supposed to work. btsco (the program) and a2play are two
> different things. You should only be able to use one of them at any
> one time, if a2play works for you at all (which it doesn't, as the
> HS-810 can't do A2DP).

That may be my interpretation of the web page. Something for me to try
when I get some more time.

So does a2play etc ask for a pin to pair with the headset as well?

P


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  parent reply	other threads:[~2005-01-08  1:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-06  4:46 [Bluez-devel] btsco under FC3 Peter Robinson
2005-01-06  7:28 ` Bob Gustafson
2005-01-06 12:24 ` Marcel Holtmann
2005-01-06 14:23   ` Bob Gustafson
2005-01-06 14:51     ` Marcel Holtmann
2005-01-06 15:33       ` Bob Gustafson
2005-01-07  6:15   ` Peter Robinson
2005-01-07  7:14     ` Brad Midgley
2005-01-07  7:19       ` Peter Robinson
2005-01-07 11:08         ` Lars Grunewaldt
2005-01-07 11:01     ` Henryk Plötz
2005-01-07 11:10       ` Lars Grunewaldt
2005-01-08  1:42       ` Peter Robinson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-01-06 15:36 Bob Gustafson
2005-01-06 15:51 Bob Gustafson
2005-01-06 17:26 ` Marcel Holtmann
2005-01-07  3:30   ` Peter Robinson
2005-01-07  4:20     ` Brad Midgley
2005-01-07  3:43   ` Bob Gustafson
     [not found]   ` <v04020a21be03b42174eb@192.168.49.19>
2005-01-07  6:06     ` Peter Robinson
2005-01-06 16:21 Bob Gustafson

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=5256d0b05010717425be7834d@mail.gmail.com \
    --to=pbrobinson@gmail.com \
    --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