|
I also ran into something else when I was loading up my new phone. If I said "send over 6000" books", it would think a long while, start sending, and then fail out after a few dozen books by losing the connection to the device.
I got it to work by sending 700 or so books at a time. It would think less time and then start sending the books. At that point, I could queue another 700 books and send those, and so on. In the end, I had 8 jobs queued up, and they ran one after the other. I've had this issue before with new devices.
Would it make sense to have calibre internally break large send requests into a bunch of shorter ones. As far as I can see, there is no downside to the user, and it fact the entire job will complete faster because whatever preprocessing it is doing before it starts sending can be multitasked with the sending of other books.
Is this a strictly Calibre thing I should post somewhere else, or is this a non-starter and I should just drop it?
|