What exactly happened/happens with the display calibration data on iOS 13?

iOS 13.1.2 metions this line on the changelog

Fixes a bug that could result in a loss of display calibration data
  1. What exactly happens if the "display calibration data" was already lost prior to the bug fix on iOS 13.1.2?
  2. Does iOS 13.1.2 restore the lost data?
  3. If not, how can we tell if our display calibration data is lost or not?



iPhone X

Posted on Oct 2, 2019 7:43 AM

Reply
16 replies

Oct 2, 2019 7:51 AM in response to Dark_Nate

It is system data that has to be available in order for you your screen to calibrate brightness, contrast, changes in background etc. It is solely used by the screen itself, it is not transferred from your iPhone and for anyone to retrieve it they would have to know how to dump the logs and then know how to read them and know the state of your environment when they changed. Notice it said "could".

Oct 2, 2019 7:55 AM in response to deggie

deggie wrote:

It is system data that has to be available in order for you your screen to calibrate brightness, contrast, changes in background etc. It is solely used by the screen itself, it is not transferred from your iPhone and for anyone to retrieve it they would have to know how to dump the logs and then know how to read them and know the state of your environment when they changed. Notice it said "could".

Hi, I understand it's system data for colour accuracy, also called ICC/ICM files on Windows, macOS, Linux etc. I work in image processing for colour sensitive photography.


My concern is the potential loss of colour accuracy. And the bug fix mentioned it "could" delete the display calibration data.


If it was lost, how can we know for sure? If it was confirmed to be deleted, how could we get it back?

Oct 2, 2019 8:05 AM in response to deggie

deggie wrote:
If this is a problem to you make a Genius Bar appointment

The nearest AASP is 100+ KM away from me.

I don't believe the data you are referring to you (which is burned into the graphics IC and screen) is what this bug is about.

Can we get some kind of confirmation on this? What exactly was this bug about? Is it possible it somehow altered data inside the IC which I'm assuming to be highly unlikely since that's a ROM.

Oct 2, 2019 8:18 AM in response to Dark_Nate

This is a user-to-user technical support site. I would suggest you call AppleCare and immediately asked to be transferred to a Tier 2 support person. Apple is extremely secretive so be ready for them to not give you certain information. They will not give you more details about what the bug was about so you can skip that question.

Oct 3, 2019 6:02 AM in response to deggie

deggie wrote:

This is a user-to-user technical support site. I would suggest you call AppleCare and immediately asked to be transferred to a Tier 2 support person. Apple is extremely secretive so be ready for them to not give you certain information. They will not give you more details about what the bug was about so you can skip that question.

I did start this case with AppleCare, they told me that genereally when data is lost, it's gone for good. But the advisor was unable to confirm regarding the state of the display calibration data, wether the bug simply deleted it from memory (RAM) temporarily or wether it wiped the data clean from its storage source. He was unable to confirm if the display calibration data for every panel was actually stored on Apple's servers, which I find unlikely.


He suggested me to start a thread on discussions.apple.com and see if I could get extra information here.

Oct 15, 2019 11:20 AM in response to Dark_Nate

THIS is exactly what we need to find out; perhaps the best way to frame the question to them would be to ask if the calibration they’re talking about refers to the (auto-)brightness/True Tone/Night Mode/etc settings. If so, we should be safe, since we could infer that it’s a problem reading/writing a .plist file kept in user-space storage. If not, then that COULD be problematic, since it’d mean it’s potentially lost data that’s on the display’s flash-ROM, or at the very least, data stored inside /dev/, or some other user-inaccessible space.


If it’s the latter, what I’m hoping is that iOS <13.1.2 is simply UNABLE to read the display’s calibration ROM, and by updating the OS, it fixes this inability and then it’s able to resume reading its previous calibration data.

Oct 18, 2019 12:56 PM in response to Dark_Nate

Essentially, if they see enough issues coming back in the logs returned to them by the millions of devices out there, THEN they take action...so, we basically need more people opting-in/not opting-out from "returning system and crash logs to Apple". The logs don't contain ANYTHING that could identify you or what you were doing, any more than those engine diagnostics on your car could tell your mechanic who's houses you've been driving to and what music you were listening to while you were driving there...


EDIT: Let me be clear, even that is a LONG shot on getting them to respond to ANYTHING, and no matter what, don't expect it to be quick...this is more of a general statement than advice on how to get them to respond to the screen calibration issue...

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

What exactly happened/happens with the display calibration data on iOS 13?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.