From owner-freebsd-bluetooth@FreeBSD.ORG Fri Oct 22 09:12:58 2010 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C592B106566C for ; Fri, 22 Oct 2010 09:12:58 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from smtp6.freeserve.com (smtp5.freeserve.com [193.252.22.151]) by mx1.freebsd.org (Postfix) with ESMTP id 61EBB8FC0C for ; Fri, 22 Oct 2010 09:12:58 +0000 (UTC) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3528.me.freeserve.com (SMTP Server) with ESMTP id 232261C0008E; Fri, 22 Oct 2010 11:12:57 +0200 (CEST) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3528.me.freeserve.com (SMTP Server) with ESMTP id 14F3B1C0008F; Fri, 22 Oct 2010 11:12:57 +0200 (CEST) Received: from rya-online.net (unknown [89.194.103.211]) by mwinf3528.me.freeserve.com (SMTP Server) with SMTP id C62711C0008E; Fri, 22 Oct 2010 11:12:55 +0200 (CEST) X-ME-UUID: 20101022091255811.C62711C0008E@mwinf3528.me.freeserve.com Received: (nullmailer pid 11556 invoked by uid 1000); Fri, 22 Oct 2010 09:12:48 -0000 Date: Fri, 22 Oct 2010 10:12:48 +0100 (BST) To: Maksim Yevmenkin In-Reply-To: <1287732977.227959.8695.nullmailer@galant.ukfsn.org> References: <1287509041.022618.4884.nullmailer@galant.ukfsn.org> <1287561876.893861.6837.nullmailer@galant.ukfsn.org> <1287732977.227959.8695.nullmailer@galant.ukfsn.org> User-Agent: Alpine 2.00 (NEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Message-Id: <1287738768.915002.8520.nullmailer@galant.ukfsn.org> From: Iain Hibbert Cc: freebsd-bluetooth@freebsd.org Subject: Re: obexapp get failure X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Oct 2010 09:12:58 -0000 On Fri, 22 Oct 2010, Iain Hibbert wrote: > I have one bug-report that I haven't looked into properly, not sure if its > obexapp or my phone (windows mobile 6) that is the problem.. if I connect > to FTRN on phone, using folder browsing service and try GET on a larger > file it fails and loses sync. I've done some tests and the largest file I > can GET is 65528 bytes (can send larger files from either side no problem) > > for example with two files (that are text files full of 'a') > > % obexapp -a touch -C ftrn -f > obex> ls > Access Owner Group Size Modified Name > .. > n/a n/a 65528 n/a test.small > n/a n/a 65529 n/a test.large > Success, response: OK, Success (0x20) > obex> get test.small > 65528 bytes streamed in 4 seconds (16382 bytes/sec) > Success, response: OK, Success (0x20) > obex> get test.large > Failure, response: Unknown response (0x53) > obex> ls > Access Owner Group Size Modified Name > Could not parse XML: (null) > Success, response: OK, Success (0x20) > obex> ls > Access Owner Group Size Modified Name > .. > n/a n/a 65528 n/a test.small > n/a n/a 65529 n/a test.large > Success, response: OK, Success (0x20) > obex> get test.small > 65528 bytes streamed in 3 seconds (21842 bytes/sec) > Success, response: OK, Success (0x20) > obex> dis > Success, response: OK, Success (0x20) > > I guess its something to do with a uint16_t and a small amount of header > but I've no time to look at that until early next week.. looking at the hcidump output for the test.large transaction, < ACL data: handle 13 flags 0x02 dlen 42 L2CAP(d): cid 0x0089 len 38 [psm 3] RFCOMM(d): UIH: cr 1 dlci 8 pf 1 ilen 33 fcs 0x46 credits 6 OBEX: Get cmd(f): len 33 Connection ID (0xcb) = 27 Name (0x01) = Unicode length 22 0000: 00 74 00 65 00 73 00 74 00 2e 00 6c 00 61 00 72 .t.e.s.t...l.a.r 0010: 00 67 00 65 00 00 .g.e.. > ACL data: handle 13 flags 0x02 dlen 11 L2CAP(d): cid 0x0044 len 7 [psm 3] RFCOMM(d): UIH: cr 0 dlci 8 pf 0 ilen 3 fcs 0x80 OBEX: Get rsp(f): status 100 len 65535 Status 100 = Continue Body (0x48) = Sequence length 65529 0000: 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 aaaaaaaaaaaaaaaa 0010: 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 aaaaaaaaaaaaaaaa 0020: 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 aaaaaaaaaaaaaaaa [...] ffc0: 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 aaaaaaaaaaaaaaaa ffd0: 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 61 aaaaaaaaaaaaaaaa ffe0: 61 61 61 61 61 61 61 61 61 0a 61 61 61 61 61 61 aaaaaaaaa.aaaaaa fff0: 61 61 61 61 61 61 61 61 0a aaaaaaaa. < ACL data: handle 13 flags 0x02 dlen 12 L2CAP(d): cid 0x0089 len 8 [psm 3] RFCOMM(d): UIH: cr 1 dlci 8 pf 1 ilen 3 fcs 0x46 credits 6 OBEX: Get cmd(f): len 3 (continue) > ACL data: handle 13 flags 0x02 dlen 11 L2CAP(d): cid 0x0044 len 7 [psm 3] RFCOMM(d): UIH: cr 0 dlci 8 pf 0 ilen 3 fcs 0x80 OBEX: Get rsp(f): status 500 len 3 it seems that the wm6 phone tells us that more is to come, so we issue a continuation get but the phone is only confused.. I don't know if this is done correctly, or can be worked around? iain