From: Pedro Monjo Florit <pmonjo2000@yahoo.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] SDP in Motorola phones
Date: Tue, 07 Mar 2006 17:27:02 +0100 [thread overview]
Message-ID: <440DB456.3030401@yahoo.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 839 bytes --]
Hi,
I am experiencing problems getting SDP information from some new
Motorola phones (I am dealing with E770). Running "sdptool browse
BDADDR", I get the attached hcidump. As it can be seen, after the SDP
SSA request, the mobile phone does not respond any data and after 20
seconds (the SDP timeout compiled in bluez-libs), sdptool issues an ACL
disconnect. During this time, the phone freezes completely. If I want to
get a specific service (say, OBEX), there are no problems.
From my understanding, the problem is that the Motorola phone does not
deal correctly with the SDP query issued by bluez. I have been trying to
debug sdptool and comparing to other implementations (Symbian seems to
work OK with Motorola) but, as Marcel says, SDP is a horrible protocol.
Has anybody experienced any similar problem?
Thanks,
Pedro
[-- Attachment #2: hcidump_motorola_sdptool.txt --]
[-- Type: text/plain, Size: 2523 bytes --]
< HCI Command: Create Connection (0x01|0x0005) plen 13
bdaddr 00:12:37:86:61:8A ptype 0xcc18 rswitch 0x01 clkoffset 0x0000
Packet type: DM1 DM3 DM5 DH1 DH3 DH5
> HCI Event: Command Status (0x0f) plen 4
Create Connection (0x01|0x0005) status 0x00 ncmd 1
> HCI Event: Connect Complete (0x03) plen 11
status 0x00 handle 41 bdaddr 00:12:37:86:61:8A type ACL encrypt 0x00
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 1 scid 0x0040
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
handle 41 policy 0x0f
Link policy: RSWITCH HOLD SNIFF PARK
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> HCI Event: Command Complete (0x0e) plen 6
Write Link Policy Settings (0x02|0x000d) ncmd 1
status 0x00 handle 41
> HCI Event: Max Slots Change (0x1b) plen 3
handle 41 slots 5
> ACL data: handle 41 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
Connection successful
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 0
> ACL data: handle 41 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
MTU 1024
< ACL data: handle 41 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
Success
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> ACL data: handle 41 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
Success
< ACL data: handle 41 flags 0x02 dlen 24
L2CAP(d): cid 0x0040 len 20 [psm 1]
SDP SSA Req: tid 0x0 len 0xf
pat uuid-16 0x1002 (PubBrwsGrp)
max 65535
aid(s) 0x0000 - 0xffff
cont 00
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
< ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
handle 41 packets 1
> ACL data: handle 41 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
< HCI Command: Disconnect (0x01|0x0006) plen 3
handle 41 reason 0x13
Reason: Remote User Terminated Connection
> HCI Event: Command Status (0x0f) plen 4
Disconnect (0x01|0x0006) status 0x00 ncmd 1
> HCI Event: Disconn Complete (0x05) plen 4
status 0x00 handle 41 reason 0x16
Reason: Connection Terminated by Local Host
next reply other threads:[~2006-03-07 16:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 16:27 Pedro Monjo Florit [this message]
2006-03-07 17:06 ` [Bluez-users] SDP in Motorola phones Marcel Holtmann
2006-03-09 10:49 ` [Bluez-users] " Pedro Monjo Florit
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=440DB456.3030401@yahoo.com \
--to=pmonjo2000@yahoo.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;
as well as URLs for NNTP newsgroup(s).