[Nexus 5 Themes and Apps] yorici:
Okay, breaking news: I have managed to calibrate registervalue 11 to gamma 2,2

Registervalue 11 has the following specifications (Results from previous post):

Minimum = 144

Most influenced = 175

Maximum = 202

Using a method I described earlier, I created a gamma image. Though this time not using the formula.

I made the rectangle(2,2) Red-175 (175,0,0)

Then I made the rectangle(2,1) Red-174 and onwards up to rectangle(1,5) being Red-168

Rectangle(2,3) became Red-176 and onwards up to Rectangle(2,6) being Red-180.

The background is Red[0,240], a calculation from earlier posts.

So, this gamma image contains the following Red values: 0, 168 - 180, 240.

Red-0	is controlled by the 24th value (which is not visible in the Faux app and is always 0)

Red-168-174	is controlled by registervalue 11 and 12	(Result from previous post)

Red-175	is controlled by registervalue 11	(Result form previous post)

Red-174-180	is controlled by registervalue 10 and 11	(Result from previous post)

Red-240	is controlled by registervalue 7 and 8	(Result from previous post)

So our gamma image is affected by registervalues 7,8,10,11,12,24

Realising this, I made registervalues 7,8 Red-255 (So the input in the Faux app is then 0 (because 255 - x))

The image has background [0,240]. Red-0 will be displayed as fully black (because the 24th registervalue is Red-0)

Red-240 will be displayed as fully red (because the 7th and 8th registervalues are Red-255 (and thus input 0)

This will create the optimum halftone.

Because Red-175 is solely affected by Registervalue 11, calibrating registervalue 11 with Red-175 is possible without having to deal with the influence of other registervalues.

In theory, calibrating registervalue 11 with this image would already be possible. But if you change registervalues 10 and 12 to Red-255 (thus input 0), the other rectangles (1,5 to 2,1 and 2,3 to 2,7) will differ more from the background, making the rectangle with gamma 2,2 (Red-175) stand out more.

So I started calibrating:

Registervalue 11 to Red-0 (input 255) resulted in the background being lighter than the rectangle

Registervalue 11 to Red-255 (input 0) resulted in the background being darker than the rectangle

Registervalue 11 to Red-105 (input 150) resulted in the background being lighter than the rectangle

etc.

After tuning, I came to the input of 119 (aka Red-136). This is an very interesting/good result as this is close to the

stock

value of value 11.

Notes:

It would be theoretical possible to have the input of value 10 and 12 at other values than Red-255 (input 0), but this does not work for some reason. Theoretically speaking values 10 and 12 would have no influence at Red-175 or the background, yet the background and Red-175 do not match if values 10 and 12 are not Red-255. When I have values 10 and 12 at Red-0 (input 255), I end up with an input of 110 (Red-145)

The calibration result is quite unsteady if you play with the

brightness

. This note and the previous note might have a connection. (I had my brightness at 100% using the the calibration with 119 as result)

You can try it too:

If you have not loaded up a profile before, check this FAQ

Download the profile and image from the attachments (and unzip)

Download QuickPic and the Faux gamma app from

this thread

Load the profile using FKU app or Nexus Display app

Check the gamma using Quickpic (must be in

landscape

mode)

Adjust the inputvalue of the 11th value using the Faux app

Profit!!:P

For those who really don't understand what they are doing: There are 24 calibration points, we have succesfully calibrate 1 out of 24. So no, this is not the final profile or something. And yes, the other colours are f*cked up on my screen too, but we have set some colors to RGB-255.. duh!

And every rectangle that doesn't say 2,2 does not represent the value it is claiming. Only 2,2 is truly 2,2. This is because I was using an general gamma photoshop file and this method is way different

I made a zip file instead of uploading them individually. This is because xda messes with the RGB values:(