[Experimental] Manual Fan Control stopped working after lid closed for long

[chertvl]

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?

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

[seerge]

@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.

[chertvl]

I have added some change that it will try to force this driver auto-start with windows all the time.

@seerge
Oh, yes, just updated to 0.200, and am exploring the features you added for me.
I apologize, I didn't know that there were changes related to force this driver auto-start with windows. In that case, I'll watch it the same way until tomorrow, and close the issue if the problem doesn't happen again tonight. Thank you very much for your responsiveness and help!

[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

[chertvl]

@seerge
It didnt take long to wait.
0.200 (experimental) version, at 23:48:33 error apears again, after screen power off and on.
Again click to confirm current or change profile to another helps to re-enable manual fan control.

Maybe we can make a some logic to try re-enable manual fan control in some delay after screen enables or lid opened?

24.12.2024 22:54:30: SAIO: DD-03-82-35-00-00-00-00-00-00-00-00-00-00-00-00
24.12.2024 22:55:08: TUF Brightness = 128 : OK
24.12.2024 23:04:12: Monitor Dimmed
24.12.2024 23:04:27: Monitor Power Off
24.12.2024 23:04:27: TUF Brightness = 128 : OK
24.12.2024 23:48:33: TUF Brightness = 129 : OK
24.12.2024 23:48:33: Monitor Power On
24.12.2024 23:48:33: AutoSetting for Online
24.12.2024 23:48:33: BatteryLimit = 80 : OK
24.12.2024 23:48:33: FnLock = 0 : 0
24.12.2024 23:48:33: Eco flag : -65536
24.12.2024 23:48:33: Mux flag : -65536
24.12.2024 23:48:33: \\?\DISPLAY#SDC416E#4&1d4bfa&0&UID8388688#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7} DISPLAYCONFIG_OUTPUT_TECHNOLOGY_INTERNAL
24.12.2024 23:48:33: \\?\DISPLAY#SDC416E#4&1d4bfa&0&UID8388688#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7} \\.\DISPLAY1\Monitor0
24.12.2024 23:48:33:  HDR: False 10 1 False
24.12.2024 23:48:33: Mode = 0 : 0
24.12.2024 23:48:33: VivoMode = 0 : OK
24.12.2024 23:48:33: FanCPU = 41-42-44-48-4B-50-54-5C-00-08-12-24-36-45-52-61 : 0
24.12.2024 23:48:33: FanGPU = 41-42-44-48-4C-50-54-5C-00-0A-11-23-35-45-54-63 : 0
24.12.2024 23:48:33: FanRangeCPU = 00-F7 : 0
24.12.2024 23:48:33: FanRangeGPU = 00-FC : 0
24.12.2024 23:48:33: Reset Mode = 0 : 0
24.12.2024 23:48:33: SAIO: BB-01-50-00-00-00-00-00-00-00-01-14-00-00-00-00
24.12.2024 23:48:33: SAIO: DD-03-82-31-01-00-00-00-00-00-00-00-00-00-00-00
24.12.2024 23:48:33: Manual fan control ON
24.12.2024 23:48:33: Error reading CPU temp
24.12.2024 23:48:34: SAIO: BB-01-50-00-00-00-00-00-00-00-01-14-00-00-00-00
24.12.2024 23:48:34: SAIO: DD-03-82-31-00-00-00-00-00-00-00-00-00-00-00-00
24.12.2024 23:48:34: Manual fan control OFF
24.12.2024 23:48:34: SAIO: BB-01-50-00-00-00-00-00-00-00-01-14-00-00-00-00
24.12.2024 23:48:34: SAIO: DD-03-82-31-00-00-00-00-00-00-00-00-00-00-00-00
24.12.2024 23:48:35: Session:SessionUnlock
24.12.2024 23:48:35: \\?\DISPLAY#SDC416E#4&1d4bfa&0&UID8388688#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7} DISPLAYCONFIG_OUTPUT_TECHNOLOGY_INTERNAL
24.12.2024 23:48:35: \\?\DISPLAY#SDC416E#4&1d4bfa&0&UID8388688#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7} \\.\DISPLAY1\Monitor0
24.12.2024 23:48:35:  HDR: False 10 1 False
24.12.2024 23:48:43: Input device not found
24.12.2024 23:56:02: TUF Brightness = 128 : OK
24.12.2024 23:57:18: TUF Brightness = 129 : OK
24.12.2024 23:58:04: TUF Brightness = 128 : OK

[seerge]

@chertvl can you run following in powershell as admin

Set-Service -Name "AsusSAIO" -Status running -StartupType Automatic

And then reboot and check if it still happens?