|
I've started having a strange issue on my Kobo Aura ONE and the catalyst (or one of) seems to have been this latest firmware update.
Basically, something glitches during the cover rendering stage when putting the device to sleep, or when navigating to the cover! The cover renders an intermediary version (often mid some transition) but freezes, never renders the full grayscale cover, and the whole system hangs. The only solution is force restarting the device by holding the power button.
The scenario above is shown in images 1 and 3 in the post attachments. In image 1 I just put the device to sleep and the cover rendering got borked. In image 3 however, I resumed reading a book and navigated back to its cover, and the cover failed to render within the book, freezing the entire system.
This happens frequently, but not every time. Also, as far as I can tell, the system shuts down and renders the cover properly every time (Image 2 attachment shows the same cover as in attachment 1, properly rendered once I held the power button for a few seconds to shut down the system, and Pratchet’s book was the last opened one.)
Obviously, I haven't tested this too many times with many different books because I don't want to force a reboot of the device that frequently, but I’m certain this didn't happen at all before this update. I use patches, but I've been using the same patch-set before, for years, with zero issues.
This also is happening with e-books that I’ve had on the device for years, so it isn’t something new I just added to the library. I sideload all my books, and strive to embed high resolution cover images in all my files, so I am used to Kobo sometimes rendering covers in quadrants, but nothing like this.
I also tried KOReader, and it seems to exhibit the same behaviour, only with pdf and djvu files, which I have it set up for. This is somewhat worrying, as it points towards a hardware issue, unless Nickel and KOReader happen to share the graphical stack that does the cover rendering?
Is this happening to anyone else? Could it be something I've done? I also updated NickelMenu to the latest version (previously it was some older one), but it was successful, didn't require config changes, and either way, IMO this shouldn't really affect sleep or covers?
Is it possible to downgrade to the previous firmware? If possible, is it advisable? I'm not really gung-ho about that prospect, but the device is very inconvenient to use because of this issue. For now I just disabled rendering covers entirely during sleep or shutdown (rendering them non-fullscreen made no difference).
I'm at a bit of a loss here so any advice is welcome. If my device is on its way out I’d still like to know.
|