From owner-freebsd-bluetooth@FreeBSD.ORG Sat Oct 23 18:07:57 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 87700106564A for ; Sat, 23 Oct 2010 18:07:57 +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 1E23A8FC12 for ; Sat, 23 Oct 2010 18:07:56 +0000 (UTC) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3524.me.freeserve.com (SMTP Server) with ESMTP id 0E6291C00087; Sat, 23 Oct 2010 20:07:55 +0200 (CEST) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3524.me.freeserve.com (SMTP Server) with ESMTP id F2EFC1C0008B; Sat, 23 Oct 2010 20:07:54 +0200 (CEST) Received: from rya-online.net (unknown [89.194.144.242]) by mwinf3524.me.freeserve.com (SMTP Server) with SMTP id CA9691C00087; Sat, 23 Oct 2010 20:07:53 +0200 (CEST) X-ME-UUID: 20101023180753829.CA9691C00087@mwinf3524.me.freeserve.com Received: (nullmailer pid 1049 invoked by uid 1000); Sat, 23 Oct 2010 18:08:12 -0000 Date: Sat, 23 Oct 2010 19:08:11 +0100 (BST) To: Maksim Yevmenkin In-Reply-To: References: <1287509041.022618.4884.nullmailer@galant.ukfsn.org> <1287561876.893861.6837.nullmailer@galant.ukfsn.org> <1287732977.227959.8695.nullmailer@galant.ukfsn.org> <1287738768.915002.8520.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: <1287857292.298365.1038.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: Sat, 23 Oct 2010 18:07:57 -0000 On Fri, 22 Oct 2010, Maksim Yevmenkin wrote: > > 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? > > hmmm... interesting.... > > could you please try to lower obexapp mtu? i.e. use -m command line > switch. try to set to something like 16k-32k and see if it makes any > difference. alas, no improvement - in fact it always seems to break when we hit the MTU even if I reduce it to 4096 (which is what the phone normally uses) > there is an OBEXAPP_BUFFER_SIZE which is set to 65536 by > default. but, i think, it might be wrong. it probably should be set to > OBEX_MAXIMUM_MTU (which just happens to be set to 65535 in my version > of openobex library). the actual buffer size doesn't seem to have any relevance here as obexapp offers MTU of 65535 in any case > i did not make any changes in this area recently. i recall doing > torture testing when i was transferring 4mb+ files between 2 unix > machines and between unix and windows machine without any problems. Its not fatal because I can send files without a problem, it is only the 'get' that doesn't work.. I blame windows mobile for being trash :) regards, iain