Definitely seems to be a problem
Howdy, Peeps. I'm using a Motorola Droid that had stock ROM, etc. The 2.2 update was pushed to me early yesterday morning. I'd just finished some World War and set the phone down to get ready for work. Since I was at home, I had just been using my wi-fi connection.
Anyway, immediately following the 2.2 update and the restart of my phone, the phone reconnected to my home wireless router (Linksys WRT54G). I noticed that the wireless indicator on the notification bar did not have any lines -- just the little dot at the bottom of the icon was lit up. Since I was in the bedroom immediately above my library where the router is, the signal is usually great (as acknowledged by Wi-Fi Analyzer on a regular basis by my 9 year-old son
), and so I usually see all three bars. I thought nothing of it initially because the phone seemed to be responding in a nice snappy way as I quickly familiarized myself with the changes to the launcher, etc. Once I restarted World War, however, I noticed that it was responding slowly at screen changes and that I was getting long waits on the Loading... screen. So, I quit the game, killed my processes, disconnected/reconnected to wifi, and checked again. Still not good. I checked the stock browser and then XScope and Opera, but no good either. Very sluggish loads with long pauses. So, this time I shut down the phone for a full restart. To my surprise, I had all 3 bars on the wifi icon in the notification bar after the restart. So, I'm thinking "problem solved! Whew!". But no, it was not and is not solved.
When I go to WiFi Analyzer and looked at the graphs. I see that my connection is tall peaks and then dead spots over time. It's as if the signal is perfect, then dead for a few seconds, the perfect again... repeating indefinitely at a regular interval of just a few seconds. When I switch to the signal meter view. I see the exact same behavior: signal meter sits buried to the left. Then, all of sudden, it swiftly moves up to a green strong signal and beeps in quick succession indicating a nice strong signal. Then it falls back to the left completely after just a couple of seconds of working great. This repeats and repeats for as long as I watch it. When I look in the Droid Settings... menu and look at Wi-Fi, it shows the phone is "connected" to my network. The strange thing is, when I watch the Wi-Fi Analyzer graphs of all of the access points and channels it can find during its scanning process, I see my signal coming and going while the other signals it can see stay visibly stable in the graphs (albeit weak since they're from my neighbors).
I've tried reconfiguring the connection on my phone, restarting my router, killing processes on the phone, restarting the phone, etc. Nothing is solving this. Since the same wireless connection was working just moments before the 2.2 upgrade was pushed, I know the upgrade has broken the wi-fi connectivity on my phone... or, perhaps more fairly, seriously impaired it.
Just to be clear on my setup. Router: Linksys WRT54G (V5). I use MAC address filtering and static IP assignment with my router. My SID is not broadcast and I use WPA/PKA-2 with AES encryption. This has been the same setup I've used for this phone from day 1 back at the beginning of December 09 when I bought it. The phone had stock 2.1 from the update pushed in Q1.
While I love some of the 2.2 features and the snappier performance, the wi-fi is busted now and it is seriously slowing down my usual use of the phone at home. With unlimited data, I shouldn't care too much; however, my house is in a bit of dead spot between towers and gets lousy cell data connectivity. In fact, my AT & T friends drop voice calls in my house and usually go outside to avoid the call drops.
In searching this wi-fi problem on Google just now, I found one other account of the same exact behavior in addition to the user vandypaul in this thread that is talking about the "looping". Is no one else having this problem? We're not making it up. Honest!
Any help or ideas from others in the community would genuinely be appreciated. I'm hoping that any others that are having this same problem will come forward with more evidence, ideas, and data to help us figure out what exactly is happening and why. I'm going to probe some more this weekend and try setting up some different connections, testing on a friend's router, etc.
Thanks to all