[P650SE] Headphone Jack Dies After Uninstalling Clevo Control Center?

Hi. I have a Clevo P650SE that I bought back in 2015. I would like to remove the Clevo Control Center application as I consider it to be worthless. It consumes systems resources and frequently changes my keyboard brightness on startup, which is something I find to be an annoyance.

I have tried many times before to remove this software but each time I uninstall it, the 3.5mm headphone jack stops working after resuming from sleep mode. The headphone jack will not function until I reboot, and the only solution to prevent the issue entirely is to reinstall the Clevo Control Center application.

I researched this problem and found several people with the same issue as me on various forums. As a workaround I tried keeping Clevo Control Center installed and just disabling the program from startup, but that did not solve the problem.

 

I believe Control Station has a fix for this.

 

That is interesting, thanks a lot. Seems like a handy alternative to Clevo Control Center!

I did find another solution after spending a lot of time researching, yesterday. The answer was posted at the link here: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1313904/comments/19

It seems that when installed, the Clevo Control Center directory contains a file called InitHeadphone.exe. When the system resumes from sleep mode, CCC runs InitHeadphone.exe to reinitiate the headphone jack.

The solution to prevent the headphone jack from 'falling asleep' without CCC being installed is to copy InitHeadphone.exe and hp.dll from the CCC directory to a different folder. Uninstall Clevo Control Center and reboot. Then create a new task in Task Scheduler with the trigger 'On workstation unlock of any user' and set the action to run InitHeadphone.exe from the new folder. In the conditions tab, uncheck 'Start only if the computer is on AC power'.

Now the headphone jack works perfectly without any hassle, and I can happily keep CCC uninstalled.

 

That'll work, and is similar to what Control Center does.

I solved the problem with upgrading my audio to the Creative G6 USB DAC/Amp. Utterly smokes the Realtek solutions in sound quality, noise, and power.

 

I did briefly look into getting a DAC about a year ago. It's hard to know whether it would be worthwhile because I've never had experience with one before. I probably don't know what I'm missing.

I have a pair of Audio Technica ATH-M50 headphones that I just use directly into the headphone jack on the laptop and smartphone. I've never had any major complaints about the sound quality when listening this way, and I have no desire to make it louder since I never go above 6% volume in Windows 10. The sound is quite flat in the laptop by default, but I use the 'Party' equaliser profile in Realtek which makes a drastic positive difference.

 

I doubt that the onboard Realtek DAC differs that much in sound quality or noise to the Creative G6. The Creative G6 will probably have a better op-amp than what is in the laptop, so you should be able to drive higher impedance headphones with the G6.

PROOF: Realtek ALC1220 vs Sound BlasterX AE-5

 

"I used a brand new 4-foot (~1.2m) gold-plated aux cable that I grabbed on Amazon and plugged it into the speaker output on my motherboard, and looped it back into the line-in input. On the Sound Blaster, I used the same cable, plugged it into the speaker output, and looped it back into the microphone input on the card."

Loopback testing only tests the capabilities of the ADC and mic circuits, and not the actual DAC output. A proper test would have outputs going to a dedicated test lab, or to a known quality soundcard with a known higher quality line-in and ADC. So all he did was prove that Realtek ADC was slightly less quality than the ADC on the G6.

I see he redid them, and tested the output with the other's input, with similar results on the dynamic range. Still, the ADC is the limiting factor.

Another site tested the G6 output on a professional test bed, and maxed out the tester at 120dB.

So, sorry, the "proof" you offered isn't proof.