Kindle -- KOReader: a document reader for PDF, DJVU, EPUB, FB2, HTML, ... (GPLv3)

[bears]

Hi everyone, I have a question regarding a Kindle Voyage with ads running Kindle OS 5.13.6 with KUAL e3deabf(20220213,a)-KV and KOReader 2022.07.

I know there have been lots of problems with the haptic page turn buttons on these devices, but I haven't been able to find any information regarding this specific case. After the device goes to sleep with KOReader running, if I awaken it with the power button, the haptic buttons do not respond until I exit and relaunch KOReader. However, if I plug the device into my computer via USB the device wakes up and the buttons are responsive. This does not happen if I plug it directly into the wall.

Launching KOReader with the standard launcher or the ASAP launcher has the same result.

Is this a known issue with a workaround? At this point I'm not sure which program is the culprit, KUAL, KOReader or Amazon's own software.

Any insight is greatly appreciated, thanks!

[NiLuJe]

We don't have a maintainer with that device, so I'm afraid I can't give you a definitive answer either .

[tomsem]

Question: is there some way to download KFX files from calibre server using KOReader (i.e. to read with the Kindle app)? It seems only to download formats support by KOReader.

Seems like it would be an easy modification to KOReader calibre client, but thought I'd check before looking into it further.

[pazos]

Originally Posted by tomsem

Question: is there some way to download KFX files from calibre server using KOReader (i.e. to read with the Kindle app)? It seems only to download formats support by KOReader.

Seems like it would be an easy modification to KOReader calibre client, but thought I'd check before looking into it further.

Yes. You need to create a file called "calibre-extensions.lua" on koreader data dir.

It should contain a list of extensions. Calibre assumes the list is in the desired order.

Here's an example of such file:

return {
    "epub",
    "fb2",
    "mobi",
    "azw",
    "xps",
    "doc",
    "docx",
    "djv",
    "djvu",
    "pdf",
    "cbz",
    "htm",
    "html",
    "xhtml",
    "pdb",
    "prc",
    "rtf",
    "txt",
    "md",
    "chm",
    "zip",
}

You just need to add the extension you want at the top of the table.


Aaaaaaaand, before you asked: Nope, there're no plans to add an UI to it. But if you want to do the job then patches welcome.

[tomsem]

Originally Posted by pazos

Yes. You need to create a file called "calibre-extensions.lua" on koreader data dir.

It should contain a list of extensions. Calibre assumes the list is in the desired order.

Here's an example of such file:

return {
    "epub",
    "fb2",
    "mobi",
    "azw",
    "xps",
    "doc",
    "docx",
    "djv",
    "djvu",
    "pdf",
    "cbz",
    "htm",
    "html",
    "xhtml",
    "pdb",
    "prc",
    "rtf",
    "txt",
    "md",
    "chm",
    "zip",
}

You just need to add the extension you want at the top of the table.


Aaaaaaaand, before you asked: Nope, there're no plans to add an UI to it. But if you want to do the job then patches welcome.

Thanks! For Kindle a KUAL extension for calibre client would probably be better, but not sure one exists. In meantime, this should do what I want.

I'll look into doing a patch.

And maybe there's a way to patch the Kindle browser to allow .kfx download if jail broken.

[jasius]

What file/folder are my reading preference settings(line spacing, page number, font size, font weight) stored in on my Libra 2? I want to do a fresh install of KO Reader but have my reading preferences like line spacing and fonts and page numbers kept.

Can someone just give me a straight forward answer as to what files I need to save to keep those settings.

[mbrisco]

Originally Posted by jasius

What file/folder are my reading preference settings(line spacing, page number, font size, font weight) stored in on my Libra 2? I want to do a fresh install of KO Reader but have my reading preferences like line spacing and fonts and page numbers kept.

Can someone just give me a straight forward answer as to what files I need to save to keep those settings.

Default settings applied to all books are kept in the settings.reader.lua file in the KOReader root folder. Per-book settings are kept in each book's .sdr file alongside it, wherever it is. If you haven't modified a default for a given book, that setting will not be kept in the .sdr file.

