Koreader running on Kobos (all of them, hopefully!)

[mbrisco]

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

[NiLuJe]

No, it's just that we run (by design, for performance reasons; and because of the way our UI loop functions) in conditions that exacerbate potential EPDC issues.

Nickel, on the other hand (by constraint, mostly because Qt), doesn't. So, while similar issues can (and have been) reproduced in Nickel, they should occur much more rarely (if ever for Joe Random) there.

(But this is a much more complex issue, possibly compounded by multiple subtle factors, because we've tried to run in a setup that more closely matches Nickel, and it apparently didn't help).

This is also kind of black box, as I don't have the device myself, so this is based on a few assumptions based on results from remote testing and my own experience with possibly similar issues on other devices (most of which are *also* based on results from remote testing, or on very hard to reproduce stuff that I couldn't get any debugging info out of), and, I'd need a local device with serial access (and possibly a custom debug kernel) to actually say for sure what the hell's happening (or not). And even if I did figure something out (and that's a big if), we probably couldn't do anything about it anyway.

What's for sure is that lab126 took their sweet time to polish a brand new board on a brand SoC for the PW5, but it payed off, as it's been rock-solid and hilariously more efficient than the competition, while the whole slew of boards that NTX put out and ended up in Kobo devices starting with Mk.8 have been... err, let's say *very* rough around the edges, to varying extents...

----

It's a bit early to say anything about the Clara 2E, seeing as we've only seen a single tester on a single device (and the kernel drop isn't out yet... *wink, wink, nudge, nudge*), but it's going... significantly worse than it ever did before ;D. Early days, though, and resolving the more obvious issues might magically make the rest better.

[MartinezzzLV]

So the last update for KOReader is live and I'm wondering what this line mean:

Kobo: Flag all the boards similar to the Libra 2 as unreliable (Clara 2E & Nia) @NiLuJe

https://github.com/koreader/koreader/pull/9691

Does it mean that team has given up on a way to work with a broken kernel of Libra or NiLuJe implemented some additional fixes for stability?

[MartinezzzLV]

Hey NiLuGe, I've seen a new patch note on koreader page:

Kobo: Flag all the boards similar to the Libra 2 as unreliable (Clara 2E & Nia)
https://github.com/koreader/koreader/pull/9691

Does it mean that you have implemented a few tweaks for stability or does Libra 2 and all other devices sharing the same kernel become partially supportable and you guys decided to give up on them?

[NiLuJe]

No changes on the Libra 2, no, that change was aimed at the Clara 2E.

[MartinezzzLV]

Gotcha, thanks! Hopefully, Kobo devs release the stable firmware someday lol

[agile76]

I've searched how to do this without luck.

Can you please tell me if there is a way to invert the page turns buttons, like in Nickel stock using Koreader on my Libra 2?

I'm running the latest stable version of Koreader (version 2022. 11).

It would be great to have an option to make both pages turn buttons go forward, however I don't think this is currently a standard setting in Koreader.

Many thanks.

[NiLuJe]

Check in [Gear] > Page turns > while inside a document.

And see the wiki for how to remap keys.

[agile76]

Originally Posted by NiLuJe

Check in [Gear] > Page turns > while inside a document.

And see the wiki for how to remap keys.

Thanks for the quick reply. I did see the option once but couldn't find it again. I've found it now and my short term solution is to put the invert button option as a gesture.

Thanks for all the work you put into this fantastic software.


Sent from my iPhone using Tapatalk

[ilovedigitalbook]

Hello! I am a new user here and I would like to point out some problems I encounter using KOReader on my Clara 2E. Here I talk about my problem. Any help would be awesome.