G-helper need a restart after windows restart to remember settings

[xM1haix]

Rules

• I made myself familiar with the Readme, FAQ and Troubleshooting.
• I understand that, if insufficient information or no app logs will be provided, my issue will be closed without an answer.

What's wrong?

Mode, Laptop Keyboard and Laptop Screen settings are not applied based on charging state after windows restart and require a restart to save them

How to reproduce the bug?

1. Start windows
2. Plug the power -> will change the settings (144Hz+OD and Turbo)
3. Unplug the power -> will change the settings (60Hz and Silent)
4. Set Laptop Screen to 144Hz + OD and Mode to Turbo
5. Plug the power (no changes)
6. Unplug the power -> will change the settings (60Hz and Silent)
7. Full closing the GHelper (from tray) and open it
8. Repeat 2 -> 5
9. Unplug the power -> settings which were just made were saved
10. Restart windows will start over from 1.

Logs

log.txt

Device and Model

Asus TUF Gaming F15 FX507VV4

Additional information.

I think this start happening from 2 versions ago 0.202 or older I was hopping someone else has the same issues and will report it.

Armoury Crate

Never installed

Asus Services

0

Version

0.204.0

OS

Windows 11 24H2

[seerge]

@xM1haix hello,

I actually don't see it.

As soon as app launches it sets all last used settings, including mode , charge limit, keyboard backlight mode, etc

2/22/2025 9:27:32 PM: ------------
2/22/2025 9:27:33 PM: App launched: ASUS TUF Gaming F15 FX507VV4_FX507VV4 :0.204.0.0en-US.
...
2/22/2025 9:27:36 PM: AutoSetting for Offline <---- LAPTOP IS ON BATTERY WHEN STARTED
2/22/2025 9:27:36 PM: BatteryLimit = 80 : OK  <--- CHARGE LIMIT
2/22/2025 9:27:36 PM: Eco flag : 1
2/22/2025 9:27:36 PM: Mux flag : 1
2/22/2025 9:27:37 PM: \\?\DISPLAY#BOE0B70#4&284db93&0&UID8388688#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7} DISPLAYCONFIG_OUTPUT_TECHNOLOGY_INTERNAL
2/22/2025 9:27:37 PM: \\?\DISPLAY#BOE0B70#4&284db93&0&UID8388688#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7} \\.\DISPLAY1\Monitor0
2/22/2025 9:27:37 PM: ScreenOverdrive = 1 : OK <--- SCREEN MODE
2/22/2025 9:27:37 PM: NE156FHM-NX6 HDR: False 8 13 True
2/22/2025 9:27:37 PM: Mode = 2 : OK <---- MAIN MODE (SILENT)
2/22/2025 9:27:37 PM: TUF_KB = 16712125 : OK 
2/22/2025 9:27:37 PM: AuraMode: AuraStatic
2/22/2025 9:27:37 PM: TUF RGB = B4-00-0A-0A-0A-EB : OK <---- BACKLIGHT MODE
2/22/2025 9:27:38 PM: TUF Brightness = 131 : OK <---- BACKLIGHT BRIGHTNESS

Keep in mind, that if power-source change happens in less than 3 seconds since previous power change, it will be ignored. This is done intentionally to prevent modes changing all the time if something is wrong with device power. But it's done like that from the very beginning, and not changed neither in 0.202 nor in any other release :)

g-helper/app/Program.cs

Line 229 in d68bdb2

if (Math.Abs(DateTimeOffset.Now.ToUnixTimeMilliseconds() - lastAuto) < 3000) return false;

Do you have exact time when scenario you explain happens so I can look deeper in the log ?

[seerge]

@xM1haix P.S. After looking deeper in the log, you indeed seem to be plugging in and unplugging your laptop all the time (every 1-2 seconds)

App reacts accordingly, but why do you do that ? Or is your power delivery just failing by some reason?

[xM1haix]

First of all thank you for your time and responses!

but why do you do that ? Or is your power delivery just failing by some reason?

The plug inside the laptop has problems and the contact is imperfect in certain positions, so until I find the position it connects and disconnects many times, becoming very annoying.
I will share a new logs in few minutes.

[seerge]

@xM1haix well, you kind of have your answer.

Power constantly going on and off in your case, making hardware / windows spam power events to app. Furthermore that's why windows spams same (i.e. online-online) power events.

And app reacts as it should, it just can be switching modes back and forth every second :)

Try to seal power connecter somehow may be ? It's a hardware problem, not software here.

[xM1haix]

@seerge Why if i full close the GHelper and start it everything works fine settings are saved when Power Mode StatusChange is switch ON or OFF?

I can record a video if this would help

[seerge]

@xM1haix because when you start G-Helper it sets all settings based on current power source.

But when you switch power source - it also does that. Just in your case it's being "fooled" by constantly spamming power-source event.

Like "fake" Online (plugged in) from windows due to a broken plug and then in a half-second "real" Offline (battery). Second event is ignored (due to a 3 second limit i mentioned above).

I'm not going to remove this limit as this will cause more trouble - app will be spamming settings all the time then. Neither G-Helper nor even windows don't know about broken charger, they can't know if laptop is really on battery now or if it's broken contact.

Btw, there is also firmware/hardware switching happening in your case probably (cause firmware also reacts on power source changes). So I just advice to fix charger :)

[xM1haix]

@seerge can you please check the video and tell me if this is normal?

00-14-55.mp4

[seerge]

@xM1haix did you read my explanation above ? :)

Also just look at this guy on reddit https://www.reddit.com/r/ASUS/comments/1go85p9/charger_problems_help/

He has similar hardware issue (non-stable power delivery) and AC just spams mode changes all the time. Do you want it to be like that ? :)

[xM1haix]

@seerge I get that, make sense why that happens but i can make it stable and apps works just fine without any kind of error after i close it then i start it, the first run is faulty and I don't see why would that be connected to the plug problem. if that would be it, then if app acts weird before closing it, it should act weird after i start it or I what I said it doesn't make sense? and please explain me why.

Thank you!

[seerge]

@xM1haix when you start app over - you manually force it to set mode again based on current power source.

When it reacts automatically on (incorrect due to hardware issue) power events from the system - it sets mode only for the first event from the chain of spam. And if first event says that laptop is "plugged", while you de-facto unplugged it after, further "unplugged" events are ignored cause they come too fast.

By the way, there is an optional setting you can set in config to delay reaction on power-source change. Try it
https://github.com/seerge/g-helper/wiki/Power-user-settings#plugged-in--on-battery-actions-delay

[seerge]

@xM1haix did setting a delay help you ?

[xM1haix]

@seerge It made worst to the software it self, if something like in the video happens GHelper stops responding, so I reset the settings and I will try to fix my connector as soon as possible but I need the laptop on daily basics, so it will take some extra time, I could close the issues now and if after I get it fixed problem will still be there I will let you know. If that's fine for you

[seerge]

@xM1haix what did you set as a delay ? Try to set a small value (1000 milliseconds = 1 second). App would indeed stop responding as it just pauses whole thing, but 1 second shouldn't be really noticeable.

But besides that I can't offer anything :) cause as I have explained you literally have underlying hardware problem, and G-Helper's automated mode switching is not the only thing affected by it.

[xM1haix]

@seerge I actually set higher value 10k

[seerge]

@xM1haix can you try 1000 as I initially suggested ?

[seerge]

@xM1haix any updates here ? :)