Database Users

Wifi Not Working On Any Rom!!

Hey guys. It's been a while but I've ran into a problem with my mytouch today when I tried to turn wifi on for the first time in forever. It just wouldnt connect. It would say aquiring ip address from [network] and then flash to disconnected, then scanning, then acquiring ip address again.
I've tried flashing a different rom, doing a nand restore to my previous rom (which had wifi working), and trying my friend's wifi and none of those worked.
Wifi stopped working after flashing this rom.
http://forum.xda-developers.com/showthread.php?t=811620
Any ideas? I'm dataless right now

hacker01 said:
Hey guys. It's been a while but I've ran into a problem with my mytouch today when I tried to turn wifi on for the first time in forever. It just wouldnt connect. It would say aquiring ip address from [network] and then flash to disconnected, then scanning, then acquiring ip address again.
I've tried flashing a different rom, doing a nand restore to my previous rom (which had wifi working), and trying my friend's wifi and none of those worked.
Wifi stopped working after flashing this rom.
http://forum.xda-developers.com/showthread.php?t=811620
Any ideas? I'm dataless right now
Click to expand...
Click to collapse
I've had issues with WPA2 networks where my phone wouldn't connect at first.
Try removing the network and starting over.

Still a no go.

Could it be a bad kernel that you've been installing?
It may also be a hardware failure (worst case scenario)
Try changing your network security type, or removing it completely.

I forgot to mention that I changed the kernal too. Still not working. I don't think (or I hope) it's not hardware failure. It's still picking up wifi signals and detecting networks. It just doesn't actually connect.
EDIT:
Wow I feel like the biggest noob now. After changing every possible thing I could think of on my phone, I restarted my router and my phone connected right after. That was really strange considering every other wireless device in the house had no trouble connecting but oh well. It works. Can't complain now. Thanks for the help guys

Same with MT3G. Can not connect any wifi now (Just 1 time after Flashing 2.2 ROM).
Don't know how to fix.
Changed 2 Froyo ROM already

same issue
Same problem here after flashing a Hero ROM like 5 months ago. Can't connect to WiFi, but I can still search and attempt to connect to a wifi network, but won't actually connect. I can still WiFi tether, which leads me to believe it's not a hardware issue...

[HELP] Cm7.0.2 don´t see wifi network

I have have updated cm7 to 7.0.2 and my gps is now working well... but now i´m facing a new issue.
I use a coffe shop wireless connection to do many things to the phone. but now it cant find the signal from that connection.
Before the update, and in cm6.1 i could connect to the wireless, now it dont show up on the wireless connections screen.
can anyone help me in here?

ICavalera said:
I have have updated cm7 to 7.0.2 and my gps is now working well... but now i´m facing a new issue.
I use a coffe shop wireless connection to do many things to the phone. but now it cant find the signal from that connection.
Before the update, and in cm6.1 i could connect to the wireless, now it dont show up on the wireless connections screen.
can anyone help me in here?
Click to expand...
Click to collapse
I had the same problem. I think it's being caused by the wifi trying to autoconnect to a remembered AP in range. I just had my phone "Forget" the network I knew it was trying to connect to (my home network) and it worked.

santisolinho said:
I had the same problem. I think it's being caused by the wifi trying to autoconnect to a remembered AP in range. I just had my phone "Forget" the network I knew it was trying to connect to (my home network) and it worked.
Click to expand...
Click to collapse
but every one sees the wifi network and i dont see...
really i am almost to downgrade to cm6.1 were there i have no trouble to wif and gps.
Today i saw the network and try to connect and fail... and then i connect and in the middle of using ebuddy disappear. then could not connect anymore.

Hi,
Cm7 is quiet weak with wifi. Meaning the signal strentgh in cm7 is less like e.g. on b 0.8.4 maybe flashing another radio helps.
Sent from my Legend using XDA App

I flash another radio and didn't work. Clear data, cache and dalvik. Nothing. Só i give a trie on nightly #58. Did a clean install and it worked. Went to the coffee shop and detect the wifi and could connect with a good signal. Tomorrow i'm going to my brother's house where i had the same problem. Then i will report if it's ok or not.
Thanks.
Sent from my Legend using XDA App

I went to the coffee shop and again... i dont see the wifi. Yesterday worked... today cant find again. I love cm7, but like this is not very good. Well, im going to downgrade. I cant find any real solution.
Sent from my Legend using XDA App

have you tried changing channels on wifi settings-->advanced-->regulatory domain? just a shot though. it worked for me on the nightlies. on latest cm7 stable though, i haven't need to change it...

