We also have found a similar issue, that we have identified as a bug in the Android base libraries for specific environments.
We observed that when a socket is forcibly closed by the application while data is still being received, a syntax-related exception can be issued either to the invocation of close() or to the currently blocked invocation of read().
Your case seems to be a variant of the one we got to know.
We are implementing workarounds for these issues in the java client library, to be available upon the next release of LS.
Our online Android demo, whose resources can be found
here, is based on a more recent version of the java client library and we may apply new workarounds on that library sooner.
The latter library is compatible with Server version 3.6 as long as the SendMessage support is not used and may be used as an unsupported preview of the fixed library.
