The iOS 17.1 update that Apple is set to release in the near future addresses an issue that "may cause display image persistence," according to Apple's feature notes for the software.
Since the launch of the iPhone 15 models, there have been sporadic reports of severe screen burn-in impacting the new devices. There was speculation that it might be a hardware issue with the OLED display, but based on the iOS 17.1 update, Apple has found and addressed a software problem that mimicked screen burn-in.
Image via MacRumors reader Josh
While most of the reports of display problems were coming from iPhone 15 users, there were also some users with iPhone 13 Pro and iPhone 12 Pro devices that saw similar issues, which is likely why Apple's release notes do not mention the iPhone 15 specifically.
Those who have noticed "burn-in" on their iPhones should update to iOS 17.1 to ensure that it solves the problem.
The iOS 17.1 update also addresses a number of other bugs. It fixes an issue that could cause the Significant Location privacy setting to reset when transferring or pairing an Apple Watch for the first time, plus it addresses a bug that could cause custom and purchased ringtones not to appear as options for a text tone.
There is a fix for an issue that could cause the iPhone keyboard to be less responsive, and Apple says that it has added crash detection optimizations for the iPhone 14 and iPhone 15 models to further refine how the iPhones respond when a vehicle crash event is detected.
Thursday February 5, 2026 12:54 pm PST by Joe Rossignol
Apple turns 50 this year, and its CEO Tim Cook has promised to celebrate the milestone. The big day falls on April 1, 2026.
"I've been unusually reflective lately about Apple because we have been working on what do we do to mark this moment," Cook told employees today, according to Bloomberg's Mark Gurman. "When you really stop and pause and think about the last 50 years, it makes your heart ...
Thursday February 5, 2026 12:22 pm PST by Joe Rossignol
Apple plans to announce the iPhone 17e on Thursday, February 19, according to Macwelt, the German equivalent of Macworld.
The report, citing industry sources, is available in English on Macworld.
Apple announced the iPhone 16e on Wednesday, February 19 last year, so the iPhone 17e would be unveiled exactly one year later if this rumor is accurate. It is quite uncommon for Apple to unveil...
Friday February 6, 2026 3:06 pm PST by Juli Clover
In the iOS 26.4 update that's coming this spring, Apple will introduce a new version of Siri that's going to overhaul how we interact with the personal assistant and what it's able to do.
The iOS 26.4 version of Siri won't work like ChatGPT or Claude, but it will rely on large language models (LLMs) and has been updated from the ground up.
Upgraded Architecture
The next-generation...
Tuesday February 3, 2026 7:47 am PST by Joe Rossignol
While the iOS 26.3 Release Candidate is now available ahead of a public release, the first iOS 26.4 beta is likely still at least a week away. Following beta testing, iOS 26.4 will likely be released to the general public in March or April.
Below, we have recapped known or rumored iOS 26.3 and iOS 26.4 features so far.
iOS 26.3
iPhone to Android Transfer Tool
iOS 26.3 makes it easier...
The iPhone 18 Pro Max will feature a bigger battery for continued best-in-class battery life, according to a known Weibo leaker.
Citing supply chain information, the Weibo user known as "Digital Chat Station" said that the iPhone 18 Pro Max will have a battery capacity of 5,100 to 5,200 mAh. Combined with the efficiency improvements of the A20 Pro chip, made with TSMC's 2nm process, the...
Weird, I was assured by so many on these forums that this was an existential problem for Apple that would prompt a massive global recall and be the end of the company.
you can't fix "burn in" with a software update lmao. it's obviously an issue with the graphics processor (if it's really been fixed).
It could very well be a software bug that is not related to the graphics processor. Modern OLED displays utilize software algorithms to mitigate screen burn by essentially keeping track of how long individual sub-pixels are lit, and at what intensity. This allows them to adjust nearby pixel luminance to account for the degradation that the pixels have encountered from normal use, and continue to produce a clean image on a display that would otherwise have screen burn. My guess is that there was a bug in the display driver firmware that caused these algorithms to overcompensate for the amount of usage that these screens were seeing, essentially causing it to over adjust the luminance of certain pixels resulting in what looked like real screen burn when these compensation values were utilized by the display driver.