did you use any other wifi tool than the cm7 internal one? Wifi analyser or similar apps may watch out for more ssid than CM7 itself
maybe the wifi channel is out of range, meaning cannel 11 or higher. Then change the channel settings in android settings

alexkno said:
did you use any other wifi tool than the cm7 internal one? Wifi analyser or similar apps may watch out for more ssid than CM7 itself
maybe the wifi channel is out of range, meaning cannel 11 or higher. Then change the channel settings in android settings
Click to expand...
Click to collapse
thanks... im trying!

[Solved] WiFi connection issues on home network

I have a strange WiFi issue. If I use any Sense 3.0 ROM I can connect to my Home WiFi network with no problem. However, If I use a Sense 2.1 ROM it fails to connect. It sits at "Obtaining IP Address" and cycles round this until I get bored of waiting. I have just tried CM7 and I get the same issue.
I have my laptop and Tablet connected to my network, so I know that is fine.
It is weird as I can connect to any other WiFi network. So the issue is with my own. But why would Sense 3.0 ROMs have no probelms, when other ROMs do, and only with my network
Anyone got any ideas?
EDIT: Resolved this in the end. I had some erroneous devices in my Router settings for my phone. I deleted them all, reconnected and it was fine. Still weird why it would work for Sense 3.0 ROMs though. Anyway, all okay now.

You get a really strange issue，Best wishs

L0cke said:
I have a strange WiFi issue. If I use any Sense 3.0 ROM I can connect to my Home WiFi network with no problem. However, If I use a Sense 2.1 ROM it fails to connect. It sits at "Obtaining IP Address" and cycles round this until I get bored of waiting. I have just tried CM7 and I get the same issue.
I have my laptop and Tablet connected to my network, so I know that is fine.
It is weird as I can connect to any other WiFi network. So the issue is with my own. But why would Sense 3.0 ROMs have no probelms, when other ROMs do, and only with my network
Anyone got any ideas?
Click to expand...
Click to collapse
something must be wrong with your rom ，are you sure you have done the wipe before flashing?

I have This issue too

I had this issue with ARHD - switched to LeeDroid and it works fine.

Yeah, is very strange. Just can't quite figure it out yet.

Power cycle your Router betweem builds and see if that does the trick.

Agoattamer said:
Power cycle your Router betweem builds and see if that does the trick.
Click to expand...
Click to collapse
I have already reset the Router once or twice but still no joy. This also wouldn't explain that if I now flash a Sense 3.0 ROM it would connect no problems.
I just did a full wipe of everything, then flashed the latest version of MIUI and same issue.

Help with fixing Wi-Fi

