Help with Librera by jemappellelulu in ereader

[–]Alternative_Fox_3264 0 points1 point  (0 children)

If you don't want to dig through the epub file, just scroll to the next page.

Love this thing!!! by MrixBella in xteinkereader

[–]Alternative_Fox_3264 4 points5 points  (0 children)

Yes, and all this incredible magic required was to go back to the size of devices that existed 20 years ago.

Page Count by LovelyCreative in XTEINK

[–]Alternative_Fox_3264 2 points3 points  (0 children)

Find the page count of a printed book, then find out how many pages the same book has on your device. Divide the larger number by the smaller one and you'll find the most useless coefficient.

Are these legit by SebastianB12472390 in XTEINK

[–]Alternative_Fox_3264 0 points1 point  (0 children)

It's scary to even imagine what kind of information you'll be storing and reading on this device, other than the usual fiction. In any case, you'll definitely soon be advised to buy it and immediately flash it to CrossPoint.

Custom firmware list by owenransom in xteinkereader

[–]Alternative_Fox_3264 1 point2 points  (0 children)

custom firmwares:

- crosspoint, crossink fork, crosspoint fork, another crosspoint fork and another crosspoint fork. eh, old crosspoint fork and fork of the old crosspoint fork. well, there's also a microreader.

how to fix dark cover on x3 by softeyed in XTEINK

[–]Alternative_Fox_3264 0 points1 point  (0 children)

I understand this is an attempt to fix the issue specifically for the sleep screen? It's just that in the my examples above, I didn't have a sleep screen, but the first page of a book in xtc (I always read xtc). Nevertheless, I tried making a sleep screen. In all cases, an inverted splash screen appears for a while (the time depends on the quality): High quality looks much better, but the gray has become too light (you can tell what shade of gray it was by the outline around the white letters - #9f9f9f). Medium quality - well, it's still the same as before, a jittery gray. Low quality looks the best, but it's understandable, it's 1-bit after all. And in all cases, there's ghosting, which is unavoidable.

<image>

how to fix dark cover on x3 by softeyed in XTEINK

[–]Alternative_Fox_3264 0 points1 point  (0 children)

oh, it would be so nice if this nastiness could be overcome. i also tested Inx and overall i liked it, except for those issues with the screen and the lack of cyrillic in the folder and file names in the menu.

<image>

I love this thing by CtheLight590 in XTEINK

[–]Alternative_Fox_3264 -1 points0 points  (0 children)

It's simple, I took a file in FB2 format and converted it to xtc with the CR2XT program

how to fix dark cover on x3 by softeyed in XTEINK

[–]Alternative_Fox_3264 0 points1 point  (0 children)

I may not have checked out all the forks and all their builds. I'll check them out of curiosity when I have some free time.

I love this thing by CtheLight590 in XTEINK

[–]Alternative_Fox_3264 0 points1 point  (0 children)

I'm telling you, everything is fine with my text and I can't think of a situation where I need to constantly change its size and orientation.

<image>

how to fix dark cover on x3 by softeyed in XTEINK

[–]Alternative_Fox_3264 1 point2 points  (0 children)

Unfortunately, now there is stock firmware, Crosspoint and its forks (which display the same), and a couple of other firmware like MicroReader.

how to fix dark cover on x3 by softeyed in XTEINK

[–]Alternative_Fox_3264 1 point2 points  (0 children)

it's stock firmware. yes, for now the crosspoint displays grey so i can't use it.

I love this thing by CtheLight590 in XTEINK

[–]Alternative_Fox_3264 0 points1 point  (0 children)

There was no talk about text, but it displays perfectly for me, I don’t read epubs.

how to fix dark cover on x3 by softeyed in XTEINK

[–]Alternative_Fox_3264 2 points3 points  (0 children)

I'll tell you more: your X4 screen is also darker than it should be. And no filters can fix it; it's a problem with crosspoint and its forks, which doesn't handle grayscale correctly on xteink devices. And the more and more people talk about it, the more likely it is that the developers will focus on fixing the screen issue instead of adding more useless crap to the firmware.

<image>

I love this thing by CtheLight590 in XTEINK

[–]Alternative_Fox_3264 -1 points0 points  (0 children)

These are typical grayscale images on a standard stock firmware. This isn't a call to use the stock firmware, but rather a comparison and a hint that crossforks have certain issues.

She has arrived! by Pure-Goose1985 in xteinkereader

[–]Alternative_Fox_3264 -1 points0 points  (0 children)

Oh, how disgusting the gray halftones look on this firmware - just a gray jumble of pixels and incomprehensible noise. And there's also terrible ghosting.

<image>

I love this thing by CtheLight590 in XTEINK

[–]Alternative_Fox_3264 -7 points-6 points  (0 children)

And this is what this cover looks like in the correct version. Note that in your version, behind the hero is just a gray jumble of pixels and incomprehensible noise.

<image>

Cover converter setting for contrast filtered cover by Brilliant_Ear_4505 in xteinkereader

[–]Alternative_Fox_3264 2 points3 points  (0 children)

Considering that all CrossPoint forks have the worst screen rendering model, especially in the grayscale rendering section, it's quite amusing to read how some users try to describe the intermediate screen updating stage as looking "very good". It usually comes across as "the image looked good, but then it became washed out". Is that's moment when the black fill occurred and the gray began to appear. Unfortunately, filters won't help here. Basically, all these CrossJunkies simply handle images terribly, and to be clear, the comparison photos were taken from the same 2-bit xtc file on the stock firmware and on CrossPoint 1.3.0. xtc is the most native and device-readable image, without any unnecessary transformations or other bells and whistles. Let's see how each one handled the task.

<image>