Honor PC Manager—essentially the Honor-flavored sibling of Huawei PC Manager—is far heavier than it needs to be.
For my use case, the features I actually care about are basically:
The third one is tolerable because drivers can always be downloaded manually from the vendor website.
The first two, however, are extremely simple settings.
In a less enlightened universe, they might have been implemented as two or three tiny utilities that read or write a few hardware values.
But then the legendary Huawei/Honor engineering wisdom arrived.
Instead, we get a large background service that sits in memory all day, accompanied by a complicated plugin system and IPC infrastructure—all so it can eventually read or write a couple of values to the hardware.
A truly enterprise-grade solution to a problem that could almost fit inside a shell script.
Fortunately, we have greate reverse engineers.
And now we also have AI, which makes exploring undocumented hardware interfaces considerably easier.
For the features I need, there are much simpler alternatives.
These tools were tested on my Magicbook Pro 16 2026, and will probably work on multiple Huawei/Honor laptops. At this level, there is little technical reason to deliberately break compatibility between models for such simple operations.
Of course, one should never underestimate unknown Huawei engineering wisdom.
A small Windows CLI tool for configuring the battery charging thresholds:
https://github.com/AceDroidX/HuaweiBatteryControl
This lets you control the charge limits without keeping PC Manager running permanently in the background.
A Windows CLI tool for configuring Goodix Newton touchpad force sensitivity:
https://github.com/edimetia3d/GoodixNewtonTouchpad
Again, no giant management suite is required just to change one hardware parameter.
From what I have found, PC Manager mainly communicates with the laptop hardware through two mechanisms.
Some devices are controlled through raw HID operations—the Windows equivalent of working with hidraw devices on Linux.
The touchpad configuration appears to use this mechanism.
In other words, PC Manager sends relatively small HID commands to the device to read or change its configuration.
Other features are exposed through WMI.
Examples include:
These operations ultimately appear to modify values handled by the laptop's Embedded Controller (EC).
So behind the impressive PC Manager architecture, some features eventually reduce to something approximately equivalent to:
write value X to hardware field Y
The journey to get there is simply much more adventurous.
If you want to implement additional Huawei/Honor laptop features, these projects are useful references:
https://github.com/aymanbagabas/Huawei-WMI
Linux support and reverse engineering for Huawei laptop WMI interfaces.
https://github.com/rs0x29a/Linux-on-HONOR-MagicBook-14-Pro-2026-AI_ZQC-P_M1010
Contains useful information about running Linux on newer Honor hardware and interacting with the platform.
https://github.com/ZachAR3/HonorControl
Another project implementing controls for Honor laptop hardware.
These repositories are also good material to give to an AI coding agent when investigating additional features.
Instead of reverse-engineering everything from zero, the agent can inspect the existing implementations, compare WMI methods, HID reports, ACPI behavior, and EC access patterns, and then build a small dedicated utility for the feature you actually need.
A surprisingly civilized use of AI: removing unnecessary vendor software.
For the MagicBook Pro 16 model I tested, I found the following EC fields:
| EC Address | Meaning |
|---|---|
0x80 | Battery charge lower bound |
0x81 | Battery charge upper bound |
0x42 | Keyboard backlight duration, low 8 bits |
0x43 | Keyboard backlight duration, high 8 bits |
The keyboard backlight duration therefore appears to be stored as a 16-bit value across 0x42 and 0x43.
These values are hardware/model-specific observations, so they should not be assumed to be identical on every Huawei or Honor laptop.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。