Framework
Laptop 12 (13th Gen Intel)
Seventeen exact-model owners establish a usable small laptop, while touch, rotation, the on-screen keyboard and post-resume input make the convertible experience conditional.
Bottom line
Omarchy runs on both 13th Gen Intel versions of the Framework Laptop 12, and several owners use the machine successfully as a conventional laptop. The convertible hardware is only part of the story: touch and pen can work, but automatic rotation, rotation lock, launching apps, the on-screen keyboard and waking or dismissing the screen saver can still require setup or unfolding the keyboard. Separate input failures after boot or resume keep this from being a low-friction recommendation.
It is a credible choice if you want a small, repairable laptop and view tablet mode as a feature you are willing to configure. It is a poor fit if you need a polished keyboard-free tablet, a backlit keyboard, biometric login or sustained workstation-class performance. Existing owners should test cold boot, repeated lid-close cycles, the touchpad, touchscreen, pen, rotation and screen-saver dismissal before relying on it away from a keyboard and mouse.
What is reported
11 findings with cited evidenceInstall and boot
Owners have installed and run Omarchy on both Core i3 and Core i5 versions. One installer flow displayed an error after the USB drive was removed at the prompt but booted normally after a forced restart. An Arch owner separately lost working Secure Boot and UEFI tooling after a firmware update, then recovered by resetting Secure Boot state and keys.
Installation is demonstrated, but keep the USB installer attached through the final reboot and preserve a recovery path before firmware or Secure Boot changes.
Desktop and graphics
Direct Omarchy owners reached working Hyprland desktops on both processor options, and an independent test ran eight Linux distributions on the Core i5 model. The retained reports do not identify a model-specific graphics failure.
The integrated graphics path is suitable for the desktop and ordinary applications. This finding does not establish gaming performance or eliminate application-specific Wayland issues.
Display, touch and pen
Owners report a working internal display, touchscreen and pen, including under Omarchy. Folded use is less settled: rotation needs additional Framework packages and Hyprland configuration, one Arch owner saw tablet-state detection fail after a cold boot, and another reported touch degrading after sleep or stylus use.
Do not read working touch as a complete tablet experience. Test touch, pen, rotation and the return to laptop mode as separate behaviors.
Keyboard, hotkeys and backlight
The keyboard works in normal use, but the original model is not backlit. One CachyOS owner reports intermittent loss of the built-in keyboard after resume, and the openSUSE owner describes occasional missed keystrokes during ordinary typing.
The lack of backlighting is fixed hardware, while missed keys and resume loss are reported behavior. Test both typing feel and several sleep cycles on the exact unit.
Touchpad and pointing
Several owners use the touchpad normally, but exact-model reports describe a cursor pinned in the lower-right corner and a dead-looking pointer after cold boot or hibernation. One Omarchy owner restores the device immediately by unbinding and rebinding the HID interface; reboot also clears the condition.
Keep a keyboard-accessible recovery path. The HID rebind is an owner-confirmed workaround for one exact Omarchy setup, not a proven universal fix.
Wi-Fi and Bluetooth
The Intel AX211 is included in working Omarchy and Arch systems. One month-long openSUSE report found Wi-Fi unstable with one ASUS router and improved when switching routers.
There is no broad evidence of a dead wireless path, but the router-specific failure means Wi-Fi should be tested on the networks that matter before travel or deployment.
Speakers, microphone and audio
Framework and its Arch installation guide identify the speaker, microphone, Bluetooth-audio and codec packages, but the retained exact-model owner reports do not isolate speaker, microphone or headset performance.
A working desktop does not prove the microphone or headset route. Test playback, recording and the 3.5 mm jack separately.
Camera
The 1080p camera is supported by the packages in Framework's Arch guide, but none of the retained owner reports documents camera quality or a complete Omarchy video call.
Test the camera and microphone together in the service you actually use, including once after suspend.
Suspend and resume
Suspend is fast and generally usable in several reports, but failures span different input paths: one openSUSE owner had a complete suspend failure, one CachyOS owner intermittently lost the keyboard after wake, one Arch owner saw touch stop responding and one Omarchy owner saw the touchpad fail after hibernation.
A successful wake is not enough. Confirm keyboard, touchpad, touchscreen, pen, rotation and session locking after several short and overnight cycles.
External displays and docks
The four expansion bays advertise DisplayPort Alt Mode, but the retained exact-model reports do not provide a controlled Omarchy monitor or dock result.
Treat USB-C display, HDMI expansion card, dock hotplug and monitor power as unverified until tested with the exact cards and display.
Evidence, no verdictSourceBattery, power and thermals
One Core i3 Arch owner estimated roughly six to eight hours under KDE and longer under a stripped Niri session. A separate Omarchy owner in the same thread estimated about 1% charge loss per hour during suspend. The openSUSE owner called battery life adequate rather than exceptional and recorded several freezes and noticeable fan behavior.
These are useful lived-use boundaries, not comparable benchmarks. Desktop environment, brightness, power profile and workload materially change runtime and responsiveness.
Changes over time
8 dated events- Owners establish the first practical battery range
An Arch owner estimates six to eight hours under KDE and longer under Niri; an Omarchy owner in the same thread estimates roughly 1% charge loss per suspended hour. Neither is a controlled benchmark.
- An Omarchy owner wires up automatic rotation
After installing Framework's Arch-side sensor pieces, one owner confirms working display, touch and tablet transforms through a Hyprland script and later a small helper application.
- Repeated Omarchy installations reach a working system
A Core i5 owner reports four installs across Omarchy 3.0.1 and 3.0.2; the only alarming final-stage error still boots after a forced restart and is avoided when the USB drive remains attached.
- An Arch owner recovers UEFI after a firmware update
The update invalidates TPM-backed unlock and leaves Secure Boot tooling unable to see UEFI. Resetting Secure Boot state and keys restores the path, though the initiating cause remains uncertain.
- Touch and tablet state become unreliable after sleep or reboot
One Arch owner loses automatic tablet-mode detection after a cold boot; a second report from the same owner later documents touch and pen degradation over time and after sleep.
- Two Arch owners report a cursor pinned in the lower-right corner
The touchpad forces the pointer back to the corner until reboot or logout, while an external mouse still works. The thread does not establish a root cause.
- A CachyOS owner loses the keyboard after resume
The exact Core i5 owner reports intermittent built-in keyboard failure after lid-close sleep; another sleep cycle does not restore it, while reboot does.
- An Omarchy owner recovers the touchpad without rebooting
On Omarchy Quattro, the touchpad intermittently looks dead after cold boot or hibernation. Unbinding and rebinding its HID interface restores pointer movement immediately; the proposed root cause remains unverified.