What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

2.3.340 Update SCREWS WI-FI AGAIN!!!!! UGH!

kevinkar

Member
Ok, this is just incredibly dumb on either Motorola or the Android developers but today I got the stupid 340 OTA update and went ahead and installed it. IMMEDIATELY after the update, I can NO LONGER connect to my router and am getting the dreaded "Connecting....Connected....Disconnecting" BS again.

COME ON! This is NOT my router. This is NOT my settings on the router. This is NOT Wireless B, G, or N. It's a problem with whatever the update mechanism does to the phone or the update overwriting some portion of the system that no longer works until you maybe stumble onto a fix. Which is what I now have to try to do.

So, to review - New phone with 2.1 connects to my existing router set to G/N mixed. NO PROBLEMS. One month later, 2.2 update installed and the phone no longer connects or stays connected when it does. After days I cripple my router by setting it to G only and it magically works until today when the 340 update is applied and NOW it won't connect to the router in G only mode! What, I now have to change it to N only?

I better not have to factory reset the phone again to make this work. This is just incredible lunacy on the part of Motorola or Android. Are they incapable of simply updating an OS while not effing with the Wi-Fi? Lame lame lame lame lame!
 
I would ask can you really blame Motorola and/or Android? Some phones, like mine, updated quite easily with the latest upgrade and have not affected any of the features I use, including Wi-Fi. Granted, mine was shipped with 2.2, so the only update I did was the 340, but my Wi-Fi works as good on 340 as it did on the previous version.

Possibly, you could blame Motorola since you might have a defective phone, or you might have to blame it on one of your apps. I am not in any way, knowledgeable enough to know what apps or things you could do to a phone to cause your problems. But I do know mine works just great.

I will add that I originally connected to a non-N router, built into the modem from Frontier; however, I later connected to my D-Link N-router with a WPA2, 50 random character password and it works quite well with either router.
 
I have to agree with retg- I am running the update and have no issues connecting to any wifi signal, even my friends miwi from his iphone. I would look at your phone first, you might have a defective wifi receiver or an even a defective router. I would go to places like starbucks or mcdonalds where they broadcast a wifi signal and see if you can replicate the problem. If it replicates outside of the house I would say it us something with the phone, if not I would say its your router.

If its your phone take it in and have it checked out. I honestly don't think its 2.3.34...

Sent from my DROIDX using DroidForums App
 
Unfortunately, the factory reset is probably be the best solution. Since updates are done OTA, they sometimes don't dl'd correctly. 99% of the time, a factory reset will take care of any issues.

DroidForums junkie!!
 
I would ask can you really blame Motorola and/or Android?
Ab-so-freakin-lutely I can blame them.

The only change was the update. I did not do anything but use the phone in the morning (connected to my Wi-Fi for the last couple of months AND it does connect to random free hot spots all over the place), got notified that the update was downloaded and ready to install, installed it, and WHAM! No Wi-Fi. Same exact problem as many people experienced with the 2.2 OTA, myself included.

So, the ONLY thing that was different was the application of the update. Nothing was changed on the router at all since the last Droid X fiasco and I did not install any software or update any other apps this morning. It was exactly as it was yesterday, the day before, the month before, etc.

Indeed, these updates change something software-wise and it's clearly not a mechanical problem with the phone. The update is the only variable.

I'm so glad I don't have to rebuild my engine every time I change the oil because I'd immediately get rid of it. This phone is pretty decent but if it does this every time I update it, it will go when I get to the "free every two" date.

As for the update not downloading correctly, I believe that's possible but unlikely. All the other apps I have installed are able to update without issue so there's no reason that only the OS updates should be any different.

K
 
Its a "NEW Every Two", not "Free". Things happen, nothing is perfect. I've seen OTAs fry BlackBerrys before!

I would ask can you really blame Motorola and/or Android?
Ab-so-freakin-lutely I can blame them.

The only change was the update. I did not do anything but use the phone in the morning (connected to my Wi-Fi for the last couple of months AND it does connect to random free hot spots all over the place), got notified that the update was downloaded and ready to install, installed it, and WHAM! No Wi-Fi. Same exact problem as many people experienced with the 2.2 OTA, myself included.

So, the ONLY thing that was different was the application of the update. Nothing was changed on the router at all since the last Droid X fiasco and I did not install any software or update any other apps this morning. It was exactly as it was yesterday, the day before, the month before, etc.

Indeed, these updates change something software-wise and it's clearly not a mechanical problem with the phone. The update is the only variable.

I'm so glad I don't have to rebuild my engine every time I change the oil because I'd immediately get rid of it. This phone is pretty decent but if it does this every time I update it, it will go when I get to the "free every two" date.

As for the update not downloading correctly, I believe that's possible but unlikely. All the other apps I have installed are able to update without issue so there's no reason that only the OS updates should be any different.

K



DroidForums junkie!!
 
Back
Top