Lune Bridge by SonoLune

reading device…

Made for nights, not for screens

Light level

Target—
1 · barely lit100

Warmth

Colour temperatureoff
1700K · candle4082K

Flicker-safe mode

Holds the backlight above the point where your panel starts strobing, and takes the rest of the dimming out of the colour matrix instead. If low brightness gives you eye strain or headaches, this is the setting that helps. Costs a little contrast in dark scenes.
PWM knee—
Lower this until flicker stops being visible. The default is a guess, not a measurement — every panel is different.

Device

Re-probe re-checks what this device supports — Night Light, Extra Dim, the panel node, and whether the overlay is actually in effect. It changes nothing; it only refreshes what is shown above.
Reset to stock clears warmth, dimming and flicker-safe mode and puts brightness back to something readable. Hold the button for a second — a screen you cannot read is a screen you cannot use to fix itself, so this one should not be reachable by a mis-tap.
If it ever goes too dark to read: hold that button, or from a computer run adb shell su -c "lunectl reset". Removing the module restores stock display settings on its way out, and holding Volume Down during boot disables every module.

Report

…

In SonoLune

Labs › Screen & rendering is where the app hands warmth and dimming to this module instead of drawing a matte over your screen. The switch only appears there once the module is installed, which it now is.

About

Lune Bridge by uraniam9 · GPL-3.0

Built as the root companion to SonoLune, a calm-first sleep and focus app. SonoLune works without root; with this module installed it stops drawing a matte over your screen and hands warmth and dimming to the display pipeline instead.

Something broken, or something missing? These open a form on GitHub that already asks the right questions, so a report does not turn into five rounds of me asking which device you are on.
No warranty. This is a root module: it changes display settings and app permissions on your device, and you use it at your own risk. It is provided as-is with no warranty of any kind, and the author is not liable for any damage or data loss.

In practice it is conservative by design — it only moves limits Android already enforces, never writes to a hardware node it does not recognise, lifts every permission it set when uninstalled, and stands down on its own if a boot fails. But nobody can test every device, and yours might be the one that behaves differently.