Let's calibrate Mako | 18Feb: ALL KERNELS COMPILED AGAINST 4.2.2
"but, but the stock colors are so natural!" - that crosses your mind and you're out, please just go elsewhere and enjoy your day!
For those that stay and want to help, here's where we're at,
Mako has a f*cked up calibration thanks to mr. muramatsu. We all know it. Google knows it. Every tech page on this planet reported it. Why Google cranked gamma and risked washed out colors? Pure terror of banding, since LG's original calibration is terrible, too. One thing we all can agree to, this is not how IPS looks, this is not how LG shipped Mako, this is not how they ship Optimus G, its not natural, its not good.
There are virtually no good presets at this point, this device is out for months and all we have is simple RGB calibration which is absolutely useless. Some kernels allow for more but at most that's still just 2 values out of nine, missing out on such aspects as whitepoint, blackpoint, saturation, etc. All values are exposed but i've seen no real use of them.
The LG kernel gives us three channels to play with, R, G and B. Each channel exposes 9 values to tweak gamma. The task here is to find out what these values are and create reasonable presets, possibly the very first ones on this plattform that make any sort of sense.
If you like to help out...
Report back on your findings please!
To those that want to play around with these numbers in their own scripts, moving values higher and lower by hand, WARNING, stick to the defaults you see LG and Google using. Don't burn your device please. If you flash the kernels i link here you are safe, i do not cross the lines, even if i probably could.
I know it's very subjective, but what can we do to help with the feedback besides saying "It's super awesome"?
theres values left that i dont understand. maybe you find them documented or you find out their function by going up and down, thats what i did. basically the idea is that you cant get perfect calibration without understanding these values and its been months since that thing is out and most people still fool around which rgb, missing out on 27 important factors. im trying my best but it costs too much time to go on like this.
a great help would be if you could put it into init.d scripts or something like that. so that people can go on and try.
imore or less figured out these values:
#define g_white -- makes whites pop by pulling contrast. higher values have more detail but look grayish, lower values look stunning but have less detail
#define g_black -- black point contrast, same as white point just for blacks. larger values make sense here
mids is just a guess. but that means there are still 4-5 values untouched. i see google is using them but i couldnt make out any tangible changes.
Originally Posted by Chughes13x
Could you elaborate on what you mean by this? I highly prefer PA's colors, but don't want screen burn in....
Sent from my Nexus 4 using Tapatalk 2
if you dont know the specifics of this kernel and the lg display just stick to the values that lg and google is using. if they dont cross 1F for instance i wouldnt attempt to do it unless i have fully understood what the value does. i have included all these values. or you read them out of the linked commit.
Originally Posted by danslecarton
May I ask how I can go back to stock with the values linked in the first post?
I never did that before
just wash your rom over. but just in case, here's the original google kernel: http://goo.im/devs/paranoidandroid/r...tockKernel.zip
make nandroids. this is not meant fr beginners, though. if you know what you are doing you can attempt to flash these kernels if you are certain they will not hurt your system. for these tests im using the aosp google stock kernel.
XDA Developer TV Producer Jayce released a video a … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?