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.
Following nearly two years of rumors about a fourth-generation iPhone SE, The Information today reported that Apple suppliers are finally planning to begin ramping up mass production of the device in October of this year. If accurate, that timeframe would mean that the next iPhone SE would not be announced alongside the iPhone 16 series in September, as expected. Instead, the report...
Key details about the overall specifications of the iPhone 17 lineup have been shared by the leaker known as "Ice Universe," clarifying several important aspects of next year's devices. Reports in recent months have converged in agreement that Apple will discontinue the "Plus" iPhone model in 2025 while introducing an all-new iPhone 17 "Slim" model as an even more high-end option sitting...
Wednesday July 24, 2024 9:06 am PDT by Joe Rossignol
Apple supply chain analyst Ming-Chi Kuo today shared alleged specifications for a new ultra-thin iPhone 17 model rumored to launch next year. Kuo expects the device to be equipped with a 6.6-inch display with a current-size Dynamic Island, a standard A19 chip rather than an A19 Pro chip, a single rear camera, and an Apple-designed 5G chip. He also expects the device to have a...
Thursday July 25, 2024 5:43 am PDT by Tim Hardwick
Apple typically releases its new iPhone series around mid-September, which means we are about two months out from the launch of the iPhone 16. Like the iPhone 15 series, this year's lineup is expected to stick with four models – iPhone 16, iPhone 16 Plus, iPhone 16 Pro, and iPhone 16 Pro Max – although there are plenty of design differences and new features to take into account. To bring ...
Apple’s iCloud Private Relay service is down for some users, according to Apple’s System Status page. Apple says that the iCloud Private Relay service may be slow or unavailable. The outage started at 2:34 p.m. Eastern Time, but it does not appear to be affecting all iCloud users. Some impacted users are unable to browse the web without turning iCloud Private Relay off, while others are...
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.
