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.
Sunday November 17, 2024 5:18 am PST by Joe Rossignol
Apple released the AirTag in April 2021, so it is now three over and a half years old. While the AirTag has not received any hardware updates since then, a new version of the item tracking accessory is rumored to be in development.
Below, we recap rumors about a second-generation AirTag.
Timing
Apple is aiming to release a new AirTag in mid-2025, according to Bloomberg's Mark Gurman....
Sunday November 17, 2024 3:03 pm PST by Joe Rossignol
While the Logitech MX Master 3 is a terrific mouse for the Mac, reports claiming that Apple CEO Tim Cook prefers that mouse over the Magic Mouse are false.
The Wall Street Journal last month published an interview with Cook, in which he said he uses every Apple product every day. Soon after, The Verge's Wes Davis attempted to replicate using every Apple product in a single day. During that...
Wednesday November 13, 2024 2:09 am PST by Tim Hardwick
Apple is set to release iOS 18.2 next month, bringing the second round of Apple Intelligence features to iPhone 15 Pro and iPhone 16 models. This update brings several major advancements to Apple's AI integration, including completely new image generation tools and a range of Visual Intelligence-based enhancements. There are a handful of new non-AI related feature controls incoming as well....
Saturday November 16, 2024 9:45 am PST by Joe Rossignol
Earlier this month, we reported about some iPhone users temporarily losing all of their notes in the Notes app after accepting Apple's updated iCloud terms and conditions. Apple has now indirectly acknowledged this issue in a new support document that outlines steps to follow if your iCloud notes are not appearing on your iPhone, iPad, or Vision Pro.
Fortunately, the notes can be re-synced...
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.
