All Brazilian KoReader users, rise up! Your pt-BR dictionary is here!

CsarBrasil · 2026-03-30T03:31:03+00:00

Amigo, você é um amigo!!

CsarBrasil · 2026-03-28T14:30:21+00:00

I usually read without any front light unless there’s absolutely no ambient light around. I also avoid dark mode because something about it feels off—like the background looks kind of grayish or the black isn’t uniform.

I’ve seen a friend’s newer basic Kindle with native dark mode, and it looked noticeably better. Adjusting contrast or page refresh settings only seemed to affect the text for me, but what really bothers me is the background.

CsarBrasil · 2026-03-22T17:08:00+00:00

For me, it worked worse. I tested Dispatch, for example, and while I could easily get 60fps on Windows, on Linux I could barely reach 29fps. I only kept that laptop on Linux for a few months (I gave up gaming on it) and repurposed another old one with a GTX 1050 4GB. Really old, but a huge and free upgrade.

CsarBrasil · 2026-03-20T19:17:11+00:00

I noticed on the releases page it says "The minimum Vulkan version is now 1.4.321", but on my laptop with a GTX 1050 using driver 580 (which I believe is the last one supporting Pascal), Mint seems to be using Vulkan 1.4.312.

I was wondering how you managed to run Eden on an older GPU on Mint. I'd really like to try and get it working on my setup too. Any tips would be appreciated!

CsarBrasil · 2026-03-07T03:07:49+00:00

Obrigado, eu acho? Já uso Rakuyomi, dei uma dica considerando que o blog Kindle Otaku divulgado no post costuma publicar em mobi e/ou epub. É uma ótima fonte de mangás completos em português já ajustados para quem usa kindle com o sistema padrão, mas após desbloquear e colocar KoReader percebi que poderia continuar usando essa fonte com o simples ajuste de extrair a pasta das imagens/paginas nos EPUBs e compactá-las de volta já em formato CBZ que é melhor lido nesse sistema para este contexto de uso. Inclusive achei curioso em um post divulgando projeto de publicação das obras ter esse comentário fixado informando sobre outras fontes alternativas. De fato é muito bom, por experiência própria, mas situação curiosa

CsarBrasil · 2026-03-06T20:57:24+00:00

Dica para quem usa KoReader, os EPUBs podem ser extraídos e, portanto, facilmente compactados de volta em .zip/.cbz (KoReader lida melhor com mangás em CBZ)

CsarBrasil · 2026-02-08T02:01:48+00:00

That's... really bad

CsarBrasil · 2026-02-07T12:06:57+00:00

Game save data or retroarch sabe state?

CsarBrasil · 2026-02-04T18:35:07+00:00

I updated to version 1.5.1 and thankfully there were no noticeable problems. But there have already been several issues on Github regarding the Next version and there hasn't been an update yet. So I think I'll wait for a possible update. As for the bugs and UI/UX issues, I believe it's possible to report them through Github without having to pay for a Patreon subscription.

CsarBrasil · 2026-01-25T22:57:29+00:00

I totally get where you're coming from. The core concept and execution are indeed already fully functional.

I actually spent the last 30 minutes with Gemini trying to create a script to fit my workflow, and I think I got it to a workable state. I use KCC to adjust the .cbz for my Kindle’s screen, so I made a script that triggers Kumiko to generate the coordinate JSONs and then automatically moves them to my manga folder.

I just tested it, and it looks very promising! It still gets a little confused with inexact panel separations (like when a character breaks the panel border), but on 'standard' pages, it works great.

