Your opinion is heard. I submit, you sound authoritative in this matter and I defer to you to diagnose an app that appears to be operated by a human to be patently hardware failure. Your words speak volumes, the public can determine whether it is useful or not. Shutting me down and accusing me of fear mongering while I post relevant information no longer renders what we have a discussion.
If healthy discourse is not the way around here, then I guess I am in the wrong place after all.
Sure, common things are common, that does not mean sharing knowledge of uncommon things is unhelpful. Also, an incorrect common diagnosis is not helpful, the solution the OP picked was not hardware failure.
This isn't medicine, where there are more grey areas to diagnose, "A weird cough? Probs a cold." vs software and hardware where many pieces of the puzzle can be fallible, and, more importantly, can be solved with certainty.
I post what I would have liked to have seen if I were in the position of the OP. I never said it was one way or another. If you offered examples of why it is nearly impossible, it would have been more helpful. But hey, you don't have to take my word any more than I do yours. I'm the patient that asks the hows and whys of a diagnosis, because I prefer to be informed.
Alas, "Aquila non captat muscas". Don't sweat it, Meg, i'm the small fly here. Funny thing is, it's already a solved case.
For those that like the research:
OP's ios ver is 6.1.4. In 6.1.6 the publicized SSL bug gotofail was a hole that allowed man-in-the-middle attacks. Apple released a statement about this security hole. OP's accepted solution, to minimize exposure to fraudulent websites, could have been a hedge against a man in middle attack from known, bad sources.
Read more: http://www.wired.com/2014/02/gotofail/
NIST's vulnerability database: https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-1266
If you are running < 6.1.6, you can check if you're vulnerable at https://gotofail.com/
Stay safe, stay patched, stay cool.
