OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
display-monitors high occasional DISPUTE

Stop an HDMI TV blanking for a moment on every click

omarchyarchendeavouroscachyoshyprlandwaylandintelamddesktop
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

Both halves of the problem are real and well cited: hyprwm/Hyprland#13338 exists as 'Samsung Smart TV flickers on interaction via HDMI — works fine under Sway', and basecamp/omarchy#8689 exists as 'Lock screen alternates black <-> lock UI every ~13.5s on AMD iGPU over HDMI', matching the AMD spurious-hotplug variant. The option names in the symptom (render:cm_enabled, render:direct_scanout) are both real, the per-monitor bitdepth = 8 and vrr = 0 fields are valid per the Monitors page, and Super+Ctrl+I is confirmed bound to 'Toggle locking on idle' in default/hypr/bindings/utilities.lua. The one hard error is step 3: vfr is not in the misc category. The Variables page lists it under Debug (debug:vfr, bool, default true), so hl.config({ misc = { vfr = false } }) targets a nonexistent option and will be rejected or silently ignored, leaving the user thinking they tested the workaround when they did not.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.

Symptom

A TV or cheap monitor on HDMI blanks for about 0.2 s on every mouse click or window interaction, then recovers. The same cable, port and kernel are fine under Sway and in a plain TTY. Only Hyprland flickers. Disabling blur, animations, hardware cursors, render:cm_enabled, render:direct_scanout and misc:vfr changes nothing.

Cause

The TV renegotiates the HDMI link (or drops out of its low-latency mode) when the compositor changes what it presents. Hyprland's presentation path triggers this on some Intel i915 + consumer-TV combinations where Sway's does not. A closely related variant on AMD iGPUs: a DPMS-off from a screen blanker makes amdgpu emit a spurious connector hotplug that reads as disconnected, producing a metronomic black/on cycle and thousands of Disabling output HDMI-A-2 lines in hyprland.log.

Fix

Work around it at the display and the compositor:

  1. Turn off the TV's own picture processing: set the HDMI input's label to PC and enable Game Mode. This is what fixes it most often on Samsung/LG sets.
  2. Pin a plain 60 Hz mode and 8-bit output so the link is never renegotiated:

hl.monitor({ output = "HDMI-A-1", mode = "1920x1080@60", position = "0x0", scale = 1, bitdepth = 8, vrr = 0 })
  1. Stop variable-frame-rate presentation from idling the link. vfr lives under debug, not misc, and misc.vfr does not exist:

hl.config({
  debug = { vfr = false },
  misc  = { vrr = 0 },
})

Leave debug.vfr = false in place only while testing. It is on by default to conserve power, so turn it back on if it makes no difference.

  1. If the flicker only happens once the screen has been idle/locked, disable the blanker rather than the compositor. On Omarchy, check journalctl --user -b | grep -c 'Disabling output'. A large number confirms the spurious-hotplug variant. Toggle idle locking off with Super+Ctrl+I.

Verify

grep -c 'Disabling output' ~/.local/share/hyprland/hyprland.log (or hyprctl rollinglog | grep 'Disabling output') stops growing, and clicking no longer blanks the panel.

Sources

hdmi-tv-flickers-black-on-every-click