public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Cc: "Henryk Plötz" <henryk@ploetzli.ch>
Subject: Re: [Bluez-devel] a2play and Toshiba SR-1 Bluetooth Headset
Date: Thu, 25 Nov 2004 13:17:13 +0100	[thread overview]
Message-ID: <1101385033.7538.101.camel@pegasus> (raw)
In-Reply-To: <20041125105615.GA19821@snoopy.src.ricoh.co.jp>

Hi Alain,

> actually I was just about to send a new mail to the mailing list.
> Just looking at the BlueZ page, I saw that there is a new hcidump 
> package so after updating I clearly saw the bitpool thing. I just
> replaced the two hardcoded bitpool min and max by the one supported
> by my headset and I got .....

I tagged the 1.15 release of hcidump some hours ago and the tarball is
now also available. Please try again with this one and send us the
binary dump created with -w.

> hum ... weird sound :-(
> 
> well I can recognize my music but sometimes it's going faster, slower
> then faster again .... 
> 
> seems also right and left channel are not same ... well can't be sure
> about that because the sound is very weird ... 
> 
> I don't know what I can do else ... just let me know.

I am interested in the output of "hcitool info" and "sdptest records"
from the BlueZ libs2 CVS. Please pipe them into a file and send them to
me.

> did you made any other modification to the CVS ? Just got it few hours ago 
> so I think except this min/max thing nothing has changed.

The Sourceforge people should really get this delay thing between
anonymous and developer CVS fixed.

Regards

Marcel




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-11-25 12:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-25  9:11 [Bluez-devel] a2play and Toshiba SR-1 Bluetooth Headset Alain Volmat
2004-11-25 10:25 ` Henryk Plötz
2004-11-25 10:56   ` Alain Volmat
2004-11-25 12:17     ` Marcel Holtmann [this message]
2004-11-26  3:40     ` Marcel Holtmann
2004-11-26  3:56       ` Henryk Plötz
2004-11-26  4:12         ` Marcel Holtmann
2004-11-26  9:00           ` Sebastien HENRIO
2004-11-26 17:29             ` Marcel Holtmann
2004-11-27  1:04               ` Henryk Plötz
2004-11-27  3:09                 ` Marcel Holtmann
2004-11-26  4:11       ` Alain Volmat
2004-11-26  4:27         ` Alain Volmat
2004-11-26  4:41           ` Marcel Holtmann
2004-11-26  4:57             ` Alain Volmat
2004-11-26  4:29         ` Marcel Holtmann
2004-11-26  4:54           ` Alain Volmat
2004-11-26  8:32         ` Brad Midgley
2004-11-26  8:07       ` 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=1101385033.7538.101.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=henryk@ploetzli.ch \
    /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