CLEVO Drivers Update Utility by OBSIDIAN-PC

Keyboard LED works nicely for the strip on my P750DM2G model. It would be neat if the strip could be made reactive, with the keyboard zones left static (in my case).

I'm not sure whether the keyboard is supposed to 'wake up' on mouse or trackpad activity yet, but it isn't doing so here.

 

Me too on a P775DM3-G. No idea what's wrong

 

About the LED control for the logo and stripes on the lid, is this actually supported on all models, from all resellers? If not, is there a list somewhere of which models do have this feature? Maybe many of us are trying for something that will never happen.

 

It seems like obsidian tools dont use %PROGRAMFILES% variable. Noticed, when i was unable do install them on my windows on drive H.

 

Yeap you are right, that is not compatible with your wifi! Sorry for that, we will fix that in some minutes.

Nope, it actually gave me a lot more work to make it work ONLY with the keyboard. Would you like a option to "Also wake up with mouse activity" ?

 

Nice update! It now saves correcly, was worth looking into the .ini file

The autodim is causing some kind of infinite loop when selected on my device. when selected the program goes beserk and I can't select anything, had to restart the tool.

glad to see something happening on the keyboard LED :3

Am still hoping that the "random breathe" mode or just rewrite the random mode with fading in and out, I doubt anyone likes the random color abrubt changing colors.

 

Updated Keyboard LED to 0.1.10

- Brightness label shows actual value and what is controlling brightness
- Added option to wake dim with mouse keys too
- other small bug fixes

 

Ok, i found a strange bug. I noticed that the keyboard backlight was not completely turning off after one minute like it used to. It would fade, but only to about 25% brightness, but never off. So i tested it with the slider, and sure enough, when i moved it from 100% to 0%, it was still lit. That was a normal bug. The strange one is, if i move the slider slower, the brightness will dim to, let's say 15%, even though it says 0%. then i tried to move it slower. Now, it got down to what looked like 5%, even thought it says 0%. If i moved the slider fast, it barely dimmed. Anyone else see that problem?

 

Make sure you are using the latest version 0.1.10, i cant reproduce your problem!

 

I was..... hmm, will try again when i get home today. If still bad, will reinstall.

 

I was hoping it might wake with mouse/trackpad movement, as an option.

 

Just pulled down the latest update and I still can't get any tabs to respond other than the 'Stripe' tab that its currently on now.

Cant change colors, or anything. Still broken.

 

The only way for the other tabs to be "Disabled" is if you have any effect selected.
Please be sure you have "Effects: None".

 

Hi John your update program work with w650kk1?

 

Ok got it. Just checked and yes that releases the 'lock'.

I would highly recommend making that more 'intuitive' to the user by showing some form of notification, label, something/anything that gives them direction.

 

Yeap i know!! I will take care of it soon

 

Thank you for the constant feedback to the community here, it means a lot "especially to me as a software dev myself"

 

I am on the latest version. So after some more playing, it only happens when using the Temp/Load Reactive tab. It works just fine under all other tabs. Maybe it has to do with the way you are polling the temps?

 

On the https://code.obsidian-pc.com/product/obsidian-tools/ website there is no P950HP6, only P950HP, whereas in the UPDATER itself there is no P950HP, only P950HP6. Maybe you forgot to sync the two lists.

Updating Windows after a clean install can only be done if the Wifi drivers are installed. If Windows setup doesn't get the Wifi working I'll have to do it myself and I should probably install the chipset drivers as well. Planning to install Windows 10 1809.

So, I install Windows, then -
If the Wifi is working I run Windows Update first and then update everything using the UPDATER.
If the Wifi is not working after Windows setup I install the chipset and Wifi drivers and then run Windows Update and then update everything using the UPDATER.
Is that the way to go?

 

Why not download what you need beforehand? No need to have to use Win Update.

 

Good idea - I suppose I could use the Force Enable All option in the UPDATER to make it download all the drivers.

 

There is actually a need for Windows Update (unfortunately).
Even when you use the Microsoft Media Creation tool, in some languages the installer will not install the latest build (at least this was true some while back).
Some of the drivers in the Updater are not compatible with older windows builds and that´s why we recommend making sure you are on the latest build.

What im adding to the Updater is a Windows Build detection that will warn you if you are not running the minimal build required for all drivers (this should be pushed on next update).

 

