Quote:
Originally Posted by kaufman
Just deleted everything out of the library and cleared CC and tried it with internal memory and it failed after 80 books.
It doesn't look like its an SD issue.
|
My original version N7 was upgraded to kitkat. It doesn't have an SD card so I can't test that. However, given that it is failing for you working with main memory, that I can test.
Three times I sent 1400 books, once with an empty database and twice overwriting. I could not make it fail. I conclude that there is something "special" either with your network setup or with LG's version of KitKat.
First, some questions:
- Calibre is running on what sort of machine? (OS & version). Mine is Win7 Pro.
- How is the machine running calibre connected to the network? Mine is by cable. If by wifi, what band & protocol is it using?
- What sort of network setup do you have? Mine uses a central fiber optic router connected to a gigabit switch. All devices go through the switch. My N7 is connected to a Netgear DG834G running in access point mode.
- What wifi band/protocol is your LG using?
What I am looking for is something that could explain what I think we are seeing; the traffic is being flow controlled somewhere, causing the connection to behave erratically.
Second, a request: given that you can make it fail reliably, could you do it while making a calibre (not CC) debug log? You shouldn't need to clean out the library again.
Sending the books again should be sufficient. My goal is to see which error calibre's networking reports, which might give a clue about where the problem originates.