The next Omarchy nearly doubles balanced-mode browser speed on Snapdragon X
A new root service gives your session a CPU floor that follows the power profile, so short browser bursts no longer wait for the clock to catch up and idle cores still drop to their lowest speed.
Image: omacom/omarchy pull request #18745 (GitHub)
Snapdragon X laptops running Omarchy have been leaving a lot of browser speed on the table in the balanced power profile. A fix is coming in the next version: DHH’s pull request, merged on November 13, 2026, reports a Speedometer 3.1 score going from 22 to 42 in balanced on a Zenbook A16 with an X2 Elite, on battery.
The PR explains the cause. The schedutil governor only raises a core’s clock as a task’s tracked utilisation grows, over tens of milliseconds, so a browser’s short bursts finish before the clock catches up. In balanced, a 2ms burst took 11ms.
The performance profile dodged that problem by switching to the performance governor, which held every core at 4.45GHz, idle ones included. According to the PR, that drew about 2W more at idle and is “the likely cause” of the hard resets seen under load on battery.
The fix is a new root service, omarchy-powerprofiles-floor. It gives logged-in users’ processes a utilisation clamp floor (uclamp.min) that follows the active power profile:
- 0 in power-saver
- 75% in balanced
- 100% in performance
The scheduler only keeps a core at that floor while a floored task is runnable, so idle cores still drop to their lowest clock. New processes inherit the floor from whatever forks them, and the service re-applies it when the power profiles daemon sends PropertiesChanged or logind sends SessionNew, with no polling. It releases the floor when stopped.
It works together with a companion change to omarchy-power-profiles-daemon (0.30-9), also merged on November 13, which keeps Snapdragon X on schedutil in every profile and removes the balanced cap. The before-and-after numbers were measured with both changes in place. That daemon PR adds that, with the floor in place, the old 75% balanced cap cost 6 points (36 capped vs 42 uncapped), and that without the floor service, performance on Snapdragon falls back to about 23.
Performance mode gives up a little, going from 47 to 45 in the same test, in exchange for no longer pinning every core at full clock. Balanced now lands close to what performance used to deliver.
The service is installed and enabled on Snapdragon machines by install/hardware/qualcomm/powerprofiles-floor.sh, and a migration takes care of existing installs when the update lands.
