One-Click Install Packages for KOReader & Plato

[thangnhoc]

Hi All,

I have used instructions from NiLuJe to install Koreader (only, not Plato) onto my Kobo Libra 2 - using script file install.ps1 with OCP-KOReader-v2022.03.1.zip

All good, I can open pdf files and read. But everytime I exit Koreader (either using Exit or Reboot etc), it gets hang up in the middle with the dots and it does not allow me to even reboot using Power button! My current solution is to connect the device to my laptop and reboot while plugging in.

That means I can never read pdf as it will get frozen again if I try to exit from Koreader!

I even try to reset my device twice (2 times) and install Koreader with the above steps freshly - but still giving same issue!

Have any of you get this issue like mine? And is there any fix for that?

Thanks,

[NiLuJe]

Do you have anything else custom installed on the device?

The libra 2 is known to suffer from fatal race conditions related to the EPDC and power delivery, so plugging it in is indeed one known solid workaround.

Since you appear to trip this with the boot spinner, you could also try swapping to the KFMon (on mobile, xrefs are painful, check it's docs) progress bar, but it might not change anything .

[JSWolf]

Originally Posted by thangnhoc

Hi All,

I have used instructions from NiLuJe to install Koreader (only, not Plato) onto my Kobo Libra 2 - using script file install.ps1 with OCP-KOReader-v2022.03.1.zip

All good, I can open pdf files and read. But everytime I exit Koreader (either using Exit or Reboot etc), it gets hang up in the middle with the dots and it does not allow me to even reboot using Power button! My current solution is to connect the device to my laptop and reboot while plugging in.

That means I can never read pdf as it will get frozen again if I try to exit from Koreader!

I even try to reset my device twice (2 times) and install Koreader with the above steps freshly - but still giving same issue!

Have any of you get this issue like mine? And is there any fix for that?

Thanks,

Does Your Libra 2 hang if you exit after only reading ePub?

[NiLuJe]

Early reports seem to hint at 4.32 having put a severe dent on the Libra 2 EPDC crazypants crashes, so you might want to try that once the dust has settled a little bit .

[Uncle Robin]

Originally Posted by NiLuJe

Early reports seem to hint at 4.32 having put a severe dent on the Libra 2 EPDC crazypants crashes, so you might want to try that once the dust has settled a little bit .

A little curiosity on my Sage after installing 4.32. I updated KFMon and restarted KOReader. The usual "launched koreader.sh " message appeared but it took fully 10 seconds before KOReader opened. I've just tried again, and it was back to the usual 1-1.5 seconds, so it seems the unusual lag was a one off. Curious, though

[MGlitch]

Originally Posted by Uncle Robin

A little curiosity on my Sage after installing 4.32. I updated KFMon and restarted KOReader. The usual "launched koreader.sh " message appeared but it took fully 10 seconds before KOReader opened. I've just tried again, and it was back to the usual 1-1.5 seconds, so it seems the unusual lag was a one off. Curious, though

Out of curiosity, why are you using KFMon over NickelMenu? It's my (albeit limited) understanding that NickelMenu is the preferred method. I doubt it'd the cause of the initial lag so this really is just me asking.

[Uncle Robin]

Originally Posted by MGlitch

Out of curiosity, why are you using KFMon over NickelMenu? It's my (albeit limited) understanding that NickelMenu is the preferred method. I doubt it'd the cause of the initial lag so this really is just me asking.

Updating Kobo Firmware disables KOReader, I do as instructed here:



After that, I click on the NickelMenu icon here

[NiLuJe]

@Uncle Robin: That's not a new behavior, FWIW. (Something something sunxi is the worst ).

[Uncle Robin]

Originally Posted by NiLuJe

@Uncle Robin: That's not a new behavior, FWIW. (Something something sunxi is the worst ).

And yet KOReader rises above it I have fully patched my 4.32 and the reading experience in stock is now for me around 85% of that in KOReader. A big jump, but as it's only achieved by a lot of patches that will all need to be reinstalled next FW update, my preferred epub reader remains unchanged - the Kobo FW now good enough to read downloaded kepubs as is

[jasius]

How long is the "importing content" supposed to last? I updated to 4.32 on my Libra 2 and then I used the alternative method to install it, the Powershell script told me it was successful, I ejected the Libra 2 from the PC properly and now it's stuck on "importing content 6%" for quite some time. I hope there's a semi-easy fix.

It's been stuck on 6% for about 5-10 minutes now. Is it fully frozen?


EDIT:
Ok, I had to turn off the kobo Libra and then turn it on again, then I had to reflash the script, that got my KO Reader back, but now in KO reader when I try and use a dictionary is crashes my ereader. Is there a fix for this?

EDIT:

There's a huge issue in the Development build right now, that's what had caused all the issues, switched back to STABLE and now all is good. Weird bugs!

Also sometimes my KO reader had ! with triangles around them for random elements of the GUI.

Also on my Libra 2 theres always been intense LAG in the UI, when I click "Turn on Wifi" it turns on but all the dialogs just quickly flash and go after a few moments of nothing.

EDIT:

It turns out todays' xxxxxxx38 build isn't stable with the newest firmware, but it's great when I switched back to STABLE build.

[vinhphucng25]

I can't install even I unzip or keep the zip file the root directory of Kobo.

[NiLuJe]

@vinhphucng25: Do *NOT* run this from inside the Kobo's volume. It's mentioned explicitly in the docs. Unplug it until the last moment if that's the only way you can prevent yourself from manually dropping files in there .

@jasius: The Libra 2 suffers from pernicious screen driver issues, that's probably what causes most of the issues you've encountered (c.f., https://github.com/koreader/koreader/issues/8414).

[jasius]

Originally Posted by NiLuJe

@jasius: The Libra 2 suffers from pernicious screen driver issues, that's probably what causes most of the issues you've encountered (c.f., https://github.com/koreader/koreader/issues/8414).

Thank you for the quick reply, is there any headway on figuring it out?

[NiLuJe]

Not really, I don't have the device, and it would probably require a serial console to even start having an actual idea of what's upsetting the kernel so much (and that's a maybe to start with, so actually being able to do something about it is another kettle of fish...).

[LivresInOz]

The automatic power-shell installation didn't work for me:

"Couldn't find a Kobo eReader volume! Is one actually mounted?
* Nothing to do! Press Enter to exit:"

The Kobo FORMA was definitely plugged in.