CLEVO Drivers Update Utility by OBSIDIAN-PC

Do you have CLEVO CONTROL CENTER installed? Does the keyboard lights work there?

 

It's a p650hp6-g. Actually though it works but doesn't check for the "leave touchpad enabled when mouse is plugged in". It's basically the same as the windows setting switch "enable/disable". Anyway, I noticed that now, the Fn+F1 doesn't switch the touchpad on/off anymore.

Is that due to the fact that the suite overwrites some setting? Or is that due to the fact I don't have CCC anymore? Because all the other Fn+whatever work fine

 

I uninstalled the clevo control center, but when it was installed the keyboard lights worked there.

 

Ahhh right...forgot about that touchpad option... will add code to check for that too...

PS. I just successfully added the NVIDIA API to fan control having a lot of fun with it

Hummm thats weird, it should work out of the box.
Maybe its better to wait until i finish it, its still beta...
The only way for it not to work is the fact that a required DLL was not installed... you can try to re/install control center and check if keyboard led works with control center installed...

 

I tried that too.

 

Any idea why Fn+1 is not working anymore for enabling/disabling touchpad?

 

You can enable / disable with control station but the keyboard shortcuts do not work is that it?
What's your model again?

Sent from my MI Note 2 using Tapatalk

 

Is there anywhere I can find a consolidated list of all the keyboard shortcuts? (Fans, etc)


Sent from my iPhone using Tapatalk

 

yep, but before uninstalling CCC and switching to the new suite the keyboard shortcut for touchpad was working. Moreover it's the only shortcut that stopped working.

model is p650hp6-g.

It's not that important but I'm just wondering why it's behaving like this. Maybe I should force a touchpad driver update?

...by the way, congrats for the software! It's a really good one. I hope you get the awards you deserve!

 

More importantly, partnerships with Clevo ODMs.

That would go a long way into cementing the success of this project.

 

damn, an aggressive fan profile now grants me 5-10°C lower spikes than before. That's nice! I guess i might really try to unlock power throttling through XTU and try to unleash some more MHz when performing simulations

 

Speaking for myself (my software)
Only Fan Control includes the option to use Keyboard Shortcuts...
Everything else that user are talking about is for the ORIGINAL keyboard FN+Shortcuts, those have drawings in your keyboard... so they are easy to find.

FAN CONTROL Milestone SUCCESS
Fan Control now includes NVIDIA API for accurate GPU access, it no longer needs OHM and it will not make any difference if you have Optimus or not, if GPU is enabled or not.
This is part of our own monitoring solution, we have decided not to rely on EC readings or 3rd party software.
Our NVIDIA monitoring gets values faster, more accurate, in a lighter way.
Will be available on the next update!

 

Agreed!
@John@OBSIDIAN-PC I know you can't say who, but have there been good conversations with other resellers?

 

Not true on my laptop. I have no problem setting the volume control to any of these settings (3, 7, 10, etc.) if I close Control Station first. If I leave Control Station open (or relaunch it after it has been closed), then what you say appears to be true - but the issue doesn't appear to be with Windows, it appears to be introduced with the launch of Control Station.

 

@John@OBSIDIAN-PC I don't know if it is only a my bug (PA71ES-G) but the RGB lights keep resetting every time I suspend the PC or I fully shutdown it (with shift key). The default "start with windows" of the keyboard led software doesn't change colors but I have to select them manually. So I've optimized the task of the software to fix my problems. The simple solution is to add a delay at the startup task (I set it to 10 seconds and changed the trigger with login) and add a second trigger to fix the wake up from sleep ( System / Power-Troubleshooter / 1 ). I hope it will be useful to someone!

 

Oh... it appears you are right :O what confused me was the fact that windows volume control takes 2 steps from the mouse wheel...
Ok ill take a look into it later!

I guess that happens to you because you have CC installed right? The purpose of Keyboard LED is to be an alternative for those who do not want to use CC.

 

No I don't have CC. I think It's related with bios because when I wake up from full shutdown the colors just flash random until Windows starts. I don't know if someone else has this strange problem but they can fix it easy!

 

Any change to CPU polling?

 

Hey John, I don't think the keyboard LED restores the settings when resuming from standby. It seems to revert to the default blue.

 

Fan Control updated to 1.0.16

