visible-sleep-screen : new package

[alefaraci]

visible-sleep-screen sets visible content as sleep screen when "Visible content" (Settings ▸ Display ▸ "Visible content") is ON. It renders the stock screen when "Visible content" is OFF. The device still performs a real deep-sleep.

Optional owner info: if Settings ▸ Security ▸ Personal information is ON, the sleep bar appends Name – Contact.

• Upstream: https://github.com/alefaraci/xovi-qmd-extensions#visiblesleepscreen
• License: GPL-3.0-only
• Arch: noarch
• Depends on qt-resource-rebuilder.
• Device/OS: all devices, remarkable-os>=3.27 <3.28.

Note on hashing: the hashtab is built per-device from that device's own xochitl, so tokens that exist on only one model (the two sleep-window paths, folioClosed, the folio-peek ids) are deliberately left cleartext. Hashing them, I experienced that would make the file unresolvable on the other device, which fails the .qmd and every other installed mod with it. A fully-hashed multi-device .qmd isn't possible apparently; this is the reason the file looks partly cleartext. The whole MainView.qml block is also kept cleartext on purpose. That exact form is the one I device-verified on both models.

Testing

Device-verified end-to-end on:

• ✅ reMarkable Paper Pure (tatsu, aarch64) — xochitl 3.27.3.1547
• ✅ reMarkable 2 (armv7) — xochitl 3.27.3.1547

Not tested:

• Paper Pro (ferrari)
• Paper Pro Move (chiappa)

I don't own either, so I want to be upfront about where they could break:

• ⚠️ A different sleep-window path (most likely). Since binaries are per-device, Pro/Move may use neither qml/tatsu/ nor qml/default/ but a path of their own. Consequence is benign: qt-resource-rebuilder just never matches it, so the sleep screen stays stock: no crash, no impact on other mods. (The MainView.qml block would still apply, also benign: with the stock opaque sleep window on top nothing shows through, so the visible effect is only that the sleep-entry white flash is gone while "Visible content" is ON.) The fix would be one extra AFFECT line reusing the same SLOT, once someone reports the path (or shares their xochitl).

[ingatellent]

To answer the question above: Only the Pure has a special path, and only, I think, on 3.27.

But: This is a very, very large qmd for something that should just be changing, I think I recall, 4 values (and then add a toggle in settings).

The qmd is only partially hashed.

I suggest not including in vellum at this stage.