Quote:
Originally Posted by chaley
At this point, no metadata is exchanged?
This is very significant. More below.
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. |
On your first question, the sequence begins with no books on device before sending books to device, so no metadata transfer.
Not all Metadata is resent. Just most of it. (this time 14900 of 16057).
I will send debug logs. It may be tomorrow as I am in a lengthy run of calibre sending metadata to device. If/when it stops again I will send logs.
Device is the Android Gingerbread device. Device has 512 MB ram and 16 GB internal with 13.3 GB free. Book files are going on 16 GB external SD card with 6 GB free after loading 16057 books.
Calibre is x64 latest version 2.26
My PC runs Windows 7 Professional with 9 GB ram and first gen core i9 processor. while processing, calibre is using 1.1 GB memory. PC has ~5 GB memory in standby.