How to upgrade?

[JSWolf]

@pazos do you maybe know why @CyberPaul's attempt to upgrade via KOReader is failing?

[pazos]

Originally Posted by JSWolf

@pazos do you maybe know why @CyberPaul's attempt to upgrade via KOReader is failing?

Is not failing. He is on last stable, with stable channel, checks update and receives "no updates available". If he changes the channel to nightly he will be prompted with an update.

Then press update and enjoy. If he finds issues with that then plese report and attach logs.

[CyberPaul]

Now I’m on the last stable version but previously I was on march version and it wasn’t allowing me to update within koreader. After that I upgraded it manually and now it is not finding a new stable as expected.

[CyberPaul]

Originally Posted by pazos

Some books are just broken.

You can ignore predefined font family without disabling the entire css with styletweaks. The one you need is in "text" -> "fonts an line height" -> "ignore predefined font families"

https://github.com/koreader/koreader/wiki/Style-tweaks

This solved it, thanks.
I don’t think the ebook is broken, it is just imposing the font.

[pazos]

Originally Posted by CyberPaul

Now I’m on the last stable version but previously I was on march version and it wasn’t allowing me to update within koreader. After that I upgraded it manually and now it is not finding a new stable as expected.

You're on last stable. When you check for updates you receive the "no updates available". That's intended until a new stable is published.

You can wait for the 2022.06 release and try to update with OTA.

Or you can test now by switching the channel to "nightly" and update right now. If you do so then you can downgrade again to last stable by switching channel again to "stable" and performing an update.

Anyhow there're not issues with OTA updates. Otherwise we will be flooded with github reports as pretty much any KO user uses that specific feature.

The only issues I'm aware are with a few pocketbook devices that are unable to use wireless properly when running in KO. But that again doesn't mean an issue with OTAs per se, but an issue that makes impossible to use whatever network service the program provides.

[CyberPaul]

Maybe my installation was broken. I will try with next stable version.
Thanks

[JSWolf]

Originally Posted by CyberPaul

Maybe my installation was broken. I will try with next stable version.
Thanks

Try on a different WiFi network in case maybe your ISP is blocked or your ISP is blocking the server. Try to download the latest nightly for your test.

[CyberPaul]

Installed June stable version succesfully.

[CyberPaul]

Unfortunately bluetooth is still a disaster on Kobo
Not working when in koreader (e.g. page turner), and most importantly, once back to nickel BT is stuck, and the only remedy is to restart the device.

[jasius]

Originally Posted by JSWolf

You have two options. You can reinstall KFMon every time there is a new firmware update or you can add a line to your NickelMenu config to run KOReader direct from NickelMenu.

Doing this via NickelMenu means you don't have to reinstall KFMon every time you update the firmware.

#menu_item : main : KOReader : cmd_spawn : quiet : exec /mnt/onboard/.adds/koreader/koreader.sh

Does this still work?

Does the Kobo Libra base firmware impact how KOReader runs on the Libra, if there are upgrades in Nickel that impact battery life or something, does that translate into KOReader?

[NiLuJe]

Originally Posted by jasius

Does this still work?

Yes.

Originally Posted by jasius

Does the Kobo Libra base firmware impact how KOReader runs on the Libra, if there are upgrades in Nickel that impact battery life or something, does that translate into KOReader?

It depends. Kernel updates could help (or hurt ;p), but fixes that are purely userland (with the exception of base system updates, which are *extremely* rare, much to my dismay) obviously won't.

Kernel updates are usually reserved for the current lineup of devices, so your OG Libra probably won't ever see one again.

[jasius]

Originally Posted by NiLuJe

Yes.



It depends. Kernel updates could help (or hurt ;p), but fixes that are purely userland (with the exception of base system updates, which are *extremely* rare, much to my dismay) obviously won't.

Kernel updates are usually reserved for the current lineup of devices, so your OG Libra probably won't ever see one again.

Thank you for the response.

I have a Libra 2, I just drop the 2 because I forget that it's a sequel.

[jasius]

Originally Posted by NiLuJe

Yes.



It depends. Kernel updates could help (or hurt ;p), but fixes that are purely userland (with the exception of base system updates, which are *extremely* rare, much to my dismay) obviously won't.

Kernel updates are usually reserved for the current lineup of devices, so your OG Libra probably won't ever see one again.

Sorry for asking again, so I put that line of code into the file "koreader" in the folder E:\.adds\nm correct?

Edit: I made a file called "config" and put it in the \.adds\nm folder with that line and it still gave me "Generator Error" when the kobo Libra 2 finally rebooted when I clicked on Nickel Menu.

[NiLuJe]

You failed to mention what you were starting from, so I have no idea what you've actually done.

The original quote assumed starting from an OCP install, which *already* ships all the required config shards.