Quote:
Originally Posted by davidfor
I just reread your original post, and there is something more going on.
Firstly, when I first insert the SD card with some books on it, after the processing has finished, the library tile shows the count of new books added and tiles for three (I think) of the new books. After dismissing these tiles, removing the card and inserting it again, only the library tile is redisplayed. It shows however many books were on the SD card as new. The same thing happens after a power off or connecting and disconnecting from the PC.
What you describe makes me thing there is a database problem. If the processing screen is displayed each time, then it definitely is corrupt. But, it could be a smaller problem in the database affecting just the table used for the tiles.
You can do a check of the database from a PC. If you use calibre, my Kobo Utilities plugin has an option to check the database. Though there is a fair chance that calibre will report an error when it sees the device and tries to read the database. Otherwise, you need an SQLite browser and execute "PRAGMA integrity_check". If it returns "OK", the the database is fine and the problem is elsewhere. Anything else and the database is corrupt.
|
I don't get the processing screen when I boot with the uSD card installed. There is a couple of minutes delay when the dancing squares freeze before the boot process continues which is much better than the delays with 2.5.x but 2.4.1 had no delay at that point in the boot cycle.
After a power cycle, the only tile for a book on the uSd card is when the currently being read book is on the uSD card. The library tiles shows shows all the books in the library as being added, Any tiles for books on the internal storage are still present as well as Reading Stats, Sync and Recommended (if they were visible before the power cycle).
The database checks out okay after the boot so I don't think it is a database issue. Not a big issue to me at this time since I don't power cycle my Aura very often but still something that I'm hoping is addressed in the next firmware revision.
Regards,
David