[jonathanwardle1992-beep]

Hold UP and tap NO. The screen goes black until the same chord, including while a pattern plays. Other keys and knobs still do their jobs. UP alone and NO alone stay as they are. Version 0.1.0-experimental, kept in sdk/drafts/screen-off/ until it is qualified. It takes key:UP+NO and patches no stock site. The base hands it each key and each composed frame.

The author reports that on a MKII, 7 November 2026, that chord blanks the glass and brings it back, on the RAM trial of screen-off-2.mwrm (OCTATRACK 1.40C, base 671f0afd406290cb). No package hash was recorded. An MKI, the stock saver, a power cycle, cycle counts and a card install are not tried.

What the guides lacked or got wrong: nothing.

• I read the guide for its category in docs/module-guides/ (and sequencing.md if it acts in time), and TESTING.md lists what I did not test. An effect module holds one effect.
• Source and media are mine or properly licensed, with authors and full licence texts kept. Nothing comes from Elektron firmware: no extracted code or tables, upgrade files or factory content, and nothing is modelled on another current Elektron product.
• Screenshots are real captures of the current module UI. Hardware results are what a named person saw on this exact build; emulator results are labelled as emulator results.
• Automatically merge and publish my module update after checks pass.
• I verified the source, licences, UI and qualification reports, including instance isolation and Part/project/reboot persistence where applicable; no required acceptance check is failed or untested.

[repeat98]

Thanks for Screen Off. As with your other modules, I'll review it properly once Threshold Slices (#1285) is done, but two things you can fix meanwhile:

1. TESTING.md has your local Windows path in it, with your user name. Please replace those paths with the package's SHA-256.
2. The package is built from screen_off.c, so please drop screen_off.s and its Linked line in manifest.py. Two copies of the same logic drift apart, and the card build can't run it anyway.

When its turn comes I'll want the usual USB steps on your unit: try then Undo; try, Keep, use it, power cycle; remove it while the screen is black. I'll also want UP held + NO compared with stock in a list, the sample editor, the arranger and the Modwerk status page, and next to a module that draws its own page, such as Tiempos.