I have looked through the logs and, unfortunately, nothing jumps out.
Some things I can say:
- Regarding reconnnects: you said
Quote:
|
At this point, the server no longer saw the mobile device as being connected while the mobile device thought it was still connected. Hitting 'disconnect' on the mobile device caused a dialog box to be displayed, reporting an unrecognized error during the connection progress and instructing me to try again. However, the mobile device cannot successfully reconnect to the server unless it is power-cycled -- force-stopping the application does not resolve the issue.
|
The logs show that every time the app was restarted the connection succeeded. None of the failures to connect were preceded by an application start. This makes me wonder whether the force-close actually closed the app. There isn't any evidence that it did. CC will close itself if you hit the back button enough times for it to ask "do you want to quit"? However ...
- The failure to connect after the failure to send is caused by your device not being able to "see" the wireless driver on the calibre computer (connection timed out), not because CC already has the socket open. Neither the UDP broadcast to find calibre nor the TCP connection to calibre succeed. This implies that the network stack in the operating system of your device is borked, because clearly after power-cycling the device both the broadcast and the connection work.
- I successfully transferred a 269MB PDF and a 552MB PDF to my Kindle Fire 8.9. Calibre is running on Win7/64. The transfer times were 3:37 and 7:24.
- The logs imply that the device went to sleep during the transfer, around 10 minutes into the transfer. For the failing book, as far as I can tell the transfer began at 2015-01-02 11:54:46. Calibre timed out 5 minutes 40 seconds later and closed the connection. Approximately 12 minutes after the start, apparently the device went to sleep. A minute later it was awakened, and 30 seconds later CC received a socket-closed exception. This means that CC was told about the socket being closed a full 7 minutes after calibre closed it. How this could happen is a mystery to me.
I am not sure how to proceed here. I can't repeat the problem, and the logs imply that the error was somewhere between CC and calibre. I am not happy with this conclusion. I would like to know *why* it is breaking.
Question: can you transfer the failing book using the content server? it uses different networking code both in calibre and in CC.