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: Wed, 05 Jul 2006 16:25:11 +0200 [thread overview]
Message-ID: <1152109512.11387.24.camel@localhost> (raw)
In-Reply-To: <44970CBD.8000802@xmission.com>
[-- Attachment #1: Type: text/plain, Size: 1984 bytes --]
Hi,
I have digged some further into this and found out the following:
Just after pairing the headset l2ping shows ping times of about 45 msec.
After starting btsco and about 5 sec after btsco has connected hcidump
shows:
1152107748.832103 < ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0042 len 5 [psm 3]
RFCOMM(d): UIH: cr 1 dlci 2 pf 1 ilen 0 fcs 0x86 credits 33
1152107748.835034 > ACL data: handle 42 flags 0x02 dlen 9
L2CAP(d): cid 0x0041 len 5 [psm 3]
RFCOMM(d): UIH: cr 0 dlci 2 pf 1 ilen 0 fcs 0x5c credits 15
1152107748.840034 > HCI Event: Number of Completed Packets (0x13) plen 5
1152107754.511244 > HCI Event: Mode Change (0x14) plen 6
After this last 'Mode Change' is received l2ping takes 4000-6000 msec
which corresponds to the delay in starting audio playback.
Additionally the hcidump for l2ping -c1 looks different (btsco running):
This is before we receive HCI Event: Mode Change (0x14) plen 6:
1152108661.495583 < ACL data: handle 43 flags 0x02 dlen 52
L2CAP(s): Echo req: dlen 44
1152108661.516393 > HCI Event: Number of Completed Packets (0x13) plen 5
1152108661.546387 > ACL data: handle 43 flags 0x02 dlen 27
1152108661.548386 > ACL data: handle 43 flags 0x01 dlen 25
L2CAP(s): Echo rsp: dlen 44
and this after we received HCI Event: Mode Change (0x14) plen 6:
1152106935.430096 < ACL data: handle 42 flags 0x02 dlen 52
L2CAP(s): Echo req: dlen 44
1152106936.918474 > HCI Event: Number of Completed Packets (0x13) plen 5
1152106939.474570 > ACL data: handle 42 flags 0x02 dlen 17
1152106939.476566 > ACL data: handle 42 flags 0x01 dlen 17
1152106939.477589 > ACL data: handle 42 flags 0x01 dlen 17
1152106939.478582 > ACL data: handle 42 flags 0x01 dlen 1
L2CAP(s): Echo rsp: dlen 44
can anybody tell me what this 'HCI Event: Mode Change (0x14) plen 6' is
about and probably how to prevent this?
A full hcidump from pairing the headset and starting btsco is attached.
Thanks in advance,
Christoph
[-- Attachment #2: hcidump.log.gz --]
[-- Type: application/x-gzip, Size: 1996 bytes --]
[-- Attachment #3: Type: text/plain, Size: 299 bytes --]
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
[-- 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 prev parent reply other threads:[~2006-07-05 14:25 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
2006-06-20 14:30 ` Christoph Lukas
2006-07-05 14:25 ` Christoph Lukas [this message]
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=1152109512.11387.24.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).