Yesterday night I noticed that black pixels do not switch off completely on my phone. (as they should on AMOLED, right?)
Try it this way:
Set your screen brightness to almost a very low value.
Now look at a picture which has a black background and very little color in the middle etc. The room has to be dark, otherwise you wont see a difference. (You can also cover your had with a blanked etc., just wait a moment, so your eyes get used to the dark environment).
Hide the statusbar, navbar etc., so only your picture is shown (Tap on the picture once in Google Photos).
When you disable your lockscreen and switch the display on and off a few times you'll see that the picture vanishes first and than the display goes completely dark. It looks like a very light yellow back-light.
Another way:
Again in dark environment power off your phone. Switch it back on and watch the bootlogo. The surroundings (everything that's black) is truly black and "switched off" and than some secs before completing boot the "back-light" switches on.
I tried to find a solution for that. The only thing I found is a setting in Kernel Adiutor named "Minimum RGB value" under the screen section which is set to 35. However lowering it to 0 does not work, the value get reset to 35 every time (Higher value does not change anything either tho).
I'm running Oxygen OS 2.2.0 with bluespark kernel + root + xposed (Gravitybox + XInternalSD)
maybe the black is not that black?
edit: just tested with fullhd resolution black picture and red dot pixel in centre(PNG file, not jpg nor bmp) and everything is working as intended - black is pitchblack(same as when u just block/shutdown ur phone)
edit2: i'm not having my reflex by my side this couple of months, but you can check it making a photo in light isolated room with low shutter speed(20sec should be enough, if they really produce light)
AlexVendettA said:
maybe the black is not that black?
edit: just tested with fullhd resolution black picture and red dot pixel in centre(PNG file, not jpg nor bmp) and everything is working as intended - black is pitchblack(same as when u just block/shutdown ur phone)
edit2: i'm not having my reflex by my side this couple of months, but you can check it making a photo in light isolated room with low shutter speed(20sec should be enough, if they really produce light)
Click to expand...
Click to collapse
Thank you for testing. I reproduced your result with a #000000 PNG and everything seems fine, as long as the brightness does not go below a certain value. Turning auto brightness off and sliding the brightness completely down enables some kind of light in the whole panel.
Could it be some android feature, which put's a light overlay over the the screen image to protect the eyes in low light environments, like these warm filter mods?
Related
I am kind of just curious about this, as I have searched the net and have found no one who has experienced the same problem.
I have a Blu Touch Book 7.0 plus, and plan on making do with it until the right phablet comes along at the right price. About a week ago I had it in my pocket as I helped to unload some heavier packages from a truck. It took some impact while in my pocket, I didn't think it took any meaningful impact. But then I turned on the screen, and everything seemed to have a blue tint. On closer examination - it didn't have a blue tint per se, but black was being displayed as blue; opaque black was opaque blue, semi-transparent blacks and darker grays and what not resulted in a blue tint. But whites and most colors displayed perfectly fine - i.e. for example, the Google home page looked completely normal. The display damage is evident even on boot, as soon as the manufacturer logo pops up before the bootanimation.
My workaround for the time being is to use a screen filter that places a semi-transparent white image over the screen, which gets rid of any hints of opaque black with about 48% transparency. It results in faint colors of course, but the colors are at least accurate with no blue tint, and the screen looks almost completely normal from the certain viewing anglea. Interestingly - the absence of opaque black seems to result in a lighter load for either the cpu or the gpu; previously the phone ran very smooth but if I had Dolphin (or another resource consuming app) open, and turned the screen off without pulling up my home page first, the screen would not always turn back on right away, either I would have to long press the power button or wait up to several seconds. Now, regardless of what I have open, I can toggle the screen on and off without lag.
So is this damage to the gpu? The screen itself? Does anybody suggest a better work-around?
Appreciate it.
Hey guys,
just as I had settled to keep my V30 (and use Lux for autobrightness) despite banding. I found something new!
If I unlock my phone and I have some white displayed, I can see the color temperature shift (like yellowish, bluish, greenish, yellowish, greenish, ....) for like 10-20 seconds, then it settle.
I also notice that when I turn off my screen, the color change back just before the screen goes off.
It's happening on every color configuration, with auto-brightness, without, etc.
Could it be a "feature"? Is it the screen adjusting it's white balance to the outside lighting?
Thanks and regards,
Dan
Nobody has ever noticed that? Just go to google on your web browser, then close your phone, unlock directly to the google home page and check the white background. Mine shift temperature (or white balance) a couple time before "settling" to one.
Nope. Not seeing this behavior at all.
Ok I found what is causing this and I think it's normal. It's just the first phone I own that does that. Here is the culprit :
https://imgur.com/gallery/pGlIF
Even with auto brightness turned off, there seems to be a white balance adjustment (which is the first time I see). This light is making it do seizure.
Has someone experienced "dancing blacks" with vertical or horizontal scrolling, specially in low bright settings?.(40 or below)
I have purchased an EU ver. Of V30 and i experience this behaviour every time i do scrolling with photos, desktop icons with black contour (like netflix) webpages with black línes or blocks... Or everything containing black colour.
When i move the photo, scroll across website... The part that contains black colour seems to dance on screen, it's hard to describe but it's something like jelly effect, the black part of the object, photo... seems slower and doesn't scroll accordingly. I went to a local store to check it on another unit and discard a faulty one and i saw the same effect.
Regards
That's the feature of all oled displays, nothing you can do with it except changing the brightness to the level it doesn't show any signs of this "violet trails"
i have that behavior too on my H930DS. no solution yet.
The phone regulates it's brightness through PWM, so that you don't have the same issue like on the g flex where the whole display got blurry and grayish when you turned the brightness down. Because the display shuts itself on and off many times per second (222 times according to a German review page), you see that when you are sensitive. Just set the display brightness higher, then you should be fine.
So is it pretty obvious , or does ghosting usually happens on low brightness on every AMOLED display or is this phone only suffering from this ?
(I saw ghosting while I was horizontally scrolling a black picture of a gray background).
Can anyone confirm this for me ? ( Not a huge issue though , it doesn't happen after the brightness is increased)
Try with this image in lowest brightness
Zoom in and move it left and right you will see a trail of weird color trailing the black circle.
its normal for amoled displays
almost all amoled screen leave purple trails when switching from pitch black to some other color pixels.. don't worry about it
Ya when scrolling in app drawer the icons looks like wobbling.
Yes this has been the case in my Realme XT as well. When you have black background in the app drawer and there is any app icon that is dark you see the icons changing their shape while we scroll.
Even in YouTube when you turn on the Dark Mode and there is any video that is pitch black you may see it leaving a trail when you scroll through the feed. This is more often when screen is in low brightness. Is this issue for all other phones with Amoled panel or only with Realme XT ?
Amoled panels basically has the lowest response time in any display technology format except "Ink Display". Every individual pixel lights up individually from switch off (black) to on (any color). Higher the brightness means higher the color spectrum shining into your eyes and thus it let you see no ghosting while at peak brightness. It's still happening but we dont usually see that clearly. Ghosting is very natural phenomenon of Amoled technology. Also these budget Amoled panel tends to big fan of burn out. So make sure you are using live wallpaper that changes or moves (stock one that comes with the ColorOS is good enough).
As title says. Suddenly my phone started to turn to green/matte/muted without contrast and very faint colours. Takes a while, like 4 or 5 minutes, but it goes back to normal while doing some kind of vsync (you can see how it forces the grey scale back to normal as some kind of vsync error). Some icons with pure black background appear with the proper contrast and colours (!!!) and If I switch auto brightness to off doesn't happen [UPDATE: now it's permanent] - No root, updated to last 2022 march patch.
Any solutions?
Thanks in advance!
EDIT: after 12 hours of partial use I've identified the green tint behaviour, it happens when the light sensor tries to adapt the screen brightness. If low = perfect colours, if high = perfect colours. All the in between = green tint.