From: Benny <bennyvasanth@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] btsco - headset profile activated but no sco packets transmitted ???
Date: Wed, 13 Apr 2005 11:08:42 +0530 [thread overview]
Message-ID: <f54d86405041222381e9da934@mail.gmail.com> (raw)
In-Reply-To: <200504042322.17493.pavouk@pavouk.org>
Dear Pavel Ruzicka,
I am also involved in testing the BT Headset functionality with the
PC. I am using a CSR based USB BT Dongle on the PC and the BT Mono
Headset is the RFMD Headset kit.
I have taken the latest CVS "btsco" files and compiled. Fedora 3(linux
kernel 2.6.9-1.667) runs on my host PC. I have taken the latest Bluez
libraries and utilities from the bluez site.
After running the "btsco" I am able to run the xmms and play songs and
test for the speaker functionality separately. But I am not able to
test the Sound recorder functionality. The SCO connection is opened
only when I press "play" for the xmms and it closes when I stop the
song. Whether I can test the mic functionality separately.
But my target application is a chat application with the usage of
Speaker and mic working simultaneosly.
Please advice of the setting I need to make.
Thanks & Regards,
Benny
On 4/5/05, Pavel Ruzicka <pavouk@pavouk.org> wrote:
> > I haven't heard success stories for using the bt110 but I can't remembe=
r
> > if we've had trouble reports on this one or not.
> >
> > > root@sigma:~/src/btsco# ./btsco -v 00:07:A4:95:41:76 2
> >
> > The only thing I would suggest is that you don't specify the channel
> > here, but I suspect btsco will autodetect channel 2 anyway.
>=20
> Hello,
>=20
> I now tried compiling snd_bt_sco for 2.6.11.6 and everything works great.
>=20
> I am using btsco 00:07:A4:0A:3F:XX or btsco 00:07:A4:0A:3F:XX 2 and both
> works.
>=20
> I have headset Jabra BT250.
> Dongle is d-link DBT-120 with 1.2 firmware.
>=20
> This sents sound from headset mic to soundcard:
> "cat </dev/dsp1 >/dev/dsp0".
> Simultaneously I start xmms, setup out to BT headset alsa device, and
> mp3 plays in my headset. Sound from headset microphone goes to my normal =
audio
> set.
>=20
> I have few questions:
>=20
> Audio is heavily delayed (about 300-400ms)
> What is the reason for this delay?
>=20
> Sound from microphone is noised. For speaking is enough, but quality is n=
ot
> much good. Is it normal?
>=20
> Best regards,
>=20
> Pavel Ruzicka
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-04-13 5:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 19:45 [Bluez-users] btsco - headset profile activated but no sco packets transmitted ??? Lars Steinke
2005-04-04 19:50 ` [Bluez-users] " Lars Steinke
2005-04-15 11:12 ` Lars Steinke
2005-04-15 12:16 ` [Bluez-devel] " Lars Steinke
2005-04-15 14:31 ` Brad Midgley
2005-04-04 20:00 ` [Bluez-users] " Brad Midgley
2005-04-04 21:22 ` Pavel Ruzicka
2005-04-13 5:38 ` Benny [this message]
2005-04-14 14:32 ` Pavel Ruzicka
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=f54d86405041222381e9da934@mail.gmail.com \
--to=bennyvasanth@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