From: "Fred Schättgen" <bluez-devel@schaettgen.de>
To: bluez-devel@lists.sourceforge.net
Cc: Simon Vogl <vogl@soft.uni-linz.ac.at>
Subject: Re: [Bluez-devel] sco link help needed
Date: Thu, 19 Feb 2004 16:29:38 +0100 [thread overview]
Message-ID: <200402191629.38846.bluez-devel@schaettgen.de> (raw)
In-Reply-To: <4034CA08.50500@soft.uni-linz.ac.at>
On Thursday 19 February 2004 15:36, Simon Vogl wrote:
> Hi,
> I desparately need some help with audio links:
> I have written two small programs that use my pc to emulate a headset
> and a handsfree device. Both work quite nicely, the rfcomm-based
> initialization takes place, and I get an SCO connection, but mysteriously,
> I don't get a single byte of audio data (I don't see it with hcidump
> neither).
>
> my setup:
> * Acer usb bluetooth dongle
> * test phones used: p800 (headset), p6600/ngage/3650 (handsfree) with no
> luck... * kernel 2.4.23
> * bluez utils&lib from cvs
> * and yes, i did register hset profile via sdptool....
>
> I had the program running perfectly already with a T68i....
> Any help appreciated heavily (for example a traace of a successful
> connection...), Simon
I wrote a small handsfree application as a part of the KDE Bluetooth
Framework. It basically worked, even though it had problems with an ever
increasing lag, which has probably nothing to do with bluez. But at the
moment it's broken and it's not very high priority, since my microphone is
also broken ;)
But you might take a look at it.. it's in kdeextragear-3:
http://webcvs.kde.org/cgi-bin/cvsweb.cgi/kdeextragear-3/kdebluetooth/handsfree/
I'll try to fix it during the next days.
Btw. I'm not sure if the sound doesn't work currently because of a kernel
problem. Maybe I should try with an older kernel.. It used to work with
2.4.24 if I remember correctly.
greetings
Fred
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-02-19 15:29 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 14:36 [Bluez-devel] sco link help needed Simon Vogl
2004-02-19 15:29 ` Fred Schättgen [this message]
2004-02-21 14:37 ` James Courtier-Dutton
2004-02-22 12:27 ` Marcel Holtmann
2004-02-22 20:53 ` James Courtier-Dutton
2004-02-22 21:30 ` Marcel Holtmann
2004-02-22 22:04 ` James Courtier-Dutton
2004-02-22 22:09 ` Marcel Holtmann
2004-02-22 23:37 ` James Courtier-Dutton
2004-02-23 7:55 ` Marcel Holtmann
2004-02-25 12:59 ` Mauro Tortonesi
2004-02-25 13:25 ` Marcel Holtmann
2004-02-25 14:04 ` Mauro Tortonesi
2004-02-25 14:23 ` Marcel Holtmann
2004-02-25 15:35 ` Mauro Tortonesi
2004-02-25 15:37 ` Marcel Holtmann
2004-02-25 15:46 ` Mauro Tortonesi
[not found] ` <1077728432.6021.522.camel@localhost>
2004-02-25 17:16 ` Marcel Holtmann
2004-02-25 17:27 ` Nils Faerber
2004-02-25 14:30 ` James Courtier-Dutton
2004-02-25 14:59 ` Dr. Simon Vogl
2004-02-25 15:09 ` Marcel Holtmann
2004-02-25 14:22 ` James Courtier-Dutton
2004-02-23 16:35 ` libs2 and utils2 Aaron Klish
2004-02-23 17:19 ` [Bluez-devel] " Marcel Holtmann
2004-02-22 21:54 ` [Bluez-devel] sco link help needed Fred Schättgen
2004-02-22 22:00 ` Marcel Holtmann
2004-02-22 22:35 ` Fred Schättgen
2004-02-22 12:44 ` Dr. Simon Vogl
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=200402191629.38846.bluez-devel@schaettgen.de \
--to=bluez-devel@schaettgen.de \
--cc=bluez-devel@lists.sourceforge.net \
--cc=vogl@soft.uni-linz.ac.at \
/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