public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Christophe-Marie Duquesne" <chm.duquesne@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Updated to bluez 3.24 from Ubuntu repo's. Headphones still disconnect after 2-3 mins.
Date: Sat, 5 Jan 2008 22:37:03 +0100	[thread overview]
Message-ID: <8ccc3510801051337t621fed03r1ccfeab924328a17@mail.gmail.com> (raw)
In-Reply-To: <d89ddf300801051234i45d2d574s65fd7954a9cbaa82@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1372 bytes --]

where did you updated to bluez 3.24? I am running ubuntu gutsy and the only
version I get with synaptic is 3.19. I had to compile my own version to have
it working

On Jan 5, 2008 9:34 PM, Brad Midgley <bmidgley@gmail.com> wrote:

> Paul
>
> If you'll let someone else get a word in... :)
>
> You'll get a lot of data, but if you run this while playing audio,
> near the end it might say something interesting about the disconnect:
>
> sudo hcidump -XV >log
>
> aplay from the console might print a decent error message.
>
> Brad
>
> On Jan 5, 2008 12:53 PM, Paul Rushworth <paul@rushworth.co.nz> wrote:
> > Paul Rushworth <paul <at> rushworth.co.nz> writes:
> > > Paul Rushworth <paul <at> rushworth.co.nz> writes:
> > > > Perhaps vlc with audio sink is the cause of the problem?
>
> --
> Brad
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>



-- 
vous pouvez consulter mon calendrier à l'adresse suivante :
http://www.google.com/calendar/embed?src=trtf7d6pmhcmnqruefapk92vks%40group.calendar.google.com

[-- Attachment #1.2: Type: text/html, Size: 2322 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2008-01-05 21:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-05 18:26 [Bluez-users] Updated to bluez 3.24 from Ubuntu repo's. Headphones still disconnect after 2-3 mins Paul Rushworth
2008-01-05 19:16 ` Paul Rushworth
2008-01-05 19:30   ` Paul Rushworth
2008-01-05 19:53     ` Paul Rushworth
2008-01-05 20:34       ` Brad Midgley
2008-01-05 21:37         ` Christophe-Marie Duquesne [this message]
2008-01-06  4:25           ` Paul Rushworth
2008-01-06  4:28         ` Paul Rushworth
2008-01-06 11:46           ` Colin Murphy
2008-01-06 13:48             ` Christophe-Marie Duquesne
2008-01-06 19:08               ` Paul Rushworth
2008-01-06 19:10             ` Paul Rushworth
2008-01-06 19:25               ` Christophe-Marie Duquesne

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=8ccc3510801051337t621fed03r1ccfeab924328a17@mail.gmail.com \
    --to=chm.duquesne@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