G-Helper causing device to occasionally turn on once battery charge limit hit

[trias702]

I am currently seeing a very odd issue with my ASUS ROG Ally X and G-Helper. Starting with G-Helper version > 0.203, my ROG Ally X will occasionally (sometimes, but not always) turn itself on when connected to the charger, and the charging level reaches the battery charge limit which I have set in G-Helper (I have it set to 90%). This happens even when the device is fully shutdown, which is even more strange. So I will turn on my device at 90% charge, then use the device until the battery drops to 40%, at which point I will shutdown the device in Windows (and I have battery charge limit set to 90% in G-Helper). My device is now turned off, fully shut down, no sleep mode, no hibernate. I now plug the USB-C charger into the device and it will begin charging. Once it hits 90%, it will sometimes turn itself on. It doesn't happen always, but like 30-40% of the time it happens.

This problem never used to happen, it only started happening about a month ago, and the only thing I did in that time was update G-Helper from 0.203 to 0.21x, and I also updated the AMD Radeon drivers, but I doubt video drivers could be causing such an issue. To try and fix this issue, I CMOS reset my BIOS and loaded optimised defaults, but that didn't fix anything, and the ROG Ally has no wake-on-ac options anywhere in the BIOS.

I am really stumped as to how this problem could be happening, but even though it happens randomly, it only ever happens once the battery reaches 90% (the limit set in G-Helper), so my hypothesis is that G-Helper might be causing this somehow?

[seerge]

@trias702 hello, G-Helper is not causing it :) It's not a driver or a firmware.

Charge limit is just a setting for a hardware when to stop charging, it will keep working (till next reboot) even without G-Helper. App version also doesn't have relation to this.

It could be some strange behaviour (or a setting) in BIOS that would cause that. Did you do any recent BIOS updates ? Try to keep charge limit on standard 80% or on 100%.

[trias702]

Thank you kindly for the reply. I did do a BIOS update to 312, but the problem was happening with the older 310 BIOS too. I wonder if perhaps it was a Windows Update which may have caused this? I will dig deeper. May I please ask why you recommend a charge limit of 80 or 100, but not 90%?

…

On Wed, Jul 9, 2025, 01:41 Serge ***@***.***> wrote: @trias702 <https://github.com/trias702> hello, G-Helper is not causing it :) It's not a driver or a firmware. Charge limit is just a setting for a hardware when to stop charging, it will keep working (till next reboot) even without G-Helper. App version also doesn't have relation to this. It could be some strange behaviour (or a setting) in BIOS that would cause that. Did you do any recent BIOS updates ? Try to keep charge limit on standard 80% or on 100%. — Reply to this email directly, view it on GitHub <#4306 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGFLGNH63II34UDZWHXCURL3HTITPAVCNFSM6AAAAACBCTPRBGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNZQGY2DSMI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[seerge]

@trias702 may be it's something with the hardware / power supply / etc (i don't know what). So it just powers device on when charging is finished ?

80% or 100% is just a wild guess, to check if that matters. Did same happen if you would set a limit using MyASUS / Asus services ?

[trias702]

Thanks again for the help. I don't have MyASUS or any other Asus software installed so I can only check with G-Helper. I have since updated all drivers on my system include Asus Control Interface, plus tweaked hidden BIOS settings using Smokeless. So far the problem hasn't happened again, but it was always random so am not sure if I have permanently fixed it. Since this cannot be an issue with G-Helper there's not much we can do here, thanks again for your help, but feel free to close this discussion thread as it's not a G-Helper issue.

…

On Wed, Jul 9, 2025, 08:38 Serge ***@***.***> wrote: @trias702 <https://github.com/trias702> may be it's something with the hardware / power supply / etc (i don't know what). So it just powers device on when charging is finished ? 80% or 100% is just a wild guess, to check if that matters. Did same happen if you would set a limit using MyASUS / Asus services ? — Reply to this email directly, view it on GitHub <#4306 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGFLGNG5DATWCW4S2NGCYTL3HUZPBAVCNFSM6AAAAACBCTPRBGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNZRGA3DONA> . You are receiving this because you were mentioned.Message ID: ***@***.***>