View Single Post
Old 03-20-2017, 07:22 PM   #3
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 roycymru View Post
With the rush of updates recently I thought one of the long term bugs would have been resolved but hasn't, namely if you use a sleep cover, on first wake up areas of the text are not as dark as then should be, because a faint image of the books cover is still displayed in the background. Can't recall others reporting this remaining bug but it definitely still occurs on my Aura H2O
That's due to how e-ink works. As changes are made on the screen, it doesn't do full refresh. As you use the device you will see faint remnant of the previous screens. This isn't as noticeable on the newer devices, but is still there. On the Touch, it can get bad quickly. Because of this, the device occasionally does a full refresh which clears everything. When reading, the default is every six page turns but it can be changed in the settings.

The cover remnants staying after waking is because a full refresh is not done during when the device is woken. This has changed a couple of times over the firmware versions, but in the versions that have done a refresh, there were a lot of complaints about the extra flashing as the device wakes. And as you can force a refresh by opening and closing the menus (tap to bring them up, tap to close them), and the affects aren't as noticeable on newer devices, Kobo have probably decided not to do the refresh.
davidfor is offline   Reply With Quote