Omarchy Hardware

ASUS

ROG Flow Z13 GZ302EA

Nineteen exact-model reports establish a working Linux tablet with exceptional CPU and integrated-graphics capacity, but the detachable input stack, microphone, brightness and suspend remain sensitive to firmware and software updates.

19exact-model reportsReport mix: three Omarchy · two Arch Linux · six Arch-based · eight other Linux

Bottom line

Three exact-model owners report using Omarchy, including a current brightness diagnosis and a physical-device test attached to a proposed hardware hook. The wider Linux record shows that the Radeon desktop and most basic tablet hardware can work, but this is not yet a low-maintenance installation. Current open reports cover an internal microphone path, touchpad clicks, immediate wake from suspend and a panel that turns black when Omarchy requests maximum brightness. Several failures have explicit working and broken version boundaries, so an old success or failure should not be treated as permanent.

An existing owner has a credible route if updates can be tested rather than applied blindly. Keep access to the ASUS keyboard firmware recovery tool, avoid Omarchy's maximum-brightness command until a model-specific cap ships, and test the keyboard, touchpad, rotation, microphone, camera and repeated suspend after kernel or firmware changes. Buyers should confirm the full GZ302EA suffix, processor, memory and panel, then decide whether the tablet form and unusual graphics capacity justify maintaining ASUS-specific packages and rollback options.

What is reported

12 findings with cited evidence
  • Install and boot

    Three independently attributable GZ302EA owners report running Omarchy, from Omarchy 3.4.1 through 4.0.0. Exact owners also reached working Arch, CachyOS, Fedora, Bazzite and Bluefin systems.

    The machine can reach a useful desktop. Installation success does not establish a complete tablet experience, and the retained direct Omarchy reports do not amount to a clean-install recipe for every configuration.

  • Desktop and graphics

    The Radeon 8050S and 8060S appear in exact-model Linux diagnostics, and one Fedora 44 Radeon 8060S result completed Geekbench 6.7's Vulkan test with a score of 118,072. A separate Omarchy setup project runs Hyprland and gamescope on the Radeon 8060S.

    There is direct evidence that the integrated GPU can drive a Linux desktop and accelerated workloads. The single Fedora score is not an Omarchy benchmark, and neither it nor the Windows review guarantees game or compute compatibility.

  • Internal display and brightness

    The 2560-by-1600 panel runs at 180 Hz in exact Linux inventories. On one GZ302EA, raw brightness values through 64,532 worked but 64,533 and higher turned the backlight off; Omarchy's 100% command requests the invalid range. Project triage confirmed the command path but did not reproduce the panel behavior on another unit.

    Ordinary display output works, but maximum brightness can produce a black screen on the documented panel. The issue remains open and the proposed cap has not shipped in Omarchy 4.0.2.

  • Keyboard, lighting and ASUS controls

    Keyboard input and backlight brightness work in current exact-model reports. The owner who found the keyboard dark on Fedora 43 with Linux 6.17.9 later confirmed visible lighting and brightness levels 0 through 3 on Linux 6.19.14. A separate owner confirmed that G-Helper Linux 1.0.62 controls the rear chassis light. Omarchy's native chassis-light integration remains unmerged, and the built-in brightness keys still have an open controller-drop report in some Proton games.

    Treat keyboard lighting, the rear chassis light and media-key behavior as separate results. Working backlights do not resolve the open gaming hotkey conflict, and released third-party chassis-light control does not mean Omarchy ships it.

  • Touchpad, touch and tablet input

    Touch, pen and the detachable touchpad work in several exact-model inventories. Other owners reported dead touchpad clicks on Linux 7.2-rc4, an external Magic Trackpad that stopped when the keyboard cover was detached and a keyboard-controller firmware state that disabled the keyboard, touchpad and rotation together. The last failure was recovered with ASUS's Windows firmware tool.

    A working pointer today does not clear the detachable input stack across updates. Preserve a firmware recovery path and retest attach, detach, touch, clicks, pen and rotation after changes.

  • Fingerprint and biometrics

    ASUS lists an infrared front camera but no fingerprint reader. None of the retained exact-model Linux reports tests face recognition or biometric login.

    This is missing evidence, not a report that the infrared camera fails. Plan on password or hardware-key login unless the intended biometric stack is tested separately.

    Not coveredSource 1, Source 2
  • Wi-Fi and Bluetooth

    A Bluefin owner showed Bluetooth working on the Nov. 19, 2025, build and missing after the Nov. 25 build; rollback restored it. A current Omarchy setup project documents an MT7925 Bluetooth reload after firmware-related WMT timeouts, while a CachyOS suspend report attributes one wake problem to the same radio stack.

    The radio can work, but firmware and kernel changes have altered both Bluetooth and sleep behavior. Keep a network fallback and verify Wi-Fi, Bluetooth and resume together after updates.

  • Speakers, microphone and audio

    One exact CachyOS owner could use the ALC294 analog fallback but could not access the internal three-microphone array through the expected ACP, DMIC or PDM path. An Omarchy setup project includes separate speaker, headphone and microphone processing profiles rather than demonstrating a clean stock path.

    Do not assume that hearing the speakers means the microphones are ready for calls. The internal microphone remains an open exact-model issue, and the retained reports do not establish the 3.5 mm path under Omarchy.

    Problems reportedSource 1, Source 2, Source 3
  • Camera

    An exact-model Omarchy setup project uses the 5-megapixel camera but reports that it can fail to re-enumerate after suspend until the USB controller is reset. The retained owner reports do not separately test the rear camera or infrared login.

    Video can work and still fail after a lid cycle. Test the actual conferencing application before and after suspend rather than treating device detection as a complete result.

    Mixed resultsSource 1, Source 2
  • Suspend and resume

    One GZ302EA suspended normally on CachyOS 7.1.6 and Linux LTS 6.18.42 but woke immediately on 7.1.8. A second owner reproduced the failure on Linux 7.2 and restored sleep only after disabling detachable-keyboard wake and unloading the MT7925 stack; an attached monitor made the failure return.

    Suspend is kernel- and configuration-sensitive. A single successful wake is insufficient: repeat the test with the keyboard attached and detached, wireless active and an external display connected.

    Mixed resultsSource 1, Source 2, Source 3
  • External displays, docks and ports

    The hardware exposes HDMI 2.1 and two USB4 DisplayPort paths. One suspend follow-up says an attached monitor reintroduced immediate wake, but the retained exact-model evidence does not isolate HDMI, either USB-C path, the XG Mobile connector or a particular dock.

    The connectors are present; reliable dock and display behavior remains unproven. Test the complete cable, adapter, monitor and lid-state combination you intend to use.

    Evidence, no verdictSource 1, Source 2, Source 3
  • Battery, power and thermals

    The chassis can sustain roughly 62 watts of combined processor and graphics load in one Windows review. A GZ302EA Omarchy setup project measured platform profiles from quiet through a custom high-power mode and warns that aggressive tuning and concurrent writes can hard-lock the system. The suspend workaround owner also reported lower sleep drain after unloading the Wi-Fi stack.

    The tablet has unusual performance headroom, but power controls and sleep efficiency are part of the compatibility story. Use measured review data as a hardware ceiling, not an Omarchy runtime promise, and treat model-specific tuning as experimental.

