KPPD - Configure post-processing settings of your display! [2015/08/09]

Raijin

Senior Member
Nov 22, 2011
374
105
0
The first thing the daemon does is read the default configuration and apply settings immediately. It sounds like the 6P comes with some pre-configured post-processing. I recommend you flash a kernel with kcal support, write down the default values, then go back to kppd and add those values to the configuration file.
I extracted the values of the KCAL sysfs files. They are:

RGB 256 256 256
Contrast 255
Hue 0
Invert 0
Min 35 (not for KPPD)
Saturation 255
Value 255
Exactly the same that are by default in KPPD postproc.conf file. I tried too to play with the settings, specially "Value", but the problem persists.

-------------------------

Apart from that, I think I found the solution to the problem.

I'm using ElementalX kernel by flar2 to use KCAL. I've been searching his thread and commits in GitHub. The changelog of the v0.03 is "Small update to fix the washed out colors when applying color settings on boot."
The commits are the ones of day Nov 6, 2015. They are taken from your KCAL repository. You can see them here: https://github.com/flar2/angler/commits/ElementalX-1.00?page=2

Like flar2 said:

Ok...I think I figured out the washed out screen when setting color on boot.
If the settings are applied while the screen is off, it happens (this is regardless of sRGB setting in dev options).
If the screen happens to be on while the settings are applied, then it works.
After that, the fix came.

I tried the v0.02. I set SManager to run on boot some RGB commands to KCAL. After the device booted, and before SManager ran the commands, I've turned off the display. After ~15 seconds, I switch it on, and, surprise, the screen colors are washed exactly the same way that I'm getting with KPPD.
The difference between that KCAL fixed bug and the one I have with KPPD is that the KPPD one is when starting the daemon with screen enabled. I have not tested to enable KPPD with the screen off, if you'd like that, tell me.

Maybe the solution is merging the commits pointed before from KCAL to KPPD.

What do you think?

Thank you for your help!
 
Last edited:

savoca

Inactive Recognized Developer
Oct 28, 2011
1,784
5,701
0
Pasadena
downloads.codefi.re
I extracted the values of the KCAL sysfs files. They are:



Exactly the same that are by default in KPPD postproc.conf file. I tried too to play with the settings, specially "Value", but the problem persists.

-------------------------

Apart from that, I think I found the solution to the problem.

I'm using ElementalX kernel by flar2 to use KCAL. I've been searching his thread and commits in GitHub. The changelog of the v0.03 is "Small update to fix the washed out colors when applying color settings on boot."
The commits are the ones of day Nov 6, 2015. They are taken from your KCAL repository. You can see them here: https://github.com/flar2/angler/commits/ElementalX-1.00?page=2

Like flar2 said:



After that, the fix came.

I tried the v0.02. I set SManager to run on boot some RGB commands to KCAL. After the device booted, and before SManager ran the commands, I've turned off the display. After ~15 seconds, I switch it on, and, surprise, the screen colors are washed exactly the same way that I'm getting with KPPD.
The difference between that KCAL fixed bug and the one I have with KPPD is that the KPPD one is when starting the daemon with screen enabled. I have not tested to enable KPPD with the screen off, if you'd like that, tell me.

Maybe the solution is merging the commits pointed before from KCAL to KPPD.

What do you think?

Thank you for your help!
I see, well I would need a 6P in hand for that.
 

Raijin

Senior Member
Nov 22, 2011
374
105
0
I see, well I would need a 6P in hand for that.
I know this only concerns to Nexus 6P users, and apparently the majority are using KCAL with custom kernels, but... Could you try to merge these commits quoted in my previous post to KPPD? When flar2 merged them from your repository, the washed colors problem was resolved.
 

savoca

Inactive Recognized Developer
Oct 28, 2011
1,784
5,701
0
Pasadena
downloads.codefi.re
I know this only concerns to Nexus 6P users, and apparently the majority are using KCAL with custom kernels, but... Could you try to merge these commits quoted in my previous post to KPPD? When flar2 merged them from your repository, the washed colors problem was resolved.
KPPD and KCAL are to completely different sources. That's like asking me to merge in linux kernel patches into the Windows NT kernel. KPPD is already updated to behave the same as KCAL, if that's what you're asking. If there's an issue with how it works, it's likely on qcom's side at this point.
 
  • Like
Reactions: Raijin

brolic925t

Senior Member
Nov 20, 2011
1,743
673
0
Corona, NY
I'm trying to use this on my g3 as I like stock cm13 kernel over our customs ones... I keep getting null on output of scripts and all permissions are set correctly... Any help?
 
Last edited:

style34

Member
Apr 15, 2011
42
3
0
To install on a device with a locked bootloader, you'll need to download the kppd release below, and unpack it to prep for some adb fun... (If you have TWRP, you can also flash this in recovery)
Can someone explain in more details please.
First option is to download the file and install it via TWRP.
The second is just to run this code via adb? Do I need to change something in the code? Do I still need to download the file?
I am missing the exact way to install kppd via adb.
 

savoca

Inactive Recognized Developer
Oct 28, 2011
1,784
5,701
0
Pasadena
downloads.codefi.re
Can someone explain in more details please.
First option is to download the file and install it via TWRP.
The second is just to run this code via adb? Do I need to change something in the code? Do I still need to download the file?
I am missing the exact way to install kppd via adb.
The commands for installing via ADB were listed directly under that quote from the OP you just posted.