Quote:
Originally Posted by gsparks2
ok, thanks.
What I am seeing is:
Connect CC to Calibre as wireless device.
|
At this point, no metadata is exchanged?
Quote:
Select books in Calibre to send to device.
Calibre sends books to device.
Calibre sends metadata to device.
<<connection lost for any number of reasons>>
Reconnect CC to Calibre as Wireless device.
CC sends metadata of every book to Calibre.
|
This is very significant. More below.
Quote:
Calibre analyzes books on device.
Calibre sends metadata back to device.
|
Calibre sends all metadata?
CC sending all metadata to calibre implies that the device book cache in the driver in calibre is corrupt. In this case it throws it away and asks for a new copy. The only way I know that it could become corrupt is for calibre to run out of memory or disk space.
Are you running calibre x64?
Are any of your drives running low on disk space? (I don't remember what OS you are running?
Possibly. Most of the underlying causes were fixed long ago. On the other hand, Gingerbread devices tended to be light on memory, and Gingerbread memory management is rather flawed, so we could be running into out-of-memory cases. These will be noted in CC's log file, and if they happen during connections then the connection is usually rudely and abruptly broken.
If you don't mind, the best way to proceed here is for me to see debug logs both from calibre and from CC. Instructions are in our FAQ answer
How do I get help? Please remove the multipie.co.uk address when you send CC's debug log. No need to bring my son into this.