remarkable2-framebuffer VS 37reader

Looks like rm2fb is now installed by default: https://github.com/ddvk/remarkable2-framebuffer/issues/90

We can currently hook into it, but only to obtain the framebuffer or send updates ourselves. 3rd party mods use remarkable-framebuffer which does the injection and easily enables 3rd party community apps/mods to use the screen.

Is is safe? there are issues like this or this

Instructions here, at the end of the "Configuration" section. Please not, however, that these settings were only added to the rm2fb repo 11 hours ago (commit). So again, best to check that up-to-date settings exist before upgrading your firmware.

It's an eInk screen, so yes-ish.

We get around this by just piggybacking on the build in application's screen display routines[0]

https://github.com/ddvk/remarkable2-framebuffer

Have you installed rm2fb? https://github.com/ddvk/remarkable2-framebuffer

This seems to have updated all the installed components. In particular, rm2fb is now on the latest release which, if I'm understanding correctly, supports 2.9. ("Support for release 2.9.0.210")

At one point I had a post on reddit about it, but I ended up deleting that. However my post did get scraped by hackster.io so here is the link to their post. https://www.hackster.io/news/diy-e-reader-incorporates-mecha... and here is my github. https://github.com/bwkrayb/37reader

Doing a write up has been a plan of mine for a while now lol I bought a 3d printer to move on from the gutted airpods box and a case has been in a half printed state just waiting for me to design the rest of it. I've run into a creative wall and haven't gotten much further.