From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] btsco - a few comments and a small .py script
Date: Sun, 21 Aug 2005 22:29:26 -0600 [thread overview]
Message-ID: <430954A6.40107@xmission.com> (raw)
In-Reply-To: <20050821192634.GA10231@uni-duesseldorf.de>
Andreas
>>>3. I have written a small Python-Script and a .btscorc
>>
>>Perfect. I gave a talk about btsco at our usergroup meeting and this
>>very question came up! (slides at http://flamebot.com/blog)
>>I will link to you or put these in a contrib dir (what do you think?)
>
>
> I don't care. I don't think this will need updates, unless the skype
> d-bus protocol gets changed in a fundamental way.
Ok, I will put it in contrib and add a note that it's derived from the
api documentation example. If you like the mod from "Whoopie" I'll apply
that too.
> [I just noticed, that the copying around is done in kernelspace. Got to
> check it there, then.]
I'll bet we could watch for this. If byte order gets reversed, it might
present a pattern that we can identify. It seems like SCO is not a
reliable transport so maybe bluez is supposed to watch for this kind of
stuff somehow. I should read up on it...
> A nice addition for me would be a software mic-boost. The quality of the
> sound is not bad, but (probably due to the ridiculously compact design
> of my headset) the dynamic range is not used appropriately.
The general solution is an adaptive boost which would be nice even for
mics that use the full range. It's a common problem so I'll bet you can
get this from one of the alsa layers in userspace.
> Another thing I noticed (which is probably not btsco related, but more
> of a general bluez problem, maybe even a general kernel problem) is,
> that I now had two occasions where my USB subsystem became unresponsive
> to a point where the machine froze.
I suppose since it's only happened twice you can't reproduce it? I'm not
much help looking over logs since I don't know what to look for.
I've seen times where the mouse starts acting whacked and focus gets
stuck on some widget even if the mouse is pointing elsewhere. I've been
meaning to restart hidd and/or reload evdev to see if it's linked to the
bluetooth mouse.
Brad
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-08-22 4:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 19:38 [Bluez-devel] btsco - a few comments and a small .py script Andreas Beck
2005-08-19 20:44 ` John Gruenenfelder
2005-08-20 20:13 ` Brad Midgley
2005-08-21 12:12 ` Andreas Beck
2005-08-21 19:26 ` Andreas Beck
2005-08-22 4:29 ` Brad Midgley [this message]
2005-08-22 12:09 ` Andreas Beck
2005-08-22 18:38 ` Andreas Beck
2005-08-22 18:53 ` [Bluez-devel] AGC and anti-noise patch for btsco kernel module Andreas Beck
2005-08-22 22:10 ` Brad Midgley
2005-08-23 15:04 ` Andreas Beck
2005-08-23 16:05 ` Andreas Beck
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=430954A6.40107@xmission.com \
--to=bmidgley@xmission.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.