MobileRead Forums - View Single Post - Glo [Glo HD] Strange files (parsed extention) in kobo-images directory

davidfor · 10-03-2015, 03:03 AM

OK, I have had a look at the database and the cover file name sent. The database has record of 133 books. These break down to:

6 sideloaded books
99 books are purchased from Kobo but are not on the device. Just the details are in the database. Five of these were downloaded on 02/06/2015 and then removed.
28 are recommendations that were downloaded 02/06/2015.

There will be at least one cover image file on the device for each of these books. There should be somewhere between 133 and 432 cover image files. The .kobo-images directory has some other images for thing like the awards.

Based on what you have said, I assume 02/06/2015 is the date you set this device up. Part of that was a sync that downloaded the details of all books you have bought from Kobo and the actual book for five of them. And the recommendations were also downloaded at this time. That is part of the set up of the device. As you haven't done a sync since then, they haven't been updated, but haven't been removed either.

From the sample cover image file names, all of them were referenced in the database. Hence, the image cleaning will not delete them.

The empty directories are because the firmware does not delete empty directories when deleting the books and the cover images. To me, this is the correct behaviour. If you are sideloading books into a directory, then you own the directory, not the firmware. Removing the directory would be the firmware making an assumption about the directory. For the image directories, these are generated as needed. Because of the way this is done, the directory can have cover images for more than one book. And as they will be reused, there is no real reason to remove them. The utilities plugin does remove them, but that was my decision when I wrote the code.

I have run an image clean on my Glo HD and one of the Touch's I have. In both cases, extra images were found. When I checked a few of these, there were no references to them in the database.

As far as I can tell, there is no problem here.

10-03-2015, 03:03 AM	#8
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	OK, I have had a look at the database and the cover file name sent. The database has record of 133 books. These break down to: 6 sideloaded books 99 books are purchased from Kobo but are not on the device. Just the details are in the database. Five of these were downloaded on 02/06/2015 and then removed. 28 are recommendations that were downloaded 02/06/2015. There will be at least one cover image file on the device for each of these books. There should be somewhere between 133 and 432 cover image files. The .kobo-images directory has some other images for thing like the awards. Based on what you have said, I assume 02/06/2015 is the date you set this device up. Part of that was a sync that downloaded the details of all books you have bought from Kobo and the actual book for five of them. And the recommendations were also downloaded at this time. That is part of the set up of the device. As you haven't done a sync since then, they haven't been updated, but haven't been removed either. From the sample cover image file names, all of them were referenced in the database. Hence, the image cleaning will not delete them. The empty directories are because the firmware does not delete empty directories when deleting the books and the cover images. To me, this is the correct behaviour. If you are sideloading books into a directory, then you own the directory, not the firmware. Removing the directory would be the firmware making an assumption about the directory. For the image directories, these are generated as needed. Because of the way this is done, the directory can have cover images for more than one book. And as they will be reused, there is no real reason to remove them. The utilities plugin does remove them, but that was my decision when I wrote the code. I have run an image clean on my Glo HD and one of the Touch's I have. In both cases, extra images were found. When I checked a few of these, there were no references to them in the database. As far as I can tell, there is no problem here.