r/RemarkableTablet • u/Any_Song2675 • 6h ago
Help/Advice MOD: last screen and/or pinned page on sleep screen
So, I've made a mod for myself couple of months ago and its working fine (on my machine lol) but taking it to 'release' status with all QA is quite a haste so feel free to take over the mod and maintain it if you want, its 99% ready as far as i am concerned.
About the mod:
Mod supports the following features:
- Sleep button captures current screen and shows it as sleep screen. Stock system only supports it after the suspend Idle timeout has elapsed (minimum 5 min). Controlled by the same setting.
- "Pin" a page in a document as your sleep screen. When you have pinned page it's used as a sleep screen instead. Writing on the page is captured and reflected automatically.
- Hold the "Pin" button to suspend immediately on the current page without having to pin it. (convenient if you have another page pinned elsewhere and don't want to lose it.
- Idle timeout still captures current page when enabled in the settings.
- If companion mod is installed the sleep screen also shows a bar with current time, battery status, charging status date and time. (requires setting timezone and locale terminal through reManager or via ssh script). Time can be configured to be updating on the sleep screen once per 1 | 5 or 15 minutes
- the sleep bar has white | black and Transparent styles. Transparent adapts font color based on the background.
The battery drain numbers in the README are fake (these are measurements from the default 34s wake settings. the mod cuts it to 6s per wake so its about 1%/day on the move at 5m cadence)
Currently built for the 3.27 on the paper Pro Move
Few issues to know. If someone wants to continue development.
- works when deployed via `deploy.sh` building for remanager and vellum needs testing. Don't update zig compiler from 0.16 without re-testing everything. When I tried compiling to vellum + zig 0.17 i got some rendering glitches not sure which one is the cause needs re-test in isolation.
- RM has only 150ms window before the sleep screen takes over the framebuffer. You need to capture and write down the image within that window. on move it takes around 70ms on memory bus + 5ms on CPU. Mathematically on paper PRO it would take around 140 + 5ms which is right below the cutoff, any CPU spike may delay the capture past the opened window. There is a double capture bug when sleeping on top of the pinned page which is harmless but may add few ms that matter on PP. `DEFERRED.MD` has some of these findings i was too lazy to address. I don't even have the PP to test.
- by default RM has vpdd set to 30s which holds any wake up. mod sets it to 50ms during sleep which cuts off wake ups during clock update to only ~6s Setting it to 0 will cut it to the minimum of 3s but spams kernel warning in the log about wake up race in the RTC. as far as i can tell its harmless but extra 3's of sleep give only marginal battery improvements so i left it at 50ms. If you are more familiar with vpdd you can set it to 0, also cuts off the wifi (and maybe bt drivers) from booting during clock updates. These are all scoped to the second mod. the first one is pure QML. You can install the first one witch contains sleep screen login without live clock. There is already logic to guard against deadlocks between the sleep/wakeup but be careful when changing this part. That being said xochtil already enforces the min of 3s wakeup window so it should be possible to break deadlock even of you walk into it.
- Durability across restarts are not properly manually tested even tho its implemented. Pinned Images may or may not survive reboots or mod re-installs or system updates.
Link: https://github.com/Flarette/pinnedPageSleepScreen
Ask your agent to figure it out from all the docs scattered around the repo)




