The calibration measures only when the screen is open and closed. There is a grace period of a few seconds to allow you to close the screen.

But yes, if you don’t do it correctly, you will burn the service part and have to replace it again.

▲

theginger 6 days ago | parent [-]

That seems an extreme measure to ensure the security/integrity of a screen hinge sensor input ( or protect this tiny revenue stream )

▲

arcticbull 6 days ago | parent [-]

It does actually perform a security function. The lid angle sensor is used to know when the device is open or closed, and when closed, it physically disconnects the microphone. If you were to be able to recalibrate it at any time, you would leave your device vulnerable to having the microphone enabled when the lid is closed. You can argue whether that justifies the practice, but it's not as simple as just burning the EEPROM serial number in that tells it to turn the display on or off. It defends the user against an attack vector.

From that perspective making it one-time programmable is not unreasonable.

▲

KurSix 6 days ago | parent | next [-]

It feels like Apple's implementation leans more toward vendor lock-in than purely user protection

▲

raverbashing 6 days ago | parent | prev | next [-]

I agree with you

Though it could be simpler if it was something like a magnet on the lid that activates a magnetic switch on the bottom part (and it would be harder to have a false negative result). But Apple is going to Apple

	▲	arcticbull 6 days ago \| parent [-]
		Yes, it could be done with a Hall effect sensor or something like they used to. The cool thing about this approach is they actually use a different angle to turn the screen off as you close the lid than they do for turning it on when you open the lid, to create a better experience. Since it is a security feature, then the "open" vs "closed" state should use the same source of truth. So it's a trade-off of complexity and experience.

▲

hnaccount_rng 6 days ago | parent | prev [-]

It should also be relevant for triggering the "closed let's lock the device" event, right?