From: Chase Douglas <cndougla@purdue.edu>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: btsco occasional loud bursts of static
Date: Thu, 02 Feb 2006 21:17:50 -0500 [thread overview]
Message-ID: <43E2BD4E.7060905@purdue.edu> (raw)
> Chase
>
> One thing to check is the code we have to accommodate a byte getting
> lost. If we don't watch for this, subsequent samples have what should be
> a high byte in the low position and vice-versa, so the result is loud
> noise for the remainder of the connection.
>
> I haven't looked closely at this, but it's really baffling to think a
> single byte could be lost from a stream of 16-bit samples like that. The
> protocol should drop entire samples when the signal is bad--losing
*> *half** a sample is a worst-case scenario.
>
> Brad
>
> > I have a dlink dbt-120 rev. b4 bluetooth adapter with a motorola hs850
> > and I use btsco to talk with people online. When I have my laptop
> > sitting on my lap, everything works fine. However, when I start to walk
> > around, the sound transmitted to the other person from my headset will
> > have bursts of loud static. I am guessing that this is a problem with
> > the connection being worse. I would like to get this resolved, and I can
> > do some coding as well. I have a 2 MB hcidump which somewhere near the
> > end has the offending sound packets. I can't find any documentation on
> > the SCO protocol, so I can't find where the static was. Can anyone point
> > me in the right direction?
> >
> > Thank you,
> > Chase Douglas
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> > files
> > for problems? Stop! Download the new AJAX search engine that makes
> > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 <http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642>
> > _______________________________________________
> > Bluez-devel mailing list
> > Bluez-devel <at> lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 <http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642>
I'd love to hlp in any way I can. I'm not sure where this code is that you
wrote of. Could you point me in the right direction? Also, I am going to need
some kind of documentation on the sco protocol. Do you know where I could find
these?
Thanks
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2006-02-03 2:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-03 2:17 Chase Douglas [this message]
2006-02-03 5:59 ` [Bluez-devel] Re: btsco occasional loud bursts of static Brad Midgley
2006-02-03 15:38 ` Brad Midgley
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=43E2BD4E.7060905@purdue.edu \
--to=cndougla@purdue.edu \
--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;
as well as URLs for NNTP newsgroup(s).