On Sun, 30 Sep 2018 01:44:28 -0400, JF Mezei wrote:
> Most likely: next path issues for IOS 12 *might* include some line
> stating that an issue with charging not starting on some phones under
> certain conditions has been resolvd". And this will be in fine print.
You're not an Apple Apologist, so I can talk to you as a fellow adult.
It's not clear yet, in the absence of a statement by Apple, where the
proximate cause of the problem lies.
> On the other hand, of the media cotinue to harp on issue, then yeah,
> Apple will make a bigger fiss about it when next IOS patch is issued.
You can minimize the impact of the severity of the problem, but, um, er, if
a phone won't charge, it's a brick (and some just don't charge).
A very expensive brick.
> Once I got bitten by my phone not having charged opvernight after 11.4,
> I learned to alwasy wait for the chime to indicate that charging has
> begun and if not, then wake phone and unlock it at which point chime
> gets in. (but mostf of the time, chime comes in automatically as I plug
> it in).
The design flaw, as exemplified by the video, is that the strange
inconsistencies from some phones charge fine, to others need a tap, to
others never charging, is threefold.
1. It's a very expensive device which should NOT be this capricious
2. Everyone who owns the expensive device has to act as its charge mommy
3. People will wake up in the morning with dead devices
Two facts are clear:
a. Apple forgot to run extremely basic real-world testing (again), and,
b. Every owner with the phone has to wake up scared every morning
If the phone were cheap, I personally could live with those two facts.
But the phone isn't cheap.