You don't even need the Microsoft Media Creation tool. Several safe places who offer last ISO for download. And in most languages. Many have the OS but lack the last patches and you can get them at Microsoft as standalone installer (no need to be connected to the web when installing).

I talk about download latest patches for your prefered OS version beforehand (if needed do the same for last Servicing Stack for the correct OS version). Have everything downloaded beforehand has always worked for me.

 

Keyboard LED Updated to 0.1.11
- Instead of disabling tabs when Effects are selected, each tab will now show a message
- Brightness change fixed for Temp / Load Reactive
- Fixed a bug in which brightness level was not being updated
- Replaced Stripe image

 

I understand that, but it´s not something i personally need, i use iPXE deploy with latest builds... the thing is... not everyone does that, and there´s no way for me to force anyone to use the latest build.
Looking at the amount of emails we get saying that a driver does not install because it says "bla bla bla not for this windows version" i can assure you that A LOT of people just grab the media creation tool, make an usb, install.
As i said before, the hardest part of coding this type of software is never the actual functionality, its preventing and thinking ahead about what can go wrong, the amount of code you need to add to make everything work in all scenarios (Languages, OS builds, Laptop models) is INSANE!
-Windows builds have a toll on the Updater, hence my soon to be introduced detection/warning.
-Windows language plays a role on some of Control Station functions
-Windows Regional settings plays a BIG role on Control Station (some regions use comma others use dot for decimals)
-Model versions play the heaviest role in all apps, it´s insane!
-Bad driver packages need all sorts of tricks for them not to go bad, different switches, triggering uninstall first, asking for reboots if needed first, etc
-Even having External Audio devices made my life hard, since requesting them inputs/outputs names crashed my Control Station
The list goes on...

I will not even talk about MS methods, you learn one and then when you need to learn the next and it´s like it´s a whole different language, it´s frustrating.

 

Sorry but this is not a very good advice. Always download the Windows ISO using the Microsoft Media Creation Tool, it's safer.

Welcome to programming. If you want we can provide you a shotgun so you can kill yourself now and avoid all the future headaches.

 

KEYBOARD LED app saying QtColorPicker v1.0.2 in the taskbar.

 

It is a smaller download as well. There are tools that allow you to download all the applicable updates and integrate them into the ISO but they are not very user friendly - yet.

 

Updater updated to 2.1.8:

-New System tab to check for Windows build version
-Added option to disable Windows automatic driver update
-Will display warning on app start if Windows build is too old
-Added button to open Windows update settings
-Improved change log display

 

Any chance you can add the Overclock fan profile mode to Fan Control, and have an option to default to that when exiting? I think it is part of the EC...or at least with CCC I was able to activate Overclock profile then close the program. Maybe I'm wrong though? Just looking for a quick fix to use a better fan profile without having all the audio popping and clicks from the DPC latency. With EC Automatic my GPU can run up to 91 celsius and start throttling while the automatic profile won't put fans any higher than 30% :/

BTW since I assume you are working on a way to access fan speeds without ACPI driver usage, it would be really amazing if you could write an actual generic interface sensor and control driver for them so they can appear in tools like OHM/HWinfo64/AIDA64 and would also be great to have your fan control program interface with said driver, but it would also allow other fan control programs to do the same job or even open your fan control app to more devices than just Clevo.
Do you know if the fan speeds and temperatures are available via i2c?
Honestly it baffles me that Clevo's software programmers didn't do this themselves...
Of course, the driver should not be free but perhaps available only with a Fan Control license.
I guess that's a part of what makes Linux great is that all hardware interfaces are open to software without having to write code to directly access the hardware from userspace. Windows should follow this...

 

You should not get Audio drops with 500ms refresh rate and using CPU Temp engine like Coretemp or OHM.
But yeah, im now focused on the service! It´s not a easy task

 

I don't know if this has been asked before: is there a benefit to switching to another CPU monitoring program for fan control (i.e. more precise readings?)?

 

Core Temp or OHM use Ring access to get temperatures, stock CLEVO (which is the internal) stacks ACPI which induces latency. If you can use them OHM or Coretemp (which works best).
They are better then the internal solution.
Future releases will have a new method which is in the works

 

John,

I've been wanting to report this since I started using the tool but just kept forgetting.

