[Experimental] Manual Fan Control stopped working after lid closed for long #3519
Comments
|
@chertvl hello, It just can't connect to AsusSAIO driver that it uses to do fan control / fan readings. Did you update to latest 0.200 (experimental) ? I have added some change that it will try to force this driver auto-start with windows all the time. |
@seerge |
|
@chertvl sure, if app will notice that SAIO driver is not working (on start) it will try to start it and also set it to auto-start with windows (and ask for admin permission if it doesn't have it). But otherwise - it should be same |
|
@seerge Maybe we can make a some logic to try re-enable manual fan control in some delay after screen enables or lid opened? |
|
@chertvl can you run following in powershell as admin And then reboot and check if it still happens? |
Hello @seerge P.s.: З наступаючими святами! Ми можемо продовжити пiсля свят, проблема не критична :) |
|
@chertvl hello, this means that driver is either not responding or returning nonsense after wake-up from sleep. Can you check if restarting G-Helper completely in this situation enables fan control again ? |
@seerge restarting app log: Found that error now is easy reprodusable. I just need to press Power button and wait around ~10sec or less for notebook will completely goes in sleep mode, than I wake up him and see that fan contolling stopped working. |
|
Hello @seerge In search of solution i've found there is must be at least 1-3 second delay when machine is wake from sleep or unlocking. |
|
@chertvl ok, thanks for checking. Do I understand correctly that to "re-enable" fan control - you just set same mode again ? I.e. if you click on existing active mode button again - fan control works again ? |
Yup, exactly. If I understand logs correcly, G-Helper try to apply all parameters again in current mode (after wake up from sleeping) every time, but problem is G-Helper does it too quickly, SAIO driver is not ready in that moment, it will be ready in 1-3 seconds. |
|
Hey, @seerge |
|
@chertvl hello, I think SAIO driver is still running, but it needs some time to "wake up" after sleep in your case. On my laptop it wakes up immediately. Now app would retry manual fan control 3 times before turning it off, if SAIO returns nonsense / zeroes. Try this build |
Jesus ;o Power (sleep) button pressed: By closing lid: |
|
@chertvl ok, glad to hear. I will include this change in the next "release" of the experimental build then. Thanks |
|
@seerge |
|
@chertvl this build should do up to 5 retries |
Rules
What's wrong?
Hey, Seerge.
Using Experimental version about 3 weeks and found one interesting behavior of this.
When I closing lid of my notebook and it goes to sleep for long time or something, after wake-up and lid opening Experimental Fan control feature stop working.
In logs I found this (below).
For some reason GHelper can not read temperature and disable manual fan control. But GHelper dosnt re-enable it when CPU temp is readable again (after wakeup from sleeping or lid is opened), and i need to manually click on same Profile or switch it to another for re-enable that function.
Can we do something with it?
Ps.: I use my notebook without fan 99% of time. only passive cooling (<60 degrees). So suddenbly enabled fan with standard bios algorithm a little bit annoying.
Thanks
How to reproduce the bug?
I dont know exactly, maybe there is only for my model, but just enable experimental fan control and close the lid for 12-16 hours, let it do they windows-sleep things.
Logs
24.12.2024 2:27:47: Lid Closed
24.12.2024 2:27:47: TUF Brightness = 128 : OK
24.12.2024 2:27:48: Monitor Power Off
24.12.2024 2:27:48: TUF Brightness = 128 : OK
24.12.2024 3:29:19: TUF Brightness = 128 : OK
24.12.2024 3:29:19: Error reading CPU temp
24.12.2024 3:29:19: SAIO: BB-01-50-00-00-00-00-00-00-00-01-14-00-00-00-00
24.12.2024 3:29:19: SAIO: DD-03-82-31-00-00-00-00-00-00-00-00-00-00-00-00
24.12.2024 3:29:19: Manual fan control OFF
24.12.2024 3:29:19: SAIO: BB-01-50-00-00-00-00-00-00-00-01-14-00-00-00-00
24.12.2024 3:29:19: SAIO: DD-03-82-31-00-00-00-00-00-00-00-00-00-00-00-00
24.12.2024 10:00:24: WMI event 87
24.12.2024 10:00:24: WMI event 123
24.12.2024 10:00:25: WMI event 235
24.12.2024 10:00:26: WMI event 88
24.12.2024 10:00:26: WMI event 123
24.12.2024 19:50:57: Lid Open
Device and Model
Asus Vivobook S15 OLED (S5506MA)
Additional information.
No response
Armoury Crate
Uninstalled
Asus Services
0 services are running
Version
0.199 [experimental]
OS
Windows 10
The text was updated successfully, but these errors were encountered: