181–190 of 253 posts
It's also great for jailbroken Kindles.
Earlier quoted context omitted.
I’m a heavy KOReader user and absolutely adore it, but I think it definitely trades user-friendliness for power and flexibility. The Kindle proprietary store has a far more user friendly UI imo, though it’s getting progressively worse (and the fact that kindles now default to showing you the store pisses me off to no end). KOReader plugins really close the gap though.
I jailbroke my Kindle and moved to KOReader last year, primarily to get away from the Amazon jail. Just the bare KOReader UX was pretty utilitarian. It lacked polish for sure. I'll have to agree that, as noted elsewhere, the KOReader menus can be difficult to get a grip on. If you're working at just the most basic level of functionality, I don't think KOReader is necessarily worse than native Kindle. The latter is ha…
Earlier quoted context omitted.
Because most of the page is dark, with light only coming from the text, the total light emitted is much less. That makes it less annoying to my wife, when I'm reading before going to sleep.
Eink doesn't emit light.
problem for me was that they vendor like 30 different dependencies in a totally bespoke way that's largely incompatible with any modern package management: it downloads them as part of ./configure (IIRC) and with no way for the OS to provide its own. so you're either stuck using the prebuilt releases without any means to patch/improve the software, or if you do want to make improvements then it's a full-time job to keep the package in a buildable state. in the end that was too much work for me and i switched to Foliate: it's noticeably slower (webkitgtk) and lacking, but it's way simpler to develop on.
maybe they've improved the build system in the last couple years, though a quick peek shows that the nixpkgs expression is still using the binary release. if it becomes practical to build from source in the future i will 100% switch back to it.
I'm immensely thankful for koreader - it improves the reading experience so fundamentally that it literally drives my purchasing decisions. I got a remarkable 2 precisely because it was known to run it well. When I got a new kindle, I went for a refurbished one hoping it'd be one FW version behind (it was! lucky me) so I could jailbreak it immediately, and run koreader. Which reminds me: - I'm still a primitive user.…
I really like that this exists, but I found the menus and UI to be rather non-intuitive. My main use case was to sync reading progress between my Kobo and my iPhone. I was able to do this using KOReader on the Kobo & the Readest app[1] on iPhone (also open source). Ultimately I decided to get rid of KOReader because it felt a bit laggy. The gestures (eg: swiping up on the left side to increase frontlight brightness)…
I really appreciate that KOReader is an option. On my older Kindle (first-gen Paperwhite), the default reading experience had declined until page turns take several seconds. Firmware update and factory reset wouldn't fix it. Using the default reader just wasn't a viable scenario. I jailbroke it, launched KOReader, and it's like I have a new e-reader. The amount of customizability gets kind of in the way, but once it'…
My only real complaint with KOReader is that the book browsing UI is file and folder based by default, while virtually all other ebook readers support some kind of cover based library view you can sort 20 different ways based on metadata rather than filenames etc. It's not a huge issue, but I find just browsing my collection to find a read a lot more enjoyable on other ebook readers. IIRC there are plugins to add thi…
I have one of those Android e-books and it's nice to find good software. Anyways I just wanted to read using the least possible resources so I'm just using a simple file manager and mupdf (in which KOreader is based). mupdf may be simple, but it's amazing.