mittense

Q: MacBook Pro Retina display burn-in?

I first noticed this after my MBP [Retina] had gone to sleep, but: when returning to the login screen (since I have it set to require a password whenever the computer is idle long enough) I noticed what appeared to a very faint ghosting primarily noticeable on darker backgrounds.

 

After messing around with it a bit, there seems to be a fairly consistent in-display ghosting that occurs without much time at all; I was able to leave my screen on (a little above half-brightness) for about 10-15 minutes and the ghosted "burn" would be of the screen I left it on (which I deliberately reconfigured so that everything would be a new position).

 

Has anyone else experienced this? Is this a normal thing that I just have to get used to? It's not really noticeable at all in standard use.

MacBook Pro (Retina, Mid 2012), Mac OS X (10.7.4)

Posted on Jun 16, 2012 10:30 PM

Close

Q: MacBook Pro Retina display burn-in?

  • All replies
  • Helpful answers

first Previous Page 560 of 642 last Next
  • by Kirk Eberle,

    Kirk Eberle Kirk Eberle Oct 25, 2013 5:58 AM in response to mittense
    Level 1 (35 points)
    Oct 25, 2013 5:58 AM in response to mittense

    I've been waiting quite impatiently for a retina MBP since the first release. Finally decided to dive in, and before I could buy one, stumbled upon this thread. Y'all gave me jitters!

     

    Seeing as I could always take the machine back if I had issues, I decided to get the new, stock $2600 15" MBP w/retina.

     

    I had a long day of reinstalling apps and grinding over of all my files (I decided I'd start from a clean install instead of doing the Mac to Mac transfer).

     

    Clearly, with all that transfering going on, the screen would have been exposed to a chance of image retention. As hard as I look, (on solid gray, solid white), I do NOT have ANY symptoms of image retention...nor the yellow-ish gradient people are bringing up. I have to say it, it's the most gorgeous display I've EVER seen!

     

    I see some folks demanding system breakdowns, I'm willing to post mine if those very requesters are willing to point me/link me as to how to do that satisfactorily (is that a word?).

     

    ---

     

    TL;DR I was scared by this thread before finally plunging into retina bliss; bought a rMBP anyway. After a long day of static screens due to software installations, I see ZERO symptoms of IR/yellowing/gradual discolorations on my new Haswell 15".

  • by Salman Khan84,

    Salman Khan84 Salman Khan84 Oct 25, 2013 6:15 AM in response to airikh
    Level 1 (0 points)
    Oct 25, 2013 6:15 AM in response to airikh

    I wanna ask you brother that the image retention you are talking about happned in which model of rmbp ??? the previous generation ones or the haswell ones..??

  • by Chris Yates1,

    Chris Yates1 Chris Yates1 Oct 25, 2013 6:23 AM in response to Salman Khan84
    Level 1 (35 points)
    Oct 25, 2013 6:23 AM in response to Salman Khan84

    It was the previous models (not Haswell....so far it would seem anyway) and the LG screens. The Samsung screens had yellowing.

     

    @Kirk - To find out which diaply you have use Spotlight and search Terminal (it will be the top hit) open Terminal and a window will appear copy and paste the following:

    ioreg -lw0 | grep "EDID" | sed "/[^<]*</s///" | xxd -p -r | strings -6

     

    And hit 'return', the first thing you'll see is Color LCD then immediately below that you'll see numbers and letters. If the letters start with LSN that means it's a Samsung display. The second line will look something like:

    LSN154YL01-A01

     


  • by vkin,

    vkin vkin Oct 25, 2013 6:32 AM in response to Chris Yates1
    Level 1 (0 points)
    Oct 25, 2013 6:32 AM in response to Chris Yates1

    Thanks for helping us out. Do you know if Image persistence is absent on new 13 inch macbook pro. I am a firsttime buyer of macbook so a bit cautious.

  • by Kirk Eberle,

    Kirk Eberle Kirk Eberle Oct 25, 2013 6:42 AM in response to Chris Yates1
    Level 1 (35 points)
    Oct 25, 2013 6:42 AM in response to Chris Yates1

    Thanks! (FYI for Anyone reading through this, I needed to install developer tools to make the above Terminal command work)

     

    Yup, it must be a Samsung:

    LSN154YL01-A01

    DLM33720124FF0PAK

    Color LCD


     

    I'm assuming that's good? Or will I be eating image retention crow in due time?

     

    (Had a Plasma TV in my time...know FULL WELL how annoying image retention can be. Thought I'd share that!)

  • by Salman Khan84,

    Salman Khan84 Salman Khan84 Oct 25, 2013 7:04 AM in response to Chris Yates1
    Level 1 (0 points)
    Oct 25, 2013 7:04 AM in response to Chris Yates1

    exactly this is what i thought ...lets c what mr.airikh has to say

  • by LifeReceiver,

    LifeReceiver LifeReceiver Oct 25, 2013 7:41 AM in response to Kirk Eberle
    Level 1 (20 points)
    Oct 25, 2013 7:41 AM in response to Kirk Eberle

    It would seem they're only putting Samsung's into the latest iteration, but in the case of lel62 the command isn't giving a result.  This could mean he has an LG, but the output is formatted differently.  What you can try is break the command apart to see what changed.  For example try this:

     

    ioreg -lw0 | grep "EDID"

     

    You should get an output like this:

     

       | | | |   | | |   "EDID" = <00ffffffffffff0006100fa00000000010150104a5211578026fb1a7554c9e250c505400000001 010101010101010101010101010101ef8340a0b0083470302036004bcf1000001a000000fc00436f 6c6f72204c43440a2020200000001000000000000000000000000000000000001000000000000000 0000000000000000e700000000000000000000000000000000000000000000000000000000000000 004c503135345754312d534a41320a200044434e333330313031335446445233414b0a2020202020 00000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000>

        | | | | | |   "FeatureControl" = {"GPUInterruptHandling"=1,"UseInterruptFilter"=1,"EDPDownSpreadDisable"=0,"Fast DisplayDetectDisable"=0,"SpreadON"=1,"PowerStates"=1,"IgnorePanelTimings"=0,"Gam maAdjustDisable"=0,"DisableDynamicFBC"=0,"RCxEIModeEnable"=1,"EnableDeepDisplay" =1,"MaximumSelfRefreshLevel"=3,"DPM"=1,"DeepRC6"=1,"CachedEDIDDisable"=0,"ASRDis able"=0,"Gamma"=1,"FBC"=1,"EnableConnectionState"=1,"RenderStandby"=1,"SetRC6Vol tage"=0,"UseProgrammedCoefficients"=0,"Watermarks"=1}

        | | | | |         "IODisplayEDID" = <00ffffffffffff0006100fa00000000010150104a5211578026fb1a7554c9e250c505400000001 010101010101010101010101010101ef8340a0b0083470302036004bcf1000001a000000fc00436f 6c6f72204c43440a2020200000001000000000000000000000000000000000001000000000000000 0000000000000000e7>

     

    Then you can take it a step further and try this:

     

    ioreg -lw0 | grep "EDID" | sed "/[^<]*</s///"

     

    Which should give you something like this:

     

    00ffffffffffff0006100fa00000000010150104a5211578026fb1a7554c9e250c50540000000101 0101010101010101010101010101ef8340a0b0083470302036004bcf1000001a000000fc00436f6c 6f72204c43440a202020000000100000000000000000000000000000000000100000000000000000 00000000000000e70000000000000000000000000000000000000000000000000000000000000000 4c503135345754312d534a41320a200044434e333330313031335446445233414b0a202020202000 00000000000000000000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000000>

        | | | | | |   "FeatureControl" = {"GPUInterruptHandling"=1,"UseInterruptFilter"=1,"EDPDownSpreadDisable"=0,"Fast DisplayDetectDisable"=0,"SpreadON"=1,"PowerStates"=1,"IgnorePanelTimings"=0,"Gam maAdjustDisable"=0,"DisableDynamicFBC"=0,"RCxEIModeEnable"=1,"EnableDeepDisplay" =1,"MaximumSelfRefreshLevel"=3,"DPM"=1,"DeepRC6"=1,"CachedEDIDDisable"=0,"ASRDis able"=0,"Gamma"=1,"FBC"=1,"EnableConnectionState"=1,"RenderStandby"=1,"SetRC6Vol tage"=0,"UseProgrammedCoefficients"=0,"Watermarks"=1}

    00ffffffffffff0006100fa00000000010150104a5211578026fb1a7554c9e250c50540000000101 0101010101010101010101010101ef8340a0b0083470302036004bcf1000001a000000fc00436f6c 6f72204c43440a202020000000100000000000000000000000000000000000100000000000000000 00000000000000e7>

     

    And finally you can try this:

     

    ioreg -lw0 | grep "EDID" | sed "/[^<]*</s///" | xxd -p -r

     

    Which will give you a more raw result:

     

    ????????!xo??UL?%

                     PT?@?4p0 6K??Color LCD

       ?LP154WT1-SJA2

    DCN3301013TFDR3AK

         ????????!xo??UL?%

                          PT?@?4p0 6K??Color LCD

     

    If they're only using Samsung I wonder what they'll be putting into the first gen rMBPs next year or the year after when we come back with IR problems.  I've still got 2 years of AppleCare, so if the IR does come back I wonder if they'll even have any LGs to give me.

  • by Colonel.Cool,

    Colonel.Cool Colonel.Cool Oct 25, 2013 8:15 AM in response to mittense
    Level 1 (0 points)
    Oct 25, 2013 8:15 AM in response to mittense

    Even if they are using mostly Samsung's screens in the 15", 13" users are still going to get IR as reported earlier in this theard as LG is the only supplier of 13" retina screen. Morality : If you want an IR Free Retina MBP, get a 15" or wait for Apple to change his screen technology next year probably (with IGZO screens).

  • by Chris Yates1,

    Chris Yates1 Chris Yates1 Oct 25, 2013 8:25 AM in response to LifeReceiver
    Level 1 (35 points)
    Oct 25, 2013 8:25 AM in response to LifeReceiver

    I'm not sure if it's me confused or others but from what I understand it's only LG that have the IR issues not the Samsung displays. The Samsung displays suffered with yellowing screens and gradients from left to right.

  • by vkin,

    vkin vkin Oct 25, 2013 9:11 AM in response to Colonel.Cool
    Level 1 (0 points)
    Oct 25, 2013 9:11 AM in response to Colonel.Cool

    Has anyone brought 13". I guess new IRIS Pro can handle 13" better than 15". the reason I want to buy 13" but am afraid of this burn in issue

  • by Chris Yates1,

    Chris Yates1 Chris Yates1 Oct 25, 2013 9:15 AM in response to vkin
    Level 1 (35 points)
    Oct 25, 2013 9:15 AM in response to vkin

    The 13" doesn't come with Iris Pro but Iris.

     

    At the moment it looks like all screens on the new ones are Samsung so IR shouldn't be an issue. You might be better of waiting a little while and keep checking the forums to see what people are saying.

  • by Canuck1970,

    Canuck1970 Canuck1970 Oct 25, 2013 9:21 AM in response to Kirk Eberle
    Level 1 (0 points)
    Oct 25, 2013 9:21 AM in response to Kirk Eberle

    Kirk Eberle wrote:

     

    Thanks! (FYI for Anyone reading through this, I needed to install developer tools to make the above Terminal command work)

     

    Yup, it must be a Samsung:

    LSN154YL01-A01

    DLM33720124FF0PAK

    Color LCD


     

    I'm assuming that's good? Or will I be eating image retention crow in due time?

     

    (Had a Plasma TV in my time...know FULL WELL how annoying image retention can be. Thought I'd share that!)

     

    It looks like you won the rMBP display lottery dude. Congratulations!

     

    Now, just pray that nothing breaks down on your machine and guard it with your life against damage and/or theft, because you might not be as lucky if you end up having to replace your machine or display panel.

     

    This is the reason why I'm still involved with this thread, because although my IR-laden LG display was replaced with a flawless Samsung like yours, there's a good chance I won't be as lucky next time...at least not until Apple cleans up their act and fixes this issue.

     

    To be honest though, after a year of speaking out about this, it's pretty disheartening to see the issue still present with a new release. That being said, Apple does buy all of the components required for the entire life of a product, up front, and the Haswell update on the 15-inch rMBPs is not that dramatic a change, so it's very likely that Apple is still pulling their displays from the same crummy spin-the-wheel-and-cross-your-fingers batch.

     

    In any case, unless Apple fixes their display problems, I will not be upgrading anytime soon and I will likely use my current machine for a long time.

  • by Colonel.Cool,

    Colonel.Cool Colonel.Cool Oct 25, 2013 9:26 AM in response to vkin
    Level 1 (0 points)
    Oct 25, 2013 9:26 AM in response to vkin

    Yes someone did and reported a few pages ago that the 13" are still suffering from IR. Sorry ...

  • by trgn,

    trgn trgn Oct 25, 2013 10:28 AM in response to LifeReceiver
    Level 1 (0 points)
    Oct 25, 2013 10:28 AM in response to LifeReceiver

    @LifeReceiver, lel62

     

    Same here, there's no information except for `Color LCD` with ioreg -lw0 | grep "EDID" | sed "/[^<]*</s///" | xxd -p -r | strings -6 on a 15" late 2013 base model.

     

    I tried your commands, LifeReceiver, and got this for the last one:

     

    ???????"??!xo??UL?%

                       PT?@?4p0 6K??Color LCD

       ?

     

     

    I don't find any evident retention or other quality issues – but this is my first day in front of a more decent screen.

    As there seem to be people getting Samsung display info from these searches I guess they sold something else to me.

  • by Kirk Eberle,

    Kirk Eberle Kirk Eberle Oct 25, 2013 10:36 AM in response to Canuck1970
    Level 1 (35 points)
    Oct 25, 2013 10:36 AM in response to Canuck1970

    Oh wow. Good to know!


    I never even knew this problem existed until yesterday, a few hours before I marched out to grab one. I'm INSANELY picky with my displays, and certainly would notice any yellow-ish dicolorations if there any to be seen. If it's said that I won the screen lottery, that's discouraging.

     

    Good luck people, just wanted to chuck my experience into the pile. Usually, it's a vocal minority spoiling things for everyone.

     

    You can trust I'll be back right here if my experience shifts from positive. It's only day 2 of owning this thing...

     

    *knocks on wood

first Previous Page 560 of 642 last Next