reMarkableScripts VS dpt-canvas

I am using a modified version of this script https://github.com/adaerr/reMarkableScripts/blob/master/pdf2remarkable.sh

Via SSH and bash script

Some scripts here on GitHub: https://github.com/adaerr/reMarkableScripts and https://github.com/simonschllng/rm-sync, with theses scripts, you can upload larger pdf files to Remarkable even the size is more than 1 GB.

You may find some projects on github, e.g. Remy, remt both are python scripts to upload to/download from reMarkable directly. Here is another script in shell to push file to rM.

I just tried the script that SataMaxx uses: https://github.com/adaerr/reMarkableScripts/blob/master/pdf2remarkable.sh and it works. Isn't his solution simpler since it doesn't requires any changes to the bashrc of the rm?

If you are at ease with the command line, pdf2remarkable.sh could allow you to easily push pdfs from your laptop to your rM. You'd need to setup a ssh key to make it easier.

Uploading works fine using https://github.com/adaerr/reMarkableScripts/blob/master/pdf2remarkable.sh

For the Sony DPT, Mooink and Fujitsu Quaderno devices from the Sony spinoff Linfiny, check how this gets faster rewrites on a more limited zone: https://github.com/DPT-RP1/dpt-canvas

> I love the writing feel of E-Ink; the software makes it unusable.

Agreed. It needs specially designed software.

> If anyone reading this is also interested in hacking around on Boox devices, let's talk, maybe: https://gitter.im/boox-users/community

I am.

I recently got a Nova Air C and I'd like to do a few things with it. I'm mostly interested in getting an optimized terminal to use with the rooting feature, to replace the termux frontend by something that'd be better optimized for eink while reusing termux packaged tools.

There seems to be private APIs to do great software, at least on the Sony DPT, Mooink and Fujitsu Quaderno devices from the Sony spinoff Linfiny.

For example, check how this gets faster rewrites on a more limited zone: https://github.com/DPT-RP1/dpt-canvas

A terminal often writes to a small portion of the screen, so everything else could remain static and without ghosting, while this portion of the screen getting new characters would get fast text rewrites, a bit like how you when you write on the notetaking app, it shows immediately yet a bit fuzzy, then it's redrawn later in high quality.

In would require talking to these APIs (so maybe with different modes for different brands like Linfiny/Boox/Remarkable/Kindle) + maintaining a simple map of the terminal screen to do invalidation/refresh as needed.