MobileRead Forums - View Single Post - Best way to delete a lot of side loaded books

MacEachaidh · 07-14-2012, 11:11 AM

G'day Danger,
Thanks for taking the time to reply!

OK, so I got brave and did a bit of experimenting. Backed up all the files in the .kobo/images folder to a folder on my PC, and then deleted every single one from my KT. Stopped the USB connection, unplugged ... and didn't even get a "processing" screen. I got my Home screen, at first with just placeholder rectangles for the recent books, and then about five seconds later the screen refreshed with the cover images. So those graphics had obviously been created anew by the KT.

I paged through my Library; each new page took roughly 3-4 seconds to display, and then it showed all the covers correctly, so again the files were newly created. Paging back through the Library again once the images had been created was near-instantaneous for each page, so I'm pretty sure the delay was only in drawing the image files each time.

Anyway, I'm happy. I now have far fewer files in my images folder, so I guess this is something that can be done as a spring-clean process every now and then. (Of course, the ideal would be if the KT cleaned up all traces of any books that have been deleted from its system.)

A couple of things I noticed:

1) The new graphics filenames aren't hashed the way the older ones were; they now have the book's title in their filename, making them somewhat easier to identify. (Mind you, these are sideloaded epubs, not kepubs, so the file name of the epub also reflects the book's title. Even so, under FW 1.9.17, these image files' names were hashed, so this seems to be a change in how they're handled by Kobo.)

2) Each cover image file generated by FW 2.0.0 is actually slightly smaller than the cover image generated from the same epub under FW 1.9.17, so there's a bit of space-saving to be had by regenerating them. Not huge amounts, but a bit.

So, all turned out well.

07-14-2012, 11:11 AM	#10
MacEachaidh Browser Posts: 745 Karma: 578294 Join Date: Apr 2010 Location: Australia Device: Kobo Touch, Kobo Aura HD	G'day Danger, Thanks for taking the time to reply! OK, so I got brave and did a bit of experimenting. Backed up all the files in the .kobo/images folder to a folder on my PC, and then deleted every single one from my KT. Stopped the USB connection, unplugged ... and didn't even get a "processing" screen. I got my Home screen, at first with just placeholder rectangles for the recent books, and then about five seconds later the screen refreshed with the cover images. So those graphics had obviously been created anew by the KT. I paged through my Library; each new page took roughly 3-4 seconds to display, and then it showed all the covers correctly, so again the files were newly created. Paging back through the Library again once the images had been created was near-instantaneous for each page, so I'm pretty sure the delay was only in drawing the image files each time. Anyway, I'm happy. I now have far fewer files in my images folder, so I guess this is something that can be done as a spring-clean process every now and then. (Of course, the ideal would be if the KT cleaned up all traces of any books that have been deleted from its system.) A couple of things I noticed: 1) The new graphics filenames aren't hashed the way the older ones were; they now have the book's title in their filename, making them somewhat easier to identify. (Mind you, these are sideloaded epubs, not kepubs, so the file name of the epub also reflects the book's title. Even so, under FW 1.9.17, these image files' names were hashed, so this seems to be a change in how they're handled by Kobo.) 2) Each cover image file generated by FW 2.0.0 is actually slightly smaller than the cover image generated from the same epub under FW 1.9.17, so there's a bit of space-saving to be had by regenerating them. Not huge amounts, but a bit. So, all turned out well.