GitHub - theantipopau/omencore: OmenCore is an Advanced Performance Control for HP Omen Laptops Take full control of your gaming laptop with precision fan tuning, RGB management, hardware monitoring, and performance optimization. (original) (raw)

Lightweight local control for HP OMEN and Victus gaming laptops

OmenCore is an independent control center for HP OMEN and Victus systems. It focuses on the local workflows people actually use in OMEN Gaming Hub: fan control, performance profiles, telemetry, keyboard lighting, OSD, power tools, diagnostics, and safe cleanup of HP background software.

It runs without ads, account prompts, cloud telemetry, or OMEN Gaming Hub. Hardware access is handled through local WMI BIOS, EC, PawnIO, Linux sysfs, and platform backends when the device exposes them.

At A Glance

Why People Use It

Current Release

Version: 3.7.1
Status: Stable release
Release notes: docs/CHANGELOG_v3.7.1.md
Release gate: docs/FINAL_RELEASE_CHECKLIST.md

v3.7.1 is a targeted post-3.7.0 stabilization release. It focuses on field reports for 8D2F, 8E41, 8BD4, 8BCD, 8574, and OMEN Max per-key RGB capability reporting.

v3.7.1 Highlights

• Quick Access uses one-click Quiet, Balanced, and Performance profiles again.
• WMI V1 fan handoff can clear stale fan floors on validated/problematic profiles including 8D2F, 8E41, 8BD4, and 8BCD.
• Profile-only models no longer receive custom curve or fixed manual fan writes.
• Hybrid AMD+NVIDIA hardware worker sessions quarantine unstable AMD ADL frame metrics while keeping core telemetry alive.
• Launch diagnostics include fan recovery state, performance apply traces, CPU temperature authority, RGB backend status, and AMD ADL quarantine expectations.
• Model identity summaries prefer exact ProductId matches instead of low-confidence model-name inference.
• OMEN Max per-key hardware is detected honestly, but the dedicated HID per-key editor/backend remains pending.

Downloads

Release artifacts are published on the GitHub Releases page.

Final GitHub release notes must include SHA256 hashes for every artifact. The in-app updater requires release hashes before it will install an update.

Quick Start

Windows

1. Download OmenCoreSetup-3.7.1.exe from Releases.
2. Verify the SHA256 hash from the release notes.
3. Run the installer as Administrator.
4. Keep PawnIO selected unless you only want monitoring and WMI-only features.
5. Launch OmenCore from the Start Menu.

Portable users can download OmenCore-3.7.1-win-x64.zip, extract it to a normal folder, and run OmenCore.exe as Administrator.

See INSTALL.md for the full Windows guide.

Linux

VERSION=3.7.1 wget "https://github.com/theantipopau/omencore/releases/download/v${VERSION}/OmenCore-${VERSION}-linux-x64.zip" mkdir -p OmenCore-linux-x64 unzip "OmenCore-${VERSION}-linux-x64.zip" -d OmenCore-linux-x64 cd OmenCore-linux-x64 chmod +x omencore-cli omencore-gui

sudo ./omencore-cli status ./omencore-gui

Prefer launching the GUI as your normal desktop user. Use sudo for CLI operations that need hardware access.

For bug reports, collect a triage bundle:

./qa/collect-linux-triage.sh

See INSTALL.md and docs/LINUX_INSTALL_GUIDE.md for Linux details.

Feature Matrix

Thermal And Fan Control

• WMI BIOS fan profile control on supported OMEN/Victus laptops.
• Max, Auto, Quiet, Gaming, Extreme, and custom presets where capability allows.
• Custom fan curves with temperature breakpoints on models with validated curve support.
• Profile-only fan gating for models where the firmware supports OEM profile modes but not safe manual curve writes.
• Restore OEM Auto action to release OmenCore fan ownership and return to firmware auto mode.
• Fan command history and launch diagnostics for field validation.

Performance And Power

• Quiet, Balanced, Performance, and custom profile routing.
• WMI thermal-policy fallback when direct EC/MSR power limits are unavailable.
• CPU/GPU power apply traces in diagnostics.
• Intel undervolt and TCC controls where the model, BIOS, and runtime allow them.
• GPU Power Boost on supported OMEN firmware.
• MUX switching where the BIOS exposes Hybrid, Discrete, or Integrated modes.

RGB And Lighting

• OMEN 4-zone keyboard lighting with profile, zone, brightness, and backlight operations.
• Model-aware fallback and serialized keyboard lighting writes.
• RGB diagnostics showing backend ownership, active path, and conflict status.
• OMEN Max per-key-capable hardware detection.
• External RGB provider surfaces for Corsair, Logitech, Razer, and system providers where available.

Note: OMEN Max dedicated HID per-key editing is not enabled until the backend is implemented and field verified.

Monitoring, OSD, And Diagnostics

• CPU/GPU temperature, load, fan level/RPM, battery, memory, storage, and GPU telemetry.
• Out-of-process hardware worker for crash isolation.
• Telemetry health states: valid, inactive, unavailable, stale, degraded, and invalid.
• Click-through OSD with RTSS FPS integration where available.
• Tray quick popup and status badges.
• Diagnostic exports with model identity, RGB path, resource footprint, fan history, launch readiness, and runtime state.