I have reached my wit's end trying to resolve my problems, so I'm posting here for ideas on fixing this, any input is appreciated!
When this started I was on stock, rooted, ICS 4.0.3 and had been for months. My wife has a nexus s with the same config and hers works fine.
Last week, my daughters sidekick 4G stopped having wi-fi internet connectivity. I turned her wi-fi off, then back on and it was fine and has been ever since. Later that night, my nexus did the same thing, the same procedure resolved it. Ever since then, my wi-fi will only work for 1-5 minutes after turning the wi-fi on. This is the only thing I can think of that changed that could have caused this. This was the first night we connected her sidekick to wi-fi.
The wifi symbol is up there, it'll be blue for up to half an hour, but won't have internet connectivity for long. One thing I noticed pretty quickly was that even though the grey wi-fi symbol is there, I can't access the router settings at 192.168.1.1 from the phone. I thought the grey wifi symbol still indicated I was connected to the router still, but it's not working. Each time this happens, I can turn wi-fi off, back on immediately and it'll work for 1-5 minutes. It appears that the more I constantly use it after turning it back on, it seems to maintain connectivity longer.
Last weekend, just after these issues started, I visited my sister and my phone operated on her wi-fi all weekend just fine.
When I came back home, my problems started immediately.
Here's what I've tried in pretty much the order I tried them:
I started by uninstalling avast, facebook, and autostarts
selected "Forget network" in access points screen and reconnected
Factory reset
Wipe dalvik cache & fix permissions
see if it worked without sim card in (it didn't)
flash GB broadcom driver
Switched router channel from 6 to 1
flash stock 2.3.6 (wi-fi problems still present)
flash OTA ICS (still had problems)
flash stock 2.3.6
flash OTA ICS
re-root
Flash PixelROM 1.60 LiteTouch
factory reset router (No wifi problems on using open network and default SSID for 30 minutes!)
resetup WPA Personal security and rename SSID same as before
Worked for another 15 minutes or so after this
flashed stock 2.3.6
flashed OTA ICS
re-rooted
Restored nandroid backup - quit working after this step
Factory reset router - worked for about 15 minutes, I decided I was ok so I setup security and SSID as before, then it quit working again
flashed PixelRom 1.60 LiteTouch
flashed stock 2.3.6
Flashed OTA ICS - THIS time I did not restore my google backups from the cloud, fearing that this was somehow restoring something that was causing me problems. It did not help.
Changed SSID on my router and reconnected phone
I have spent countless hours trying to fix this. I don't believe it's the hardware because the router factory reset seems to help quite a bit, works fine on unencrypted default router settings, and it worked on my sister's wi-fi.
I have nmap and wireshark and have a basic working knowledge of them. I have adb setup and usable on my computer. I also have dd-wrt installed on my router and have for years. Is there any kind of IP or hardware logging I could perform with these tools to help figure out what's going on??? ANY help is GREATLY appreciated!!

Well i'm no expert with any of this, but it sounds more like a router issue.. If both your sidekick and nexus have the same characteristics of failing wifi, it cant be the devices..
If you've already reset your router and it does the same exact thing, maybe it is something wrong with the router itself. You said it connected fine at your sisters house, so it cant be any hardware within the phone.. The only thing I could think of is maybe try a different router in your house to see if it works? If that helps get rid of the connectivity issue, then you can just get a new router and be happy with the wifis

I don't think a *hardware* problem with the router would only affect 1 device connecting to it wirelessly. I would think that kind of issue would affect all devices on the network.
Which makes me wonder if there's a setting on the router that may be causing it somehow, or some combination of packets might somehow cause the router to block my phone.
But again, I'm open to ideas here and I appreciate your input. I think getting another router will be my next step if I don't hear anything better by the time I get my next paycheck.

nevarDeath said:
I don't think a *hardware* problem with the router would only affect 1 device connecting to it wirelessly. I would think that kind of issue would affect all devices on the network.
Which makes me wonder if there's a setting on the router that may be causing it somehow, or some combination of packets might somehow cause the router to block my phone.
But again, I'm open to ideas here and I appreciate your input. I think getting another router will be my next step if I don't hear anything better by the time I get my next paycheck.
Click to expand...
Click to collapse
Ohh, I thought you had said that both the sidekick and nexus were having problems connecting. My bad.
But yeah have you changed any settings on it lately? Or messed with anything related to the router? Some setting may be kicking your device off after 5 mins, maybe some frequency setting or something dumb like that, I have no clue.
I know how it feels to have funky wifi, so I was only trying to help. good luck

Have you removed DD-WRT from your Wireless Router and back to stock OS? I had a Linksys router with DD-WRT and after about 3 years it started working so weird it became useless with any device. Had to buy a new one.
BTW, are other devices connecting fine to this router?
As swamp goblin stated, I would try with a new router.

It sounds like an issue on your router (or AP) with mixed client settings. I have had this issue with an old Netgear AP.
Try forcing "WPA2 with AES only" if all clients support it, otherwise force "WPA with TKIP only". If you have mixed B/G/N devices, force the fastest mode that all devices support. I use "G only".
Then remove and re-add the router on all your devices.
Also check for router firmware updates, and if you use DD-WRT firmware, find the Wiki page for your model and revision and use the suggested build there. The DD-WRT database they have is a mess and should not be used!

swamp goblin said:
Ohh, I thought you had said that both the sidekick and nexus were having problems connecting. My bad.
But yeah have you changed any settings on it lately? Or messed with anything related to the router? Some setting may be kicking your device off after 5 mins, maybe some frequency setting or something dumb like that, I have no clue.
I know how it feels to have funky wifi, so I was only trying to help. good luck
Click to expand...
Click to collapse
I haven't changed any settings, until this problem began, which makes this even more maddening. I appreciate your input regardless
Oogway13 said:
Have you removed DD-WRT from your Wireless Router and back to stock OS? I had a Linksys router with DD-WRT and after about 3 years it started working so weird it became useless with any device. Had to buy a new one.
BTW, are other devices connecting fine to this router?
As swamp goblin stated, I would try with a new router.
Click to expand...
Click to collapse
I haven't removed it. I thought I had a model that couldn't go back to stock, but I WILL be looking into this. The other devices connecting fine are Sidekick 4G, Wife's Nexus S, Acer Aspire one, HP tx2000 laptop, and my wife's HP laptop. I also have my satellite receiver connected via ethernet.
SpookyTunes said:
It sounds like an issue on your router (or AP) with mixed client settings. I have had this issue with an old Netgear AP.
Try forcing "WPA2 with AES only" if all clients support it, otherwise force "WPA with TKIP only". If you have mixed B/G/N devices, force the fastest mode that all devices support. I use "G only".
Then remove and re-add the router on all your devices.
Also check for router firmware updates, and if you use DD-WRT firmware, find the Wiki page for your model and revision and use the suggested build there. The DD-WRT database they have is a mess and should not be used!
Click to expand...
Click to collapse
I will certainly try these settings. Thanks for the tip on the wiki page

I had this problem too, I solved only flash again my radio...
Try if solve...
Or if don't work try to make a reset.
Sent from my Nexus S using Tapatalk 2 Beta-4

SpookyTunes said:
...Try forcing "WPA2 with AES only" if all clients support i...
Click to expand...
Click to collapse
THIS FIXED IT! I tried it first since it was the simplest solution and I've been 4 days with no loss of connectivity since I changed it to AES only, which all my clients do support! Thanks so much!

[Q] VZW 4.1.2 latest build, won't connect to FIOS router

So, my wife got a Droid RAZR M. First thing we did was download the 2 updates from Verizon. Current version is 98.18.78.XT907.Verizon.en.US
I get home, and go to connect to my FIOS Actiontec MI424WR-GEN3i running the latest firmware available. (40.20.7)
Running WPA PSK, in b/g/n compatibility mode, with SSID on.
The phone refuses to connect. It will see the SSID, an even automatically identify that it's WPA PSK security. But when I go to connect, the signal drops to almost nothing, then doesn't connect. I make it forget the network and start fresh, same thing. Reboot the phone, same thing.
WPS is not active on the FIOS router firmware, so I can't try to connect via WPS.
I've got a Galaxy Nexus connected to the wifi and about 6 different wifi devices (laptops, xBox, HP Touchpad, etc). So, I know it's not the config of the router.
Anybody have any idea of what's going on with this thing? My wife doesn't want me to root it, but I'm getting close. However, please do not just suggest rooting it, because I would really like to resolve this wifi issue with the stock build.

dvsDave said:
So, my wife got a Droid RAZR M. First thing we did was download the 2 updates from Verizon. Current version is 98.18.78.XT907.Verizon.en.US
I get home, and go to connect to my FIOS Actiontec MI424WR-GEN3i running the latest firmware available. (40.20.7)
Running WPA PSK, in b/g/n compatibility mode, with SSID on.
The phone refuses to connect. It will see the SSID, an even automatically identify that it's WPA PSK security. But when I go to connect, the signal drops to almost nothing, then doesn't connect. I make it forget the network and start fresh, same thing. Reboot the phone, same thing.
WPS is not active on the FIOS router firmware, so I can't try to connect via WPS.
I've got a Galaxy Nexus connected to the wifi and about 6 different wifi devices (laptops, xBox, HP Touchpad, etc). So, I know it's not the config of the router.
Anybody have any idea of what's going on with this thing? My wife doesn't want me to root it, but I'm getting close. However, please do not just suggest rooting it, because I would really like to resolve this wifi issue with the stock build.
Click to expand...
Click to collapse
I don't think rooting it will solve the issue. have you tried changing the router to WEP?

jco23 said:
I don't think rooting it will solve the issue. have you tried changing the router to WEP?
Click to expand...
Click to collapse
The m works fine on WPA PSK(as I am connected to a WPA PSK network as I type this).
This sounds like some of the bugs that have been reported before.
If I were you, I'd try a factory reset, and if that doesn't work, go back to the store. Since you're not rooted, you've got a good warranty claim. Last option is to root and try WiFi connection fixer, which worked for me in the past.
Good luck...
Sent from my XT907 using Tapatalk 4

sloosecannon said:
The m works fine on WPA PSK(as I am connected to a WPA PSK network as I type this).
This sounds like some of the bugs that have been reported before.
If I were you, I'd try a factory reset, and if that doesn't work, go back to the store. Since you're not rooted, you've got a good warranty claim. Last option is to root and try WiFi connection fixer, which worked for me in the past.
Good luck...
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
Turned it in under warranty today. Turns out the speaker you use when you hold the phone to your ear didn't work (my wife normally uses the speakerphone, so she didn't discover this till last night) We'll see what happens when we get it back next week. Worst part? They gave her this old LG Vortex running 2.2 as a loaner phone..... she is going nuts trying to deal with the low-res tiny screen and going back to 2.2 after being on 4.1 for so long really sucks.