zlacker

>>ffaser+(OP)
reMarkable just open-source your display drivers and E-ink render stack please. I'm pretty sure the pressure curve issue can be solved just by tuning a few parameters in the code. I appreciate reMarkable for adhering to GPL and giving us trivial root access to the machines, but while you're there I really don't see why you don't just do it fully.

Even with the limited amount of usability, the community has already made some amazing additions, for example KOReader. Imagine how far we'd get if we can just write any app we want for reMarkable. I would completely get a typefolio and ditch my laptop if I have the ability to *easily* write my own app on the reMarkable without going through the loops of binary patching and other quirks.

>>GZGavi+ffc
I'm not sure how that hasn't been done already. They're running linux so the drivers and kernel changes should be covered by gpl.

>>scheme+cVc
The display driving code is part of their "xochitl" binary, which is not GPL (and might not be allowed to be, eink-the-company is rather protective of their tech and waveforms). ~All modding happens by reverse engineering the binary to call into that code, either to change behavior (rmhacks) or to act like a display driver for other software: https://github.com/ddvk/remarkable2-framebuffer

The rest has been released a few times, though last I checked it was quite out of date. Far from ideal, but still significantly better than most companies: https://developer.remarkable.com/