Thread: Random, unpredictable failure to connect
View Single Post
Old 07-22-2015, 04:26 PM   #23
NSILMike
Guru
NSILMike turned on, tuned in, and dropped out.NSILMike turned on, tuned in, and dropped out.NSILMike turned on, tuned in, and dropped out.NSILMike turned on, tuned in, and dropped out.NSILMike turned on, tuned in, and dropped out.NSILMike turned on, tuned in, and dropped out.NSILMike turned on, tuned in, and dropped out.NSILMike turned on, tuned in, and dropped out.NSILMike turned on, tuned in, and dropped out.NSILMike turned on, tuned in, and dropped out.NSILMike turned on, tuned in, and dropped out.
 
Posts: 735
Karma: 35936
Join Date: Apr 2011
Location: Shrewsury, MA
Device: Lenovo Android Tablet
Quote:
Originally Posted by chaley View Post
If you exit a program with network sockets open then it usually takes a minute for the program to quit. This is caused by the timeout on the sockets.

If calibre thinks a device is connected via WiFi then the socket will be open. No other device can connect, and calibre cannot quit. If in fact no device is really connected then the problem should resolve itself in 60 to 90 seconds. If a device is in fact connected then it will remain in this state for a long time.

What happens if instead of rebooting the computer you restart the device?
The device is a Nexus 7 (2012.) I tried that a few times when this was happening initially. It made no difference so I gave up on it. Haven't tried it this time...
NSILMike is offline   Reply With Quote