View Single Post
Old 09-26-2022, 08:14 PM   #3466
mbrisco
(gtfo/freak)
mbrisco ought to be getting tired of karma fortunes by now.mbrisco ought to be getting tired of karma fortunes by now.mbrisco ought to be getting tired of karma fortunes by now.mbrisco ought to be getting tired of karma fortunes by now.mbrisco ought to be getting tired of karma fortunes by now.mbrisco ought to be getting tired of karma fortunes by now.mbrisco ought to be getting tired of karma fortunes by now.mbrisco ought to be getting tired of karma fortunes by now.mbrisco ought to be getting tired of karma fortunes by now.mbrisco ought to be getting tired of karma fortunes by now.mbrisco ought to be getting tired of karma fortunes by now.
 
Posts: 115
Karma: 2288752
Join Date: Nov 2019
Device: Likebook Alita
Seeing as the new Clara 2E is running the same CPU as the Libra 2, I wonder what the KOreader experience will be like on it.

@niluje Thank you for writing that explanation for me, even though try as I might, even as a developer myself, I couldn’t parse most of the technical jargon of it From what I understand, the Libra 2 stock UI (Nickel) tries to work around the problems by slowing down the latency, while KOReader runs in real time and thus has problems. Is that what you meant? And Nickel also uses Autostandby, which KOReader doesn’t by default because it causes stability issues? If I got that right, then why doesn’t the autostandby cause these issues in Nickel too?

I don’t quite understand how stock Nickel can run so well but KOReader has a hard time: it seems like either it’s not worth optimizing KOReader for the i.MX6SLL chip like Nickel has, or KOReader has to run on top of Nickel and the i.MX6SLL can’t handle both. Is it one of those? :P
mbrisco is offline   Reply With Quote