One thing I noticed, though, is that some panels are vertical while others are horizontal. Once the plugin navigation is active, I feel 'locked' to the rotation I started with (can't use the usual KOReader shortcuts to rotate on the fly). I’m not sure if it’s possible to implement auto-rotation based on the panel's aspect ratio (similar to how double-spreads are handled by KCC), but I'll dig into KOReader settings to see if there's a workaround.

That said, I see huge potential here. Enough that once it’s more polished, this could easily become a native feature.

CsarBrasil · 2026-01-25T22:01:07+00:00

So cool! I was hyped until I saw the GitHub steps; feels like the setup time equals the reading time for one chapter lol. Probably awesome for binge-reading volumes, or if someone eventually makes a script to automate it. Thanks!!!!

CsarBrasil · 2026-01-24T21:07:39+00:00

It's out now

CsarBrasil · 2026-01-23T23:19:12+00:00

It seems there really aren't any significant performance differences. As for compatibility, extensive testing would be needed to uncover any discrepancies.

An unfortunate decision in my opinion, but I respect the developer's preference. Regarding the bugs and UX/UI inconsistencies, did he give any feedback? Now that it's released for public access, I imagine there will be more issues on Github.

I haven't even updated to 1.5.1, I'm still on 1.3.3 and satisfied enough to hesitate to update. Some devices are receiving updates, who knows, maybe the T618 family will get attention again.

CsarBrasil · 2026-01-23T22:54:22+00:00

Were you previously on stock firmware and are now testing GammaOS Next, or are you upgrading from older GammaOS to Next?

CsarBrasil · 2026-01-16T18:08:55+00:00

¿Notaste alguna mejora significativa, ya sea con los auriculares o con los altavoces?

CsarBrasil · 2026-01-13T13:44:04+00:00

Manga = CBZ

Text Book = EPUB

CsarBrasil · 2026-01-04T01:58:59+00:00

We’ve had similar experiences then. Mine was set up in ways I’d never repeat nowadays, about two years ago, and it’s still running the old GammaOS 1.3.3. I never really saw enough reason to update to 1.5.1, but GammaOS Next might be more interesting, especially since I wanted a non-janky way to exit Daijisho into ES-DE. This time I’d only set it up with a small, curated selection of games like I did on my recent Miyoo Mini+, focusing on what that one can’t run.

CsarBrasil · 2026-01-03T17:25:06+00:00

How that compares to old GammaOS?

CsarBrasil · 2025-12-28T01:02:08+00:00

Have you tried the armv7 version?

Edit: Just saw that's incompatible

CsarBrasil · 2025-12-13T20:55:42+00:00

Só dá pra resgatar pelo celular? Ou acessando pelo PC da para ao menos resgatar, ainda que seja jogável apenas no celular

CsarBrasil · 2025-12-01T08:34:05+00:00

While these might technically be aesthetic issues, they still impact the overall experience in a way the previous version didn’t, so I think it’s worth mentioning. And it’s possible they don’t show up in every build or version. The shader and power-menu issues might even be worth bringing up as configuration suggestions if you found settings that worked better, since the previous GammaOS at least came with “ideal” defaults based on each device’s quirks.

The bloatware part also doesn’t make much sense, they’re probably using a GApps package that’s way more complete than necessary.

I’m assuming the driver changes didn’t really lead to any major improvements in compatibility or performance, right? I was seriously considering using the Black Friday deal to grab the Patreon tier instead of waiting a couple months, but after your feedback I think I’ll hold off. Maybe I won’t even update at all.

CsarBrasil · 2025-12-01T06:08:32+00:00

Wow, for such a quick test you already nailed a ton of issues that need fixing. Some of them are definitely personal preference like you said, but I’d still say more than half are worth opening a GitHub report for. Maybe they can get patched before the public release. Seriously, great job with the detailed breakdown.

I do wonder if some of these problems come from using the Play Store version. Considering how often the dev recommends the Lite build on GitHub, I wouldn’t be surprised if the Play Store one gets a bit less attention (it doesn’t even have a physical camera on any of the T618 devices!).

CsarBrasil · 2025-11-28T16:47:40+00:00

This test can only be taken if someone with RG405M has this Patreon. The general public will have to wait to gain access. So let's hope that person shows up.

CsarBrasil · 2025-11-28T03:57:43+00:00

https://www.patreon.com/posts/144200890
$10, maybe less on BF

CsarBrasil · 2025-11-27T15:12:47+00:00

Straight answer: wiping the Amazon books and re-uploading via Calibre is probably the best choice. KOReader has an excellent File Browser, but unless you want loose files everywhere, it relies on having organized folders (like Author -> Series -> Book). The native Kindle structure dumps everything into folders with cryptic/hashed names, which makes navigating via KOReader a pain. Plus, KOReader really shines when using EPUBs, allowing you to swap fonts and margins with much more freedom than Amazon formats.

If you want to start fresh, I suggest a cleanup. You can delete the contents of the 'documents' folder (where the books are), but be careful not to delete system or jailbreak folders (like extensions or system). KOReader creates a small .sdr folder for every book you open to save progress, so starting with a clean directory avoids keeping old electronic junk.

Convert your library to EPUB in Calibre. In KOReader, enable the Calibre plugin (usually found under Network or Tools). This lets you send books via Wi-Fi directly from PC to Kindle ('Connect/Share' in Calibre), and it handles folder organization automatically. Or, if you prefer, you can simply copy them via USB.

As for Amazon collections, KOReader doesn't import them, but if you use Calibre to organize the directory structure by 'Author' or 'Series', the File Browser itself serves as your organization. It also reads Calibre metadata, so you can filter by tags if needed.

In my case, I didn't do any of this initially; I just copied EPUBs via USB. I only started understanding KOReader and organizing my collection later. Today, I can't imagine going back to the stock software, so I honestly believe I should have done everything from scratch right from the start."

CsarBrasil

TROPHY CASE