Quote:
Originally Posted by mathuin
My theory (and I'm only a novice Android app developer, so take it for what it is) is that the CC connection code has a bug keeping it from letting go of the connection, and that connection state is persisting which is why rebooting is the only way to make the app let go of that socket.
|
An app cannot keep a socket open that has been closed by the operating system. It get an exception every time it tries to use a disconnected socket. CC uses this exception to reset the connection. The CC debug log will show this happening, assuming it does.
Sending 144MB in 37 seconds is reasonable performance.
Is there any chance that you are running out of space on the device?
I look forward to receiving the CC debug logs.