toltec VS webinterface-onboot

It's just linux under the hood and they give you root access. So you can install anything that you can compile, and you have access to all the compiled packages in entware [0].

For sync, I have wireguard and syncthing. For backups, I use rsync. For epubs, I have koreader. I even installed netsurf for fun, but I don't use it often. I was even using gocryptfs at one point, but that workflow kept breaking with updates so I stopped using that.

All of the tablets that I have seen perform handwriting recognition via a cloud service, so that doesn't interest me and I haven't come across any local solutions for rM (although it's been over a year since I last checked).

It's an unusually nice experience for such an open platform.

[0]: https://toltec-dev.org/

3.x support will come to toltec, I've been blocked by stuff outside of my control a couple of times. Including things happening in my life that I won't get into.

You can see the current progress here: https://github.com/toltec-dev/toltec/issues/820

As for the comment on the kernel change, that was actually an ask by someone in the community: https://github.com/reMarkable/linux/issues/8

I love seeing work in this space! I made a collaborative whiteboard app for the reMarkable a while ago: https://github.com/fenollp/reMarkable-tools

It is packaged in the homebrew Toltec repo https://toltec-dev.org/

Remember to read the warning on Toltec home page:

- https://toltec-dev.org/

Do you ever plan to put your own tools and stuff on it? If so I would reccomened staying on 2.15 so you can use https://toltec-dev.org/. Also newest version 3 software forces infinite scroll and a lot of people absolutely hate it. I happily stay on 2.10. You can change versions as well, unofficially. Not sure if using the cloud still works with that, lots of us have cut that out entirely.

Definitely start by installing toltec if your device is on version <=2.15.1.1189, https://toltec-dev.org

The only other active binary hacks I'm aware of are rM-signature-patch and webinterface-onboot. Those are to solve specific issues though, they do not modify anything you may see. They can both be applied after ddvk.

While no longer enabling the web interface setting is great, the real magic is in what is now possible. The web interface keeps running when the usb cable is disconnected, which means that it still has the ability to upload and download files, there is just no way to connect to it. But now that we can ensure the web interface is always running and accessible via webinterface-onboot and webinterface-persist-ip, we can write programs that connect to the device over wifi but can still use the web interface under the hood. This is useful as uploading a file to the device most any other way will require restarting the device to see the file, and work is still being done on programs that can generate pdfs from the new file format (the web interface can). As a first step in that direction, I created..

- This program will not start/enable the web interface nor ensure that the usb interface maintains the ip 10.11.99.1 [WebInterface-OnBoot](https://github.com/rM-self-serve/webinterface-onboot) does this for version 2.10 but I do not have the newest software to test against. Using something like [webui_invincibility.sh](https://github.com/reHackable/scripts/wiki/webui_invincibility.sh) with [WebInterface-OnBoot](https://github.com/rM-self-serve/webinterface-onboot) would ensure that [WebInterface-Wifi](https://github.com/rM-self-serve/webinterface-wifi) works on boot.