# Div Acer Manager Max: NitroSense style fan and profile control for Linux

> Div Acer Manager Max is an Avalonia based Linux desktop app for Acer laptops that talks to the Linuwu Sense kernel drivers, offering performance profiles, manual and automatic fan control, a battery related section, backlight and boot animation toggles, and a small daemon that keeps working when the GUI is closed. The project states it is under passive development.

**PXDiv/Div-Acer-Manager-Max** — Div Acer Manager Max is a Linux GUI for Acer laptops using Linuwu Sense drivers. It replicates NitroSense functionality with fan control, performance modes, battery limiter, and more. Built with Avalonia, it offers a clean, easy-to-use interface for managing system performance and cooling.

- Repository: https://github.com/PXDiv/Div-Acer-Manager-Max
- Stars: 749 · Forks: 76
- Language: C#
- License: GPL-3.0
- Published: 2026-10-21 · Updated: 2026-10-21 · Language: en
- Canonical page: https://hysenlabs.com/projects/pxdiv-div-acer-manager-max

## The same controls NitroSense gives on Windows, on Linux

Div Acer Manager Max is a feature-rich Linux GUI utility for Acer laptops, built on top of the Linuwu Sense drivers. Its stated purpose is to replicate and expand on what Acer's NitroSense and PredatorSense do on Windows, and to do it in a Linux context where neither of those tools exists.

The application is written in C# with Avalonia, which is why the interface is described as modern and clean rather than a collection of GTK dialogs. The description of what it does covers the familiar ground: full fan control, performance modes, battery optimization, backlight settings, and a live system information display.

The project is explicit about its own status in a caution block near the top. It is under passive development, and the README asks people to star the repository to show support. That single line sets the expectations for everything else here, since a passive project with a driver dependency underneath it is a different proposition from an actively maintained utility, and the rest of the documentation reads accordingly. The licence is GNU General Public License v3.0, with a LICENSE file in the repository root.

## The feature list, and the parts that hide themselves when unsupported

The implemented features are grouped by what they control. The performance and thermal profiles are Eco, Silent, Balanced, Performance and Turbo, and they are adjusted automatically based on whether the machine is on AC or battery, with Turbo hidden when running on battery or when the hardware does not support it.

Fan control offers manual and automatic modes, and manual control is disabled automatically when the Quiet profile is selected. There is a direct control over the LCD override setting, a configurable keyboard backlight timeout, and toggles for Acer's boot animation and startup sound. The live system information display shows the current performance profile, the fan settings, the calibration state and more.

The GUI hides what the hardware cannot do. The dynamic UI removes unsupported features rather than showing a control that fails when pressed, and the daemon auto-detects feature support per device, so a machine without a controllable fan curve simply does not get the panel. That is a better approach than the alternative, where a user discovers the limitation by clicking, and it is a direct consequence of the driver layer exposing what the embedded controller actually implements rather than what the marketing implies.

## A daemon that survives the GUI and can restart itself

The smart daemon is the component that does the real work. It auto-detects feature support for the specific device, communicates with the GUI in real time, and can run independently of the GUI, which means the fan control and profile settings stay applied when you close the window or the app is not running.

The resource cost is stated as roughly 10MB of RAM, and the daemon has a recursive restart mechanism to fix software issues, which the README compares to the behaviour of the same problem on Windows. That comparison is telling, since the reason such a mechanism exists is usually that the driver interface gets into a state where the tool has to be reset, and the project has chosen to handle that in the background rather than make the user notice.

The repository layout reflects the split. The DAMM-Daemon/ directory holds the daemon and the DivAcerManagerMax/ directory holds the Avalonia application, and the two are joined by a solution file, DivAcerManagerMax.sln. The daemon is also what the troubleshooting section points at, with the log file at /var/log/DAMX_Daemon_Log.log, which is where you look first when something is not applying.

## Installing is a shell script with four menu options, and the drivers are optional

Installation is a release package and a script. Download the latest release from the Releases section, extract it, and make the setup script executable.

```bash
   chmod +x setup.sh
```

Then run it, either by right-clicking the file and choosing Run in Terminal, or from a terminal in the extracted folder.

```bash
     ./setup.sh
```

When prompted, the menu offers four choices. Option 1 is Install, option 2 is Install without Drivers, option 3 is Uninstall, and option 4 is Reinstall or Update. A reboot is needed once the installation completes.

That second option matters more than it first appears. The whole application sits on the Linuwu Sense kernel drivers, and the setup script can install them for you, which saves a lot of work, but it also means the script is compiling and installing kernel modules on the user's machine. The alternative path installs the GUI and its daemon while leaving the driver layer to the user, which is the sensible choice for anyone who already has those drivers or who wants to review what the script does before running it. The troubleshooting section backs this up, since an UNKNOWN laptop type is usually a driver compilation failure and the fix is having the appropriate kernel headers.

## The dedicated Nitro key is bound by capturing the real scancode

