3 ms·
Your idea would indeed take a lot of power and probably suffer from precision issues. What GP was talking about was a set up where you would be able to take a
by olympus 9y ago
Your idea would indeed take a lot of power and probably suffer from precision issues. What GP was talking about was a set up where you would be able to take a picture of your phone's screen and then overlay a transparent inverse image to counteract the burn in. A single overlay would be child's play for the X's GPU, and you could put scanners in Apple stores. This would have the added benefit of getting customers back into the stores every few months.
- rlanday 9y agoWhy would Apple sell a phone that requires bringing it back to the Apple Store every months to correct a problem that no previous model of iPhone developed? This idea is completely nuts.
- etaioinshrdlu 9y agoIt is probably maintenance that only rarely/never has to be done, like changing a battery.
- deleted 9y ago[deleted]
- olympus 9y agoWhy would Apple put a screen with this issue on their most premium phone ever? They've acknowledged the problem, and I would like a way to fix it when it develops. I'll be cranky if their only offer is to replace the screen when it could be done cheaper (a high dpi scanner and image overlay).
- paulmd 9y agoWhy not track the cumulative amount of R, G, and B activation for each pixel and then model a predicted burn-in mask based on the actual usage?
- olympus 9y agoBecause of askvictor's point. Logging every single pixel value would suck down battery life equivalent to recording your screen every moment it is on. If you stored cumulative pixel activations in an array (like I would think of doing), you are going to overflow an integer value very quickly, or run into floating point issues. If you stored it as a video or in a DB, you are going to have weeks worth of video that need stored.
- tatersolid 9y agoSampling at a very small fraction of the number of pixels would suffice for long-term statistics. Say one pseudo-randomly chosen pixel per second. An exponential average would pretty much eliminate storage growth.
- deleted 9y ago[deleted]
- askvictor 9y agoThat might work. However, it would also have the effect of making the entire screen less bright. OLED burn-in is the opposite of CRT burn-in - pixels that have been used more than others shine less brightly. To compensate for that you'd need to drop the brightness of every pixel down to the worst affected pixels. Perhaps you could attempt to increase the power to 'burnt-in' pixels, but that would presumably only compound the problem and reduce their lifespan.