Koreader running on Kobos (all of them, hopefully!)

[Frenzie]

Most values seem to be hardcoded, e.g., here. But if might be better to provide some information about what you're trying to accomplish? Just because the program is a certain way doesn't mean it's set in stone.

[pblasi]

Originally Posted by Frenzie

Most values seem to be hardcoded, e.g., here. But if might be better to provide some information about what you're trying to accomplish? Just because the program is a certain way doesn't mean it's set in stone.

Well I'd just like to set a more useful range of contrast values for the font I'm using in my epubs and according to my taste. For example, a range of 0.9 to 2.0 with 0.1 step would be better to me. So, if it's hardcoded, it means I cannot change this preset values?

In general for the entire UI, and in addition to to existing graphical preset-based GUI, having option to enter an exact value with a numerical pop-up keyboard would be great (as long-pressing is for info, let's say double-tap to enter exact value, as an example). That would open the doors of fine tuning control for those who want it but keeping the GUI clean and simple. With all the customization power and features koreader has, I think this little feature would be a very well integrated and nice addition. I don't know where's the place to make this kind of suggestion...

Thank you!
Pau

[Frenzie]

Originally Posted by pblasi

Well I'd just like to set a more useful range of contrast values for the font I'm using in my epubs and according to my taste. For example, a range of 0.9 to 2.0 with 0.1 step would be better to me. So, if it's hardcoded, it means I cannot change this preset values?

You can set anything you want in defaults.persistent.lua or settings.reader.lua. It just means you can't (persistently) adjust what you can set through the GUI.

[pblasi]

Originally Posted by Frenzie

You can set anything you want in defaults.persistent.lua or settings.reader.lua. It just means you can't (persistently) adjust what you can set through the GUI.

Sorry I'm missing something... How can I set a contrast of 1.3?

[Frenzie]

There's https://github.com/koreader/koreader...aults.lua#L101 and kopt_contrast for settings.reader.lua.

[pblasi]

Originally Posted by Frenzie

There's https://github.com/koreader/koreader...aults.lua#L101 and kopt_contrast for settings.reader.lua.

Well, for epubs at least, modifying https://github.com/koreader/koreader...aults.lua#L101 does not change contrast default.

Then, I guess you mean "copt_gamma" for "kopt_contrast" (in settings.reader.lua), but here the value is 15 when in GUI corresponds to a contrast of 1.0. Then setting a gamma of 18 results in a good contrast level (unknown 1.?) to me.

Thanks.

[Frenzie]

Yes, copt_ is for crengine and kopt_ is for paged media.

[gothi]

Hey there fellas,

Would it be possible to refresh the screen multiple times per page turn? I've noticed that with my old Kobo Aura, a single refresh just isn't enough to "clean" the screen and ghosting and artifacts remain. What I'm doing as a workaround at the moment is to do a force refresh using a swipe gesture just after a page turn. It's not really that inconvenient but I was just wondering if there's an easier way of forcing 2 (or more) refreshes per page turn. I've scoured the config files and I've checked online but I couldn't find any info about this.

With my new Kobo Forma, I don't have these ghosting/artifacts even after a refresh every 10 pages but on my old beloved Kobo Aura, which I still like to use on the train, it is just very evident.

Any help would be greatly appreciated. Thanks!

[NiLuJe]

Not currently, no. You'd probably need a flashing white screen between pages, more than a double-refresh, as refreshing the same content twice is likely to do more harm than good, although that's less apparent on text than on mixed content .

The Aura was an odd duck in Kobo-land, as far as refreshes are concerned. You could try disabling explicit REAGL calls (basically, set that to false in the phoenix block near the bottom of ffi/framebuffer_mxcfb.lua).

[gothi]

Originally Posted by NiLuJe

You could try disabling explicit REAGL calls (basically, set that to false in the phoenix block near the bottom of ffi/framebuffer_mxcfb.lua).

Thanks, man! Tried this out but I don't think it makes any (noticeable) difference at all. Is this the same as disabling Regal in Nickel's developer options?

[Frenzie]

Originally Posted by gothi

Is this the same as disabling Regal in Nickel's developer options?

It's likely comparable. Why, do you see a bigger difference in Nickel?

[NiLuJe]

Note that the Nickel dev options are sometimes misleading (in that you may see a toggle for something the hardware doesn't actually support).

As the Aura is a very peculiar beast as far as REAGL is concerned, I can't be sure of what that toggle does without a strace (or, barring that, the eink bits from the syslog, possibly).

[gothi]

Originally Posted by Frenzie

It's likely comparable. Why, do you see a bigger difference in Nickel?

I would say they're about the same. It's as if the page is not refreshing fully. Some parts of a text is noticeably darker. A force refresh in Koreader fixes it though, making everything on a page look even/consistent.

[serdar0020]

I just tried to upgrade from 2019.08 to 2019.09.3. I always launch the Koreader with fmon. This time I couldn't exit from the Koreader, but got a crash report. Only a reset and re-install of 2019.08 helped

[Frenzie]

Without knowing what the crash report said that's a bit hard to judge. Could be https://github.com/koreader/koreader/issues/5356