- NVIDIA API fully implemented! - Faster and Better monitoring, Optimus fully functional - PLEASE REPORT!
- Added another CPU Engine Monitor - CORE TEMP, you can now select CORE TEMP or Hardware Monitor! - PLEASE REPORT!

More engines soon, for now CORE TEMP seems the better (not tested with 8th Gen)
We intend to add our native engine for CPU too, just like we did with NVIDIA API.
If you have other famous monitoring engines that you find more accurate please report.

PS. for CORE TEMP we do not use CPU Package, we are using highest Core Value! This seems to be a more accurate approach.

BETA NOW OPEN AGAIN!!! - Yes you can use fan control for free at the moment!

Have fun and thank you for making this probably the most advanced Fan Control software!

We are soon going to add a lot more tuning options:
- Shared cooler logic
- Load Based Prediction
- Ramping/Update Interval in 3 temperature ranges
- Much more to come!

 

I have the top tier Obsidian Tools License and would like to give the fan app a try and purchase one out of beta. Is there a link to a DL?


Sent from my iPhone using Tapatalk

 

Hey John, your latest forces my coretemp to pop up every second..right now i cant use fan control and core temp simuntanioulsy, because the coretemp window is on top of everything. switching to OHM does help tho.

 

So, i haven't been using the fan control full time yet, being in beta and all, but I gave it a try while playing about 2 hours of AC Origins, and I gotta say, i'm impressed! With CCC, I would have random crashes while playing, always around a temp spike. With CC, i did not get 1 crash! All i used was EC automatic, have not played with any settings. Using Core Temp.
Also, I can report that the GPU info does load while in Optimus mode.

Thanks again for all the work!

 

Got it!
Weird glitch where it makes Core temp restart.
It's an easy fix, will do it first thing tomorrow...

Sent from my MI Note 2 using Tapatalk

 

The latest version also keeps waking up the GPU when on battery. Even when using the old OHM setting. Didn't do this in the previous version. I.e. RIP battery life.

 

How are you monitoring that?

Sent from my MI Note 2 using Tapatalk

 

Using GPU-Z/OHM, OHM will report GPU temp as 0 when it's asleep, and GPU-Z will not show gaps in the sensor bars. But every second or so it will briefly wake up when the fan control is running. Battery life at 100% = around 1.5 hours. With the previous version or without fan control running, OHM shows GPU temp staying at 0 and GPU-Z will show blank readings for all the sensors. Battery life = 3.5 hours.

 

Thanks for reporting.
Should also be easy to solve.
What is probably triggering activity is the sensor query, so I'll query it only if GPU is enabled

Should have it fixed soon
Time for some sleep, will get back at it in 8h...

Sent from my MI Note 2 using Tapatalk

 

Here's what I mean:

No prob, thanks.

I've attached an example of what I mean. Left side is is fan control off/old version, right side is current fan control.


Also unrelated but not sure if you saw my last message, keyboard LED tool doesn't seem to set the values after resuming from standby even when the EXE is running in the background. It reverts to the default blue. Double-clicking the keyboard app icon in Control Station will restore the set values.

 

Can you show a small video how that works ?

 

@ John@OBSIDIAN-PC What are OHM or CoreTemp used for? ...I mean, since the Control Center is using throttlestop already couldn't you monitor the cpu using throttlestop in order to limit monitoring threads and queries? Wouldn't this be "more efficient"?

Might be a dumb question but I'm kinda curious

 

My LED App doesnt start with windows anymore at my work laptop.
my private one it still works. any tipps how to fix this?

 

I wish... Currently there is no way to access TS data...
In the final fan control we will have our own monitoring too, but I want to give users the chance to select any monitoring app that they already use, this way you can reduce the amount of background apps querying sensors...
Oh and Control Station does not use ThrottleStop at all...

Sent from my MI Note 2 using Tapatalk

 

Untick start with Windows and re-tick it again...
KeyboardLED is ultra beta, a lot of work ahead... I need more time

Sent from my MI Note 2 using Tapatalk

 

I tried that several times of course, didnt work. No showstopper, i will wait for a fix patiently keep it up!

 

Hummm starting it up is just a simple Task Scheduler entry... Can't see how it would go wrong unless you changed something in the task.

Sent from my MI Note 2 using Tapatalk

 

I changed nothing in the task scheduler. seems my package is a bit corrupt and i need a clean install.
all i did was adding the LED shortcut to shell:startup, without success tho.

 

