I found a reproducible issue on my GL.iNet Mudi 7 (GL-E5800 EU) where the CPU usage increases significantly depending on which USB-C charger is connected.
I tested several power sources using the exact same USB-C cable (the original Apple USB-C cable that came with my iPhone Air), so the only variable was the charger/power source.
All tests were performed while the Mudi 7 battery was already at 100% charge.
I also rebooted the Mudi 7 during troubleshooting, but the issue still persists.
Test results:
Anker power bank → CPU usage is normal
Apple 20W charger (original charger from a 2021 iPad Pro) → CPU usage is normal
Anker 45W charger with display → one system process continuously uses around 21% CPU
Apple MacBook Air M5 original charger → the same process continuously uses around 21% CPU
The behavior is reproducible. When switching from one of the affected chargers to the Apple 20W charger or the Anker power bank, CPU usage returns to normal.
Since the same cable, the same Mudi 7, and the same 100% battery state were used in all tests, this seems to be related to how the Mudi 7 handles certain USB-C PD chargers, possibly involving USB-C PD negotiation, charging management, or the related hardware/driver.
The abnormal CPU usage remains stable at approximately 21% instead of being a short spike during initial PD negotiation.
Firmware is 0805release
I also used ChatGPT to help troubleshoot the issue, analyze the test results, and organize the findings into this bug report.
Thank you for providing the detailed test results and analysis.
We tested several laptop chargers and other common chargers locally but were unable to reproduce the issue.
Could you please provide the exact model numbers and output specifications of the Anker 45W charger and the Apple MacBook Air M5 charger? If the Anker charger has multiple USB-C ports, please also let us know which port was used during the test.
I've also discovered a more serious problem: the battery temperature remains between 41.5-41.8 degrees Celsius even with the Mudi7 under almost no load (the battery is fully charged, and the room temperature is around 27 degrees Celsius). I've updated to the latest version 4.10.0_beta4, but the problem persists. I suspect the cause might be a quality issue with the battery or the Mudi7 itself. Should I initiate the after-sales service process?
Some temperature increase during charging or shortly after reaching full charge can be normal.
Was the temperature measured shortly after the battery became fully charged, or had the Mudi 7 remained connected to power continuously?
Could you please disconnect the power, leave the device idle for 20–30 minutes, and check whether the battery temperature decreases?
Please also ensure the device is placed in an open, well-ventilated area and is not covered by or placed on fabric or other heat-insulating materials.
Thanks for your reply. I've been keeping it plugged in the charger the whole time. I might have been overly anxious about the battery temperature. Previously, when I only used the wireless repeater mode on my Mudi7, the battery temperature remained between 31-35 degrees Celsius. But yesterday, I simultaneously enabled Ethernet Port (WAN), wireless repeater mode, and a 5G SIM card, and also restarted the Mudi7 several times in a short period, causing the temperature to exceed 42 degrees Celsius and triggering the "overheating and stopping charging" message several times. Today, when I again only used wireless repeater mode, the battery temperature returned to around 35 degrees Celsius and is slowly decreasing.
Thank you for the update and for sharing the detailed.
Since the device was continuously connected to power, power and charging management may have contributed additional heat.
As the temperature returned to around 35°C and continued to decrease after the workload was reduced. This indicates that the battery is functioning normally and does not overheat abnormally.
Thank you again for your detailed testing and support.
