obexapp get failure

Iain Hibbert plunky at rya-online.net
Sat Oct 23 18:07:57 UTC 2010


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




More information about the freebsd-bluetooth mailing list