Paul,
Edit: While writing this, I remembered another post on a similar problem. When I finished, I went looking for it so that I could point to this. Of course it was the same poster. I have no idea why, but the probable cause just clicked into my brain when I read your post this time.
I think I know what is happening, but I don't have my Touch with me to test.
There are three or four different versions of the cover that the firmware uses in different places. Some time ago, Kobo added a new version and it seemed to replace a different file. But, this seemed to be only on the Touch. Because of this, I changed the files the driver generated. Testing on my Glo, it is using the file that I no longer send to the Touch on the for the current book tile on the home screen. I will check this with my Touch when I get home tonight.
If you want to confirm it, you can create the file yourself. The missing image file will be named with the suffix and extension " - N3_LIBRARY_FULL.parsed". The start of the image file name with look like "file____mnt_sd_" The the rest of the name is the file name of the book. The image files are stored on the SD card under "koboExtStorage\images-cache". If you search for the name of the book, you should find three image files. If yo copy the one that ends with " - AndroidBookLoadTablet_Aspect.parsed" to a new file with the same name but ending in " - N3_LIBRARY_FULL.parsed", that will create the file that I believe is missing.
To give some examples. For the book "High Citadel" by Desmond Bagley:
It is in: F:\Bagley, Desmond\High Citadel - Desmond Bagley.epub
The image file to find is: file____mnt_sd_Bagley,_Desmond_High_Citadel_-_Desmond_Bagley_epub - AndroidBookLoadTablet_Aspect.parsed
The image file to copy this to is: file____mnt_sd_Bagley,_Desmond_High_Citadel_-_Desmond_Bagley_epub - N3_LIBRARY_FULL.parsed
These are in: F:\koboExtStorage\images-cache\50\146
The two numbers at the end of the directory change depending on the file name used. That is why I suggest a search.
I will check this when I get to my Touch. If I am right, I'll fix it in the driver. It is an easy change, so it should get be in tomorrows release. Having a confirmation from someone else with a Touch and 3.0.x or 3.1.x firmware would be good.
David
Last edited by davidfor; 12-19-2013 at 01:07 AM.
|