And will you also make your own throttlestop in order to reduce background apps even more?

 

Nop... TS is already too good, cant even imagine the work behind it...
Would be cool if the developer added a Shared Memory feature with sensor values!

 

@ John@OBSIDIAN-PC, seems like something wrong with latest Fan Control v1.0.16. I'm not sure why. After switching back to EC Automatic, the fans do not spin which is very dangerous. I does not happen at previous version.

 

^ the version you gave me spins fans on EC Automatic, @John@OBSIDIAN-PC

So cross check those maybe?

 

Nop actually is a bug... well kinda...
What happens is, the security settings are still activating during EC Automatic or Max Speed, which should not happen, because when that happens it will enable manual control and set to max fans, but then when it gets out of security ranges it will still keep a fixed manual control over fans...

Update Released!

 

Does this update address the GPU wakeup issue?

 

Fan control broken. Free version. Specs in my sig. CCC installed.
In fan control, if I select EC Max speed, fans go to max as expected, but then when I go back to EC automatic (still in the fan control app), the fan speed comes down a little bit, but remains way too high for the idle load. No output monitor, so I can't tell you the actual speed, but sounds like 80%. Stays that way even if I quit the app. I have to launch CCC, select max speed, then automatic, and then the fans quiet down.

If I select manual mode, all sliders are at 0. The default values seen earlier are not there.

EDIT: the normal EC automatic speed behavior came back after I exited ControlStation and relaunched it. That might be needed after an update.

EDIT2: now going from max to EC automatic, the GPU fans are stuck on noisy. Becomes OK after a while.

EDIT3: fan control causes system (ntoskrnl.exe) to show 12-14% CPU usage. (as seen in task manager). Becomes OK after a while.

 

New update should fix this!
I just spent ALL DAY working on Optimus!

Basically what all monitor apps do is either wake GPU on launch and keep monitoring it and keep the gpu enabled, OR, will show output ONLY when you manually awake it... i hate both solutions.

NVAPI used to NOT wake the GPU, well this is broken on most recent drivers.... in fact i tested a bunch of software and i could not believe my eyes, some monitoring / OC software keeps waking and turning off GPU, causing more battery drain and stutter!!!

I tried a different approach, i monitored all methods (to get values from GPU) to find which do not activate the GPU so i could use them to check if GPU is activated or not, then i run the remaining code ONLY if GPU is active.

There was no sample, or guide on how to solve this, basically there should be a way to use NVAPI to know if GPU is enabled or not, BUT, getting values that would allow me to know this, like get power states and most of usage metrics will end up enabling it... hence i made my own method.

This might still need some tunning but on my test units it is already working as intended!

Yeah, transition might get stuck, that was something temporary until next update....



For both of you...
Please update to Latest Version!

Fan Control 1.1.00
-NVAPI + Optimus Check - PLEASE REPORT!
-Improved Startup
-Removed Security Settings from EC Automatic / Max Speed - It was never supposed to be there!
-Improved transition to EC AUTOMATIC mode

 

1.1.00 is still waking up the GPU every second or so

Edit: it's fixed

 

FC 1.1.00 GPU fan still getting stuck in high speed on going from max to EC automatic. Exiting FC does not fix this. Only running CCC and switching fan modes gets things back to normal.

Btw. NVIDIA has their own tray icon which shows whether the GPU is in use or not. They must have that code somewhere.

 

Are you sure the app you are using to monitor that isn't the one doing that?
I tested on 2 different systems and it was working fine.

Sent from my MI Note 2 using Tapatalk

 

Yeah I have those apps running all the time anyway. As soon as I closed Fan Control, the GPU stayed asleep. I'll do some more testing just in case.

Edit: OK it seems like OHM was waking it up as it was a different instance to the one started by Fan Control. Seems to be working as intended now. Thanks!

 

Hummm maybe the code did not get pushed on last update.
Here is another, please report if its now fixed!

Fan Control 1.1.01
I remembered someone was using OHM to control a cooling pad or whatever was it...
So it makes sense the following new behavior:
- If you select a CPU Monitoring like OHM or Core Temp when the app starts it will check if it is running first
- If it is running it will not do anything and just use the values
- If it is not running it will start the engine you have selected
I also added a new option in System Tab
-You can choose to leave it open if you want, either because you need it for other things or because you want to actually use it to look at the values!
Fan Control will no longer overwrite the settings for any engine