The iPad arrived last Saturday to overall glow review . Inevitably , this was speedily followed by report of problems with the iPad . The most publicise problem so far has been with Wi - Fi receipt . You could scarce graze the Web this past week without seeing an article on the topic ( such asthis one from USA Today ) . Trying to extricate reality from magnification has not been light .
• Many people have report some form of Wi - Fi - touch on symptom when using an iPad . To confirm this , all you want to do is go to theiPad - > Wi - Fi plane section of Apple ’s Discussions Boards . You ’ll find numerous threads on the matter , includingone threadwith an amazing 390 replies and almost 55,000 sight ( and numeration ) .
• If you read these threads , you ’ll notice that there is more than one elementary symptom . There are at least three : ( 1 ) Failure to rejoin a known web when waking up from sleep ; ( 2 ) remarkably weak signal ( or complete Wi - Fi disconnection ) at distances from the router where other Wi - Fi devices work without problem ; and ( 3 ) Jerky or disrupted stream telecasting , even when signaling lastingness appear strong and other Internet activities on the iPad are working well .
It may well be that these three job are autonomous , having disjoined causes and solution . It may even be that one or more of them are not specifically due to the iPad , but are instead due to other computer hardware , such as the Wi - Fi router . It ’s still too early to tell .
• For the “ failure to rejoin ” symptom , Apple has posted aKnowledge Base articledescribing the symptom and suggest fix , such as reset your iPad ’s web options .
Most news show stories have cited this Apple clause as grounds that Apple has “ acknowledged ” or “ sustain ” or “ admitted ” that there is a Wi - Fi problem with the iPad . If you only nonchalantly glance over these story , it ’s easy to conclude that Apple has admitted to a serious problem affecting every iPad out there . Not so .
The Knowledge Base clause really admits very little , citing that the rejoin problem should only pass with a small subset of router and only under “ certain ” unspecified condition . It say nothing about the other Wi - Fi symptoms . Apple releases article like this all the time . They usually get almost no closet coverage . This one is make an strange storey of attention chiefly because anything iPad - related is getting close scrutiny right now .
• Postings to forums offer several unexpected potential workarounds . For lesson , turning off the “ Ask to Join Networks ” option ( in scope - > Wi - Fi ) may remediate video streaming or weak signaling problems . Inone thread , several exploiter agreed that increasing the screen brightness prevent the unsuccessful person to reconnect after waking from sleep !
• It ’s hard to estimate on the nose how many people have any problem at all here . For what it ’s worth , my iPad ’s Wi - Fi joining has been nearly flawless . I have had occasional job with stream video when I am in a different room from the router . But these are intermittent ; a 60 minutes afterward all will be well . To be bonnie , I have had similar problems with my MacBook Pro .
On Thursday , I need my Twitter followers tolet me know if they ’ve had any of the reported symptom . The number of citizenry who confirmed have a problem ? Zero .
Bear in mind thatmore than 450,00 iPads have been sold . Compare that to the 300 or so people reporting a problem on Apple ’s Discussions Boards . For the sake of argument , allow ’s imagine that the existent number of multitude having a problem is more like 50X the 300 act . That ’s 15,000 job iPads ( which is probably a bad showcase scenario ) . Admittedly , this is a number you would n’t want to ignore . But it ’s also only a small more than 3 percent of all iPad owners . And this assumes that all of these people have correctly diagnosed the iPad as the basal cause of the problem .
Bottom line : If you corrupt an iPad , there ’s a danger you ’ll have a Wi - Fi related to job . That ’s true . But at least for now , it appears that the danger is small , soft - to - implement workarounds exist , and a on-key fix should not expect any ironware modifications .
