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

[JSWolf]

This thread belongs in the KOReader forum and not the Kindle Developers forum. Please someone with access move this thread. Thanks.

[jhowell]

Originally Posted by JSWolf

This thread belongs in the KOReader forum and not the Kindle Developers forum. Please someone with access move this thread. Thanks.

The moderator notice in the first post indicates that this thread is specifically for discussion of the Kindle version of KOReader.

[Waylander]

Originally Posted by DNSB

You might want to try the version from https://fw.notmarek.com/khf/. Click on KOReader to download Marek's latest version which has worked for me. So far the ones from KOReader's Nightlies have not worked on my PW4/WinterBreak. As of today, the version from there is koreader-kindlehf-v2024.11-131-g5cd9494ae_2025-01-10.targz (please note the odd targz extension). Under Windows I use 7-Zip to open the file (right-click, 7-Zip => Open archive). You may need to rename it to .tar.gz otherwise.

Many thanks for this. I'll do as you recommend.

[j.p.s]

Originally Posted by JSWolf

This thread belongs in the koreader forum.

Originally Posted by knc1

It is exactly where it should be, read the first post.

Originally Posted by JSWolf

Why is this thread not in the KOReader forum?

Originally Posted by NiLuJe

Something which is plainly explained in the OP, in a giant moderator green card .

Originally Posted by JSWolf

This thread belongs in the KOReader forum and not the Kindle Developers forum. Please someone with access move this thread. Thanks.

Please stop.

(All the above quotes are from this thread.)

[plug313]

hey guys probably stupid question... but how do I see my books in this? I can't find the library? or does this thing work with file system browsing only? I imagined I'd be able to access my kindle books as normal or no?

I'm usually an ace at this stuff and jailbreaking the kindle itself was pretty straightforward... even installing this app. but I'm at a complete loss now. I'm so confused about what to do now with my jailbroken device, besides using it as normal lol I'm so lost

[snake218]

Originally Posted by plug313

hey guys probably stupid question... but how do I see my books in this? I can't find the library? or does this thing work with file system browsing only? I imagined I'd be able to access my kindle books as normal or no?

I'm usually an ace at this stuff and jailbreaking the kindle itself was pretty straightforward... even installing this app. but I'm at a complete loss now. I'm so confused about what to do now with my jailbroken device, besides using it as normal lol I'm so lost

Books are in /documents folder.

But, keep in mind Koreader don't support Amazon file formats, so books in azw, azw3 or kfx won't show in the file explorer.

[plug313]

Originally Posted by snake218

Books are in /documents folder.

But, keep in mind Koreader don't support Amazon file formats, so books in azw, azw3 or kfx won't show in the file explorer.

ah..... thank you for the information! I didn't realize that... pretty much all my books are purchased from amazon, does that mean there's really nothing I can do with a jailbroken device at all in my specific case?

[shamanNS]

Even for book formats KOReader supports it still doesn't support opening books with DRM
So, in order to read any of those Kindle store books you would need to deDRM (remove the DRM protection) them and then convert them into epub format and finally transfer them to be read with KOReader.

[Gabbb]

If as a Kindle pw3 user I decide to live in KOreader what are the battery expectations? Especially if I want to use Koreader's UI for wifi switching, without relying on Kindle's airplane mode?

[stanislav2000]

Hello.
I need help.
I installed koreader-kindle-legacy on my Kindle 3 Keaboard. Everything works, but I would like to ask if there is a possibility to set some of the keyboard buttons for page turning. I found no such option in the koreader Мenu.

P.S. I have CoolReader3 installed on the same Kindle - there is such option by simply editing the keymap.ini file.

[Pichael]

Originally Posted by DNSB

You might want to try the version from https://fw.notmarek.com/khf/. Click on KOReader to download Marek's latest version which has worked for me. So far the ones from KOReader's Nightlies have not worked on my PW4/WinterBreak. As of today, the version from there is koreader-kindlehf-v2024.11-131-g5cd9494ae_2025-01-10.targz (please note the odd targz extension). Under Windows I use 7-Zip to open the file (right-click, 7-Zip => Open archive). You may need to rename it to .tar.gz otherwise.

Thanks for this. I can now finally use KOreader on my Oasis 10th gen.

However, does anyone else have an issue with this version and opening large epub files?
On my Oasis3, when I try to load epubs that are 10MB+ in size, it is painfully slow. I opened a 13MB epub and it took possibly 5 minutes to open.
When I leave the book and try to re-open, I have to go through the same slow 5 minute process every time.

Is there anything I can do about this? For now I converted a copy of the epub to .azw3 in Calibre and am accessing it through the regular Kindle library, but I would love to figure out what the problem is and use KOReader for all my reading.

[BionicGecko]

Originally Posted by Pichael

Thanks for this. I can now finally use KOreader on my Oasis 10th gen.

However, does anyone else have an issue with this version and opening large epub files?
On my Oasis3, when I try to load epubs that are 10MB+ in size, it is painfully slow. I opened a 13MB epub and it took possibly 5 minutes to open.
When I leave the book and try to re-open, I have to go through the same slow 5 minute process every time.

Is there anything I can do about this? For now I converted a copy of the epub to .azw3 in Calibre and am accessing it through the regular Kindle library, but I would love to figure out what the problem is and use KOReader for all my reading.

I don't believe there is a fix for that, unfortunately. It's better than it used to be though - in the past the whole book layout would be recomputed every time the formatting changed, so you would have to wait those 5 minutes every time you changed the font size, margins, etc. Now those calculations are done for the current page first and the rest is done in the background.

I guess the developers would have to implement a similar logic when opening a book (i.e. compute the layout for the last page read, display this page, and do the rest in the background), but that's not how it's done now.

[Frenzie]

It'd also be quite hard to do, and I think generally speaking we prefer it this way.

It drives me nuts when in Nickel it's suddenly not responding because it's loading the next chapter, I press next page again, and then suddenly it turns two pages.

Only that means a gigantic omnibus should be split up a bit into different files.

Size is fairly meaningless by itself btw, if most of it is images for example or even just plain text. It's mainly if you have huge numbers of HTML nodes that performance/memory can be an issue.