loading a single book taking too long
 

I lost my entire library because my SD card dropped dead. My PC won't even recognize the card. I went to reload my library to the internal memory and noticed that the process was taking 30 seconds or longer per book. The more books that got loaded, the longer the wait. I finally ended up using USB and didn't have any problems.

I now noticed that loading a single book from the content server is taking quite a bit longer than it used to. I am using a Galaxy Tab A and CC version 5.1.2.4 (331). Any help would be greatly appreciated.

~Dave

See FAQ: http://cc_faq.multipie.co.uk/index.p...=95&artlang=en

See this thread for a long discussion:
https://www.mobileread.com/forums/sho...d.php?t=274054

Thanks for the assist Gsparks2. I followed the above advice and it seems to have fixed my problem. A book will load at about one per second or so. A big improvement.

According to the article: "Android internal memory uses a file system that does not have this problem. It is near constant time regardless of the number of files. This is why we don't see these performance problems when using internal memory."

I am using internal memory. Using the template "{first_author:%1.1s}/{first_author}/{title} - {authors}" and resending my books fixed my problem. I am a little confused but very grateful! Thanks again for the assist.

~Dave :thanks:

I am also confused.

CC will use the SAF for internal memory, but the SAF should use the native file system. If it does not but instead uses something like FAT32 (why? I have no idea) then you will see the behavior you describe. I don't see that behavior on my test devices, but clearly that doesn't say much.

I am considering changing CC to (try to) determine if it has "real" read/write privileges for a folder, and not using the SAF in that case. CC will have these privileges in main memory, and *might rarely* have them for an SD card. If CC does have the right privileges then it can avoid all the SAF nonsense and perhaps offer better performance.

My concern is that any attempt I make might get it wrong and break things. Given that you are seeing behavior I do not see, I think my concern is justified.

My experience with loading to android device internal memory was that it took 0.2 to 0.3 seconds per book.