View Single Post
Old 06-07-2022, 06:28 PM   #78
rtiangha
Evangelist
rtiangha ought to be getting tired of karma fortunes by now.rtiangha ought to be getting tired of karma fortunes by now.rtiangha ought to be getting tired of karma fortunes by now.rtiangha ought to be getting tired of karma fortunes by now.rtiangha ought to be getting tired of karma fortunes by now.rtiangha ought to be getting tired of karma fortunes by now.rtiangha ought to be getting tired of karma fortunes by now.rtiangha ought to be getting tired of karma fortunes by now.rtiangha ought to be getting tired of karma fortunes by now.rtiangha ought to be getting tired of karma fortunes by now.rtiangha ought to be getting tired of karma fortunes by now.
 
Posts: 495
Karma: 356531
Join Date: Jul 2016
Location: 'burta, Canada
Device: Kobo Glo HD
Quote:
Originally Posted by NiLuJe View Post
Nobody's answered me on that front in the related KOReader GH issue, FWIW.
I just read this comment and that's the EXACT same behavior I get on my Glo HD sometimes, both in nickel and in koreader. Funny thing is that I've had this device since 2016 but only really noticed this happening more frequently during the pandemic after a firmware upgrade (can't remember which one; I think it was in the 4.20s). And it looks like the Glo HD kernel was updated in that timeframe, so maybe there's a connection? In the meantime, to work around it, I disabled dithering in the developer settings which helps a bit, but not all the time.

Anyway, I recently imported a couple of books whose covers or images manage to consistently power off my device. Inspired by this thread, I tried changing the governor to ondemand and I was able to get past the cover on one of those books. With the other one, I couldn't get past things unless I also disabled dithering. If I had more samples, I'd see if performance would work consistently with dithering on, but I don't.

No idea what that all implies though.

Last edited by rtiangha; 06-07-2022 at 06:44 PM.
rtiangha is offline   Reply With Quote