Hacker News Reader

Comment by dodslaser | Hacker News Reader

Probably, but not necessarily. Could also be a code change that works perfectly fine for the OEM part, but not the third-party one.

Manufacturers can't realistically be expected to guarantee a device will keep working as normal with third-party parts.

View on HN

Sure, but having the screen stop working because of an unforeseen coincidence is very different from intentionally breaking the screen with malicious intention. Besides, has there been a single documented case in the history of smartphones where a device manufacturer changed the communication protocol with a display via OTA update after the phone shipped?

I can think of a myriad of things such as enabling a feature that was previously disabled/in development, updates to calibration values/curves, tweaking timing and power saving control registers, etc.

Any of these could throw off a third party part if not implemented exactly the same way.

Sure, but we also know for a fact that Apple does a lot of tweaking to disable non-genuine parts. Seems as likely.

Surely Apple maliciously went after some tiny third party that sells 3 screens per year.

Occam’s razor..

Apple, that rules their supply chain with an Iron fist and prosecute owners of independant repair shops?

Why would they ever have a plan to make sure only their screen works with their phone?

Apple has had internal memos leaked in the past where incompatibilities were specifically engineered in macOS with plausible deniability, so I wouldn't be so quick to give a benefit of doubt.

Reply on news.ycombinator.com