I'm not sure if this has been brought up before, but I wouldn't be surprised if it was missed. I am the type of user who likes to use the phone at full brightness, as it does not seem to have a huge negative impact on my battery life in day to day operations.
I was looking carefully at the browser on the Galaxy and wondered why the whites looked so dimmed in comparison to other parts of the operating system.
I had already done the following:
1. Turned the OS brightness all the way up.
2. Turned browser brightness all the way up.
3. Disabled the screen power saving mode.
I then downloaded a flashlight application and maxed it to 100% while switching to the browser with the Home key multitask, and going back and forward between the flashlight app and the browser app, it is very clear that the browser is not pushing max brightness. Even though the brightness settings on both the OS and the browser are maxed, it seems as though the browser is capped to 80% brightness or so.
My friend also verified this during his test run, as he has just bought the Samsung Vibrant and noticed the same thing. I understand many will just leave the auto-brightness setting on, but that's not really addressing the issue here.
Is there a way for an XDA developer to correct this issue through a patch or ROM?
thanks
I checked with the shell and when brightness is at 100% it has an absolute value of 255, the same when I'm at the browser set with full brightness, so it seems it's working as it should.
You can check it with this command
Code:
cat /sys/devices/platform/s3cfb/spi_gpio.3/spi3.0/blacklight/s5p_bl/actual_brightness
darksnarfer said:
I checked with the shell and when brightness is at 100% it has an absolute value of 255, the same when I'm at the browser set with full brightness, so it seems it's working as it should.
You can check it with this command
Code:
cat /sys/devices/platform/s3cfb/spi_gpio.3/spi3.0/blacklight/s5p_bl/actual_brightness
Click to expand...
Click to collapse
I don't know, I experience the same thing as the OP. Everything's bright, except when surfing the web.
Same issue here. I use Opera in bright daylight.
Sent from my GT-I9000 using XDA App
If you go in to the brightness settings there is an option at the very bottom called "Power saving mode". I'm not sure if that is having any effect on the browser.
Thanks for the numbers, but I gotta say, just comparing the flashlight app and hitting the back arrow to toggle to the browser, it is beyond obvious that the browser is not as bright as the flashlight application. I used google with it's white background and zoomed in to an area that was just white to avoid other distractions.
This is the best way to test since there will be no transition in between the application toggle and you see the screen dim easily.
As indicated by my original post, I have also turned off the power saving feature so that is not a concern. Someone did say that the Behold 2 has the same cap for their browser and that this is a samsung specific setting that's probably there to save battery. I haven't been able to confirm it on that phone yet but just give the flashlight test a chance and you'll see.
oh one last thing i noticed is, when going from the browser back to the flashlight, sometimes the flashlight app is also dimmed at the same level brightness as the browser, but tapping the screen 'wakes' up the app into full brightness.
TGalaxy browser brightness
To me it's very obvious that the browser is dimmed down, I'd say more than to 80%... Having google as the default homepage couldn't make it more obvious when opening the browser! Samsung obviously thought that no one with a decent eyesight will buy their phone. Or anyone who feels capable of managing their phone's battery life themselves.
It's just one of those niggling things that had to be included, lessening the experience of an otherwise rather breathtaking phone. Another one is the compulsory vibration when charging is finished - makes me wonder when others, or the developers for that matter, charge their smartphones! I charge them overnight, and of course every night... or at least used to, as with the Galaxy S, I can no longer sleep.
I think I've been through every menu possible to change these couple of features, with no success... if anyone knows anything, please share.
It happens on the dim-side, too
I have the same problem, but on the dim side. The browser brightens the screen when it comes on if you have the brightness set to zero. I like it dimmed all the way at night if I'm reading in bed when the lights are out and my partner is asleep, but it keeps turning it up so it's pretty bright in the pitch dark. Arrgh. It's my phone, can't I set it the way I want? Grr.
I've read that there are limitations on how much the screen dims and brightens unless you have a rooted phone and you use an app that's not built into the OS.
I rooted mine and there are some configuration apps that will set it to 0, but I think the built-in operating system slider doesn't go all the way to zero and might not go all the way to 255 when you slide it to the very edges. Supposedly it only goes to 10 on the low side from the notes on some apps.
So, probably it's a similar limitation on the slider for the screen brightness in the browser. We're probably stuck with this problem until someone writes an app that lets you change this setting to any value between 0 and 255 since the default sliders don't allow the low side and I'm guessing not the high side either.
So . . . any android developers out there, it would be cool if you could make an app to change this setting if it's available programatically somewhere.
I tried the "Dimmer" and "Brightness!" apps from the market. But none of them 'Keep' the brightness at the minimum always.
Nexus 5 Calibration:
Welcome to this thread: This thread is all about colors and displays. Nexus 5 only though!
- “Easy part: Apps, profiles” is for those that just want to mess around with some of the user created profiles and then move on. You can find the frequently asked questions about the profiles here!
- “More technical part” is for those who are more interested in this topic. Reading this part is recommend before calibrating.
- “Calibration” is for those who want to create a profile themselves (requires colorimeter or spectrometer).
- “Testing without a colorimeter” is for those without a colorimeter, but are still anxious to mess around ^^
- “Current state of development” shows the questions we don’t know the answer to yet.
Click “Click to show content” to extend the information!
Easy part: Apps, profiles
How do I get a color calibration app?
Make sure you have a compatible kernel first, like Franco's
Either use:
Nexus Display Control (Free)
FKU (paid)
Faux123 Kernel Enhancement (paid)
Kcontrol (paid)
How do I get profiles?
They are pre-installed! Just tap:
FKU: Color Utils - Load a color profile - Import preloaded profiles
NDC: Load a color profile - Import preloaded profiles
Faux: No need to do anything!
KControl: Not available
Newest collection of profiles.
Link 1 (Be sure to give a thanks to @vomer)
Link 2 (Be sure to give a thanks to @The Gingerbread Man)
If you download a new profile, you have to put them in a specific location:
FKU: /franco.kernel_updater/color_profiles
NDC: /nexus_display_control/color_profiles
Faux: /com.teamkang.fauxdisplay/profiles
After this, you can select and apply the profile.
How do I apply a profile?
Nexus Display Control App or Franco Kernel Updater App:
1) Tap 'Load a color profile' (Under color utils in FKU)
2) Select your profile
3) Hit Apply
4) Turn screen off and on to view result*
FauxClock:
1) Color/Gamma – Gamma Profiles
2) Select your profile
3) Hit Apply
4) Turn screen off and on to view result*
KControl: Not available
* On some kernels not required
Which profile is the best?
There is no best profile unless you buy a colorimeter. Here is why:
Every display is different, so the profiles that are perfect for one display will probably not be as perfect on your display.
Everything is subjective: You might like a more blueish screen, you might want accurate colors. All depends on you what is perfect
Even if you have a seemingly perfect profile, you can't test it without a colorimeter
How do I test my profile?
This is a tricky question. I have tried to develop ways to test a profile without the use of a colorimeter and I failed. It's impossible. You will never know the exact gamma, color temperature, etc etc.
There are things you can test however! Move on to part: Testing without a colorimeter!
But if you do have a colorimeter, check out: Calibration (requires colorimeter)
I love this profile. How do I set it as standard?
Check the checkbox 'Set colors on boot' in the app. (It’s a slider in FauxClock)
Problems:
Help I screwed up! How do I revert?!
Rebooting the device resets the display to stock settings (unless you ticked ‘Set on Boot’)
Or load up the stock profile (in attachments below).
(If the previous don’t work, your issue is more severe. Reflashing kernel, rom should work. If not, you have a hardware issue. Google for more info or RMA)
I don't see any difference! Why?
1) Do you have root and is root applied to the app?
2) Did you turn your screen off and on?
3) Note that the differences can be small.
4) Clearing app data and cache can do magic.
If none of these solutions work, verify that colors do change with the profile "Test your settings" (Download below)
If the profile and app work, you should get a very blue screen. (Revert by rebooting or loading other profile)
If the profile doesn't work, please search thread first, then ask questions. Your question has most likely been answered already!
The app doesn't work! :crying::crying:
1) Verify you are using a compatible kernel! Franco/Faux/Elementalx are all compatible. There are certainly more compatible kernels. Just check in that kernel thread if the kernel is compatible.
2) Verify that you have root and that the app gets root.
Please search the thread before posting! Usually your question has already been answered 5 times.
If I want to load a profile, the app force quits. Help!
The profile is invalid. Redownload it or use another profile. If this doesn’t work, try clearing data and cache of the app.
More technical part: Gamma, color temperature and colorimeters
Definitions you must at least heard of
Luminance
Luminance is a photometric unit to describe the amount of light coming from the screen. It is usually measured in cd/m2 (also called nits). It is comparable to brightness, but brightness is the perceived luminance (so subjective luminance you could say). Example: A display with a luminance around 100 nits is not so bright in the sun, but very bright in the dark. The luminance in both examples is the same, while the perceived brightness is not.
Gamma
The eye has a non-linear response to light. To correct this, gamma correction is applied.Without doing this, images look too light. Increasing gamma, means increasing the saturation. More info
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Color temperature
Color temperature is basically a measure of the color hue of white light that is measured in Kelvin (K). When you increase the color temperature, the hue becomes more blueish, decreasing it will result in a more yellowish/reddish screen.
RGB
When you are looking at a digital image, you are looking at a lot of pixels that make up this image. Each of those pixels consists out of a three sets of RGB numbers. These numbers can range from 0 (black) to 255 (white). For example: 255,255,255 will produce white, whilst 255,0,0 will produce red. RGB values themselves do not say much. You have to tell in what colorspace there are. These different colorspaces have different gamuts. Webcontent and our display use sRGB.
Here is a RGB color mixer to get a grasp on RGB.
More info on gamuts
Saturation
The vividness of a color. This can range from black/white to neon like colors.
Contrast ratio
The contrast ratio is the ratio between the brightest color (white) and the darkest color (black) your display can produce. Our Nexus 5 displays usually have around 920 (based on various measurements I have seen).
Useful links for more information:
Wikipedia:
Luminance
Gamma
Color Temperature
RGB
Gamut
Saturation and more
Contrast Ratio
Cambridge in color
GammaFAQ by Charles Poynton (expert) (Might be a bit outdated as 1998)
ColorFAQ by Charles Poynton (expert) (Might be a bit outdated as 1998)
Some color math by Bruce Lindbloom
Saturation vs. Vibrancy (vid)
How LCD works (hardware)(vid)
What do the parameters mean?
In total there are 24 parameters (of which 23) are displayed. Each parameter controls the luminance of a part of the RGB range. All other aspects (gamma, color temperature, saturation, contrast ratio) are derived from that. As stated, each parameter controls a portion of the range. Shown in this image are the ranges:
Note that the ranges do overlap in certain values. This means that one RGB value can be controlled by two parameters. (But never three!)
Let's take parameter 11 as an example: Parameter 11 has a range of 144 to 202. These RGB values can be altered by altered parameter 11. Most affected by parameter 11 is RGB(175). This RGB value will change the most when altering parameter 11. Respectively, RGB(144) and RGB(202) will change the least.
Negative and positive?
Also you might have noticed, there are two arrays for red, two for green and two for blue. Why? It’s for more precision:
These two arrays get combined to form one resulting figure. It’s not as simple as 10 and 20 become 15. Therefore I recommend keeping the difference between the parameters small in order to avoid confusion. Also the negative and positive are not equal. 10 & 20 do not produce the same outcome as 20 & 10.
Overall it’s best to keep the same when calibrating initially. But when you need a certain luminance you can’t achieve when they are the same, divert them. This method works the easiest and you don’t lose track of your changes so easily.
The White Point
The White Point is an odd setting. It does not control the color temperature in any way, form of shape. It’s also highly doubtable that the LG devs ment the white point in the curves adjustment tools of Photoshop. Currently the exact function of it is unknown, but what we know is the following:
Although the range can be 0 to 255, it actually ranges till 63. After that it loops. (0=64=128=192 and 63=127=191=255)
It’s main purpose is to allow more control over the RGB curve. Instead of controlling ranges of RGB curves, the White Point is an overall setting that adjusts every channel and every RGB value.
The recommend setting is between 29 and 33 and the middle value is 31
What would be the ideal settings?
When you capture an image with a camera, you want to see the same colors on your screen as the colors in real life right? Well, that is called an accurate screen.
Though, a lot of manufacturers don't provide accurate colors. Why not? Because the masses like punchy colors with a higher color temperature. The truth is that we have become accustomed to those colors. An accurate display seems a bit yellow nowadays. But there is a way out! Once you experience a true accurate profile, the other profiles seem really blue. Like all the things in life, we get accustomed to it.
An accurate profile would contain:
Banding: None
Color Temperature: 6500K
Gamma: 2.2 - 2.4
Properly saturated colors (Automatically achieved with calibrated gamma)
Contrast ratio: Higher is better, but above 930 is already pretty good for our LCD displays
How accurate is stock?
Actually, stock is quite accurate in comparison to other phones. There is certainly room for improvement, but they definitely tried to calibrate our screen correctly. The color temperature is around 6500K (+- 300K). Gamma is a bit too low (2.0), but in comparison to other phones it is quite good.
I like the punchy colors, can I keep them?
Of course! Your display, your rules. Having a higher color temperature isn't necessarily bad, though you must compensate a little bit. The changed settings would:
Color Temperature: 7500K
Gamma: 2.3 - 2.5
Note that for compensation for the higher color temperature, you increase the gamma a bit. This also works the same way around for lower color temperatures. Also, the same things like no banding still apply
Calibration (requires colorimeter)
Requirements for calibration
A colorimeter (Like Xrite i1 Display Pro (recommended by Display Expert Francois Simond))
HCFR
Faux Gamma App or any other app that can edit these parameters (Like Kcontrol or FKU)
Microsoft Excel or any other sheet program (Like Libre Office)
Nexus 5 with compatible kernel
Time
At which brightness should I use to test?
Unless you use autobrightness, I recommend using the brightness you use the most. But, you have to keep using that brightness for comparisons of profiles. So pick a brightness to your likings, but be consistent! (And no auto brightness!). I usually use 100%.
Let’s get started!
Step 1: Preparations
1) Set the screen timeout to 30 minutes or longer.
2) Keep your screen on for 30 minutes at the predetermined brightness. You can use you phone, just don't turn your screen off.
(Your display needs to stabilize by warming up. If you were to measure in the first minute you will see that the results are quite different than after 30 minutes. To ensure proper calibration, one must warm up the screen for at least 30 minutes)
3) Make sure you have all the requirements listed above. Also download “Shades of Grey” to your phone and “Display Calibration Nexus 5 by yorici.xlsx” to your pc.
4) Extract the images from the file explorer to a folder on your phone. There are multiple versions. I suggest reading further first, but if you can’t wait, extract “Shades of Grey (Recommended).zip”
5) Connect your colorimeter to your pc and open up HCFR.
6) In HCFR: Press 'new' - Select 'View images' - 'Next'
- Then under 'Select a sensor in this list': Your colorimeter (Can be any name). Do not use a meter correction file unless you know what you are doing. - 'Next'
- Display Type: 'LCD White LED IPS' - Reading Type: 'Display' - OK
7) In HCFR: Go to Free Measures and make sure you have set the mode in RGB
Test if it works by pressing F7. It should have measured once now and you get a table of data with one row. If you click on it, you will see more data in the left pane below.
8) If your screen hasn't warmed up for 30 minutes now, just play a game or do something else. It might be useful to get a charger as you will have your display constantly on for the rest of the steps.
Step 2: Set the goals
It is up to you what color temperature and gamma you want. I suggest you first read "More technical part: Gamma, color temperature and colorimeters" first before beginning with this. The accurate settings are there too. It's up to you how you want to calibrate though. These are my tips you should keep in mind:
Red is the limiting color in our display. Try to keep it maximised and play with blue and green
The blacks can be harder to calibrate. Try to aim for an accurate gamma though. Color temperature is less of importance because you won't see blue or red blacks as good as you would see blue whites or blue blacks.
Always turn screen off and on after editing parameters. No changes will occurs if you don't!
As you will have to turn off your screen a lot, it might be easier to temporarily disable your lockscreen. This can save some time.
Step 3: The first parameter
1) Open the Shades of Grey folder with a Gallery App (I prefer QuickPic)and just open the first image (begins with “a RGB(255,255,255)....”). These images are sorted in the right order, you will only need to swipe.
2) Do a 'Free Measure' by pressing F7. I do usually three times for more accuracy:
Those three results I combine in one value with less decimals (usually 1). You will always get three different results, so you can't use just one of them. You will need to average them out. This creates uncertainty and therefore you remove two decimals. (If you get three times the same result, please keep it to one decimal. It's very unlikely you will get three times the same results another time)
3) Note these values in max luminance in the spreadsheet
4) Measure the second image (black) and note these values in min luminance. When you edit them, you will see the other values change.
5) It will probably the case that the first two values aren't resulting in your desired goals. Now you must correct this by editing the parameters. Open up Faux Gamma App (or any other app that can edit the parameters like FKU or Kcontrol)
6) Let's say I want to achieve 6500K. For that to happen, every color channel needs to result in the same value. Lred=Lgreen=Lblue.
In my previous result: Blue and green were higher than red. Red was maxed out, so I need to decrease blue and green
In Faux Gamma App (and Kcontrol) the first 12 parameters are reversed: Increasing parameters will decrease colors
In FKU this annoyance is removed: If you increase any parameter, the corresponding color will always increase
To decrease blue and green for the first value, I need to increase the first parameter in Faux Gamma App and decrease in FKU. Pay attention to which parameter you are editing. The 13th to 23th parameters are normal.
How much you should adjust is not determined. The only thing you know is that when you have a difference of 5 in luminance (Desired vs. irl), the adjustment in the parameters should be less than when the difference is 50.
7) In general this applies: The more accurate each parameter was calibrated in relation to the next parameter, the better the gamma.
The more accurate each color channel (Red, green and blue) was calibrated in relation to another, the better the color temperature.
Step 4: The rest of the parameters
1) When you are done calibrating the first parameter, continue to the next parameter. I usually start by calibrating all red, then green and finally blue.
2) In the Gallery, swipe to "c - p(2) - RGB(254,254,254)". This means parameter 2 (the c is for the right order in gallery apps). Measure this three times and take average.
3) Swipe to "ca - RGB(255,255,255)". Measure it three times and take average. This is max luminance again.
4) (Optional for parameters 1 – 14) Swipe to "cb - RGB(0,0,0)". Measure it three times and take average. This is min luminance again.
5) In the spreadsheet: Fill in max and min luminance. Then compare the first average of p(2) with the suggested value of parameter 2 in the spreadsheet.
6) Adjust accordingly in Faux Gamma App, Kcontrol or FKU. Screen off/on! And repeat substeps 2 to 5 until desired value = p(2) value.
7 - 99) Repeat for every other parameter.
PRO TIP: Save your work every 6 parameters! Just save it as a profile. When you reboot, you might lose your progress as the default profile is stock.
Temporarily get rid of your lockscreen. Unless you use Faux Kernel, you will need to turn your screen off and on a lot. Removing the lockscreen will ease that a bit and save you time!.
NOTE: If you want to save some time, you can skip measuring blacks (cb - RGB(0)..) every time. Just measure it fifty times with F8 mode while moving the colorimeter over the screen. Take average of those and keep it at those. You should get “Shades of Grey (No blacks).zip” then. It is better to measure black for 15 to 23 though!
Step 5: Review the results
1) Get Voodoo Screen Test Patterns App (free)
2) Open the app and set the amount of measurement points in the settings. [More=better, but more difficult]
3) Set the equal amount of measurement points in HCFR: (I use at least 25, b/c 24 parameters)
HCFR – Measures – Parameters – Number of Grayscale levels
4) Press “GO” and it will show images on your PC. You have to press next on your phone to keep up with the images.
NOTES: It’s a bit wonky and you should take multiple attempts at this for more accuracy
If calibration is done correctly, the color temperature should be around 6500K (+- 75K). The average gamma should be very close to your setting. The gamma line itself can be a bit squigglier, but keep it around the gamma you have chosen earlier.
Step 6: Share and contribute!
Please share you final product of hard work!
1) Save your profile using the Nexus Display Control app (FKU has this functionality too).
2) With a file explorer navigate to nexus_display_control/color_profiles and locate your profile.
3) Gather results from HCFR (right-click - save): gamma and color temperature (with saturation, luminance, near white, near black you are even better ;P)
4) Claim your glory and post the profile, HCFR images and you goals (which gamma and color temperature were you going for?) in this thread as a reply!
If you are really satisfied with the result, please consider buying me a beer I have done a lot of research to get to these results and they have all been done in spare time.
Testing without a colorimeter
Most of the users don’t have a colorimeter and you might not either. What can you test?
Banding: Less accurate, but still possible, you can check banding! By using gradient you can review the smoothness of the gradient. I have included gradients that are capable of doing this! You are looking for sudden interuptions in the gradient. If it is good, the gradient will appear smooth without any distortions.
Color Temperature: Though, incredible inaccurate and very biased, you can check color temperature subjectively. I do not recommend relying on it, but you can see the differences in hue and adjust the parameters. Though there is no way to measure it. I have included gray images that you can use!
You just swipe through the pictures and you will notice the different hues. Though it subjective to judge which one is incorrect…
Gamma: Short answer: No, not really.
Long answer (involves Display Tester App):
Although Display Tester App (and more apps alike) claim to test gamma, their results are biased . The principle the Display Tester App relies on is the following:
You create a background with a grid. The grid is composed of RGB (255,255,255) and RGB (0,0,0). This is the same as 0% and 100% gray. Because the eye can’t see individual pixels, the grid blends to a half tone: 50% gray. If you place a 50% gray block on the background, they should match. Up till this part, everything is correct.
There is one problem: The Display Tester App only tests 50% gray. 50% gray results in RGB (186,186,186). So basically, you are only testing only one RGB value out of 256.
To make this even more fun: The Display Tester App also messed up the background… While it should be a perfect grid of 0 and 255, it actually goes from 0 to 8 and 247 to 255. No, this is not better, it only is more biased. You can’t rely on RGB (1 to 254) as they are not calibrated yet.
If you have used the app, you may have noticed that changing the viewing angle, changes the outcome. The outcome is also dependent on ambient lighting, if the screen has been warmed up for 30 minutes, your eyes, brightness.
With so many variables you can’t believe this app will produce any reliable result… Even if it did, it would only count for RGB (186).
My advice: Do not rely on the Display Tester App or any other app that claims to be able to measure your gamma!
Notes:
- 50% gray = 0.5^(1/2.2) * 255 = 186 (It’s not 127/128 due to gamma correction)
- You can see for yourself that the app is biased: Change parameter 9 (any color) to 255. Open the app: no real difference right? The 2.2 box will remain the same and the background too, while if you look at photographs there is noticeable something wrong! This can’t be right, can it?
Saturation: Forget it.
Contrast: Very complicated process with another camera perhaps. Google is your friend. (It will be quite inaccurate: the camera alters the picture too (white balance))
Color checker cards
You could buy color checker cards and use those to calibrate. It's a bit cheaper.
Disadvantages:
Less accurate than a colorimeter due to inaccuracy of the eye and ambient lighting
Only one calibration possible: 6500K, gamma 2.2
If you are going to spend more than 40 on it, I suggest you buy a cheap colorimeter instead.
Should I use the RGB sliders?
Short answer: No, only for very specific purposes.
Long answer:
The RGB sliders shouldn’t be used if you want to improve your screen. If you want to make your screen all red, the sliders are perfect.
What the sliders to is limit the RGB range. If you set the red slider at 240, RGB(255) will become what normally was RGB(240). Every RGB value gets relocated from there between RGB(0) and RGB(240). You are basically limiting the amount of colors you can display. Not that awesome right? (Unless you want to do this)
Current state of development
Not everything has been uncovered yet:
Can be predicted how much one should increase a parameter to get a certain luminance?
My idea: Let’s assume that an increase of parameter Y with amount X always increases Luminance(Y) with the same amount. Let’s call the screen’s calibration when every parameter is set at 0, the base calibration. That base calibration is different for each display and define the characteristics. When measured correctly, one could calculate how much each parameter should be increased to get the desired luminance.
Explanation needed for the strange behavior of the first 8 parameters when all set to 0.
What is the mathematical connection of the white point in relation to the parameters?
The so called ‘white point’ is the only parameter that can adjust the entire RGB range. What is the mathematical connection between each individual parameter and the white point?
Changelog and credits:
Changelog:
26-5-14: Initial post placed
27-5-14: Fixed link, added color checker cards (Thx Tzfardaya), added white point measurements in post #2
1-6-14: Fixed type, thx @nihil0
16-6-14: Added profile: Yorici_Calibrated_Punch (see second post)
20-6-14: Added more info in FAQ under "How to get profiles?"
Immense thanks to:
@supercurio, @myfluxi, @faux123, @franciscofranco, @mag01, @rajendra82, @gpvecchi, @Tzfardaya, @granets, @tkoreaper, @ChazzMatt, @neriamarillo, @vomer, @The Gingerbread Man and everyone that helped with this!
If you still have any questions that weren’t explained (clearly enough), feel free to ask in this thread. I will keep adding questions which I think are useful!
NEW! Gamma Corrected Brightness (GCB)
Let's do a little experiment shall we? Set your screen's brightness at 0%, 50% and 100% consecutively. Notice something odd? That's right! The 50% doesn't seem like 50%. Why you ask? Well you are not a robot, but a fabulous human that perceives brightness different (i.e:non linear). Well how do you fix this?
We are introducing Gamma Corrected Brightness! This will solve that nasty issue we talked about. Best thing yet, this baby comes with multiple modes and works for every brightness level! And this will save you battery too! With GCB you will have a greater tendency to set a lower brightness than you normally would and that saves battery life!
Four modes are:
- Stock
- Gamma 2.0 (Stubborn) – A little bit more stubborn than the natural one for those who need that
- Gamma 2.2 (Natural)– The natural one that seems normal like it should be!
- Gamma 3.0 (Nightmode) – This one is for night times ^^
How to use:
1) Download and install Furnace Kernel
2) Open terminal
3) Enter for:
Stock: echo “0” > /sys/module/lm3630_bl/parameters/gamma_correction
Stubborn: echo “1” > /sys/module/lm3630_bl/parameters/gamma_correction
Natural: echo “2” > /sys/module/lm3630_bl/parameters/gamma_correction
Nighttime: echo “3” > /sys/module/lm3630_bl/parameters/gamma_correction
4) Done!
If you love Gamma Corrected Brightness, please consider to buy @savoca and @yorici a drink!
_________________________________________________________________________________________
Profile:
Yorici_Calibrated_Punch:
Goal: Maximum brightness possible with 2.35 gamma
Result:
Average gamma: 2.36
Contrast ratio: 1:1017
Color temperature: Around 8800K
Higher saturation due to higher gamma
Maximum brightness of 500 nits vs 440 nits on stock
So brighter, more saturated and higher color temperature: what is usually called punchy!
Advanced graphs:
The color temperature might appear to be really bad, but there is a reason for this:
On full black I get these luminances: R:0,4 G:0,4 B:1,2. The color temperature of this is > 12.000K. To preserve maximum brightness I had to keep these values. This difference of 0,8 slims down when luminance gets higher. And you can see that from 25% gray and on the color temperature remains more stable.
You will also notice that gamma gets a bit more wobbly at the end. That is because the measured values change more dramatically than at the beginning of the curve. I might try to decrease the wobblyness more in the future.
See attachments for profile!
Yorici_Calibrated_Accurate
Still in the works.. (Harder to make)
_____________________________
White point:
I have taken 16 measurements of the entire RGB curve and made gifs out of them:
Luminance:
RGB levels:
Color Temperature:
The slight bumps some times are due to mistakes, vibrations (got a text), etc. Ignore them.
What can we learn from this about the white point?
The white point seems to have the most effect on red (as seen in Luminance)
Extremer white point (towards 0 and 63) tend to increase the differences between the colors
That diversion gets bigger 50% - 100% gray with white point 31 - 63
That diversion gets bigger 0% - 50% gray with white point 0 - 31
White points 0 to 10 and 53 to 63 are more unstable and lead to unpredictable results.
A white point around 31 seems the best
Anything else?
Nice thread ...
great post buddy :good:
everyone: be sure to tag me if you make new profiles and want them added to my server
There is a way to do a very basic calibration without a colourimeter... but it requires a set of digital colour cards...
Basically a sheet printed with specific squares of colour you take a picture of said card, and then compare the colour displayed on screen with the colour of the card.... With a proper calibration, the two will match. (after correcting white balance)
Tzfardaya said:
There is a way to do a very basic calibration without a colourimeter... but it requires a set of digital colour cards...
Basically a sheet printed with specific squares of colour you take a picture of said card, and then compare the colour displayed on screen with the colour of the card.... With a proper calibration, the two will match. (after correcting white balance)
Click to expand...
Click to collapse
But again dependent on your eyes, ambient lighting, etc. ;/
Not ideal, but I can't disagree that it is indeed a method.
yorici said:
But again dependent on your eyes, ambient lighting, etc. ;/
Not ideal, but I can't disagree that it is indeed a method.
Click to expand...
Click to collapse
More reliant on your eyes than ambient lighting, since you should look at the picture under the same light. but yeah, it's a very rough way... Slow, tedious, and usually used more to check the calibration and white balance/colour correct photographs than actually calibrating the screen....
Tzfardaya said:
More reliant on your eyes than ambient lighting, since you should look at the picture under the same light. but yeah, it's a very rough way... Slow, tedious, and usually used more to check the calibration and white balance/colour correct photographs than actually calibrating the screen....
Click to expand...
Click to collapse
I assume you would buy a white tile that is 6500K? I could mention it in my thread though
yorici said:
I assume you would buy a white tile that is 6500K? I could mention it in my thread though
Click to expand...
Click to collapse
Heh, the white card is based on srgb, and is what a "properly calibrated and full srgb gamut" display should show at 255/255/255, same with the black card (0/0/0).
I also have an 18% grey card...
Makes white balancing a photograph extremely simple....
But can also be used (with great difficulty) to help calibrate a display (or check the displays calibration)
My man, I am subscribed! I'll update the required posts and threads by me when I'm feeling fresher (sober) in the AM
Edit
Nice to see this got stickied nice one!
Sent from my Nexus 5 using Tapatalk
nice thread, but the link to vomer's screen profile is broken because you add (" ") between the link
The Gingerbread Man said:
My man, I am subscribed! I'll update the required posts and threads by me when I'm feeling fresher (sober) in the AM
Edit
Nice to see this got stickied nice one!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'm happy with the sticky as well
gravityy said:
nice thread, but the link to vomer's screen profile is broken because you add (" ") between the link
Click to expand...
Click to collapse
Good catch
Color temp is pretty good stock. For me its the gamma that drives me nuts. I've been waiting for your results to start with mine. As you noted Franco fixed his interface.
Thanks a ton. Spent my donation/app fund this week on Peek. You're up next.
Subscribed! Awesome work and lots of good info. Thanks @yorici
Are you able to share with us your profile @yorici? Will definitely be referencing this thread when I buy my own colorimeter in the coming month!
Sent from my Nexus 5 using Tapatalk
blackt5 said:
Color temp is pretty good stock. For me its the gamma that drives me nuts. I've been waiting for your results to start with mine. As you noted Franco fixed his interface.
Thanks a ton. Spent my donation/app fund this week on Peek. You're up next.
Click to expand...
Click to collapse
Haha great dude! Yeah it's more gamma that needs some attention, but color temp can be improved too. Also, if you have the money and you are willing to spend it, I would suggest buying a xRite i1 Display Pro. You would want this one for the speed. It very quick in measuring. (I got it recommended by Francois Simond. He has been calibrating the displays of the One Plus One) If you are completely crazy about colors, you should buy a spectrophotometer. But that is > €1000...
Bobtehblob said:
Are you able to share with us your profile @yorici? Will definitely be referencing this thread when I buy my own colorimeter in the coming month!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I must confess Everytime I start calibrating I discover something I don't know yet and I begin investigating it further Yesterday I took 16 measurements of the white point of which I will posts gifs of (So you can see the change). I just get intrigued and stop calibrating So I have some half baked profiles I need to continue.
In my opinion n5 display looks better than any other smartphone display I came across. It's just so easy on the eyes, I get a headache when I look other oversaturated panels. I'm not a gamma expect but I know how people faces are supposed to look so I pay a lot of attention to the skin tones when I look at the images on my phone, and any custom made profile can't be compared in the terms of color accuracy to the stock one. After all, can we calibrate the screen better than Google?
Bright Red Nexus 5
Updated post 2 with gifs about the white point! Please comment if you feel I missed something or concluded wrongly
defffizz said:
In my opinion n5 display looks better than any other smartphone display I came across. It's just so easy on the eyes, I get a headache when I look other oversaturated panels. I'm not a gamma expect but I know how people faces are supposed to look so I pay a lot of attention to the skin tones when I look at the images on my phone, and any custom made profile can't be compared in the terms of color accuracy to the stock one. After all, can we calibrate the screen better than Google?
Bright Red Nexus 5
Click to expand...
Click to collapse
The 'look at the faces' is indeed a good test to see if the display is a bit oversatured. Can we calibrate better? Yes, definitely.
The reason for this is that Google didn't do the calibration LG did. And LG had to build a profile that was an good average on all displays. No display can be exactly the same and especially when you have millions of units. The calibration is therefore not optimized on a per display basis and you can improve it
@yorici,
I have a eye one pro
Hi Guys,
Is there a way to automatically turn off the screen at night (during a specific time).
Is there any app to do this ? Or tasker/IFTTT/Tockle profile to do the same ?
I would like a swipe-from-the-right switch similar to the mute switch (swipe from top) which puts the watch into airplane mode and deactivates the always on mode, too. (=night mode)
WatchMaker app just got (after the last update) tasker plugin. You can switch different faces based on different parameters. If you build a face with dim mode - off and you will activate-it after midnight (as an example), then you will get exactly what you want.
Any example for this.. I am unable to figure this out
You need to install "tasker" also, in parallel with "watchmaker".'Go to watchmaker app and create the watch face you desire (or download one from the internet - there are plenty to choose from).
Take the watchface of your choice and create a duplicate.
On the duplicate add a BLACK png file on top of everything and activate-it only in dim mode.
Then, set-u tasker to switch on the duplicate face while it's night and to the original face in the rest of the day.
Now, you will basically have the same watchface in all circumstances, but at night, the dim mode will just be black (which, in the amoled world, means, screen off).
ro_explorer said:
You need to install "tasker" also, in parallel with "watchmaker".'Go to watchmaker app and create the watch face you desire (or download one from the internet - there are plenty to choose from).
Take the watchface of your choice and create a duplicate.
On the duplicate add a BLACK png file on top of everything and activate-it only in dim mode.
Then, set-u tasker to switch on the duplicate face while it's night and to the original face in the rest of the day.
Now, you will basically have the same watchface in all circumstances, but at night, the dim mode will just be black (which, in the amoled world, means, screen off).
Click to expand...
Click to collapse
you can do the same thing without Tasker:
add a BLACK png file- or even better: a shape with the color black and size of 512x512px - on top of everything and activate-it only in dim mode
then use the following formula in the opacity field:
{dh23} > 18 and 100 or {dh23} < 7 and 100 or 0
red indicates the time in which to apply the filter (in my case between 19:00 and 07:00)
praddz said:
Hi Guys,
Is there a way to automatically turn off the screen at night (during a specific time).
Is there any app to do this ? Or tasker/IFTTT/Tockle profile to do the same ?
Click to expand...
Click to collapse
I'm just using "Slumber for Android Wear"
It makes the screen black when you put the watch on his cradle.
No airplane mode though
2k4ever said:
you can do the same thing without Tasker:....
Click to expand...
Click to collapse
Oh .. you are sooo right ... I missed that possibility ... it was a situation of not seeing the forest because of the trees
ro_explorer said:
Oh .. you are sooo right ... I missed that possibility ... it was a situation of not seeing the forest because of the trees
Click to expand...
Click to collapse
yes, WatchMaker is great on its own - but I really love the tasker integration!
I'm using the above formula to set a 50% opacity shade during the night hours in order to dim the screen
btw: the same thing should be possible with Facer
2k4ever said:
yes, WatchMaker is great on its own - but I really love the tasker integration!
I'm using the above formula to set a 50% opacity shade during the night hours in order to dim the screen
btw: the same thing should be possible with Facer
Click to expand...
Click to collapse
i have used tasker to set the black watch face in the night. but 1 problem, watchmaker works only when one of the faces from watchmaker is selected. If i select any of stock watchface, the tasker thing does not work as it is mentioned in watchmaker app description that to change the face one of the watchmaker faces should be selected on the watch..
Of course it's working like that, seriously, what have you expected?
If/when the main wear app will allow changing faces remotely via tasker (or it will offer an API for that) then we will be able to do that.
Anyway, my watch is turning off by itself while it's placed in the charger. It will not turn off immediately but after few minutes.
praddz said:
i have used tasker to set the black watch face in the night. but 1 problem, watchmaker works only when one of the faces from watchmaker is selected. If i select any of stock watchface, the tasker thing does not work as it is mentioned in watchmaker app description that to change the face one of the watchmaker faces should be selected on the watch..
Click to expand...
Click to collapse
I haven't tried it myself, but FaceLift could be what you are looking for
it should allow you to switch to watchmaker (which you have to pre-set with a black image) and back to the stock face at certain times
ro_explorer said:
Anyway, my watch is turning off by itself while it's placed in the charger. It will not turn off immediately but after few minutes.
Click to expand...
Click to collapse
As I understand it, praddz wants the watch to turn off during a certain time frame, not when charging
If you want the watch to turn off immediately when charging and are willing to enable developer options, for me it works to set the keep screen on option to enabled
At night I just deactivate Screen Alway ON to have screen off while charging. So easy that changing face or other workaround no ? Long press button and just click on screen parameter.
ro_explorer said:
Of course it's working like that, seriously, what have you expected?
If/when the main wear app will allow changing faces remotely via tasker (or it will offer an API for that) then we will be able to do that.
Anyway, my watch is turning off by itself while it's placed in the charger. It will not turn off immediately but after few minutes.
Click to expand...
Click to collapse
Figured I'd chime in that changing faces from the app is confirmed for the Lollipop/Wear 2.0 update rolling out this week. On another note, it would be cool to have the 5.0 notification system integrated into Wear, so things like Quiet Hours, Priority interruptions, etc. Maybe someday.
Am i missing something? My watch automatically turns the screen off when it's on the cradle, after about 10 minutes.
cashisback said:
Am i missing something? My watch automatically turns the screen off when it's on the cradle, after about 10 minutes.
Click to expand...
Click to collapse
I am there with you bud...
I said the same thing...
Hey Ara! Thanks for tackling this series. I know that AC ranges from 101 articles, to device rumor mill articles, to tasker tutorial type articles, and based on comparing the comments of the full spectrum of articles, it looks like the tasker crowd might not be as large as some of the other crowds that read and are interested in ACs other stories, so... props to ya for taking on the giant.
I've been using tasker since I had the OG Droid and have loved its functionality. Lately though, I've been stumped on one thing in some of my tasker profiles that I just can't seem to nail down. It's a function that you may or may not be familiar with unless you've done other types of programming, specifically logic programming like ladder logic (PLC). I'm looking for an ON DELAY TIMER, not just a timer that begins and continues counting when a series of contexts (permissives) is activated, but a timer that will ONLY count while the contexts are true, and will stop counting AND RESET when at least one of the contexts isn't true. This way, if you want something to happen 5 minutes after your screen is on and your screen hasn't shut off into sleep mode, it will execute a task, but if for some reason the screen does shut off before 5 minutes, it will not execute the task and will begin counting from 0 sec the next time the screen turns on. I've tried to make custom ON DELAY TIMERS with variables and other methods, but my profiles just don't work the same as if there were just a simple ON DELAY TIMER task built in (Currently with variables, I can only start a timer based on contexts, and then check in an amount of time to see if the contexts are still true at the end of the timer, but nothing to stop the profile if a context goes false during the timing... so with my screen example, tasker can't tell the difference between the screen turning on for a minute, off for 3 minutes and on for 2 minutes and the screen being on for 6 minutes straight.). Anyway, if you, or anyone reading this stupid long comment, knows where to find this ON DELAY TIMER, or how to create one in tasker, please spread the wealth! Thanks!
Phone number Search
You can accomplish this but it will eat some RAM.
Have contexts trigger delay timer task.
In delay timer :
1 add variable, say %timer and add 1.
2 wait 1 second
3 stop task if criteria are not met.
4 goto step 1 (variable add) if %timer < set number.
5 whatever action you want triggered when counter reaches end
You can add some steps before the #1 listed for a dialog, spinner, etc if you want user to set new time each use.
Hope this helps.
Zac
I would like to use my fire tablet as an alarm panel. Found a few apps that display full screen web pages, that works good. In the development options I turned on "stay awake" so the panel could always be on. After like 30 seconds of no using the screen just barley dims. I would like to dim the screen as much as possible after no use. Anyway to override this amount? I found several apps that can set the dim amount, but just by a schedule, not by inactivity. Or even a web browser app that can control the dimming when not in use?
Thanks a bunch!
Coods said:
I would like to use my fire tablet as an alarm panel. Found a few apps that display full screen web pages, that works good. In the development options I turned on "stay awake" so the panel could always be on. After like 30 seconds of no using the screen just barley dims. I would like to dim the screen as much as possible after no use. Anyway to override this amount? I found several apps that can set the dim amount, but just by a schedule, not by inactivity. Or even a web browser app that can control the dimming when not in use?
Thanks a bunch!
Click to expand...
Click to collapse
Unfortunately, not possible on this device. Minimum brightness level set in kernel (possibly a panel/controller limitation) with no known workarounds (via Xposed). To date this is the only device I own that exhibits this behavior.
Thanks for that info Davey. Maybe I'll see if I can create my own app with a webview that will dim when not touched for a period of time. Since it seems an app can control the dim level. Thanks again.
Coods said:
Thanks for that info Davey. Maybe I'll see if I can create my own app with a webview that will dim when not touched for a period of time. Since it seems an app can control the dim level. Thanks again.
Click to expand...
Click to collapse
Ah - so you are not experiencing any dimming vs dissatisfied with the minimum level. Couple thoughts:
- might be able to use an automation tool like Macrodroid or Edge (w/Xposed) to dim the screen on a particular action like last user action or time of day; Tasker (a fan favorite) can do this as well but is overkill for your needs IMO
- blue light filters can emulate deeper dimming levels but you won't realize the associated battery saving as backlight level remains untouched; the again you device is likely plugged in when used as an alarm clock
Unfortunately Macrodroid and Tasker can not listen for inactivity/idle events. Sounds like an Android limitation: http://macrodroid.freeforums.org/inactivity-period-as-trigger-t86.html
Not sure what Edge (w/Xposed) is, not finding that?
Thanks Davey!
Coods said:
Unfortunately Macrodroid and Tasker can not listen for inactivity/idle events. Sounds like an Android limitation: http://macrodroid.freeforums.org/inactivity-period-as-trigger-t86.html
Not sure what Edge (w/Xposed) is, not finding that?
Thanks Davey!
Click to expand...
Click to collapse
Edge is a module for Xposed Framework. You might also consider a different trigger sequence than inactivity/idle, eg: touch, activity atart or time of day. Might need to get a little creative with the thinking