[jasius]

Originally Posted by mbrisco

Default settings applied to all books are kept in settings.reader.lua. Per-book settings are kept in each book's .sdr file alongside it.

So if I find that file, save it and then transfer it back onto my e-reader all my reading preferences will come right back?

[mbrisco]

Originally Posted by jasius

So if I find that file, save it and then transfer it back onto my e-reader all my reading preferences will come right back?

updated what I wrote to clarify: if you haven't modified a particular setting for a book, that won't be reflected in the individual .sdr folder for the book. So if you're confident that you haven't modified any default settings, only a per-book setting, then simply keeping that .sdr folder will restore your settings for that book. If you *have* modified any default global settings, you have to bring along the settings.reader.lua file as well (but that also brings a lot of other KOReader settings, and I understand you want to get rid of those)

[jasius]

Originally Posted by mbrisco

updated what I wrote to clarify: if you haven't modified a particular setting for a book, that won't be reflected in the individual .sdr folder for the book. So if you're confident that you haven't modified any default settings, only a per-book setting, then simply keeping that .sdr folder will restore your settings for that book. If you *have* modified any default global settings, you have to bring along the settings.reader.lua file as well (but that also brings a lot of other KOReader settings, and I understand you want to get rid of those)

So it's trickier than I first thought.

Thank you for following up and clarifying things for me.

[NiLuJe]

On the other hand, if you're just reinstalling KOReader and not doing a factory reset, you don't care about the .sdr folders, as you're not going to touch those.

Just keep a backup the settings folder and settings.reader.lua and you're good.

c.f., my backup script for all the gory details (spoiler alert: it's slightly outdated ;p).

[jasius]

Originally Posted by NiLuJe

On the other hand, if you're just reinstalling KOReader and not doing a factory reset, you don't care about the .sdr folders, as you're not going to touch those.

Just keep a backup the settings folder and settings.reader.lua and you're good.

c.f., my backup script for all the gory details (spoiler alert: it's slightly outdated ;p).

My Kobo Libra 2 always crashes(the screen dims instantly and I have to do a hard reset of the device with the power button) when I plug a USB port in and select "Share" when I have KO Reader in use trying to transfer from a PC, it'll work with Nickel, but not KO Reader, this wasn't always the case, I just need to figure that part out. Is there any particular file that would tell you exactly what's happening?

Also lately when I try to wirelessly transfer books they go into the wrong dir, and I'm not sure how to fix that so the might go in the right place.

Otherwise everything is perfect, if I could just transfer files over USB without the KO Reader crashing instantly, it'd be 100% perfect.

[NiLuJe]

If the kernel hangs, there's nothing your or I can do, as logging in the USBMS tool is not persistant.

The best you can do is monitoring the syslog (logread -f) over SSH via WiFi (in the stock shell only, not ZSH), but it's very very likely the usual Libra 2 EPDC hang, so you're unlikely to get anything useful out of it.

I'm mildly curious if you can pinpoint *when* is stopped working, as that's... stranger (nothing should really have changed much in terms of refresh patterns).

EDIT: Except I just remembered that having Wi-Fi enabled "fixes" the Libra 2 EPDC hangs, so, hahaha. >_<".

[jasius]

Originally Posted by NiLuJe

If the kernel hangs, there's nothing your or I can do, as logging in the USBMS tool is not persistant.

The best you can do is monitoring the syslog (logread -f) over SSH via WiFi (in the stock shell only, not ZSH), but it's very very likely the usual Libra 2 EPDC hang, so you're unlikely to get anything useful out of it.

I'm mildly curious if you can pinpoint *when* is stopped working, as that's... stranger (nothing should really have changed much in terms of refresh patterns).

EDIT: Except I just remembered that having Wi-Fi enabled "fixes" the Libra 2 EPDC hangs, so, hahaha. >_<".

What would be causing the kernel to hang all of a sudden on the Libra 2 when plugging it into USB?

[NiLuJe]

The usual Libra 2/Nia/Clara 2E EPDC shenanigans?