Related
Hi guys,
i did a search but have found nothing regarding this kind of problem.
My display shows some kind of pattern on plain colors.
http://dl.dropbox.com/u/16054199/screen.jpg
Its worst on grey and white, (certainly) not seen on a black screen, and its almost not visible on the highest screen brightness. But, its very distracting on everything below and also visible in pictures etc. if looked closely.
I come from a S2 which had not this effect. Is it a faulty screen or a normal effect of the pen tile matrix?
I see the same thing when my screen dims down before it goes to sleep.
Sent from my Galaxy Nexus using xda premium
Just before it goes into sleep mode? (which afaik is even darker than the darkest setting while it`s awake).
I clearly see it under medium backlight setting, the grey elements of the market are a place where i always see it.
hate to break it to you, but that's just how the screen is(especially when the brightness is turned down & on plain colors). i've had 2 Nexus' and both did the same, even the ones on display in my local verizon store are the same way.
Turn the brightness up and it will go away. It's a quirk of the screen technology.
Allright, so i have to live with that... Thanks for your answers!
Is it possible to edit the levels of the automatic screen brightness?
soulcrash said:
Allright, so i have to live with that... Thanks for your answers!
Is it possible to edit the levels of the automatic screen brightness?
Click to expand...
Click to collapse
If you're rooted and have Clockworkmod you can use this:
http://forum.xda-developers.com/showthread.php?t=1377410
Just make sure you meet the requirements and follow the directions in the thread. I have used this on a Verizon LTE Galaxy Nexus and didn't have any issues, even though it is in the CDMA form.
I am not the dev of this mod, just passing along the info.
awesome, thanks a lot!
I wonder if there's some kind of deeper hidden meaning to the pattern, some kind of subliminal message jk
Terminators run on Android...
I find the dimmest screen toggle still too bright. I find it embarrassing to use in dark public spaces.
Is there a way to dim the screen even more?
Download the screen filter app from the play store. Literally puts a filter effect on the screen to make it appear darker making it much easier to use in the dark.
Yes its possible to take the screen much lower, but we have to edit the framework. Nobody had done this mod yet for some reason.
CM9 has the ability to change the screen lowest settings built in
B97 said:
Download the screen filter app from the play store. Literally puts a filter effect on the screen to make it appear darker making it much easier to use in the dark.
Click to expand...
Click to collapse
+1. I use Screen Filter also, it's uber handy for reading at night when the light seems too bright. If you've got hardkeys like I had on my Desire, you can even turn them off.
i wrote a tutorial on how you can mod the frameworks apk. it's very easy and you can change the brightness levels to anything you want. here's the thread
screen filter only puts a transparent layer on the screen and messes with the colors. modding the frameworks will lower default brightness to any level you want. you can raise it too if you like.
Thanks for all the ideas. I went with the easiest one, Screen Filter.
AOKP also has an option to reduce screen brightness...
dynamicpda said:
Thanks for all the ideas. I went with the easiest one, Screen Filter.
Click to expand...
Click to collapse
Good man!
Sent from my GT-I9100 using XDA
neotekz said:
i wrote a tutorial on how you can mod the frameworks apk. it's very easy and you can change the brightness levels to anything you want. here's the thread
screen filter only puts a transparent layer on the screen and messes with the colors. modding the frameworks will lower default brightness to any level you want. you can raise it too if you like.
Click to expand...
Click to collapse
Great work, I've been wondering why nobody did this mod yet for the nexus. I made that same mod on my atrix, using the sgs2 thread as well. But I've been too lazy to do it for nexus.
The above mod is the best option. Screen filter doesn't achieve the same results. The above mod reduces power draw as well when on the lower brightness setting of 5 or so. Screen filter just hides the higher brightness but has same power draw.
RogerPodacter said:
Great work, I've been wondering why nobody did this mod yet for the nexus. I made that same mod on my atrix, using the sgs2 thread as well. But I've been too lazy to do it for nexus.
The above mod is the best option. Screen filter doesn't achieve the same results. The above mod reduces power draw as well when on the lower brightness setting of 5 or so. Screen filter just hides the higher brightness but has same power draw.
Click to expand...
Click to collapse
That would be correct for back-lit screens. For the Galaxy Nexus screen, though, Screen Filter does help reducing power draw as a darker screen content = lower brightness.
I used to use SF for quite a while until I got fed up of it causing stutters to most animations. After thorough examination I concluded that the Nexus's GPU is the culprit. For some reason it just doesn't like multiple graphics being updated at once. Modding the overlay XML allows it to run at full speed.
Can anyone confirm the same reduced framerate issue?. It's also the reason why some ROMs include a setting to remove the navigation buttons glow. I tested with CM9 on the SGS2 and experienced none of the stutters in cases where the GN would. Another example: sliding between sections (comments, ralated, etc.) in YouTube is laggy iff the video is playing.
fnf said:
That would be correct for back-lit screens. For the Galaxy Nexus screen, though, Screen Filter does help reducing power draw as a darker screen content = lower brightness.
I used to use SF for quite a while until I got fed up of it causing stutters to most animations. After thorough examination I concluded that the Nexus's GPU is the culprit. For some reason it just doesn't like multiple graphics being updated at once. Modding the overlay XML allows it to run at full speed.
Can anyone confirm the same reduced framerate issue?. It's also the reason why some ROMs include a setting to remove the navigation buttons glow. I tested with CM9 on the SGS2 and experienced none of the stutters in cases where the GN would. Another example: sliding between sections (comments, ralated, etc.) in YouTube is laggy iff the video is playing.
Click to expand...
Click to collapse
Agreed, GPU just isn't good enough. I hate the lag with the button glow animations on!
I use an app called root dim, it's really useful. Let's you use a brightness level of 1, which is really quite dim. Free, too.
Sent from my Galaxy Nexus using XDA App
Remoteconcern said:
Agreed, GPU just isn't good enough. I hate the lag with the button glow animations on!
I use an app called root dim, it's really useful. Let's you use a brightness level of 1, which is really quite dim. Free, too.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Thanks for the tip, on the Galaxy Nexus it's possible to set the brightness to 0 by writing to /sys/class/backlight/*/brightness but the brightness is checked and reset to the minimum (default 10) every time the screen is turned on. I guess Root Dim works to the same effect so it runs as a system service. Still, it'd be an awesome addition for people who haven't bothered to mod.
fnf said:
That would be correct for back-lit screens. For the Galaxy Nexus screen, though, Screen Filter does help reducing power draw as a darker screen content = lower brightness.
I used to use SF for quite a while until I got fed up of it causing stutters to most animations. After thorough examination I concluded that the Nexus's GPU is the culprit. For some reason it just doesn't like multiple graphics being updated at once. Modding the overlay XML allows it to run at full speed.
Can anyone confirm the same reduced framerate issue?. It's also the reason why some ROMs include a setting to remove the navigation buttons glow. I tested with CM9 on the SGS2 and experienced none of the stutters in cases where the GN would. Another example: sliding between sections (comments, ralated, etc.) in YouTube is laggy iff the video is playing.
Click to expand...
Click to collapse
Screen filter may reduce power. But amoled screens save power with lower brightness. There is no difference between lcd vs led on this issue. And modifying the framework to bring min brightness down to 5 rather than 15 saves much more power than screen filter. Its no contest. This isn't different from lcd in this case.
---------- Post added at 03:20 PM ---------- Previous post was at 03:14 PM ----------
fnf said:
Thanks for the tip, on the Galaxy Nexus it's possible to set the brightness to 0 by writing to /sys/class/backlight/*/brightness but the brightness is checked and reset to the minimum (default 10) every time the screen is turned on. I guess Root Dim works to the same effect so it runs as a system service. Still, it'd be an awesome addition for people who haven't bothered to mod.
Click to expand...
Click to collapse
Yes we can write to that sysfs file, but it gets reset. The mod to the frameworks incorporates that backlight file so its now able to go down to 1, 2, 5, or whatever you want. It makes it now stock, so you are no longer capped at 10 (actually I think 15 is the cap I see). But that mod is just removing this cap and making it lower to whatever you want. Stock.
So no extra app is needed. No additional tweak. It now makes the stock brightness able to go down to 1 by itself whenever it needs.
Well, after 5 months of looking out for the best values, I've experimented and all and found out these to be the best. Even at lowest brightness, the screen is crisp and clear just like it's supposed to be.
People who have the Purple Screen issue, I highly recommend you use these values.
Requirements -
1. Franco Kernel Updater (TKT wouldn't give that much brightness/crispyness to the screen)
2. ICS Gradient Fix (Check Signature)
3. Franco Kernel
First up, flash Franco's latest kernel.
Secondly, make sure you don't have any 2 or more applications which have Color Control options (Like, Franco Kernel Updater and TKT - Remove TKT and stay with Franco). If you do have 2 or more installed, please set all values to default on all applications including Franco's. (In TKT, click on menu and select reset preferences and reboot).
Third, fire up Franco Kernel Updater and get to the CC options and set these :
Color Multipliers -
Red - 280
Green - 292
Blue - 350
Gamma -
Red - 4
Green - 0
Blue - 9
Disable Contrast Adaptive Brightness - Yes (Tick)
Contrast Control : -24
OMAP Gamma - 1.2
These values work BEST with MoDaCo's JB Build. Tested on Jr1, Jr.1.1, Jr2.
Please note : This is simply a band aid, not a total fix. The purple screen and grain issue is probably a hardware issue. This settings are extremely crisp on my device. You need to get adapted to them.
Thanks to -
1. Franco for his amazing kernel and application.
2. Morfic for introducing contrast control into the kernel world and of course for his kindness. (You're the sweetest developer I've talked to).
Best of luck with these settings guys!
Please, don't forget to click "Thanks"!
It made everything look over-saturated for me.. plus, is it safe to jack up the settings like this?
It did improve the grainy screen on low brightness problem, though.
Well, i think the best values i've EVER Seen.
Oh dear, so f****ng awesome.
via Google Galaxy Nexus
Made my eyes hurt.. Too cold.. I'm trying to get my screen as close to 6500k as possible.
Sent from my Galaxy Nexus using Tapatalk 2
Thank you for this! By far the best optimization of colors I've ever seen. Maybe colors are a bit over-saturated but thats how Super AMOLED should produce.
Doesn't lacking the values up that high create burn in???
Sent from my Galaxy Nexus using xda premium
craigbailey1986 said:
Doesn't lacking the values up that high create burn in???
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Try reducing every multiplier value by 40. 280 to 240, 292 to 252 and 300 to 260.
This can never be an all-in-one "fix" because of the way screen technology works. Everyone's screen will have different degrees of the problem itself (purple tint & grain), on top of that they will all have a slightly different color temperature, contrast level, saturation etc. By providing the values that worked for you, you're just going to have a thread where half the people think it looks great, half think it looks awful, and everyone thinks everyone else is crazy.
A better idea might be to describe the steps you took to arrive at your own numbers, things you looked for, how you tweaked them to get to the best values.
Look Excellent to me - Screen absolutely Pops, so vivid and the gradient issues are not visible.
Thanks so much!
Those high values are gonna kill your screen
OP settings work well for me (similar to my 200 215 280, -2 0 10, -23, CAB off), but OMAP always makes things worse IMO. With OMAP at 1.2 I instantly see banding again where with it off the gradients are smooth. OP settings with OMAP 1.0 are excellent however, reducing the magenta and yellowing I was seeing with my others. I am worried about the burn-in though..
What's this about burn in? Do these settings cause it?
I sort-of mispoke. Burn-in is possible, but high multipliers are more worried to wear out those pixels/degrade them faster.
Edit: I'm going for more of a "Trinity Blue" sort of solution now: 215 235 280, -2 0 15, -24, CAD off, OMAP unset. Still trying to find that balance that gets rid of the magenta/yellow at all points.
Okay guys try out 180,192 and 250 as the color multipliers. No burn issues then. I'm on it right now. Its great!
I'm using Trinity kernel, TKT, and Display Tester Pro for calibration. The gamma test shows that my particular settings should be red=2, green=3, blue=2. The color gamma settings are not relative to one another and are not "mixed together" for adjusting color. Each one is a separate adjustment for that color's correct level of brightness for midtones, relative to darkest and lightest levels. Together, the three settings add up to correct gray brightness levels, not to correct gray colorlessness.
If you look at a chart containing only black, 50% gray, and white, the color multipliers should be adjusted to remove any trace of color tint from the gray. The easiest way to do it is set the weakest color to 200 and reduce the other two colors until the gray has no color tint at all. The properly set color gamma settings, on the other hand, should make the 50% gray have the correct lightness level.
If you have yellow tint, there's not enough blue. Magenta tint means not enough green. Cyan tint, not enough red.
The color multipliers, unlike the gamma settings, are relative to one another. Once you have them set correctly relative to one another, moving them all up or all down together pnly changes the overall brightness of the display. The wrong overall brightness level will remove detail from either the black end or the white end. Too much brightness is also bad for the screen, not to mention battery drain.
So anyway I'll shut up now and I hope everyone gets their screens looking perfect.
gsm gnex / cm9 / trinity / 1420 MHz
for whatever reason trinity seems to be giving me better screen color, but im sure I could do the same with franco, anyways, my gamma settings are untouched, I found that modifying the color to these values makes the purple tint go away for me:
Red:135
Green:135
Blue:190
Trinity Contrast -15 to -25
Have you tried adjusting it for 18% gray? I can nail it pretty close with 180,150,190 and 8,0,8 but gamma is a complete ***** on this display...
strumcat said:
I'm using Trinity kernel, TKT, and Display Tester Pro for calibration. The gamma test shows that my particular settings should be red=2, green=3, blue=2. The color gamma settings are not relative to one another and are not "mixed together" for adjusting color. Each one is a separate adjustment for that color's correct level of brightness for midtones, relative to darkest and lightest levels. Together, the three settings add up to correct gray brightness levels, not to correct gray colorlessness.
If you look at a chart containing only black, 50% gray, and white, the color multipliers should be adjusted to remove any trace of color tint from the gray. The easiest way to do it is set the weakest color to 200 and reduce the other two colors until the gray has no color tint at all. The properly set color gamma settings, on the other hand, should make the 50% gray have the correct lightness level.
If you have yellow tint, there's not enough blue. Magenta tint means not enough green. Cyan tint, not enough red.
The color multipliers, unlike the gamma settings, are relative to one another. Once you have them set correctly relative to one another, moving them all up or all down together pnly changes the overall brightness of the display. The wrong overall brightness level will remove detail from either the black end or the white end. Too much brightness is also bad for the screen, not to mention battery drain.
So anyway I'll shut up now and I hope everyone gets their screens looking perfect.
gsm gnex / cm9 / trinity / 1420 MHz
Click to expand...
Click to collapse
arzbhatia said:
Okay guys try out 180,192 and 250 as the color multipliers. No burn issues then. I'm on it right now. Its great!
Click to expand...
Click to collapse
It's been discussed few times already - going above 200 can lead to screen burn in. On SAMOLED screens blue color wear out first and peeps really shouldn't touch this setting. Better set lower red/green values. Screen will look a bit darker so don't cranck up contrast too much, -10 should be good enough.
herzzreh said:
Made my eyes hurt.. Too cold.. I'm trying to get my screen as close to 6500k as possible.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
look at the graphs.
http://forum.xda-developers.com/showpost.php?p=29037317&postcount=1
herzzreh said:
Have you tried adjusting it for 18% gray? I can nail it pretty close with 180,150,190 and 8,0,8 but gamma is a complete ***** on this display...
Click to expand...
Click to collapse
You can see where your gamma should by by installing the free version of Display Tester from the Play Store. Go to Color, Gamma, and slide the gray screen to the left to see the red page. Find the vertical bar that most closely matches the red bacground. The number on that bar is where your gamma should be set for that color. Mine is spot on at 2.3. Then slide to green page and do the same. Then the blue page. My green gamma reading is 2.8, meaning it isn't quite as bright as the red or blue, so I have to turn it up a hair. My blue is good at 2.3. The adjustment sliders in TKT only give me whole-number choices, so I get as close as possible with 2, 3, 2. I'm just guessing there, since TKT doesn't have normal gamma increments. Anyway good luck taming your gamma.
galaxy nexus (gsm) / cm9 / trinity @ 1.4GHz
Hi all. I've seen this feature in the first note and now I see it again.
Adjusting tone save the energy saver based on image analysis
Is this option really make a difference?
h t t p://imageshack.us/f/202/20130221221021.png
No 10 posts so sorry for link
I always have it set to off. I had it on but never noticed any difference. My guess is that if you are looking at a very colorful image, prolly the screen will lighten more up or over-saturate the colors to look nicer. Maybe even the brightness who knows.
According to a cnet article:
" There's another adjustment on the Note 2 to that significantly affects picture quality. Samsung applied the cryptic moniker "Auto adjust screen tone" (AAST) to a check box at the bottom of the Display menu. Uncheck it and the phone's full light output capabilities are unshackled, nearly doubling its contrast ratio and improving its ability to compete with ambient light. Turning off AAST also improves color accuracy slightly. "
Seems like changes the colour tone of brighter colours to reduce their brightness.
I keep it on since I like milder screens.
If you prefer low brightness and want to save power , keep it on.
If you find yourself using high brightness often, turn it off.
Sent from my GT-N7100
HypoDest said:
According to a cnet article:
" There's another adjustment on the Note 2 to that significantly affects picture quality. Samsung applied the cryptic moniker "Auto adjust screen tone" (AAST) to a check box at the bottom of the Display menu. Uncheck it and the phone's full light output capabilities are unshackled, nearly doubling its contrast ratio and improving its ability to compete with ambient light. Turning off AAST also improves color accuracy slightly. "
Seems like changes the colour tone of brighter colours to reduce their brightness.
I keep it on since I like milder screens.
If you prefer low brightness and want to save power , keep it on.
If you find yourself using high brightness often, turn it off.
Sent from my GT-N7100
Click to expand...
Click to collapse
Thanks you for info.
Does anyone know how to turn off the s20's adaptive display feature? (I'm not asking about adaptive brightness.) I'm on a US snapdragon, unlocked, regular S20. Thanks!
I am referring to:
"Samsung's adaptive super AMOLED screen optimizes the color range, saturation, and sharpness of the picture depending on what you're watching or doing."
https://www.samsung.com/us/support/answer/ANS00063051/
The vivid/natural, white balance, and advanced RGB settings mentioned in that link do NOT seem to impact the adaptive display feature. (And in fact, white balance and RGB settings don't seem to do anything at all... If anyone has thoughts about why THAT is, or how to make them actually have an effect, I'm interested.)
I have tried turning off dark mode completely, turning off the video enhancer, and turning off the dark mode on wallpaper, but the problem persists and impacts things like apps and pages in Chrome - basically everything.
If I look at my task switcher, app screens will often look the way I want them to in the preview, but when I click on one, after about a second the display adjusts and changes the image to something brighter, whiter, and less what I want. This is true whether adaptive brightness is on OR off.
I'm trying to use a screen filter to manually set the screen to the settings I need, and it feels like the screen is fighting the filter and countering it, and I think this business with the adaptive display optimizing color and saturation could be the problem. Or if you have other ideas for the source of the problem, I want to hear them.
Any help is appreciated!
Erre én is k
dovesong said:
Does anyone know how to turn off the s20's adaptive display feature? (I'm not asking about adaptive brightness.) I'm on a US snapdragon, unlocked, regular S20. Thanks!
I am referring to:
"Samsung's adaptive super AMOLED screen optimizes the color range, saturation, and sharpness of the picture depending on what you're watching or doing."
https://www.samsung.com/us/support/answer/ANS00063051/
The vivid/natural, white balance, and advanced RGB settings mentioned in that link do NOT seem to impact the adaptive display feature. (And in fact, white balance and RGB settings don't seem to do anything at all... If anyone has thoughts about why THAT is, or how to make them actually have an effect, I'm interested.)
I have tried turning off dark mode completely, turning off the video enhancer, and turning off the dark mode on wallpaper, but the problem persists and impacts things like apps and pages in Chrome - basically everything.
If I look at my task switcher, app screens will often look the way I want them to in the preview, but when I click on one, after about a second the display adjusts and changes the image to something brighter, whiter, and less what I want. This is true whether adaptive brightness is on OR off.
I'm trying to use a screen filter to manually set the screen to the settings I need, and it feels like the screen is fighting the filter and countering it, and I think this business with the adaptive display optimizing color and saturation could be the problem. Or if you have other ideas for the source of the problem, I want to hear them.
Any help is appreciated!
Click to expand...
Click to collapse
they removed the option to close adaptive display since Note 9 starting from s10 it is always on and can't be disabled
They removed the option to close adaptive display since Note 9 starting from s10 it is always on and can't be disabled
It was something like attached picture on Note 9
Ah hah! I think I figured out a solution to my problem (which was that the whites were too blue and bright and vivid as compared to everything else on the screen, no matter what settings I used on Twilight or another screen filtering app). For anyone who comes after me with a similar issue: the native blue light filter doesn't JUST turn on/off - it has an opacity setting which you can find and adjust by clicking on "blue light filter" in your display settings menu, to the left of the on/off toggle switch. Turning it all the way up (to the right) tones down the whites and blues without impacting the rest of the colors on the screen, which for me at least creates a much better color display ratio.