HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
ddvk
remarkable2-framebuffer
C2020–2026
ddvk / remarkable2-framebuffer

remarkable2-framebuffer

remarkable2 framebuffer reversing

7Distinct people
10Mentions
0Explicit recommenders
312GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

remarkable2 framebuffer reversing

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year10 dated mentions

Observed mentions: 2020-11-17 16:28:34 UTC to 2026-06-03 11:15:36 UTC.

012342020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC404
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC202
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC202

What Hacker News says

10 sources
Nice. That latency is tough though. On that topic, I wrote an equivalent "magic mirror" type tool that lets you write to the mirror/oracle/VLM on the remarkable and get an answer back. A few possible solutions I explored: 1) You can try and consume (and possibly write to) the frame buffer directly. https://github.com/ddvk/remarkable2-framebuffer was my starting point. This gets you instant updates about what's going on. I guess you could pair this with speculative decoding to get a much faster output. 2) You can use the streaming API on the device to stream the screen to a beefy server, possibly over Tailscale, letting you do everything off device. 3) You can write your own Qt app; ddvk's repos are a good starting point here. I ultimately instructed claude to write me my own app. Which worked enough to scratch my itch, and I never use it.
Read the rest
But this was five months ago, an eternity in vibe hobby projects, so perhaps modern tooling would let me get it in shape and be more usable. Basically, it worked, but VLMs weren't great at what I wanted -- decorating a blank page with a grimoire-style answer to a written question while leaving the original text alone -- and getting it started / stopped from the pen UI is difficult. Where my mind goes for your project is that I think it'd be nicest to keep a sort of Jupyter notebook somewhere that's the canonical representation, that would have your handwritten blocks and an interpretation, and then the output. then a render layer to get it back onto the screen. At that point, I don't think I'd care very much if it's stored as a PDF on the device, which points back to having this be an app. Either way it's fun to tinker! the RM line is very hackable, and I still wish it were even easier, the hardware just makes you think of so many possibilities.
In Show HN: Edsger – A handwritten Clojure REPL for the reMarkable 2
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/
In Remarkable Pro Colors
Usually the reason is that people want to continue using the built-in interface with just some additions, instead of replacing and maintaining a separate installation. It would be nice if someone were to start working on an aftermarket linux distribution/ecossytem that targets eink devices. It's a lot of work to do, though, so I'm not surprised that nobody has picked up that torch yet. Some notes on the reMarkable, it is running a custom linux distribution that is based on Openembedded Core[0]. The company publishes their modifications to the linux kernel[1], so one person has created their own linux distribution for the original reMarkable tablet [2]. The reMarkable 2 currently has no native framebuffer driver for the screen, due to it being software controlled by the UI application, which requires a workaround for custom applications[3]
Read the rest
In E-ink is so Retropunk
OP here. thanks for all the comments. some more info: rmkit is a library (and group of devs) for creating apps on the rM (and now Kobo). outside of rmkit, people typically use Qt to write apps, but there's many routes[0], including SAS[1]: a solution that uses unix pipes. the rM2 requires a bit more hacking to get working than the rM1 because their framebuffer driver[2] is embedded in their software for rM2 and requires updating rm2fb every time remarkable releases a new update. there's alternative drivers[3] to drive the display in development. i will keep updating the article based on feedback, thank you and keep hacking [0]: https://remarkable.guide/devel/index.html [1]: https://rmkit.dev/apps/sas [2]: https://github.com/ddvk/remarkable2-framebuffer/ [3]: https://github.com/matteodelabre/waved
In E-ink is so Retropunk

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.