View Single Post
Old 07-06-2018, 08:41 PM   #623
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by Mrs_Often View Post
The "out of order" display was due to an incorrect(ly interpreted) format in the SyncTime/Date Added.

Did you sideload the left most book before or after updating your device?

If before, have you tried removing and re-sideloading the anchored book? You can also manually remove the book from the home screen (tap-hold, remove, remove from home screen [or similar words with the same meaning]). That will fix the visible part of the issue, but not the date format issue.

By the way, the left most book is supposed to be the one that gets its cover shown in sleep mode. It's just, the most recently read book should be promoted to the left most position (because of the most recent date change).
Sorry, I should have said, but this fixes the cause of the problem. The problem was caused by an error when the books are imported. Books already on the device with the problem will still suffer from it.

To fix it for the books already on the device, either remove them and add them again, or if you are a calibre user, use the metadata update function of my Kobo Utilities plugin to fix the date. Otherwise, if you have any SQL skills, you can fix them yourself.
davidfor is offline   Reply With Quote