From: Eugene <it.had.even@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Possible insignificant bug in, pcm_bluetooth.c (bluez-utils)
Date: Tue, 08 Jan 2008 11:52:16 +1000 [thread overview]
Message-ID: <4782D750.4000207@gmail.com> (raw)
In-Reply-To: <mailman.378267.1199593295.26582.bluez-users@lists.sourceforge.net>
[-- Attachment #1: Type: text/plain, Size: 533 bytes --]
Hello, thanks for answer
> I changed this in cvs. Send a unified diff next time... it's quicker
> to figure out what you've found.
>
>
yes, I should do it this way :)
> the other hcid.conf suggestion is to remove sniff from lp. Do you have
> any other bt devices that you use? Is hcitool con only showing the
> a2dp connection?
>
>
It seems to be mystical, but when I reset all setting to their defaults,
all chops were gone!
Don't know what to suggest now.
Mplayer was talking about broken pipe. May be it is an alsa issue?
[-- Attachment #2: it_had_even.vcf --]
[-- Type: text/x-vcard, Size: 55 bytes --]
begin:vcard
fn:Eugene
n:;Eugene
version:2.1
end:vcard
[-- Attachment #3: Type: text/plain, Size: 278 bytes --]
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
[-- Attachment #4: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next parent reply other threads:[~2008-01-08 1:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.378267.1199593295.26582.bluez-users@lists.sourceforge.net>
2008-01-08 1:52 ` Eugene [this message]
2008-01-05 14:31 [Bluez-users] Possible insignificant bug in pcm_bluetooth.c (bluez-utils) 1
2008-01-05 14:57 ` 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=4782D750.4000207@gmail.com \
--to=it.had.even@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