Configure Displays, Wi-Fi, Bluetooth, and Audio on Omarchy

Set up Omarchy 4K and HiDPI scaling, multiple monitors, Wi-Fi, DNS, Bluetooth, and PipeWire audio with a layered troubleshooting method.

Omarchy exposes display, network, Bluetooth, and audio controls through top-bar panels. Use a panel for normal configuration before editing files; that separates hardware or driver failures from a typo in a custom configuration.

Display scaling and HiDPI

Open the display panel with Super + Ctrl + D. Omarchy defaults target high-PPI displays. A 27- or 32-inch 4K screen commonly needs fractional scaling, while 1080p and 1440p screens are usually closer to 1x. Use Super + / and Super + Alt + / to step through the ratios supported by the current release.

To change text without scaling the whole desktop:

omarchy display text size 14
omarchy display text size reset

Restart applications that retain the old size. GTK accepts only integer GDK_SCALE values, so fractional monitor scale and application text scaling solve different problems.

Multiple monitors

An external display extends the desktop by default. Start with the display panel and Trigger → Hardware for mirroring, disabling the laptop panel, brightness, and layout. For persistent resolution, position, rotation, or workspace rules, open the current ~/.config/hypr/monitors.lua through Setup → Monitors.

Record before editing:

output names from hyprctl monitors;
native resolution and refresh rate;
connector, GPU, and dock;
a recoverable copy of the working configuration.

Change one display at a time. If an edit causes a black screen, use a TTY or revert the last user-level file.

Wi-Fi, Ethernet, and DNS

Current Omarchy uses NetworkManager. Open the panel with Super + Ctrl + W; use nmtui or the omarchy network command group in a terminal. Ethernet is normally automatic.

DNS comes from DHCP by default. Setup → Network → DNS offers Cloudflare, Google, or a custom resolver. Diagnose by layer:

Does the adapter and radio exist?
Is it associated with an access point?
Did it obtain an IP, gateway, and correct time?
Can an IP address be reached?
Does name resolution fail?
Did a VPN, proxy, or firewall alter the path?

A browser failure does not prove Wi-Fi is disconnected. Preserve status first, then use Update → Hardware → Wi-Fi to restart the relevant component.

Bluetooth

Open Bluetooth with Super + Ctrl + B, enable the radio, and pair. For repeated disconnects, record device type, battery, kernel version, and possible 2.4 GHz interference.

Do not depend on a Bluetooth keyboard at disk unlock. Keep a wired keyboard or 2.4 GHz receiver. For a transient post-update failure, try Update → Hardware → Bluetooth before deleting all pairing state.

Audio and microphone

Super + Ctrl + A opens master volume, output selection, and per-application mixing. Test speakers, headphones, microphone, HDMI/DisplayPort, and Bluetooth profiles separately.

For a silent recording, first identify whether the capture mode was no audio, desktop audio, or desktop plus microphone. Then inspect PipeWire devices. Compare a conferencing app with a simple recorder to distinguish system input, app permission, and app-level device selection.

Collect useful hardware evidence

Provide Omarchy version, kernel, GPU/network/audio hardware, connection method, recent update, reproduction steps, and redacted logs. “Audio is broken” plus random restart commands is not a diagnosis.

Use the troubleshooting guide for the complete order and your first day for post-install checks.

Sources: Omarchy Monitors, Networking, and The Top Bar.