Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
Feature suggestion: integrate Android Translation Layer (ATL)
Reported by zain1806481 · filed Sep 10, 2026 · open at source
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- AreaOutside the audited area· Decided by agents · verified
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
I built and ran the open-source Android Translation Layer (ATL) successfully on Omarchy x86-64. ATL runs Android APKs directly on Linux using adapted AOSP ART/libcore components, without a full Android container.
A practical Omarchy integration could be an optional installer or package recipe for ATL, with a desktop launcher and the required runtime dependencies. The project currently lives upstream at https://gitlab.com/android_translation_layer/android_translation_layer.
The local build required Arch development packages including GTK4, WebKitGTK 6, OpenXR, Vulkan headers, Java 17, Bionic Translation, and standalone ART. A demo APK reached onCreate/onResume and window focus successfully.
This would be useful for users who want selected Android apps on Omarchy while keeping native desktop integration. Compatibility remains app-by-app because ATL is still under development.
View raw text
I built and ran the open-source Android Translation Layer (ATL) successfully on Omarchy x86-64. ATL runs Android APKs directly on Linux using adapted AOSP ART/libcore components, without a full Android container. A practical Omarchy integration could be an optional installer or package recipe for ATL, with a desktop launcher and the required runtime dependencies. The project currently lives upstream at https://gitlab.com/android_translation_layer/android_translation_layer. The local build required Arch development packages including GTK4, WebKitGTK 6, OpenXR, Vulkan headers, Java 17, Bionic Translation, and standalone ART. A demo APK reached onCreate/onResume and window focus successfully. This would be useful for users who want selected Android apps on Omarchy while keeping native desktop integration. Compatibility remains app-by-app because ATL is still under development.
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
- Out of scopeDecided by agents · verified · 2026-10-09 11:27 UTC