Just wondering because I've seen a few posts already about screen burn-in, but I've had my Nexus since launch and have no problems at all. Is it because the people that are having the issue are using the GSM version and have had it longer? Is it because those people have their screens on all day?
I'm just trying to get a baseline to understand where the problem might be coming from. Don't get me wrong, I'm not in highschool so I have no need to keep the phone screen on 4+ hours a day (I average somewhere around 1:30 a day, but most of that is reading and answering texts/emails)...but just curious.
For anyone with burn-in problems just post which version you have (and when you got it, if you could) and the average screen on-time per day that you have. Maybe this could lead to a "best practice" document to keep it from happening to others!
I am afraid that this might be a redundant post you just made.
There is no physical difference between GSM and CDMA variation's SAMOLED screens. There should be more difference between which factory and/or country it was made than between GSM and CDMA.
I know you have already, but please refer to the posts made on:
http://forum.xda-developers.com/showthread.php?t=1509123&page=2
And I'll re-post the post I made over there on here as well for your information.
----------------------------------------------------------------------------
This will probably happen to all of us to some degree sooner or later.
The image retention that lasts 1-3 seconds we might see within a month or two usage is actually one of the characteristics of AMOLED "Ghosting effect"
which is not the same as AMOLED "reverse led fatigue" (or although technically incorrect but more widely understood term "Burn-ins") which maybe seen as permanent image retention shown as yellowish outlines of icons / keyboard outlines, etc.
Sadly, there's really nothing you can do about this problem after the fact, except to change the screen itself if it is really bothersome. Or you may try to change/delete/make transparent of the permanently placed icons/other objects/pictures to try to reverse these effects.
The only preventive measures would be changing screen rotation from vertical to horizontal, and make sure you don't have the screen on at a stay still image (preferably set auto screen off to 30seconds or so.)
----------------------------------------------------------------------------
charlescom said:
I am afraid that this might be a redundant post you just made.
There is no physical difference between GSM and CDMA variation's SAMOLED screens. There should be more difference between which factory and/or country it was made than between GSM and CDMA.
I know you have already, but please refer to the posts made on:
http://forum.xda-developers.com/showthread.php?t=1509123&page=2
And I'll re-post the post I made over there on here as well for your information.
----------------------------------------------------------------------------
This will probably happen to all of us to some degree sooner or later.
The image retention that lasts 1-3 seconds we might see within a month or two usage is actually one of the characteristics of AMOLED "Ghosting effect"
which is not the same as AMOLED "reverse led fatigue" (or although technically incorrect but more widely understood term "Burn-ins") which maybe seen as permanent image retention shown as yellowish outlines of icons / keyboard outlines, etc.
Sadly, there's really nothing you can do about this problem after the fact, except to change the screen itself if it is really bothersome. Or you may try to change/delete/make transparent of the permanently placed icons/other objects/pictures to try to reverse these effects.
The only preventive measures would be changing screen rotation from vertical to horizontal, and make sure you don't have the screen on at a stay still image (preferably set auto screen off to 30seconds or so.)
----------------------------------------------------------------------------
Click to expand...
Click to collapse
I'm sorry, you misunderstood my point of the post. I realize the hardware is identical (as far as the screen is concerned), I'm more interested in kind of how much screen on-time has a strong chance of creating permanent burn-in. I have a max of around 1:30 of screen on-time per day and I haven't seen a hint of burn-in...so I'm wondering if there's some magic number of on-time that will cause the problem to a much higher degree.
What I'm really hoping for is that, for instance, if we find people with 2:30 of screen on-time seem to really have the issue but people with 2 hours or less don't...then it might be a helpful practice to kind of keep screen time to a minimum above that. I realize it's not really helpful for most people (because nobody wants to curve their usage), but it's a limitation of the hardware.
Or maybe if a majority of the people with the problem seem to keep on the screen for 15-20 minutes at a time...that would help, as well.
Its going to happen. All amoled screens get it. The 2 verizom demo units at the store here have it really bad cause the screen is on all day. If you use transparent top and bottom bar, full screen in browser, and rotate your screen periodically, you can avoid the issue.
RogerPodacter said:
Its going to happen. All amoled screens get it. The 2 verizom demo units at the store here have it really bad cause the screen is on all day. If you use transparent top and bottom bar, full screen in browser, and rotate your screen periodically, you can avoid the issue.
Click to expand...
Click to collapse
Oddly enough none of my previous amoled based devices (captivate, SGSII, Galaxy Note) shows any signs of burn in but GNex shows slight ghosting/slight burn in of the notification bar. It's feintly visible when i open the xda app
Related
Hey guys , I have a problem, whenever i browse a site with a gray background, the screen is all the way down from its brightness ( since i use it indoors most of the time) i see like a semi black blurry line coming down top half the screen, you can notice it more in a gray background/image then with a color, but if you notice where the blurry line is, and is actually quite thick, though after you notice it, and switch to other colors, you can tell that there is a contrast difference between the color background and where the line is..
Im taking the phone to the sprint rep, i've already mentioned it to the Phone operator, and she mentioned she will note it, and i can just take the phone in.
( taking a screenshots odviously is useless, I'll bring up photoshop and somewhat portray what i see on the phone screen when i get home from work )
Though my phone hasn't been suffering with the android OS over percentage usage or anything of sorts, no LOS or nothing else, just the Wifi Scanning Bug..
If u over look it, you wont see much different and more when the screen is fully bright, but when the brightness is taken all the way down,you can see it! wtf... so i might as well take the risk, and see if i can get it replaced and hope that the next phone will be good too eh?
Could it be some Semi-dead LED, or burnt?..
I know that the way i write makes no sense lol, sorry english is my second language, im cuban
If your within your 30 or 14 day return why not? Obviously its bothering you so get new one. But do it right before your 30 day is up cause hopefully the second batch of epic touches will be out
Sent from my SGH-I897 using XDA App
I just got my Galaxy nexus (an hour ago), and I'm getting around using it pretty well except for one thing which is annoying me big time.
The screen seems to dim or change its color balance when viewing certain things. Whites are usually dimmed at most times, but when I view other things, the dimness goes away and whites become very radiant.
It seems like the phone is adjusting automatically to things on the screen for the sake of energy saving. How do i disable this!?
Yes, I have my Brightness on manual and set to full. That is not the issue.
okay wow this is getting annoying... Two more issues:
1-The thing won't transfer files while im using windows 7 "the device has either stopped responding or has been disconnected". When using OSX Lion, it isn't even detected.
2-There is chinese text here and there no matter what I do for language settings.
This is my first android phone ever, and I'm not liking the experience so far...
Look, I've tried searching for these two issues, and I did not find any threads with them resolved. Maybe I'm computer illiterate. Maybe I have a very low IQ, but can you just help me resolve these issues IF you know how to resolve them without just going into my thread and be like "Oh look, another noob", and proceed with leaving?
PS: I AM A NOOB.
Protip 1. Read up on amoled technology a little. And then read some of the issues some phones like galaxy s2 had. Your dimming is normal. It sounds like you're just more sensitive to it.
Protip 2. Download the appropriate drivers. In device manager, you want it to say android adb interface when you're phone is plugged in.
Protip 3. Take a chill pill. It is okay to be a noob. It happens. Your attitude comes off as annoying or you're freaking out over nothing. Solving problems take time and we are not sorry xda can solve them instantly for you. Patience, amigo.
My grandma beat me down and took my nexus. Sent from a jitterbug with beats by dre.
You might try turning of Auto Brightness and set it somewhere you feel comfortable... I just decided when I got this phone that I'd make myself get used to the adjustments and it's worked out well.
IMHO the adjustments going from white to black are less noticeable on 4.0.3
As far as the dimming, you have Auto Brightness on. Go to settings, screen and set the brightness to something else.
Sent from my Galaxy Nexus using xda premium
Is_907 said:
You might try turning of Auto Brightness and set it somewhere you feel comfortable... I just decided when I got this phone that I'd make myself get used to the adjustments and it's worked out well.
Click to expand...
Click to collapse
GinoSylum said:
As far as the dimming, you have Auto Brightness on. Go to settings, screen and set the brightness to something else.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I take it you missed the part where the op said his brightness is set on manual?
samsung drivers
for the drivers use this post
http://forum.xda-developers.com/showthread.php?p=20311264
PDAnet installs the drivers for you nice and easy, then you can remove from your phone and pc and the drivers will stay behind.
at this time there is no way to disable the screen dimming function. samsung's other phones have this feature as well, with an option to disable it in settings. its a power saving feature. for whatever reason google did not give any option to turn this on or off. so for now we have to wait if maybe a ROM can disable it.
For OSX you need to download Android file transfer for it to be seen.
Sent from my Galaxy Nexus using xda premium
Thank you everyone ...Sorry for the attitude earlier.
It seems like I got one of the GNexus phones which have a really good screen (The colors are just mind blowing), its only the dimming thing which is getting in the way. Also, I've tried to update to 4.0.3 and checked out the developer's section of the GNexus forum, but the steps are kind of overwhelming and I'm having my final exams at university right now, so I'll have to wait for a week to just sit back and read everything slowly and correctly.
One more thing, is there a download link to the official 4.0.3 mod ? It seems like everyone here prefers modded images one way or another.
lol. the dimming you are referring to is probably from current draw or a trait inherent to amoled. some people have mentioned they notice "dimming" like on white background browser and you pop up your keyboard. the white will get dimmer or yellower, or black more grayish. this is what you're talking about?
pukemon said:
lol. the dimming you are referring to is probably from current draw or a trait inherent to amoled. some people have mentioned they notice "dimming" like on white background browser and you pop up your keyboard. the white will get dimmer or yellower, or black more grayish. this is what you're talking about?
Click to expand...
Click to collapse
Its the opposite. When you draw the keyboard out, the whites get brighter and stronger. I don't have yellowing on my phone (thank god), but I do have dimming.
top make it simple:
The more the blacks = The brighter/stronger the whites.
Clearly a voltage issue for power consumption's sake. As the phone physically switches of diodes to achieve true blacks, more energy flows to lit diodes and they in turn become brighter.
Isn't there some sort of tweak deep enough to give full power to all diodes at all times regardless of what's on the screen (Full power even if the entire screen is white) ?
Firstly, welcome to Android. Once you get used to it you'll love it. I gave the same problem Windows 7 sometimes usually large video files and need to say that the adb drivers are not required to transfer files to the phone - I don't have them installed and I can still transfer data.
I have to say this is my first amoled device and I haven't noticed any dimming unless I have auto brightness on of course which I understand you don't.
Sent from my Galaxy Nexus using XDA App
BLL00 said:
Its the opposite. When you draw the keyboard out, the whites get brighter and stronger. I don't have yellowing on my phone (thank god), but I do have dimming.
top make it simple:
The more the blacks = The brighter/stronger the whites.
Clearly a voltage issue for power consumption's sake. As the phone physically switches of diodes to achieve true blacks, more energy flows to lit diodes and they in turn become brighter.
Isn't there some sort of tweak deep enough to give full power to all diodes at all times regardless of what's on the screen (Full power even if the entire screen is white) ?
Click to expand...
Click to collapse
ah yes. you're correct. i had it backwards.
I have the same issue with transferring large amounts of data using Windows 7. Looking for a fix too.
Investing the time to learn how to setup the SDK and using ADB will be well worth it.
BLL00 said:
Its the opposite. When you draw the keyboard out, the whites get brighter and stronger. I don't have yellowing on my phone (thank god), but I do have dimming.
top make it simple:
The more the blacks = The brighter/stronger the whites.
Clearly a voltage issue for power consumption's sake. As the phone physically switches of diodes to achieve true blacks, more energy flows to lit diodes and they in turn become brighter.
Isn't there some sort of tweak deep enough to give full power to all diodes at all times regardless of what's on the screen (Full power even if the entire screen is white) ?
Click to expand...
Click to collapse
Out of the three results I found searching for this topic, I'm glad I checked this thread.
The exact thing I was wondering was:
Is there any way to disable the screen from getting brighter when my keyboard comes up on the screen?
From reading your response, it seems that the screen getting brighter is a result of the design of the screen, suggesting that there is no way to stop it from happening. The only thing I've been able to do to make the screen remain at the brightness I set it is to change the theme of my keyboard to a brighter or lighter color based theme.
I'm using Swiftkey with the Neon keyboard, it looks great and I love it!
I had a Samsung Vibrant previously to the Galaxy Nexus, and there indeed was a "Power Saving Option" in the settings and if I remember correctly that stopped the screen from getting brighter with the keyboard on screen. Has any fix / ability to change this on a stock Galaxy Nexus running JB been found? It's just barely annoying enough for me to notice it, plus I'm a stickler for more battery life and I can feel my battery dying the brighter the screen gets. ( I know this last part may be a mental thing, but still. Haha. )
Just received my second One X from amazon UK (first was sent back due to charging issues).
Been getting some weird things with the screen on this one, which I haven't heard of in the other threads. I have a fair amount of pixels on the screen that will flicker white on certain screens, particularly on the pull-down notification. The pixels seem to be roughly distributed along two vertical lines on the screen, and there's about 20-30, although it's hard to tell since they never flicker all at once. The white pixels don't show up in screenshots, so I don't think it's a software issue, although it's possible, I suppose.
They never show up on solid colors as far as i can make out, but i get them on the camera preview and in the notification drawer (seems to be that shade of grey combined with the fine texture that sets it off). Very occasionally I get it on the bubbles live wallpaper. I also get it when viewing screenshots of the notification pulldown, so it seems to be the colour/texture, not the actual window being drawn.
I can't tell if this is a software or hardware issue.. I've done a few reboots and a factory reset, which did absolutely nothing. It's always the same pixels, which suggests hardware to me, but then it's oddly specific circumstances that set it off.
Any ideas/anyone else getting similar issues?
Edit: re-reading your post it may not be what I thought. Info below for the "usual" screen flicker issue.
It's a well known issue that pretty much everyone has. The backlight flickers slightly due to a voltage drain when the CPU is busy, causing whites and greys to turn a slightly warmer "colour" for a moment.
It's fixed in the 1.29.11 (not 1.29.7) update which just rolled out in Europe and should follow in the UK in about 2 weeks. It takes up to 2 more weeks after the update for it to monitor the voltage of your individual screen and learn to compensate so the flicker goes away.
Yeah, it's not the backlight, it's literally single pixels flickering from their correct colour to white.
So I've been through the standard factory reset crap with customer service, and they're recommending I sent it in for repair. Has anyone had any luck with the repair centre (I'm in the UK)?
Not sure if it's even worth sending it back since I'm still not sure if it's a hardware or software issue. If it's a software issue, will they fix it, or will they just turn it back and go "nope, couldn't find anything"?
I have EXACTLY the same issue, but with two pixels only, I'm almost convinced it's a hardware fault because I'm on a custom rom and it's still there, I got mine without a warranty though so I'll have to deal with it, any suggestions other than acceptance?
I have same issue, i change the rom and now its fine. it was almost on 3 or 4 roms, and finally its disappear
kami2k said:
I have same issue, i change the rom and now its fine. it was almost on 3 or 4 roms, and finally its disappear
Click to expand...
Click to collapse
Well thank you that's rather comforting to know, fingers crossed
Has anyone else experienced bad screen burn-in / image retention issues with their Note 2?
I've only had the phone just over 90 days, but I've already got some pretty severe burn-in. I use an app for equities trading several hours every day and after a few months of use, the icons and other parts of the app that remain static are plainly visible at all times on any screen that isn't completely black.
For now to slow it down I've re-themed the app and replaced as many static elements as I could with transparent .PNG files and no text.
Any idea if Samsung will replace the display under warranty for these types of issues? (From what I've been able to find, it sounds like they refused to cover it for the S3, then reversed their position and began covering it for some folks - curious what their policy is now)
Here's an example screenshot - this is a blank white screen. It's MUCH more noticeable in person.
Although I havent had it in my note 2 yet, my galaxy s2 had it. I went in to sprint and they swapped it for me because I had insurance. Didnt pay anything. Goodluck though.
Sent from my SPH-L900 using Tapatalk 2
I had it bad on my S2. The notification bar and active apps icons were visible on all white and blue screens and so was my keyboard. Sprint sent me home said they don't see that as an issue and the phone works fine so as long as it worked they don't care. Samsung on the other had took down notes then asked me to ship it to them. Never got to send though because the lady refused to be without a phone. As of now my Note 2 has been burning in the notification bar again after about a month of use. I think that's why they made the S4 notification bar the same as whatever ur background is.
Sent from my PG86100 using xda app-developers app
Because the damage cannot be reversed, try inverting your screen colors to see if you can get the other pixels to burn in and equalize. I did about 5 minutes of Google research and saw that the blue pixels burn out the fastest, so trying a negative color should burn the rest of them. Inverting colors can be found in Settings --> Accessibility or (in CM10.1) Settings --> Advanced (under device) --> Screen (tab).
smmiller506 said:
Because the damage cannot be reversed, try inverting your screen colors to see if you can get the other pixels to burn in and equalize.
Click to expand...
Click to collapse
Thanks for the suggestion..
I'm giving that a try, but I imagine it'll be hard to even out ~3 months worth of 4-6+ hour a day usage..
PoorHomey said:
Thanks for the suggestion..
I'm giving that a try, but I imagine it'll be hard to even out ~3 months worth of 4-6+ hour a day usage..
Click to expand...
Click to collapse
Probably, but it is a fix. Your only other option is to let it continue burning out the pixels as before, without inverting the colors, in the hope that you may be able to RMA/warranty the thing. I guess AMOLED screens are known to have this issue. Call up Sprint or Samsung and see what they will do if the problem gets worse.
smmiller506 said:
Probably, but it is a fix. Your only other option is to let it continue burning out the pixels as before, without inverting the colors, in the hope that you may be able to RMA/warranty the thing. I guess AMOLED screens are known to have this issue. Call up Sprint or Samsung and see what they will do if the problem gets worse.
Click to expand...
Click to collapse
All monitors will do it, given enough time.
Sent from my SPH-L900 using Tapatalk 4 Beta
Skripka said:
All monitors will do it, given enough time.
Click to expand...
Click to collapse
Apparently for Samsung's Amoled displays, "enough time" equals ~90 days of several hour a day usage.
I was aware that the display could suffer from burn-in/image retention, but I had no idea it would happen this badly and this quickly.
Hello everyone.
First of all I'd like to state that I'm a massive noob on this forum, so if I'm being stupid for not finding a thread about this subject yet, please refer me to it. My apologies.
I've recently bought my LG G3 like 2 months ago. Now, I'm the type of person that likes perfection, so I've already tweaked my phone to the max (without 'hacking' into the system though), for as far as I'm concerned.
I was wondering if any of you know an app or trick to always show a digital clock on the screen, even when it's locked (untouched). I've read on forums that a lot of people complain about battery draining owing to the latter. Though I'm searching for just a tiny, dimmed clock on top of my screen so I can always look up the time without even tapping the screen. My logics tell me that those few pixels used will never really benefit to massive battery draining, and even if it would, I'm still curious whether it's possible yes or no.
I've tried the NoLED app. But like most apps, this is just another Daydream tweaker, which obviously is not what I'm looking for.
So in conclusion, I'm looking for a tiny little clock destined for the top of my screen, always visible, dimmed (to save battery life), not in the way Daydream does (since this leaves the entire screen on [draining more battery life than my idea IMO]).
Anyone know a trick, app or tweak to achieve this?
Thanks in advance!!
Jurjen
With the LCD screen on the G3 (and most other phones), you can't really do what you want. Whenever the screen is on, the backlight is turned on for the entire screen. So even if the clock only takes a tiny bit of screen, the backlight will use the same amount of power as if the clock took the whole screen.
Only OLED screens, as used on Samsung, Moto, and the Nexus 6 allow the device to light only specific pixels.