What Omarchy 4.0.2 changes for hardware compatibility

The hardware changes are specific

The release improves detection reliability for Apple displays. The underlying change stops trusting a predictable cache location when no private runtime directory exists and accepts a cached display path only when it still identifies the expected kind of character device.

The release also fixes migrations on Bash 5.3. That matters to someone updating or moving an existing setup, but it is not evidence about fresh-install compatibility on a particular laptop.

Most hardware compatibility questions remain open

The official comparison does not modify the version-pinned NVIDIA, T2, Framework, Dell XPS, Asus, Surface, Lenovo Yoga or Tuxedo handlers used in our current guides. It removes one general input-group setup step, alongside a much larger security-hardening release.

That leaves the same practical unknowns in place: hybrid graphics, sleep and dock behavior, battery life, internal displays and model-specific peripherals still depend on exact-machine observation. A quiet diff is not a passing test.

What changes on this site

• If an Apple display was not detected reliably, 4.0.2 is the first stable release that includes this fix.
• If a migration failed under Bash 5.3, 4.0.2 includes the relevant repair.
• Guides that cite 4.0.1 still describe 4.0.1 behavior; the release notes alone do not prove that a particular laptop, GPU, dock, or sleep path now works.
• Hybrid graphics, battery life, internal displays, docks, and model-specific keys still require evidence from the exact configuration.