Acer laptops have a dedicated key for their performance suite, the N key on Nitro machines and the PredatorSense key on Predators, and the setup script can bind it to open the application.

The reason the implementation captures the key during setup instead of hardcoding it is a small piece of kernel detail that the README explains carefully. Both buttons are the same to the embedded controller, sending the scancode 0xf5, which the kernel maps to keycode 425 on most models. Some models carry a udev hwdb quirk that remaps it to prog1, which is 148, instead. Since the mapping is not the same everywhere, the setup captures the code from an actual press rather than assuming one.

Two models are listed as confirmed so far, the Nitro ANV16S-41 and the Predator PHN16S-71, both on 425.

There is a caveat for people who remap keys themselves. A key remapper such as keyd or kmonad grabs the keyboard exclusively, so the detection service never sees the button at all. The instruction for those users is to bind the key in the remapper's own configuration instead, where it typically surfaces as f16 or XF86Launch7 after keyd has taken it. That is the kind of conflict that is invisible until you happen to use both tools.

## Where the project depends on somebody else's kernel work

The dependency chain is worth being explicit about, because it determines who fixes what. The custom drivers for this project come from the Div-Linuwu Sense project, which the README says is built entirely on top of the Linuwu Sense drivers, with the project giving thanks to those developers for enabling hardware-level access on Acer laptops. The Linuwu Sense repository is the foundation, and this repository is a consumer of it.

That means a driver-level problem in the foundation is not something the DAMX maintainer can fix, and the README reflects this in its support routing. If your device is not on the compatibility list, the project says DAMX will still work on most devices, but asks you to file the issue on the Linuwu Sense page, and adds that such issues will be ignored on the DAMX page. The compatibility list itself is a separate document in the repository, and the FAQ page is the recommended first stop before opening an issue.

The project is also where the practical limits of a passive project show. Features are marked as fully implemented, and the readme asks for bug reports, feature requests, pull requests and help testing on different Acer laptop models. What it does not promise is a response time, and with the underlying driver layer maintained separately, the realistic expectation is that a new laptop model works if the driver supports it, and that the GUI adapts to whatever the daemon reports.

## Conclusion

Adopt Div Acer Manager Max if you own an Acer Nitro or Predator laptop and want the fan curve and performance profile controls that NitroSense and PredatorSense give on Windows, since the app covers the same ground on Linux and hides features your hardware does not support. Do not adopt it if your machine is not Acer, or if you need active upstream work, because the project states it is under passive development. Before you install, check the compatibility list, and if your laptop type shows as UNKNOWN after a restart, verify the kernel headers are present so the drivers actually compiled.

## FAQ

### What is Div Acer Manager Max and what does it do?

It is a Linux GUI utility for Acer laptops built on the Linuwu Sense drivers, replicating and expanding on Acer's NitroSense and PredatorSense. It provides performance and thermal profiles, manual and automatic fan control, an LCD override setting, keyboard backlight timeout control, boot animation and sound toggles, and a live system information display.

### How do I install Div Acer Manager Max?

Download the latest release, extract the package, make setup.sh executable with chmod +x setup.sh, then run ./setup.sh and choose from the menu, where 1 installs, 2 installs without the drivers, 3 uninstalls and 4 reinstalls or updates. Reboot the system when the installation finishes.

### Why does my laptop type show as UNKNOWN in Div Acer Manager Max?

The troubleshooting section says to try restarting first, since it happens sometimes, and if it persists that usually means the driver installation failed. The cause to check is missing kernel headers for compiling the drivers, and the log file at /var/log/DAMX_Daemon_Log.log is where the details are.

### Can I bind the Nitro or PredatorSense key to open Div Acer Manager Max?

Yes, the setup script can do it. The script captures the keycode from an actual press rather than assuming one, because the button sends scancode 0xf5, which the kernel maps to 425 on most models while some models remap it to prog1, 148. If you use keyd or kmonad, bind the key in the remapper's configuration instead, since a remapper takes the keyboard exclusively and the detection service will never see it.

### Is Div Acer Manager Max actively maintained?

The project states in a caution block that it is under passive development, and the last push was on 2026-09-22. The releases listed are 1.0.2-h1 from 2026-07-23, 1.0.2 from 2026-07-20 and 1.0.2b-pre from 2026-07-20, and the licence is GNU General Public License v3.0.

## Sources

- [Issues](https://github.com/PXDiv/Div-Acer-Manager-Max/issues)
- [License: GPL-3.0](https://github.com/PXDiv/Div-Acer-Manager-Max/blob/main/LICENSE)
- [PXDiv/Div-Acer-Manager-Max on GitHub](https://github.com/PXDiv/Div-Acer-Manager-Max)
- [README](https://github.com/PXDiv/Div-Acer-Manager-Max/blob/main/README.md)
- [Releases](https://github.com/PXDiv/Div-Acer-Manager-Max/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/pxdiv-div-acer-manager-max