Date: Sat, 23 Oct 2010 14:48:15 -0700 From: Maksim Yevmenkin <maksim.yevmenkin@gmail.com> To: Iain Hibbert <plunky@rya-online.net> Cc: freebsd-bluetooth@freebsd.org Subject: Re: obexapp get failure Message-ID: <AANLkTinU1YpT=kVNHH28fkG2UuMdaRKNWzSmTa4Nq77K@mail.gmail.com> In-Reply-To: <1287857292.298365.1038.nullmailer@galant.ukfsn.org> References: <1287509041.022618.4884.nullmailer@galant.ukfsn.org> <AANLkTimVZRNp8oh9%2BVQ6rPbXXFjdNqpgSQ2AqWjqATJY@mail.gmail.com> <1287561876.893861.6837.nullmailer@galant.ukfsn.org> <AANLkTi=V8pm51C4D58KRsiz0FfhOiU=NnUYGQJdeUwxA@mail.gmail.com> <1287732977.227959.8695.nullmailer@galant.ukfsn.org> <1287738768.915002.8520.nullmailer@galant.ukfsn.org> <AANLkTi=iHT9WOVuNq_VFfWo6R3J1ynkhGBV0s6VkS_Uw@mail.gmail.com> <1287857292.298365.1038.nullmailer@galant.ukfsn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Iain, >> > 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.. =A0I 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) i'm sorry, i don't understand. are you saying that you only able to "get" up to mtu bytes? in other words, if you set mtu to 4096 bytes (in obexapp client) you can only "get" 4096 bytes even though actual file size is bigger than 4096 bytes? >> 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 hmmm.... really? obexapp definitely calls OBEX_SetTransportMTU() in both server and client modes. if that does not work than i must be misusing this call. >> 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.. =A0I blame windows mobile for being trash :) interesting. so it works in one direction (put) but not in another (get). could you please try it with regular windows/linux machine if you have any? i'm curious if this behavior is only demonstrated with windows mobile. also, what is the windows mobile version? thanks, max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTinU1YpT=kVNHH28fkG2UuMdaRKNWzSmTa4Nq77K>