/article-new/2015/12/iPad-Pro-Cable-250x174.jpg?lossy)
Apple has confirmed that updating to iOS 9.2 should prevent an issue that caused some iPad Pros to become unresponsive after charging from continuing in the future.
Shortly after the launch of the iPad Pro, some early adopters began complaining about an issue that caused the 12.9-inch tablet to become unresponsive after charging, requiring a hard restart to restore functionality.
Apple acknowledged the problem in a support document on its website, stating that it was "investigating" the issue, and has now updated that support document to reflect that "iOS 9.2 or later" should prevent the issue from occurring again.
The issue affected both 32GB and 128GB iPad Pros on iOS 9.1, including Wi-Fi and LTE models, and some users speculated that restoring from an iCloud backup during setup may have contributed to the freezing issues.
iOS 9.2 was released on Tuesday alongside OS X 10.11.2, tvOS 9.1 and watchOS 2.1.
Top Rated Comments
Running the update now on my 5S.
Keep us posted on if iOS 9.2 fixes the iPad Pro charging issue by testing on your iPhone 5s?...... keep you all posted.
Excellent news. Wonder why only some were affected
Probably because they use different components and made at different times from different batches.Everything, even computer chips are physical items with tolerances in them.
Apple has confirmed ('https://support.apple.com/en-us/HT205648') that iOS 9.2 or later ...
Or later? That makes it sound like 9.2 might actually not fix the problem, and we might have to wait for a later release for the fix.Confused...
Or later? That makes it sound like 9.2 might actually not fix the problem, and we might have to wait for a later release for the fix.
I assume they mean if you buy an iPad Pro that comes with 9.1 pre-installed on it, that upgrading to 9.2 or later (if 9.3 is out by that point) will fix the issue.Confused...
Alpha code: Test it in house and fix the stuff that's broken (99% Good)
Beta code: Test it with users and fix the stuff you didn't think would break that the beta testers found (99.99% Good)
Release code: Test it in the real world and fix the stuff that you didn't think would break that the customers found (99.999% Good)
(note: the "goodness" numbers are pulled from my posterior, but here's the thing... if you have a million lines of code, and you're at 99.999%, you still have 10 lines of code that are bad, so if anything, I'm guessing way low on my percentages. Oh yeah, it only takes 1 line of code to really mess things up.)