Color saturation & accuracy - OnePlus 2 Real Life Review
If you're colorblind, please disregard this thread. Rate this thread to express how you deem the color saturation and accuracy of the OnePlus 2's display. A higher rating indicates that you think that color accuracy is very high and saturation is excellent.
Then, drop a comment if you have anything to add!
Anandtech frowns on the greys
XDA_RealLifeReview said:
If you're colorblind, please disregard this thread. Rate this thread to express how you deem the color saturation and accuracy of the OnePlus 2's display. A higher rating indicates that you think that color accuracy is very high and saturation is excellent.
Then, drop a comment if you have anything to add!
Click to expand...
Click to collapse
According to Anandtech the accuracy of colour is not very good, especially in the greyscale range. Also, he says that it is a little too blue even otherwise. Does anyone here have any different opinions?
(Can't post the link here yet)
Color saturation is very poor, as I have switched from Xiaomi Mi4 it looks as if colors are washed off.
The stock calibration is too bleak for my taste. I added a little more contrast and saturation. It's android after all
Coming from the Galaxy Note 2 and LG G3, I'd say the colors are great. Not insane like on Galaxy phones though, but much better than on LG G3. For blue/red, the color temperature is settable even on the stock OxygenOS. It appeared too warm at first, so I sent the dial almost all the way to "cool" to get what seemed like a correct white color.
I had note4 and oneplue 2 color saturation is very bad.
Using Boeffla kernel I managed to get this display almost perfect concerning whitebalance and colors.
How about lets see some display settings you guys used to improve color/image quality
I find the screen too cool (I came from a s6 which i found too warm).
Would love to see some settings too.
tlxxxsracer said:
How about lets see some display settings you guys used to improve color/image quality
I find the screen too cool (I came from a s6 which i found too warm).
Click to expand...
Click to collapse
for me by far, the best display is Samsung AT&T Captivate, no phone had reached my expectations until now. I'm satisfied with OnePlus 2. I would be happy if someone shared KCAL settings.
Hi i'd like to have a screen like Samsung Phones with good saturation and good contrast. How can I do for changing those option(If I need boeffla kernel how can I configure the app for having à magnific screen?)
(I haven't installed yet but I will do it soon)
Thanks
As a happy owner of a x-rite ColorMunki, I've managed to find the time to run some tests on the phone screen and find a suitable configuration for Boeffla Kernel's color settings.
First, some values for the un-calibrated display, with the default configuration (rgb 255, saturation 255, hue 0, display value 255, contrast 255) and maximum brightness:
Black level = 0.2751 cd/m^2
50% level = 122.72 cd/m^2
White level = 578.07 cd/m^2 (quite close to the 600 cd/m^2 that OnePlus claims)
Approx. gamma = 2.24
Contrast ratio = 2101:1 (am I mistaken or OnePlus claimed "only" 1500:1??)
White chromaticity coordinates 0.2896, 0.3019
White Correlated Color Temperature = 8532K
Gamut coverage: 90.1% sRGB (not great)... http : // imgur. com /wb8kylH ... sorry but I can't post proper links yet.
Extremely "cold" color setting, with a quite remarkable contrast ratio and decent brightness. I'm quite impressed by this display!
To achieve a D65 (6500K) whitepoint and 2.2 gamma, as per sRGB standards, I've used the following settings:
red: 255
green: 233
blue: 159
saturation: 255
hue: 0
display value: 260 (it basically affects the gamma)
contrast: 255
resulting in:
Black level = 0.2804 cd/m^2 (shouldn't change)
50% level = 122.72 cd/m^2 (dictated by the gamma)
White level = 517.92 cd/m^2 (lost some brightness, unavoidable)
Approx. gamma = 2.19 (much closer to 2.2)
Contrast ratio = 1847:1 (I can live with that!)
White chromaticity coordinates 0.3121, 0.3288
White Correlated Color Temperature = 6540K
In my opinion, increasing the saturation above 255 is counter-productive, as it will only result in clipping. Furthermore, the vast majority of media content (unless you're working with professional Adobe RGB-based workflows) has most likely been designed for sRGB devices - or at least something with comparable gamut coverage. AMOLEDs are exceptional in terms of "color richness", but might result - if not properly calibrated - in unrealistic over-saturated colors.
The side-effect of these settings is the appearance of banding in images with blue gradients, such as... blue skies. I'm afraid, though, that this can't be solved in any way.
Cheers
GiMo84 said:
As a happy owner of a x-rite ColorMunki, I've managed to find the time to run some tests on the phone screen and find a suitable configuration for Boeffla Kernel's color settings.
First, some values for the un-calibrated display, with the default configuration (rgb 255, saturation 255, hue 0, display value 255, contrast 255) and maximum brightness:
Black level = 0.2751 cd/m^2
50% level = 122.72 cd/m^2
White level = 578.07 cd/m^2 (quite close to the 600 cd/m^2 that OnePlus claims)
Approx. gamma = 2.24
Contrast ratio = 2101:1 (am I mistaken or OnePlus claimed "only" 1500:1??)
White chromaticity coordinates 0.2896, 0.3019
White Correlated Color Temperature = 8532K
Gamut coverage: 90.1% sRGB (not great)... http : // imgur. com /wb8kylH ... sorry but I can't post proper links yet.
Extremely "cold" color setting, with a quite remarkable contrast ratio and decent brightness. I'm quite impressed by this display!
To achieve a D65 (6500K) whitepoint and 2.2 gamma, as per sRGB standards, I've used the following settings:
red: 255
green: 233
blue: 159
saturation: 255
hue: 0
display value: 260 (it basically affects the gamma)
contrast: 255
resulting in:
Black level = 0.2804 cd/m^2 (shouldn't change)
50% level = 122.72 cd/m^2 (dictated by the gamma)
White level = 517.92 cd/m^2 (lost some brightness, unavoidable)
Approx. gamma = 2.19 (much closer to 2.2)
Contrast ratio = 1847:1 (I can live with that!)
White chromaticity coordinates 0.3121, 0.3288
White Correlated Color Temperature = 6540K
In my opinion, increasing the saturation above 255 is counter-productive, as it will only result in clipping. Furthermore, the vast majority of media content (unless you're working with professional Adobe RGB-based workflows) has most likely been designed for sRGB devices - or at least something with comparable gamut coverage. AMOLEDs are exceptional in terms of "color richness", but might result - if not properly calibrated - in unrealistic over-saturated colors.
The side-effect of these settings is the appearance of banding in images with blue gradients, such as... blue skies. I'm afraid, though, that this can't be solved in any way.
Cheers
Click to expand...
Click to collapse
Ive tried these settings and it just made my screen really yellow and warm, I still prefer using the "extreme amoled" setting listed in AK's kernel thread.
tofuboi01 said:
Ive tried these settings and it just made my screen really yellow and warm, I still prefer using the "extreme amoled" setting listed in AK's kernel thread.
Click to expand...
Click to collapse
Well, all displays differ physically... but most importantly it's a matter of personal preference.
Personally, I am accustomed to the "yellow and warm" display (I'd find the default settings way too cold and blue ) as it matches every other screen that I have around me, and I find it appropriate to rely on an industry-standard color space/calibration. At this point, I can blame the content creator (i.e. whoever took the picture/drew the image) for not using sufficient saturation .
GiMo84 said:
Well, all displays differ physically... but most importantly it's a matter of personal preference.
Personally, I am accustomed to the "yellow and warm" display (I'd find the default settings way too cold and blue ) as it matches every other screen that I have around me, and I find it appropriate to rely on an industry-standard color space/calibration. At this point, I can blame the content creator (i.e. whoever took the picture/drew the image) for not using sufficient saturation .
Click to expand...
Click to collapse
I am using your screen value, contract and saturation setting though, it makes a change from the extreme amoled look but using opposite colours, R:235,G:245,B:256. I prefer cooler/whiter looking screen i guess haha.
Rooted, flashed boeffla kernel, installed boeffla app and adjusted color, saturation and gamma. Looks better than any other 1080p for me now.
tofuboi01 said:
Ive tried these settings and it just made my screen really yellow and warm, I still prefer using the "extreme amoled" setting listed in AK's kernel thread.
Click to expand...
Click to collapse
I cannot find the thread
alexferdean said:
I cannot find the thread
Click to expand...
Click to collapse
AK kernel thread is closed as the developer switched phones but if you go onto the thread over at original development AK kernel and look at post 2, there's a list of kcal settings.
kimas65 said:
I had note4 and oneplue 2 color saturation is very bad.
Click to expand...
Click to collapse
which is the best phone overall?? i have a note 4 and im thinking to buy oneplus 2
The Funky Pear said:
which is the best phone overall?? i have a note 4 and im thinking to buy oneplus 2
Click to expand...
Click to collapse
Stay with note 4
Sent from my A0001 using Tapatalk
Related
[Q] Increase contrast or modify gamma
Hello, The screen on my smartphone has a very slight problem. Shades of gray are dull and lack contrast. I searched for an app to increase the contrast of the display, but I didn’t have found. I tested several app to modify the brightness or decrease the contrast as "ScreenDim Full" and "Screen Adjuster". But I didn’t find any app to increase the contrast. So I need your help. What app can increase the contrast (not decrease)? I think that increasing the gamma may also allow me to have a better display. In an AOSP ROM, in the settings, we can choose between two gamma values: 2.2 or 1.9. What value to modify in which system file to change this gamma value? Thanks !
[APP][5.0+] color changer - get high contrast to your display
It is very good for IPS screen except Hwawie phones To get the most powerfull color Select custom & change S value to 1.89 play store link https://play.google.com/store/apps/details?id=mobi.omegacentauri.red Regards,
Downloading
I don't understand, does this actually change the RGB? I thought that was only possible with a custom kernel?? Sent from my Nexus 6P using XDA Labs
Does anyone know the RGB values for cm13's night mode?
Awesome about to try
Some roms cannot xhange rgb. This apps helps but it trial for the feature. Sad
I know its would be pretty easily acheived through tasker with the current version, but an update to change colour profiles (particularly the daylight oversaturated one) based on ambient light level would be most appreciated. Great app otherwise! Especially useful for kernels and devices that don't support kcal.
Any change of values results in framerate drop across ui. I'm using Xperia ZL on stock 5.1.1. The stutters in ui are constant until switch it back to normal and reduces the experience greatly. If there was a way to increase saturation without having to deal with those frame drops it would be awesome. If you can fix it with an update please do it. The stutters I experience are similar to those when I enable simulate colo space in developer options.
this app is awesome to increase saturation and get more vivid colors
GCam Port for Essential PH-1 [Based on different devs]
Alright some of you have seen my contributions in the magisk thread by aer0zer0 but i seem to update it a lot and seem to spam the thread up, so i decided to make a seperate thread where i can post updates and edits. //: Q:Reason for using this over arnovas and cstarks gcams? A:These settings are made especially for essentials IMX 258 and use more vibrant colors as seen in samples, plus the noise settings are manually tweaked by me and keep getting better as i tinker with them more, as well as the gcams provided by arnova and cstark use custom set blacklevel fix which is not an good idea, tolyan's uses dynamic black level which adjusts the tint values by ISO settings as said when checking the Fix Black level option. :// Grab my compiled version with preset here- 5.3 https://mega.nz/#!qk4ggYqC!Pb3gY6DW0KNYd6huvbEvIARIGhdRrJckLZYBPnZ8q9I 6.1 Preset build based on MGC_6.1.021_V1d-Advances_test2.apkhttps://drive.google.com/file/d/1QV88P65dzBAy7wJTlozei24owB8mzA5U/view?usp=sharing Old method below we are using tolyans builds https://www.celsoazevedo.com/files/android/google-camera/dev-tolyan009/ 1: Advanced Settings //: Final JPG quality hdr+ = 100% //: Resampling method = Raisr //: Fix Black Level = on //: Enable Motion = on //: Max BlackLevel offset = 25 or 50 2: Noise Reduction -> tuning back cam Rev 0.23 - October 9th //: Tuning master switch = ON • Apply custom sensor noise model = ON • Custom sensor noise offset a = 3000 • Custom sensor noise offset b = 22500 (default) • Custom sensor noise scale a = 2117875 • Custom sensor noise scale b = 113625 //: Apply custom denoise params = ON • Custom luma denoise at high ISO values = 1.5 • Custom luma denoise at average ISO values = 2 • Custom luma denoise at low ISO values = 0.4 • Custom chroma denoise at high ISO values = 40 • Custom chroma denoise at average ISO values = 10 • Custom chroma denoise at low ISO values = 2.55 • Custom denoise revert factor at high ISO values = 0 • Custom denoise revert factor at average ISO values = 0.05 • Custom denoise revert factor at low ISO values = 0.05 3: Back to Advanced Settings -> Saturation //: Highlight Saturation: 1.2 //: Shadow Saturation: 2.0 Samples: https://imgur.com/a/O9hYlBh Noise settings differences: https://i.imgur.com/ICn5fmi.jpg
We need more people like you. Thanks!
I appreciate you, thanks .
praise be to the @TheIronLefty
aer0zer0 said: praise be to the @TheIronLefty Click to expand... Click to collapse not til i make the apk recompiler work
Slow Motion does not appear to be working with this. Crashes app. Sent from my PH-1 using Tapatalk
Spey said: Slow Motion does not appear to be working with this. Crashes app. Click to expand... Click to collapse Still need the magisk mod, but you can turn it off.
We should use HDR+ enhanced right?
aer0zer0 said: Still need the magisk mod, but you can turn it off. Click to expand... Click to collapse Thx 4 reply. Will keep using SloMo on GoogleCamera-Pixel2Mod-Arnova8G2-V8.1.apk for time being. Was hoping to find 240fps (120fps only on this Arnova). Sent from my PH-1 using Tapatalk
HaloTechnology said: We should use HDR+ enhanced right? Click to expand... Click to collapse Both work just fine.
Huh, this might make me finally install Magisk. Just for your information, you might have missed that, another developer going by the name of ArtZ did something similar, just for a regular apk (https://www.celsoazevedo.com/files/android/google-camera/dev-artz/). He developed for the LG G6 which shares the IMX 258 with the PH-1 and very much focused on color reproduction. I've been using his latest apk since its release and always returned to it when testing other ones in between since the color reproduction is much better in HDR+ enhanced compared to other apks, his settings might be of interest to you as well in your development. Edit: after testing tolyans build with your settings I'm definitely impressed by the speed and noise settings, but color reproduction is still significantly better with the black level settings introduced by ArtZ. The color shift can best be seen when taking a low light picture with HDR+ and HDR+ enhanced, the latter will often have a green tint. ArtZ talked a bit about his settings in this post: https://forum.xda-developers.com/showpost.php?p=75432324&postcount=1568. Integrating a PH-1 specific color fix into a Gcam apk could very well be worth the work.
Skirr said: Huh, this might make me finally install Magisk. Just for your information, you might have missed that, another developer going by the name of ArtZ did something similar, just for a regular apk (https://www.celsoazevedo.com/files/android/google-camera/dev-artz/). He developed for the LG G6 which shares the IMX 258 with the PH-1 and very much focused on color reproduction. I've been using his latest apk since its release and always returned to it when testing other ones in between since the color reproduction is much better in HDR+ enhanced compared to other apks, his settings might be of interest to you as well in your development. Edit: after testing tolyans build with your settings I'm definitely impressed by the speed and noise settings, but color reproduction is still significantly better with the black level settings introduced by ArtZ. The color shift can best be seen when taking a low light picture with HDR+ and HDR+ enhanced, the latter will often have a green tint. ArtZ talked a bit about his settings in this post: https://forum.xda-developers.com/showpost.php?p=75432324&postcount=1568. Integrating a PH-1 specific color fix into a Gcam apk could very well be worth the work. Click to expand... Click to collapse My settings are based of Artz's, in my testing i never got green or magenta tint on my settings, however i did have those issues when u used to use ArtZ's last builds
Skirr said: Huh, this might make me finally install Magisk. Just for your information, you might have missed that, another developer going by the name of ArtZ did something similar, just for a regular apk (https://www.celsoazevedo.com/files/android/google-camera/dev-artz/). He developed for the LG G6 which shares the IMX 258 with the PH-1 and very much focused on color reproduction. I've been using his latest apk since its release and always returned to it when testing other ones in between since the color reproduction is much better in HDR+ enhanced compared to other apks, his settings might be of interest to you as well in your development. Edit: after testing tolyans build with your settings I'm definitely impressed by the speed and noise settings, but color reproduction is still significantly better with the black level settings introduced by ArtZ. The color shift can best be seen when taking a low light picture with HDR+ and HDR+ enhanced, the latter will often have a green tint. ArtZ talked a bit about his settings in this post: https://forum.xda-developers.com/showpost.php?p=75432324&postcount=1568. Integrating a PH-1 specific color fix into a Gcam apk could very well be worth the work. Click to expand... Click to collapse If you don't care about slomo or hevc, you don't need magisk
TheIronLefty said: My settings are based of Artz's, in my testing i never got green or magenta tint on my settings, however i did have those issues when u used to use ArtZ's last builds Click to expand... Click to collapse The settings you describe though do only cover chroma and luminance noise handling, right? There are no IMX 258 specific black level offsett settings (aside from activating "Fix Black Level") applied like the ones ArtZ describes: Release (default is 64.0 for all) 0x427F70A4 # 63.86f 0x427FB852 # 63.93f 0x427FB852 # 63.93f 0x428047AE # 64.14f (Decimals are very important. There's visible differences using for instance 63.85 instead of 63.86!!!) I haven't found that option in tolyans build, but I remember some apks would let you change these 4 values in 0.1 intervals. I tried the upper values in a few of those builds a while ago but they never gave the same result compared to the ArtZ apk, probably because ArtZ directly integrated them in the build including the second digit. I'll try to whip up a quick comparison album this evening between the Essential cam, ArtZ v3.0 Taimen and the tolyan build with your settings to illustrate what I mean with respect to the green tint. In the meantime, here is an older album I created this February with a few different ports, including the ArtZ v3.1 (which, oddly enough, is older than the v3.0). You can cleary see how most ports handle HDR+ (which i dubbed ZSL in the image descriptions back then) similarily but differentiate heavily when using HDR+ enhanced (HDR+ in the image description): https://photos.app.goo.gl/iGKAjwAD6PbUrgia2 aer0zer0 said: If you don't care about slomo or hevc, you don't need magisk Click to expand... Click to collapse You're right of course, I initially misread and thought the settings described by TheIronLefty were part of a specific magisk gcam module, not "just" settings for tolyans build.
Skirr said: The settings you describe though do only cover chroma and luminance noise handling, right? There are no IMX 258 specific black level offsett settings (aside from activating "Fix Black Level") applied like the ones ArtZ describes: Release (default is 64.0 for all) 0x427F70A4 # 63.86f 0x427FB852 # 63.93f 0x427FB852 # 63.93f 0x428047AE # 64.14f (Decimals are very important. There's visible differences using for instance 63.85 instead of 63.86!!!) I haven't found that option in tolyans build, but I remember some apks would let you change these 4 values in 0.1 intervals. I tried the upper values in a few of those builds a while ago but they never gave the same result compared to the ArtZ apk, probably because ArtZ directly integrated them in the build including the second digit. I'll try to whip up a quick comparison album this evening between the Essential cam, ArtZ v3.0 Taimen and the tolyan build with your settings to illustrate what I mean with respect to the green tint. In the meantime, here is an older album I created this February with a few different ports, including the ArtZ v3.1 (which, oddly enough, is older than the v3.0). You can cleary see how most ports handle HDR+ (which i dubbed ZSL in the image descriptions back then) similarily but differentiate heavily when using HDR+ enhanced (HDR+ in the image description). Click to expand... Click to collapse I tried using those settings on arthurs build, i even discussed about it in magisk thread, but i never got the same results too. Besides i cant really do anything about integrating it, since i dont know how to work with java.
@TheIronLefty, looks like colour noise reduction is a bit overdone in your sample. Very apparent on the depth of field scale on the old lens.
When I try to install tolyans build, it says "update existing application" and I am unable to install it... Any fixes? Sent from my PH-1 using XDA Labs
NummerEinsNerd said: When I try to install tolyans build, it says "update existing application" and I am unable to install it... Any fixes? Click to expand... Click to collapse Uninstall any other custom GCAM application and try again.
Genghis1227 said: Uninstall any other custom GCAM application and try again. Click to expand... Click to collapse I have already done that, still won't work :/ Sent from my PH-1 using XDA Labs
aer0zer0 said: Still need the magisk mod, but you can turn it off. Click to expand... Click to collapse which magisk mod do I need to activate slow mo on pie?
Please set 'OPR of Always On State under 15%' when Build Watch Face
When build the custom watch face, the setting for Galaxy Watch Designer 'Current OPR' for 'Always on state' is too high which recommend to set lower than 15%. It is advice to reduce lower than 15% for this setting before build successfully. Is anyone know how to adjust the low bit color to lower than 15%?
I suggest you have the image for the AOD to have more black in the background. Pure black pixels are completely off so it will help in lowering your OPR. Check images for a face I use. You can see the difference in OPR in the sample images. Hope this helps. https://imgur.com/a/5uFHZjt https://imgur.com/a/BrdfLPX
I was having the same issue with my OPR (On Pixel Ratio) being too high and searched the net for a long time tonight. I even modified the background image that I was using to be very dark (almost couldn't even see the original graphic). I also played with the text color for each section. I turned off all AOD settings and still couldn't build my TPK. I didn't seem to have this problem before version 1.6.2 but finally figured it out. The image I was using was 256 X 256 so of course I had to resize it to fix within the Circle Template. What I did wrong was to stretch the image out way beyond the Circle Template lines. So I went and modified my original image so when I re-sized it, it didn't go beyond the Circle Template lines very much. This allowed me to not even have to create an AOD image (I was creating a watch face for personal use only) then I could build the .TPK (for either 4.0 or 3.0) and install on my watch. I've included a screenshot to show my mistake and the correction. https://www.mediafire.com/view/awxhd398q129jct/012419_Before_and_After_Circle_Templates.jpg/file
most accurate color space?!
Thought this would be a good thing to know in case we have to edit something on the fly. I have heard our phone covers 94% of Adobe SRGB in certain modes? What info can you share about adding/modding/tweaking color space profiles on our device. If anyway has info please share. Thanks "Mod please move this to Q&A thanks sorry about that"
DCI-P3 has always worked well with me, slider exactly in the middle.
SRGB is always supposed to be the most accurate. If the gamut of the display seeing your on extends past the SRGB points in the gamut, then it becomes oversaturated. The intensity of the oversaturation depends on how far post the SRGB it goes. If it's inside the SRGB points in the gamut, you're then undersaturated.
The question should be: "which mode most accurately represents x/y/z colorspace?". If you need sRGB then the answer is usually different than if you needed accurate DCI-P3 or Adobe RGB. There is no Adobe SRGB. Adobe RGB and sRGB are two different color spaces. And the answer for sRGB and DCI-P3 is Natural mode as it switches between those 2 color spaces depending on content being displayed. Source: http://www.displaymate.com/OnePlus_7Pro_ShootOut_1P.htm#APL_Accuracy For Adobe RGB you'd need a custom kernel.
Lol were not taking about Adobe color space. We're taking about what a op7 pro can produce which is SRGB and the variations from that such as presets like vivid, natural, dp3 and a custom gamut for over/under saturation. On this phone, SRGB is the neutral color gamut.
thedamnone said: The question should be: "which mode most accurately represents x/y/z colorspace?". If you need sRGB then the answer is usually different than if you needed accurate DCI-P3 or Adobe RGB. There is no Adobe SRGB. Adobe RGB and sRGB are two different color spaces. And the answer for sRGB and DCI-P3 is Natural mode as it switches between those 2 color spaces depending on content being displayed. Source: http://www.displaymate.com/OnePlus_7Pro_ShootOut_1P.htm#APL_Accuracy For Adobe RGB you'd need a custom kernel. Click to expand... Click to collapse I've also selected Natural mode for me,Other modes are just too saturated or faded in SRGB