Originally Posted by Overthrow
Wow! I did not know BW posted crap! Thats the worst logic I have heard in ages. They counted people of message boards, multiplied by 1000 and said its less than 1% of iPhones sold. And they are only counting people with screen problems.
Cause for Concern?
Even if we were to assume that for every person who has posted about problems on a Web forum there were 1,000 more, the total number of glitchy iPhones would still be in the ballpark of 1% of the 1 million iPhones Apple says it will sell by the end of September. And as yet there is no reason to believe the problem rate is anywhere near this high.
So is 1% an acceptable failure rate for a new device with a lot of new technology? Yes (unless you happen to own one). ISuppli's Jagdish Rebello tells me that it's not uncommon in the wireless industry to see failure rates on new products as high as 3% and 4%, especially when the product is entirely new or, as in Apple's case, the company is building its first phone.
What's important is that the failure rate goes down over time. As products mature, and the understanding of the various pitfalls in the manufacturing process improves, Rebello says, the failure rate drops in most cases to 1% or less. We don't know the actual failure rate on the iPhone. Apple isn't in the habit of releasing such data, mainly because it's not material to earnings. Apple's spokesperson declined to comment on the subject.
But one would have to believe that if there is a problem, Apple is doing what companies in this position always do: Figure out what it is and fix it. We on the outside are forced to simply speculate, and in some cases overreact.
What about this guy?
Join Date: Apr 2006 Well, that didn't take long. Its not hardware. In under 20 minutes of surfing(wifi) iPod crashed. After the first crash it wont last more than a few seconds(of safari use).
I had 3 tabs open, and frequently switched pages after selecting a link, being aggressive to aggravate the problem. After the first crash all it takes is reading an already loaded page to re-crash iPod. The problem surfaces with less aggressive initial usage, it just takes longer, so please don't tell me I'm expecting too much.
I still urge people with the issue to report it via Apple support. 2 updates, and they have NOT fixed the problem. They need pressure to make this fundamental capability stable.
I'll give them a call and see if they still want me to send my old phone in, but form a diagnostic stand point, the new phone loaded with my data should be just as useful.
Edit: An update. Just spent nearly 1hr on the phone with Apple support. There was nothing in his database to indicate this is a know, being worked on, issue. He had me try a few things I hadn't already tried, and I was still able to repeat the iPod crash while surfing. In fact the entire phone crashed(black w/ apple-logo) during some of our testing(this is the brand new loaner phone). So, as I've said all along, it doesn't look like Apple has been working on this issue. I (or others) should have called this in with version 1.0.0. Whining on the forums has not brought this to Apples attention.
AFAIK those were recommendations, not limits of the browser. Did you not disprove this yourself. Also people were arguing what a 10 MB web page means. Is it HTML, or with graphics included, or with all the data structures generated also?
Web page sizes are artificially limited to 10MB each, 8 pages max, according to Apple's documentation.