tree a8465a750da0f44f2ebc2485fe8a2de805cf1f58
parent ee1dc6221fc9193fb135386244e61e557a07260d
author Anders Petersson <anders3.petersson@sonyericsson.com> 1288161510 +0200
committer Jaikumar Ganesh <jaikumar@google.com> 1288221239 -0700

Bluetooth OBEX timeout problem.

Long time to show notification of file transfer failed after
canceling transfer via remote part.

Device A is in contact with our device, B. When device A Cancel
a transfer operation, it sends OBEX_OPCODE_DISCONNECT HeaderID
and the length of package to B. B use the length of package to
read remainder bytes from A. If the bytes B read do not meet the
received length it will block and wait for remainder bytes from A.
But when B compute the remainder bytes it forgets to subtract
the three bytes it has already read through HeaderID and the length
of the package. So the operation was blocked until the operation
timeout.

Change-Id: I0f8bf62d3119e081b5c01af9fc05fe586fd4fabc