Something I have noticed with the Lightning of the Keyboard LED side is that its actually much lower "dimmer" than the original functionality.

Yes before you ask, I have the brightness turned all the way up in the app. Its most noticeable when I am booting up the laptop and it shows the generic "yellowish" color before the Keyboard LED app is loaded and applies its color. It is MUCH brighter there. Then the LED Keyboard control takes over, applies my color and its much dimmer.

This is for a P870TM1.

 

There is not actuall brightness control, at least i´m not using it, if you use a primary color like RED, going "dimmer" is just going from Red to Black in the RGB scale.
So what you report should only happen if you have a different color then the one it uses to boot up then you can probably notice a "dim" effect when it changes to the selected color because some RGB colors are dimmer then others.
You can make the test, install control center and set Brightness to max, then in Keyboard LED reduce the brightness and set it to max again, check to see if there is any difference with same colors.

 

I have already done a test just to confirm it wasn't just my eyes playing tricks based on the different colors.

I set the color to the default yellow'ish / white that loads with windows and its still dimmer.

 

Could be an initialisation issue. I have noticed that the brightness slider settings don't get applied until you move the slider a little bit. Windows 10 behaves funny sometimes.

 

Any luck obtaining one? Thanks!

 

Really sorry but not only i havent found much time for it but i also dont have them in stock!

Notice:
-Full Windows Service (by the book) to pool value = Done (direct EC Access NO DPC LAG) - Internal testing being done
-UI User software to access service and display values (testing purpose) = Done - Internal testing being done

HAPPY DAY!

 

Hi John,

My new Obsidian laptop arrived recently and I love it! I have one issue in that today the GPU Fan 2 is now always on and I'm unable to control it via the Fan Control software. Do you have any solution to this problem?

Many thanks

 

What model is it?
Usually GPU Fan 2 is in sync with GPU fan 1... unless you changed "Second GPU fan mode" in the Behavior tab.

EDIT:
To anyone that wants to test, a quick gui based on the same code that we will be using for the service:
https://www.obsidian-pc.com/CLEVOMonitor.zip

It´s CLEVO EC reading + NVAPI

YES it uses a very similar dll like the ECView, NO it will not damage your laptop, this is as clean and safe as it can get, way better then the CLEVOMOF stuff...
We wrapped it and contained it and it uses the best code i probably ever written.
PS. didn´t waste time on UI since it´s testing purpose only.

Report:
- Let me know if it´s not working on your system!
- Specially interested on SLI systems

 

Sorry for not mentioning this, It's an N850HP6 i7.

I tried changing the Second GPU fan mode to Force Sync to GPU Fan 1 but it didn't change anything.

It started after I left Steam downloading games overnight and the laptop seemed to hibernate by itself after a while, even though on power options I have it not to sleep at any point while plugged in. So I'm not sure if that caused anything.

I tried modifying the speeds in the loaded fan table and it works for GPU Fan 1 but 2 stays at a steady level the whole time. It's not loud, just always on.

I tried running CLEVOMonitor just now and get the following message: "This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem."

 

Update: It seems to have stopped by itself. I'm not sure why but let's hope the problem doesn't come back!

EDIT: The fan started up again. Very strange!

 

Uhm... Your system only has 2 fans, 1 CPU and 1 GPU, no idea where you get the idea from that you have 2 GPU fans.

Here is a picture of your notebooks cooling:

 

I got the idea because there's fan control settings for 3 fans and I could seemingly control the first 2. But maybe it's just the GPU fan refusing to turn off fully

 

Those 3 fans are meant for systems like mine and the P870 series who have 3 fans.

It's more than likely that the CPU fan refuses to turn off.

 

Where are you controlling the supposed fans? Are you using the MANUAL mode?
And yes, your system does indeed ONLY have 2 fans.

 

Thank you both for clarifying It definitely wasn't the CPU fan as I can hear that turn on and off.

I'm controlling them by tweaking the numbers using the software in the attached image.

Note that it's been working as intended for a few hours now so please feel free to disregard my posts. Have a great day

 

Ohhh the table based.
Although it shows 3 blocks you can use only two in your case.
That's just the default values so that it works with all units.

Also .. it's all going to change soon, the service is gona rock!

Sent from my MI Note 2 using Tapatalk

 

Awesome, looking forward to it!