I've been noticing a few interesting things with my Galaxy S2 and wanted to know if these things would be something to be concerned off.
1). With faith, I finally updated the firmware to 2.3.5. Now, the yellow tint is gone. However, the areas circled in the pictures attached continue to show the same washed-out effect. Instead of the usual blue color in the Notification Area, the areas circled, show a much pale tone. This becomes very visible in grey backgrounds (i.e. accessing Marketplace and Notifications Area) and low brightness in Browser. I don't know if this is a defect in the display or software related like the Yellow-tint.
2). After updating the firmware, the kernel version has Intratech's username at the end? Is this suppose be like that? I thought the Kernel, would be the same as before as stock. The phone confirms this is a official Samsung Firmware, so i'm guessing I have not rooted yet.
3). At lowest brightness, in complete darkness, if you squint and look very carefully in Notifications Area, you can see a faint vertical line across the Notifications Area-only. Doesn't affect anything else though.
4). If you look carefully at the Notifications Area, 2/3 of the screen is darker, while the right is fairly 1/3 is brighter as indicated by the arrow in the picture attached. Is this a way to compensate for the yellow-tinge on the left?
5). The auto-rotation feature doesn't always work whenever display toggles between verticle and horizontal position. Is this something all users face?
6). Lastly, I'm not getting any close to 4,000 on Quadrant Standard even with virtually nothing running in the background. My scores are only ranging between 3000 and 3500 in Quadrant Standard, is my hardware defective? I never had a situation where temps crossed 40 degrees Celsius. My device is normally maintained at 29 degrees Celsius and on average, 31 degrees Celsius. I feel like the CPU is constantly clocking at various speeds.
Please leave your feedback. Thanks a lot.
SAlmighty said:
I've been noticing a few interesting things with my Galaxy S2 and wanted to know if these things would be something to be concerned off.
1). With faith, I finally updated the firmware to 2.3.5. Now, the yellow tint is gone. However, the areas circled in the pictures attached continue to show the same washed-out effect. Instead of the usual blue color in the Notification Area, the areas circled, show a much pale tone. This becomes very visible in grey backgrounds (i.e. accessing Marketplace and Notifications Area) and low brightness in Browser. I don't know if this is a defect in the display or software related like the Yellow-tint.
2). After updating the firmware, the kernel version has Intratech's username at the end? Is this suppose be like that? I thought the Kernel, would be the same as before as stock. The phone confirms this is a official Samsung Firmware, so i'm guessing I have not rooted yet.
3). At lowest brightness, in complete darkness, if you squint and look very carefully in Notifications Area, you can see a faint vertical line across the Notifications Area-only. Doesn't affect anything else though.
4). If you look carefully at the Notifications Area, 2/3 of the screen is darker, while the right is fairly 1/3 is brighter as indicated by the arrow in the picture attached. Is this a way to compensate for the yellow-tinge on the left?
5). The auto-rotation feature doesn't always work whenever display toggles between verticle and horizontal position. Is this something all users face?
6). Lastly, I'm not getting any close to 4,000 on Quadrant Standard even with virtually nothing running in the background. My scores are only ranging between 3000 and 3500 in Quadrant Standard, is my hardware defective? I never had a situation where temps crossed 40 degrees Celsius. My device is normally maintained at 29 degrees Celsius and on average, 31 degrees Celsius. I feel like the CPU is constantly clocking at various speeds.
Please leave your feedback. Thanks a lot.
Click to expand...
Click to collapse
For me, nothing dramatic recognizable.
1).
Your pictures do not show me any problems or defects.
But this is subjective and maybe you can see more differences when looking directly on your phone's display.
2).
I can not see Intratech's name in your kernel, but this is nothing to bother as it is still recognized as original / stock kernel.
I also think that your phone is not rooted. But you should know, if you flashed a rooted kernel or used another rooting method (like flashing an insecure kernel, using SuperOneClick ans re-flashing a stock kernel).
3). + 4).
The notification area can be used for adjusting the brightness of the screen (click on the bar at the top ans hold your finger there for a second, then move it to the right to increase or to the left to decrease the brightness) - maybe that's why you can see different areas in the notification bar?!
5).
Auto-rotation is not available in every screen and/or app. It should work in your browser, in email app, in video player, etc..
6).
The benchmark scores depend on many different factors. I have flashed a lot of ROMs and kernels (most of the time official and/or stock ones), and I usually get 3000 - 4000 in Quadrant.
For example, the economy mode reduces the speed of the CPU to get a better battery life. Please be sure to disable such performance "stopper" before running a benchmark.
If you want to reach higher scores, you should look for a custom ROM which is "specialized" for high performance.
Original/stock ROMs usually try to enhance battery life and are not focused on a maximum performance.
Thing is when you look at the area outlined in black, the the color is not equal as to the rest of the screen. Instead, the areas outlined in black appear more pale. This doesn't even affect the overall picture quality, but it is sure visible in lower brightness and in situations like accessing marketplace and notifications area and web browser.
Another thing I noticed is that with medium brightness, you begin to spot a faint horizontal line in a plain white background on the top (it doesn't flicker or go on and off, it's just there). if you put the brightness at full level, that line doesn't even exist, is it software?
and when you set the brightness to lowest, a strange faint blank vertical line appears when you see in pure darkness but only in a confined area of the notifications area. is this amoled-related?
when rotating the screen while in notifications area, I can see faint lines that appear on the sides of the screen; looks to be like ghosting. i've seen other S2's and those lines seem to be permanently fixed regardless of what way you orient the phone. instead of those lines that are permanently fixed, mine just magically disappears, but it takes seconds for it to blend with the current position. hope you know what I mean.
please let me know
thanks again
Hard to tell by the pictures, but if you believe the screen to have a fault, then return it under warranty.
or could it be I'm making it a big deal out of the ordinary? lol
I sense a small variation in the tone in that area of the display (right triangle), before removing the yellow tint by upgrading to 2.3.5, this area used to distract me a lot. is this usual in SAMOLED+ displays?
perhaps, I've uploaded a much clearer photo now. if you look on the bottom left and top right you will see what i mean. is this normal or is something wrong. is this usual with SAMOLED? please let me know, thank you
here are the areas highlighted, please check and let me know, thank you
i have a cross shaped formed in the upper right of my screen tho my phone is a nexus s.its still amoled.i noticed it when having a gray background in a dark room.also when i pull out the keyboard for 5 to 10 seconds then pull down the notification bar while the keyboard is still there i can clearly see image retention of the keyboard in the notification tray.i also see this in market when searching for an app and it loads i can see the retention of the keyboard in the grey background.f
Related
There are a few threads out there that have touched on this issue but none as far as I can see that deal with it directly.
The problem comes when you display a pure black screen in low light conditions. It shows that the AMOLED screen is actually grey / blotchy / cloudy instead of being pure black. Initially I thought mine had fingerprints or smudge marks on it, until I realised they were behind the screen. I guess I might have got a phone with a screen that was replaced, but the amount of people who have also reported a similar issue leads me to believe that it might be a manufacturing default? The blotches / clouds on the screen dont change, but exhibit a random formation as one would expect from a defect. It is also possible to see a very faint outline of light running along 3 edges of the screen.
Naturally this is a situation that doesnt reveal itself very often. But I as I use my phone a lot at night, especially reading ebooks or watching films, you start to notice it more and more where you have large expanses of empty black screen.
What I would like to know is how many people have got screens that exhibit this behaviour and how many of you have sent them in for service or had them replaced?
Is it a common issue and something that is to be expected from this type of screen?
You can test if yours has this problem using 'Screen Test' (its free) from the market place. It cycles through solid colours and patterns every time you touch the screen.
Just do it in bed with all the lights out P), give your eyes a few seconds to adjust and see what your screen looks like displaying pure black.
I'm very interested in everyone's experiences and any input or information you have.
Thanks everyone in advance!
ps: I came from a ZTE blade (OLED) which has a uniformly dark grey background when displaying pure black. I kinda expect this as it is a budget phone (albeit with a better than budget screen), but I didnt expect the SGS2 to be quite as bad.
Use "screen adjuster" from the market and set contrast to -60
i have never seen this black low light screen defect. but i am asking you people if any of you have noticed that ugly blurry shadows which are perfectly visible with low light, on white backgrounds especially. they look like marks above the actual display and make high quality images look like low resolution.. it is annoying as hell..
I have this. Noticed it one night when my phone was switched off and charging.
Sent from my GT-I9100 using XDA App
I also have this, noticed the first evening i used the phone...you can notice this during the screen wake delay, or when in a call if you cover then uncover the proximity sensor...don't know if it's a defect but sure it bugs me, i know many won't notice it and will say they don't have this...i will add that if u look carefully to the screen dimmed at lowest brightness in a low light (buy not dark) environment, like early morning, you'll see some "interferences" behind the image, also the darker/yellower left half screen is still visible in these conditions
These things shouldn't be there in a 500€ phone
Sent from my GT-I9100 using XDA App
Thanks for the feedback already.
@elmerendeiro: I have also noticed some 'interference' lines on my phone from time to time. I did a bit of research and it seems when your phone's brightness is set around 25 - 30% it picks up interference from either the wifi or 3g radio. Notch the brightness either above or below this level and you wont see it anymore.
I agree with you when you say we shouldn't be having these problems on such an expensive phone.
It bugs me too - if it wasnt for this i'd have to say it would be an amazing phone
Might give the Samsung service center a call and see if its something they're aware of and if they are replacing screens with this problem?
I'm always using the lowest brightness (0% or whatever it is), at stock browser there is an option to change brightness too so you can get even lowest brightness then you got...
While I'm doing that I've notice that there are some pretty invisible lines - about 2 vertical lines on the right side of the screen - while viewing white or gray page.
The more the brightness is lowest you can notice it, and the more the brightness is higher you could not see it.
Its not like the burning screen thing as I never keep the screen on too much time on the same point (and always using Live Wallpaper), I know how its look like because I had it on my Nexues One... its showing only when using lowest brightness and could see it on white or gray wallpaper (I've notice it on google search at browser)
Anyone have any idea why is it happens (again, when you make the screen brighter its gone) and is it safe to use the lowest brightness or should I avoid it and put the brightness to little bit more ?
PsyOr said:
I'm always using the lowest brightness (0% or whatever it is), at stock browser there is an option to change brightness too so you can get even lowest brightness then you got...
While I'm doing that I've notice that there are some pretty invisible lines - about 2 vertical lines on the right side of the screen - while viewing white or gray page.
The more the brightness is lowest you can notice it, and the more the brightness is higher you could not see it.
Its not like the burning screen thing as I never keep the screen on too much time on the same point (and always using Live Wallpaper), I know how its look like because I had it on my Nexues One... its showing only when using lowest brightness and could see it on white or gray wallpaper (I've notice it on google search at browser)
Anyone have any idea why is it happens (again, when you make the screen brighter its gone) and is it safe to use the lowest brightness or should I avoid it and put the brightness to little bit more ?
Click to expand...
Click to collapse
AFAIK it is not dangerous for the display.
There are many screen filter apps available to lower the brightness even lower, and never heard someone reporting a damaged screen because of this.
Usually, your lower the brightness of the display to reduce the battery consumption for a better battery life.
If that is your aim, then try to use as black background as possible.
With dark/black screen the battery consumption of an OLED (like our AMOLED) display is lower than on light (white) background.
And you won't see the "pretty invisible lines".
maybe a burn in ...
It_ler said:
AFAIK it is not dangerous for the display.
There are many screen filter apps available to lower the brightness even lower, and never heard someone reporting a damaged screen because of this.
Usually, your lower the brightness of the display to reduce the battery consumption for a better battery life.
If that is your aim, then try to use as black background as possible.
With dark/black screen the battery consumption of an OLED (like our AMOLED) display is lower than on light (white) background.
And you won't see the "pretty invisible lines".
Click to expand...
Click to collapse
Well, actually when I thought about it I was playing a game "Jetpack Joyride" for almost two hours continuously and played it a lot at the last days, even though the screen at the game is changed every time, the 'roof' has some constant lines, so maybe it cause the 'burn in' vertical line/s that I see.
The weird thing is that burn in looks better and 'tougher' when using higher brithness and not lower as in this case...
When I put high brightness the 'burn in' seems to dissapears.
Is it possible or its something else? [I know AMOLED screens are pretty sucks about that situations of burn in things]
Hello, I own a i9100 and I have some burn-ins at the top of the screen that replicate some buttons of a browser or something, and some burn-ins at the bottom as well. I have read that leaving overnight an app that's constantly switching colours, with full brightness, could help a bit on that. I also read that leaving a blank screen (white image) on the same conditions (overnight, full brightness) would help as well. My question is, how true these both things are? I don't want to end with a bigger problem than the one I currently have. The burn-ins are most viewable at Blue, Red, and Black screen colors.(like if I put a background with one of those colors on it)
Never had any of these on my S2,but from my experience with the galaxy s plus,these tricks won't work.None will to be honest.It's permanent.This shows how immature amoled technology is.Learn to live with it or replace the screen if that bothers you much.
what a sign you got there...
Lucky you. Mine is not THAT noticeable if you're using it normally, but as soon as you open something with a plain color on it, the burn in shows itself on all its glory. So right now you can't tell if leaving the white image all the night or the thing switching colors will damage my screen more?
mwehehe
Well,back then when I tried every method you described above on my i9001,I didn't noticed any improvement nor any further damage.Even after running those for 10h+.So I assume it's safe.Can't say the same for the S2 though,have no problems with it.
I (and at least one other person) have experienced what seems to be screen brightness or color temperature shifting/flickering that's visible on predominantly white or bright pages/screens. It's extremely subtle, but noticeable. For my phone, it seems not to occur at 100% brightness, but I typically keep it around 70%, and it's much more visible then.
Is anyone else experiencing something similar? You can go to a site or settings screen on the phone that's mostly white background, browse Twitter, Google Now, etc., and look closely at the white space and see if it seems to shift around to you.
Cheers all.
Hello,
Never had a phone with Always on feature so I would like to ask if is a normal behavior to see for a few seconds a clock image retention from AOD when the phone is unlocked.
I have LG V30 H930 EU unlocked model.
Been using a H932 with AOD since day one and have never seen any image retention issues from it's use.
It's not very visible, you have to look very closely and perhaps also have some specific colored wallpaper. It lasts only 2-3secs and then slowly disappears. AOD needs to be on a screen for at least 30-60mins I think.
src151 said:
It's not very visible, you have to look very closely and perhaps also have some specific colored wallpaper. It lasts only 2-3secs and then slowly disappears. AOD needs to be on a screen for at least 30-60mins I think.
Click to expand...
Click to collapse
But the AOD constantly moves.
As previously stated, the AOD on the V30 is not a static image, but a dynamic image, (it rotates to several locations on the screen at a certain interval). That should preclude it from issues involving image burn-in or retention.
Having said this, there is an app on the Play Store that Samsung owners use to combat burn-in on their OLED equipped phones. I don't remember what it's called, but you should be able to do a search by topic. The other thing I would recommend is avoiding having the AOD on it's bright setting. Its a bit too much, even in bright daylight, and it does increase the chance of image retention, IMO.
Bright setting is off, but the brightness of AOD at least on my end is dynamic and depends on the light sensor. This "bright setting" to my eyes do almost nothing.
Ok nevermind, probably I'm just nitpicking... I appears to be "visible" only on a pinkish part of the wallpaper. It's one of the default.
I have (what I consider) an annoying slow, fade to black when I turn off the screen. Perhaps your "retention" is the same, slow change of state for the screen?
Maybe we can call it this way. I'm coming from LG G4 IPS screen which is changing such things instantly obviously and I don't know what is "normal" for OLEDs. As i said, clock number from AOD after unlocking has its footprint for a moment on a wallpaper, slowly disappears.
The screen is otherwise pretty good if I cosider some horrible issues reported here or on reddit.
But still apart from this "retention" issue I found 2 more, but basically small issues described here:
https://forum.xda-developers.com/showpost.php?p=75657168&postcount=670
so don't know what to do.
I'm still within 14 days return/replace period, but I'm worried about worse screen since this is still a lottery.
Not sure what is your issue. Turning off the screen is doing fine. Just one quick "animation" and everything is off.