Ditch the hub.
Keep the control.

What it does

Modes

Eco · Balanced · Performance, one click, the OMEN key, or a hotkey. Each mode remembers its own fans, power gain and GPU choice, and the whole app takes that mode's colour.

Fan control

Auto (this model's own curve), Max, Manual per fan, or your own curve: seven points you drag, a floor, a ramp delay, and a separate GPU curve if you unlink it. The live reading rides the curve so you can see what it is about to do.

Max fan

Full speed with a way back: it returns to Auto once the chips are below 60° for two minutes, or after 15, 30 or 60 minutes.

Power gain

OGH's "Smart Performance Gain": +0 to +15 W on the CPU+GPU budget that NVIDIA Dynamic Boost draws from.

GPU power

Base · Boost · Max, or follow the mode.

Graphics

Hybrid, Discrete (the MUX) or iGPU only, whichever your firmware offers. Written the way OGH writes it, with the restart it needs.

Lighting

The keyboard drawn as it actually lights. Pick a key, a row, a zone or the whole board, then a hue and a shade; or Breathe, Cycle, Wave, or hand it to Windows Dynamic Lighting. Per-key selection is there for the boards that have it.

Display

Refresh rate, and the lowest rate on battery if you want it.

Optional driver

Ohman needs no driver. If you want one, a click in Settings installs PawnIO, open source, signed, and the same driver FanControl and LibreHardwareMonitor install. With it Ohman reads the CPU's own temperature instead of whichever sensor Windows exposes, which is the fix for boards that report a flat 28°, along with the power limits and the reason the chip is holding back. On boards whose firmware refuses fan levels it sets them through the embedded controller instead. Removable from the same row, any time.

Benchmark

Ctrl+Alt+R in a game: it warms up, then measures average FPS, 1% and 0.1% lows and stutter, with temperatures, power and fans beside them. Every run is kept and makes a card to share. How it’s measured.

Live

CPU and GPU temperature, package watts, fan speeds, load, clocks, chassis sensor, battery. CPU temperature on the tray icon.

Tray

Everything above without opening the window: modes, fan mode, power gain, refresh rate, GPU power, graphics, lighting, brightness and every switch.

OMEN key

Opens the panel, cycles modes, toggles max fan, or runs a command of your choice. OGH's key handler is stopped, reversibly.

Safety

A thermal guard forces max fan on a hot CPU, a hot chassis or stalled fans, and can be switched off. Fan levels between 1 and 1800 rpm are refused, because no fan holds them; 0 is allowed, which stops them.

Extras

Starts with Windows without a UAC prompt, Eco on battery, Windows power mode sync, hotkeys, an on-screen flash when a key changes something, and an update check that never installs anything for you.

How it works

HP exposes a BIOS mailbox as the WMI class hpqBIntM. Ohman uses the commands OGH uses: performance mode, max fan, fan levels, CPU+GPU power budget, GPU power, graphics mode, keyboard lighting, plus read-only queries. The OMEN key arrives as a WMI event (hpqBEvnt). Every byte and every measured firmware behaviour is written down in docs/research.md.

• 0x1A mode
• 0x27 max fan
• 0x2E fan levels
• 0x29 power budget
• 0x22 GPU power
• 0x52 graphics mode
• 0x20009 lighting

One executable, with a settings file and a log beside it. To remove it, turn off Start with Windows and Take over the OMEN key first, then delete the folder: those two are the only things Ohman writes outside it, besides the share cards and CSVs you save yourself (Pictures\Ohman, Documents\Ohman).

Supported laptops

Every OMEN and Victus laptop is supported. Ohman asks the firmware what generation it is and drives it accordingly, hiding any control your firmware does not offer.

A green board id has been confirmed by its owner (30 so far).
Every other board still runs, it has just not been confirmed by a person yet. Help get yours verified.

Your board id is in Ohman under Settings, or from (Get-CimInstance Win32_BaseBoard).Product in PowerShell. A board that is not in this table still runs, and most of the boards in it have no entry of their own either: Ohman asks the firmware what it is and uses what it answers. The table is a reading aid, not the list of what the code knows.

Verify yours

Try every control Ohman gives you: the modes, the fan modes, power gain, GPU power, graphics switching and the keyboard. If you installed the driver, say whether the CPU temperature looks right and whether the fans still behave. Check nothing is stuck after you exit, then Settings → Report Issue and open a Verify my laptop issue with what it copies.

Five minutes, and everyone on your board gets the tested profile.

If something is wrong on your model

1. Settings → Report Issue. Collects your model, board id, BIOS, system-design data and fan table, copies it, and opens a prefilled issue. No personal data.
   If Ohman will not start, tools\support-info.cmd writes the same thing to a file.
   If the driver is the part that is wrong, tools\drivertest.cmd says why in one page.
2. Paste it in, and say what OGH does differently on your model. OGH's own log helps most, from a session where you clicked every mode: %LOCALAPPDATA%\Packages\AD2F1837.OMENCommandCenter_v10z8vjag6ke6\LocalCache\Local\HPOMEN\
3. A laptop is one entry in src/Platform.cs. Nothing else in the app is model-specific.