All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Lukas <christoph.lukas@gmx.net>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Slow connection to Motorola H500 Headset
Date: Tue, 20 Jun 2006 10:32:02 +0200	[thread overview]
Message-ID: <1150792323.8983.1.camel@localhost> (raw)
In-Reply-To: <44970CBD.8000802@xmission.com>

[-- Attachment #1: Type: text/plain, Size: 1283 bytes --]

Hi Brad,

thanks for your quick reply.

> > Audio transfer is working perfectly in both directions, the only minor
> > annoyance is that it takes several seconds for every connection to be
> > established.
> 
> maybe the headset is parking itself between connections. I don't know
> much about what can be done to influence its policy though.

It seems as if the headset enters some kind of 'powersave' mode after a
few seconds.


> you could start up hcidump before you bring up the headset and tell us
> what the dump looks like at the start. we might be able to tell what
> slows things down.

I did the following steps to produce the two attached hcidumps:

hcidump.log.fast.gz:
* start hcidump
* switch headset on
* wait for link key request and immediately start btsco
* wait for btsco to be ready and immediately start aplay
=> This results in an immediately starting audio playback

hcidump.log.slow.gz:
* start hcidump
* switch headset on
* wait for link key request and immediately start btsco
* wait about 30 sec. after btsco being ready before starting aplay
=> This results in an delay of 3-5 seconds before audio playback is
starting

This behaviour is reproducable.

If anybody has any hints what is happening here that would be great.

Thanks in advance,
Christoph



[-- Attachment #2: hcidump.log.fast.gz --]
[-- Type: application/x-gzip, Size: 29338 bytes --]

[-- Attachment #3: hcidump.log.slow.gz --]
[-- Type: application/x-gzip, Size: 50284 bytes --]

[-- Attachment #4: Type: text/plain, Size: 0 bytes --]



[-- Attachment #5: 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:[~2006-06-20  8:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19 19:56 [Bluez-users] Slow connection to Motorola H500 Headset Christoph Lukas
2006-06-19 20:44 ` Brad Midgley
2006-06-20  8:32   ` Christoph Lukas [this message]
2006-06-20 14:30   ` Christoph Lukas
2006-07-05 14:25   ` Christoph Lukas
2006-07-07 14:44     ` Ulisses Furquim
2006-07-07 15:48       ` Christoph Lukas
2006-07-07 17:14         ` Ulisses Furquim
2006-07-07 18:07           ` Christoph Lukas
2006-07-07 20:19             ` Ulisses Furquim

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=1150792323.8983.1.camel@localhost \
    --to=christoph.lukas@gmx.net \
    --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 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.