System Tools

• Guided OMEN Gaming Hub cleanup.
• Bloatware scanner and removable HP app inventory.
• Memory optimizer and gaming-mode helpers.
• Per-game profile automation.
• Auto-update with SHA256 verification.

Hardware Support

OmenCore is built for HP OMEN and HP Victus laptops. Desktop OMEN systems are treated conservatively.

Model support is keyed by ProductId where possible. Diagnostic exports include a model identity summary so unsupported or inferred profiles can be fixed without guesswork.

Requirements

Windows

• Windows 10 build 19041+ or Windows 11.
• Administrator rights for WMI BIOS, EC, MSR, fan, and power operations.
• Self-contained .NET 8 runtime in release builds.
• PawnIO recommended for advanced EC/MSR features and Secure Boot-compatible low-level access.

Linux

• x64 Linux with hp-wmi, ec_sys, or compatible hwmon/sysfs interfaces.
• Root privileges for hardware writes.
• A normal desktop session for the Avalonia GUI.
• Kernel support varies heavily by model and distro.

Backend Priority

Windows fan control normally follows this order:

1. WMI BIOS - preferred for modern OMEN laptops.
2. PawnIO-backed EC/MSR paths - advanced access where safe and validated.
3. OGH proxy - last-resort fallback when local firmware paths require it.

Linux control normally follows available sysfs/hwmon capability:

1. hp-wmi / platform profile.
2. hp-wmi hwmon PWM and fan input paths.
3. ec_sys for older models.
4. Diagnostic-only mode when no safe write path exists.

Known Limits In 3.7.1

• Some v3.7.1 fixes still require physical hardware validation, especially fan ramp-down and GPU wattage parity.
• OMEN Max per-key RGB editor/backend is not implemented yet.
• OGH Eco mode parity is tracked but not implemented.
• Direct PL1/PL2 controls remain firmware/MSR gated on many systems.
• Exclusive fullscreen OSD behavior depends on Windows composition, RTSS, game mode, and anti-cheat behavior.
• 8574 legacy OMEN 15 support is partial until fresh 3.7.1 diagnostics confirm effective fan command readback.

Development

Build

git clone https://github.com/theantipopau/omencore.git cd omencore dotnet restore OmenCore.sln dotnet build OmenCore.sln --configuration Release

Run Tests

Build Windows Artifacts

pwsh ./build-installer.ps1

Expected outputs:

• artifacts/OmenCoreSetup-3.7.1.exe
• artifacts/OmenCore-3.7.1-win-x64.zip

Build Linux Artifact

pwsh ./build-linux-package.ps1

Expected outputs:

• artifacts/OmenCore-3.7.1-linux-x64.zip
• artifacts/OmenCore-3.7.1-linux-x64.zip.sha256
• artifacts/version.json

Release Checklist

Before publishing a stable GitHub release:

1. Confirm VERSION.txt, project versions, installer version, README, and INSTALL all match.
2. Run dotnet restore, Release build, test suite, and git diff --check.
3. Build Windows installer/portable and Linux zip.
4. Generate SHA256 hashes for all artifacts.
5. Add hashes, known limits, and hardware validation status to GitHub Release notes.
6. Upload artifacts.
7. Tag the release only after the final notes and artifacts match.

The current release gate is tracked in docs/FINAL_RELEASE_CHECKLIST.md.

Troubleshooting

Windows logs are stored under %LOCALAPPDATA%\OmenCore\. Linux diagnostics can be collected with sudo ./omencore-cli diagnose --report.

Documentation

• INSTALL.md - installation, upgrade, portable use, Linux setup, uninstall.
• docs/CHANGELOG_v3.7.1.md - current release notes.
• docs/FINAL_RELEASE_CHECKLIST.md - release gate.
• docs/3.7.1-BUG-REPORTS.md - field report tracking.
• docs/LINUX_INSTALL_GUIDE.md - Linux details.
• docs/ANTIVIRUS_FAQ.md - antivirus and driver guidance.
• docs/DEFENDER_FALSE_POSITIVE.md - Defender guidance.
• drivers/PawnIO/README.md - PawnIO backend details.

Version History

Older release notes live in docs/.

Contributing

Useful contributions include fresh diagnostic exports, model ProductId verification, EC/WMI behavior reports, Linux sysfs snapshots, translations, and focused bug fixes. Please include logs and the model identity summary when filing hardware-control issues.

Safety And Disclaimer

OmenCore is provided as-is. Fan control, EC writes, undervolting, GPU power changes, and MUX switching can affect stability and hardware behavior. Use restore points, read capability warnings, and avoid enabling unverified hardware restore paths unless you understand the recovery steps.

OmenCore is not made by or endorsed by HP.

Links

• GitHub: https://github.com/theantipopau/omencore
• Releases: https://github.com/theantipopau/omencore/releases/latest
• Issues: https://github.com/theantipopau/omencore/issues
• Discord: https://discord.gg/9WhJdabGk8
• Donate: https://www.paypal.com/donate/?business=XH8CKYF8T7EBU

License

MIT License. See LICENSE.

Third-party components include LibreHardwareMonitor, Hardcodet.NotifyIcon.Wpf, PawnIO, and vendor RGB SDK files where bundled. See the relevant source folders and driver documentation for details.