Changes over time

17 dated events
  1. Rear lightbar is unavailable in an early report

    Fedora and current asusctl detected the keyboard lighting device but not the separate chassis lightbar.

  2. Bluefin update removes Bluetooth

    Bluetooth worked on the Nov. 19 build, disappeared on the Nov. 25 build and returned after rollback.

  3. Keyboard backlight writes have no visible effect

    An exact Fedora owner found the sysfs controls accepted brightness changes while the keyboard remained dark.

  4. Hyprland 0.54 breaks special workspaces

    An Omarchy owner traced misplaced windows and a toggle-floating crash to the 0.54 transition; the same owner reported that 0.54.1 did not resolve it.

  5. Released G-Helper update enables the rear chassis light

    An exact CachyOS owner confirmed that the proposed GZ302EA lighting change fixed the rear RGB light. The change then shipped in G-Helper Linux 1.0.62.

  6. Brightness keys drop controllers in some Proton games

    On Bazzite, the built-in brightness keys disrupted virtual gamepads in three tested games while the same keys on an external keyboard did not.

  7. Windows firmware tool recovers the input controller

    After the controller entered bootloader mode, the keyboard, touchpad and rotation stayed unavailable across Linux environments and a BIOS update. ASUS's keyboard firmware tool restored all three.

  8. Control center crashes when the keyboard is detached

    The Arch owner reports that rog-control-center 6.3.4 worked and 6.3.6 or later crashed after detaching the keyboard cover.

  9. Internal microphone path is missing

    CachyOS exposed an analog ALC294 fallback but not a usable path for the built-in three-microphone array.

  10. Newer kernel restores keyboard backlight control

    The original Fedora reporter confirmed visible keyboard lighting and working brightness levels 0 through 3 on Linux 6.19.14. This does not establish support for the separate rear chassis light.

  11. Project main fixes the detached-keyboard control-center crash

    The original Arch reporter built rog-control-center from the main branch and could no longer reproduce the crash after detaching the keyboard. The retained evidence does not identify the first packaged release with the fix.

  12. Linux 7.2 release candidate loses touchpad clicks

    The detachable touchpad appeared as broken duplicate nodes on CachyOS 7.2-rc4. The issue remained unresolved on Sept. 2.

  13. systemd merges an internal-input classification

    The upstream hwdb now marks this keyboard and touchpad as internal so disable-while-typing can apply correctly.

  14. Linux 7.1.8 breaks s2idle

    The same machine suspended on 7.1.6 and Linux LTS 6.18.42, then woke immediately on 7.1.8. The problem persisted on 7.2 without keyboard-wake and Wi-Fi workarounds.

  15. Omarchy maximum brightness turns the panel black

    An exact owner measured the safe and failing raw backlight values; project triage confirmed that Omarchy sends the unsafe 100% request.

  16. Chassis-light prototype passes an exact-device test

    An Omarchy contributor reports that proposed code synchronized the rear light with keyboard brightness on a GZ302EA; the pull request remained open.

  17. asusctl 6.4.0 exposes current platform controls

    An exact GZ302EA inventory reports fan curves, charge threshold, throttle policy, keyboard brightness and Static, Breathe and Pulse Aura modes.