maybe all the people in this thread with the GM build installed (all developers of course!) should log the issue via the developer channel as they should be doing.
afterall, the GM build is only for developers, not for end-users.
now, the mute mutton does not mute!!! in 4.2 GM b
now, the mute mutton does not mute!!! in 4.2 GM b
OK, I'm not going to lie to you, but this may be a problem at your end, not with the software.
I say this because I have experienced this WiFi issue on two iPads both running 3.2.2 at a friends house, but only there. My iPad runs fine at my uni and at home, as well as on the WiFi at my fiancée's office. But I can get the issue to consistently reappear at my friends house and only at his house. I'm not sure if it is his router or intereference from the neighbours, but it is definitely localised.
One less unsatisfied iPad user! 4.2GMb is working fine for me now. I don't know exactly what solved the problem, but after I reset my router and change the WiFi channel from auto to "6" (there are a lot of routers nearby, all set to channels like 1 or 2), it works like a charm. 4.2 is super fast, for example the transition from the first home screen to the search box is now silky smooth, while with 3.2.2 there was a bit of stuttering. WiFi performance is excellent as well, i managed to get the same SpeedTest reading with the iPad and with my desktop connected directly to the router via ethernet.
+1.
I'd been experiencing the WiFi issues also since WiFi launch day back in April. Tried three different routers (Linksys, Netgear and Uverse Motorola), and had the signal dropping repeatedly. I installed inSSIDer on a Windows laptop and saw that all my neighbors were running on channels 6-8. As soon as I changed by router config to run on channel 11, all WiFi issues disappeared, from build 3.2.2 - 4.2GM - 4.2GMb.
It's definitely worth taking a look at.
Matt
I changed my router from 11 to 6 to 11 channels just to make sure.
But it still doesn't work.
What's funny is that I am using a same router at work and 4.2b was working fine at work.
But not at home...
This is very frustrating.
Update to 4.2.1. See if it's still buggy. If so, then try the gimmick I posted above.