Latest iOS Update Shows Apple Can Use Software To Break Phones Repaired By Independent Shops (vice.com)
The latest version of iOS fixes several bugs, including one that caused a loss of touch functionality on a small subset of phones that had been repaired with certain third-party screens and had been updated to iOS 11. "Addresses an issue where touch input was unresponsive on some iPhone 6S displays because they were not serviced with genuine Apple parts," the update reads. "Note: Non-genuine replacement displays may have compromised visual quality and may fail to work correctly. Apple-certified screen repairs are performed by trusted experts who use genuine Apple parts. See support.apple.com for more information." Jason Koebler writes via Motherboard: "This is a reminder that Apple seems to have the ability to push out software updates that can kill hardware and replacement parts it did not sell iPhone customers itself, and that it can fix those same issues remotely." From the report: So let's consider what actually happened here. iPhones that had been repaired and were in perfect working order suddenly stopped working after Apple updated its software. Apple was then able to fix the problem remotely. Apple then put out a warning blaming the parts that were used to do the repair. Poof -- phone doesn't work. Poof -- phone works again. In this case, not all phones that used third party parts were affected, and there's no reason to think that, in this case, Apple broke these particular phones on purpose. But there is currently nothing stopping the company from using software to control unauthorized repair: For instance, you cannot replace the home button on an iPhone 7 without Apple's proprietary "Horizon Machine" that re-syncs a new home button with the repaired phone. This software update is concerning because it not only undermines the reputation of independent repair among Apple customers, but because it shows that phones that don't use "genuine" parts could potentially one day be bricked remotely.
Here's what you say:
Agree totally -- this is Apple going out of their way to fix something that is totally not their problem.
Here's what the summary says:
So let's consider what actually happened here. iPhones that had been repaired and were in perfect working order suddenly stopped working after Apple updated its software.
I can't explain why you think Apple is the hero here, but it has nothing to do with reality.
lucm, indeed.
A sensor that outputs a PWM signal, or something that accepts it (such as a servo) has a specified allowable range and curve that it COULD use, and an actual range that it DOES use.
Servo controllers nominally output pulses between 1ms (zero position) and 2ms (full rotation). Actual servo models don't exactly conform to this "standard", so you tune your control to the specific model of servo.
Analogously, the DMX protocol standard says that the BREAK is signaled by a pulse of AT LEAST 88 microseconds (and up to one second). Many controllers fail to read the spec carefully try to output exactly 88 microseconds, sometimes falling a bit short. If you program your DMX to work according to the standard, and test it with truly conforming peers, it'll fail to work with the many DMX items that don't quite conform, or are borderline, sometimes falling a couple microseconds short. To have compatibility with "almost compliant" neighbors, DMX outputs can output a 92 microsecond break, and receivers can accept a 84 microsecond break.
I suspect that's what happened here. The third-party parts ALMOST matched the Apple parts. Maybe they were barely complaint to the spec while the Apple parts were well within spec, or maybe the third-party parts were almost compliant. Either way, they didn't work quite the same, so customers saw failures. Apple adjusted it to work within the parameters of the third-party parts.
I highly suspect if you tested MAF sensor or O2 sensor speced with an output range of "up to 0-5V", you'd find some model's actual range is 0.2-4.5V, while another model's actual range might be 0.3-4.7V. Firmware tuned for the first, the OEM model, wouldn't work quite work as well with the second one - even though they both have "0-5V output".
This is not a subtle difference, it's called fanboism.
How is Apple supposed to prevent issues like this happing with third party replacement parts? It's not realistic for them to somehow find out about all such parts being produced, acquire samples themselves, and then test their software updates against them. If repairers are not advising customers that they're using non-Apple parts then the fault is with the repairers, otherwise the fault is with the customers.
The only way I could see it being Apple's fault would be if they intentionally, maliciously released an update to fail with third-party parts. Nobody outside of Apple can be sure about whether they did that or not so it just degenerates into an argument between the haters and the fanbois. If "Error 53" was Apple malice, later thought better of, why would they try again with this latest issue?