Display panel: first-party Miracast / Wi-Fi Direct display support (mirror + extend)

[realchrisolin]

Summary

I’d like to extend the built-in Display bar panel (omarchy.monitor) with Miracast / Wi-Fi Direct display support — still one Display dropdown (brightness, text size, scale, outputs), not a separate cast icon.

Working prototype (personal plugin + fork branch):

• Standalone plugin: https://github.com/realchrisolin/omarchy-miracast
• Branch on fork of this repo: https://github.com/realchrisolin/omarchy/tree/feat/display-miracast
  (shell/plugins/panels/monitor/ on top of current quattro)

Looking for maintainers’ take on whether this belongs in-tree, stays a third-party plugin, or should be split (UI in Omarchy / capture stack external).

Motivation

Portable Miracast sinks (battery wireless monitors, TV dongles, etc.) are common. Today Omarchy has strong Display controls but no integrated WFD path, so people cobble NetworkManager P2P + an external source. Putting scan/connect/mirror/extend next to brightness/scale matches how the feature is used: “this is another display,” not a separate media app.

What it does (today)

From the Display panel:

• Scan / connect / disconnect Miracast sinks
• Mirror (capture the laptop output) or Extend (Hyprland virtual output named after the peer, placed left/right/above/below)
• Stream-mode pills from sink-advertised CEA modes (e.g. 720p30 / 1080p30)
• Scale / position changes under live capture: pause → move focus → apply → healthy restart
• Disconnect teardown: migrate workspaces, restore cursor, re-assert eDP, park then remove the virtual output

Keyboard shortcuts in the panel: scan, doctor, connect/reconnect, stop, mirror/extend, firewall helper.

Architecture (high level)

Layer	Role
Panel.qml / Model.js / MiracastService.qml	U
Plugin bin/miracast-ctl	P2P/NM orchestration, ex
Plugin bin/monitor-state / monitor-scale	Enric
FluxCast	W
Optional patches/fluxcast/	VAAPI/QSV + power bia

Runtime deps beyond stock Omarchy: dnsmasq, wf-recorder, ffmpeg, plus a FluxCast tree (FLUXCAST_ROOT). Settings live under ~/.config/omarchy-miracast/.

Design choices worth debating

1. In-tree vs plugin — Feature is large (bins + FluxCast coupling). Shipping as omarchy plugin add … may be healthier than growing first-party omarchy.monitor until the UX settles.
2. FluxCast patches — Encode/mode patches are out-of-tree; I'm working on getting patches and a PR submitted upstream but they likely won't be in a stable official release anytime soon.
3. Bin naming — Prototype keeps helpers under the plugin bin/. First-party Omarchy style prefers omarchy-* in top-level bin/; happy to reshape.
4. Extend vs mirror defaults — Default extend @ ~720p30/1080p30 for portable sinks; open to Omarchy defaults.
5. Scope non-goals (for now) — Sink battery over WFD2 (sinks we tried don’t expose it), Google Cast, AirPlay as a source, DRM/Netflix reliability.
6. Indirectly relates to Proposal: Optional Global Workspace Mode for Multi‑Monitor Setups #8412

Ask

• Is first-party Display+Miracast desirable for Omarchy, or should this stay a community plugin?
• If desirable: preferred packaging (panel-only PR vs panel + omarchy-miracast-* bins vs plugin registry)?
• Any hard constraints on pulling in FluxCast / wf-recorder / NM P2P?

I can open a draft PR from feat/display-miracast once direction is clear — or keep iterating on the standalone plugin if that’s the better fit.

Test notes (my machine)

• Hyprland + Omarchy shell, Intel laptop Wi-Fi
• "HotYeah" brand portable display / Miracast sink (WFD 1.0)
• Mirror and extend; mid-session scale/position; reconnect; disconnect without leaving eDP wedged

Happy to run any checklist you care about (Wi-Fi chipset matrix, firewall, multi-monitor, battery encode path).

[realchrisolin]

latest version of the SUPER + CTRL + D display dropdown:

Fluxcast changes: IlyaP358/fluxcast#128

[realchrisolin]

[kwizeraFredie]

It would be amazing if this worked as smoothly as the Windows version, i have faced this issue many times where i want to connect a linux pc running omarchy or any other linux distros to wireless displays they do connect but there is a visble lag so if that can be fixed this would be a game changer