From: Brad Midgley <bmidgley@xmission.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] problem using skype + BT headset, Linux OS
Date: Sun, 03 Jul 2005 22:31:26 -0600 [thread overview]
Message-ID: <42C8BB9E.30304@xmission.com> (raw)
In-Reply-To: <42C29EB2.8080502@lesagepono.be>
yes, there is a "noisy microphone" bug in our sourceforge list. I
suspect it's happening somewhere other than btsco (the daemon) and btsco
(the kernel module)
Laurent@lesagepono.be wrote:
> Hi all,
>
> back again with a persistent problem. It seems specific with this
> "assembly" (?) : Linux OS + BT headset + skype. In fact there is no
> problem when I use the headset to listen : the problem is when I use the
> microphone. The first time I set up btsco, and use Skype (or other phone
> client), the micrphone creates a terrible noise. I hangup. I reconnect.
> Generally, this is OK. (don't know why it doesn't work the first time).
> But with skype, the problem appears again. I can place one or two calls,
> then the noise appear and my peer does not hear anything he could
> understand. After that, I often get this error with "btsco -v"
>
>> i/o needed: connecting sco...
>> Can't connect SCO audio channel
>> : Software caused connection abort
>>
>>
>
> while with hcidump, nothing is visible. I just see the dump of the last
> call:
>
>> > SCO data: handle 44 dlen 48
>> > SCO data: handle 44 dlen 48
>> > SCO data: handle 44 dlen 48
>> > SCO data: handle 44 dlen 48
>> > SCO data: handle 44 dlen 48
>> > SCO data: handle 44 dlen 48
>> > SCO data: handle 44 dlen 48
>> > SCO data: handle 44 dlen 48
>> > SCO data: handle 44 dlen 48
>>
>
> I remeber someone had a similar problem a few days ago. Any idea? A bug?
>
> thanks
>
> Laurent
>
>
>
>
> -------------------------------------------------------
> 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-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
-------------------------------------------------------
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2005-07-04 4:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 13:14 [Bluez-users] problem using skype + BT headset, Linux OS Laurent@lesagepono.be
2005-07-04 4:31 ` Brad Midgley [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=42C8BB9E.30304@xmission.com \
--to=bmidgley@xmission.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