Unable to do full calibration on MBP M2

For the first time ever I managed to pass the Full Calibration on my MBP 16" M1 Max, like legit I was using Calibrite Display Plus HL, back then around March I gave up because it failed over and over again, now after several macOS update (Tahoe 26.5.2) I tried it once for the meme, it failed twice saying "Make sure the room is dark and the temperature is not too high or low", but after that it passed as above.

So the allegation that a YouTuber said that the Tahoe 26.4.1 was buggy with the Full Calibration is therefore not true anymore, or at least on my case it is fixed with the 26.5.2

[Edited by Moderator]

I did four successful calibration runs today, one on my M1 Ultra Mac Studio and Studio Display XDR, and three on my M1 Max MacBook Pro 16. Both were running macOS Tahoe 26.5.2. Two used the default display preset and two used the HDTV BT.709-BT.1886 preset. One default display preset had True Tone and auto-brightness enabled, and one had it disabled. However they all completed.

I think some (maybe most) of the failures are due to the somewhat fragile nature of the Pro Display Calibrator program, coupled with UI behavior that makes it appear to hang (but it is not). It will sit for long periods with a black screen, and there is no progress info, not even "progress dots."

I believe Apple's own documentation states that "Logging out, switching to another user, changing resolution or mirroring, or letting your Mac go to sleep will cause the calibration process to fail."

Users seeing a black screen and no response for long periods will naturally press keys to try and "wake it up." It's possible that may destabilize it. It's also possible that any sleep, or display timeout or energy-saving power off might crash it. I'm examining all these areas.

I've now done a total of five full calibrations on my M1 Max MacBook Pro 16, macOS Tahoe 26.5.2. I've used both the default XDR P3-1600 nit preset and the HDTV BT.709-BT.1886 preset. It ran OK each time.

The only failure I saw was on July 1, and study of the logs showed an uncaught USB device error. The only USB device in use was the Calibrite probe itself.

Therefore, I've made several attempts to induce several USB connect/disconnect events at the same point in the calibration cycle, so far w/o success. If the sixth consecutive full calibration doesn't fail (despite being provoked with USB events), I'll do another attempt with 'sudo pmset -a disablesleep 0', which re-enables sleep functions, to be controlled by user-configured System Settings. I had sleep disabled (per Apple's recommendations for Pro Calibration) but I need to test the typical user case, where they would probably have sleep functions enabled.

The calibration goes through several phases, as listed below. The July 1 crash I observed happened during phase 5.

Phase 1: Setup (~2 min): DCP (Display Co-Processor) UserCalibration commands put the panel under direct calibrator control, bypassing normal color management; factory data loads.

Phase 2: Warmup (~30 min from cold): holds a fixed pattern while panel temperature climbs ~26 to 30 °C; measurements are only valid at thermal steady state.

Phase 3: Gamma (~6 min): steps through a tone ramp, probe-measures each patch, builds per-channel transfer-function corrections.

Phase 4: Primaries (~1.5 min): measures R/G/B/white chromaticities, computes the color-correction matrix.

Phase 5: Validation + auto-fine-tune (~35 min): validation measurements and checks (white point/luminance, RGB at max backlight, primaries, gamma; delta-E computed internally), then ProCalibrator's autoFineTuneInternalInside applies candidate corrections and enters the ~30-minute stabilization/cooldown wait. The panel then settles from the max-backlight thermal excursion while the app polls stability at geometrically growing intervals. It ends with fresh measurements to verify the settled result.

Phase 6: Commit (~4 min): The profile/table is writen via DCP (Display Co-Processor) toolbox command 0x1010005, Apply Table, and returns to the normal pipeline.

Thanks. I spent lots of time getting debug and logging scripts ready in case I can make it fail. I just finished a successful calibration run (IOW it did not fail) on my M1 Ultra Mac Studio, macOS 26.5.2, 27-inch Studio Display XDR. I had the System Settings > Displays > Preset HDTV BT.709-BT.1886 selected. I can try others in case that is a factor, but it takes an hour per attempt.

Can you tell me more info about your config when it failed? Machine type, monitor version and macOS version. What reference preset did you use? Is there any chance you typed any keys while it was running?

Have you tried this again? Does it fail each time?

In System Settings > Lock Screen, what was your setting for "Turn display off when inactive?"

In System Settings > Energy, did you have "Prevent automatic sleeping when the display is off" enabled or disabled?

suits1346 wrote:

Has anyone been able to do a full calibration using Calibrite Display Plus HL on a MacBook Pro M2 with MacOS 26.5?

hmmm...

Have you searched the developers website or contact their: Support/Help/FAQ/Known issues/compatibility/updates

ref: https://calibrite.com/us/calibrite-technical-support-home/

UserCalibration_ReadEAN failed: 0xE00002F0

Calibration toolbox command 0x1010005 failed reason 0xe00002f0

Calibration failed to query calibrated backlight scaling factor from IOMFB

It crashed on my M1 Max MacBook Pro 16 on macOS Tahoe 26.5.2 when running calibration with the Calibrite Display Plus HL. I've captured a lot of debug information (I'm a former developer) and am studying this. I also have an M1 Ultra Mac Studio and 27-inch Studio Display XDR monitor, so I'll be testing that next.

Today a friend of mine successfully ran full calibration on an M4 Mac Mini, macOS 26.5.1, Calibrite Display Plus HL, Apple Studio Display. I'm concerned it is intermittent or non-deterministic. If it takes multiple 70-minute attempts to get a single failure, I need to have all my debugging and logging scripts configured in advance to catch this.

A further complication is the need for two-machine debugging. The failure on my M1 Max MBP16 essentially locked up the UI, so I had to connect via ssh. I wasn't prepared for that so only got a few things. I'm creating and testing in advance several scripts so I can do this from another machine and get good data on the first attempt.

I am facing the same issue. The Apple Display Pro Calibrator fails every time (and frequently crashes) when using the Calibrate Display Plus HL colorimeter in Tahoe 26.5.1 to do a full display calibration on either my MacBook M2 Pro or the Apple Studio XDR display.

Does anyone know if it is even possible to create a support ticket? It seems impossible to know whether Apple developers are aware of the issue and working on a resolution.

Codex tells me it is because of “UserCalibration_ReadEAN failed 和 IOMFB” . 26.5.2