[Solved] WiFi connection issues on home network - Desire HD General

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.

Related

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...

Wifi out of range? Please help!

I'm having a problem and wonder if anyone here could help me. I have a rooted evo 4g that had CM7 which pretty everything worked on. I recently just switched to Swagged Out Rom and updated my PRL. After flashing to Swagged I realised anytime I try to connect to my router it says out of range. Flashed back to CM7 and same issue.
I checked my girlfriends phone, and she is getting the same result. I havent made any changes to my network, or router. Wifi works fine for my laptop. router is running DD-WRT v24-sp2 (12/28/09) micro.
yahar said:
I'm having a problem and wonder if anyone here could help me. I have a rooted evo 4g that had CM7 which pretty everything worked on. I recently just switched to Swagged Out Rom and updated my PRL. After flashing to Swagged I realised anytime I try to connect to my router it says out of range. Flashed back to CM7 and same issue.
I checked my girlfriends phone, and she is getting the same result. I havent made any changes to my network, or router. Wifi works fine for my laptop. router is running DD-WRT v24-sp2 (12/28/09) micro.
Click to expand...
Click to collapse
ive had that problem a few times, what works for me is turning off the wifi router and turning it back on and then try to connect. otherwise if that doesnt do it only thing i can think of is something is messed up with your rom/kernel. may want to try wipe cache and reflash rom.
Go into our GUI of your router and change your wireless channel first. Sometimes its the router they can work great on one item and crap on another your probably on a crowded channel.
Sent from my Mophukin Photon runnin Skinny1, One.Four OC like a Boss...
edit: it was taking forever to connect lol. changing the wifi channel did the trick. thanks for the help all!
maybe flash a different modem?

Wifi issues

My Acer is stock and was running fine. Now when I try to connect, all it says is obtaining IP address. I tried shutting down and restarting and the normal modem reset stuff...What is happening?
Fourstarzzzz said:
My Acer is stock and was running fine. Now when I try to connect, all it says is obtaining IP address. I tried shutting down and restarting and the normal modem reset stuff...What is happening?
Click to expand...
Click to collapse
Had the same with my A500 & Android 3.0. Connected with WiFi (I have two different accespoints at home and tried both) I was able to connect with my home network & server, but Internet connection failed. The same as with my HTC Sensation with an early rom.
This had to do with the DCHP protocol on the router and Android, it is not always implemented as it should. On my HTC I was able to manually assign an IP adress, that's not possible on the Acer. That fixed the problem for then on my HTC. The problem was gone after an OS update.
I turned the WiFi router connection on on my HTC Sensation and connected to the Wifi router with my Acer. That worked and I was able to download an A500 Android update from 3.0 to 3.1 over 3G (365 Mb). Took me nearly an hour, but after installing the update WiFi worked flawlesly.
Hope to be of any help,
Fazer
If it's a home router you are having issues on, try changing channels on the router.
Thanks, Will keep in minder. My.problem is solved after a Rom upgrade on my A500.
Sent from my A500 using xda premium

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!

Wifi won't stay connected (not D-Link problem)

My phone has problems staying connected to wifi. It's often disconnected and has to reconnect when I wake my phone up (even though it's set to not turn off during sleep) and it'll disconnect and reconnect sometimes even when the phone is awake. I've read about people having problems with D-Link routers, but none of my routers are D-Link. The problem seems to have improved a lot after I flashed my modem to the MDL modem, but it still comes up. Does anyone have any solutions or would anyone know what could be causing this? I'm currently running the Wicked rom but I had this problem even when my phone was completely stock. Has anyone had this problem go away after switching to an AOSP-based rom?
AZImmortal said:
My phone has problems staying connected to wifi. It's often disconnected and has to reconnect when I wake my phone up (even though it's set to not turn off during sleep) and it'll disconnect and reconnect sometimes even when the phone is awake. I've read about people having problems with D-Link routers, but none of my routers are D-Link. The problem seems to have improved a lot after I flashed my modem to the MDL modem, but it still comes up. Does anyone have any solutions or would anyone know what could be causing this? I'm currently running the Wicked rom but I had this problem even when my phone was completely stock. Has anyone had this problem go away after switching to an AOSP-based rom?
Click to expand...
Click to collapse
I still have this problem, it disconnects and reconnects minutes later. I am on stock, stock kernel and rooted. could it be a root problem?
It can't be a root problem because I had this problem even when the phone was completely stock. I'm wondering if it's a TW problem, which is why I asked if anyone still had this problem after switching to AOSP (the Wicked rom I'm running now is TW).
If it were me, I would try a different modem, but thats just me.
Is there a thread with the available modems?
AZImmortal said:
Is there a thread with the available modems?
Click to expand...
Click to collapse
What device are you on, could be another fix.
AZImmortal said:
My phone has problems staying connected to wifi. It's often disconnected and has to reconnect when I wake my phone up (even though it's set to not turn off during sleep) and it'll disconnect and reconnect sometimes even when the phone is awake. I've read about people having problems with D-Link routers, but none of my routers are D-Link. The problem seems to have improved a lot after I flashed my modem to the MDL modem, but it still comes up. Does anyone have any solutions or would anyone know what could be causing this? I'm currently running the Wicked rom but I had this problem even when my phone was completely stock. Has anyone had this problem go away after switching to an AOSP-based rom?
Click to expand...
Click to collapse
Just because it isn't a DLINK wireless ap doesn't mean you won't issues. All the consumer-grade wireless routers/ap's share a narrow range of chipsets made by broadcom, atheros, etc.. So, the brand has nothing to do with it.
I would suggest getting a logcat if you can or try another wireless ap somewhere else. I've got a TPLINK wireless router with OpenWRT flashed, runs flawless.
TheAxman said:
What device are you on, could be another fix.
Click to expand...
Click to collapse
SGH-I337 (AT&T)
chaosclarity said:
Just because it isn't a DLINK wireless ap doesn't mean you won't issues. All the consumer-grade wireless routers/ap's share a narrow range of chipsets made by broadcom, atheros, etc.. So, the brand has nothing to do with it.
I would suggest getting a logcat if you can or try another wireless ap somewhere else. I've got a TPLINK wireless router with OpenWRT flashed, runs flawless.
Click to expand...
Click to collapse
I never said that only D-Link routers have problems. There's a well-known issue with D-Link routers so I wanted to state up front that I don't have any D-Link routers in case anyone wanted to suggest that it could be the cause.
http://www.zdnet.com/samsung-acknowledges-galaxy-s4-wi-fi-connection-problem-7000015431/
Does anyone have any solutions/possible causes?
From another thread...
http://forum.xda-developers.com/showpost.php?p=43495950&postcount=60
and
http://forum.xda-developers.com/showpost.php?p=43501841&postcount=64
See if that helps your issue and if it does make sure to thank the original poster of the threads. Good luck.
scott14719 said:
From another thread...
http://forum.xda-developers.com/showpost.php?p=43495950&postcount=60
and
http://forum.xda-developers.com/showpost.php?p=43501841&postcount=64
See if that helps your issue and if it does make sure to thank the original poster of the threads. Good luck.
Click to expand...
Click to collapse
Thanks, I actually came across that solution already but I don't seem to have that option under the advanced options. I'm not sure if it's because I'm running the Wicked rom.
AZImmortal said:
Thanks, I actually came across that solution already but I don't seem to have that option under the advanced options. I'm not sure if it's because I'm running the Wicked rom.
Click to expand...
Click to collapse
He said the option was only available while originally connecting and setting up the connection for the first time. Maybe you can try to delete the wifi connection all together and then let it re-detect and go through the set up process again...if that is an option.
My phone was doing this on my friends router but not on my home router. He searched google & found something stating that the S4 dont like routers with AES encryption for the security. He changed his router security to TKIP+AES encryption & the next time I was there wi-fi stayed connected with no constant reconnect problems. Buuuut, my home router security is just AES & I have no issues connecting to it, yet at least. Dont know if this will help anybody else out but its worth a shot to play with your routers security settings.
I thought I had an issue with my I337 S4 do the same thing.turns out my phone was just bouncing around trying to connect to 6 other open WiFi signals I've used
So just to give an update, I tried installing another router in my house as an access point and the phone has no problems staying connected to it, so there's definitely something that the phone doesn't like about the other routers that I'm running. I'm reluctant to say that there's anything "wrong" with my old routers because no other device had a problem staying connected, but if anyone else experiences the same problem, changing routers/APs could work. Fwiw, my old routers had Broadcom chipsets while the new one has an Atheros chipset. I'm going to try updating the firmware for the old routers to see if it helps (I run DD-WRT and Tomato on all of my routers).
AZImmortal said:
Thanks, I actually came across that solution already but I don't seem to have that option under the advanced options. I'm not sure if it's because I'm running the Wicked rom.
Click to expand...
Click to collapse
I'm having the same constant-disconnect issue as well and searching for solution.
I'm rooted, on stock rom and cant find any "key management" option at initial connect. Issue was happening when unrooted as well.
No issues when connected to router at work, but have connected two other, albeit older android devices to home router without issues.
home router is dlink dir655
bo8 said:
I'm having the same constant-disconnect issue as well and searching for solution.
I'm rooted, on stock rom and cant find any "key management" option at initial connect. Issue was happening when unrooted as well.
No issues when connected to router at work, but have connected two other, albeit older android devices to home router without issues.
home router is dlink dir655
Click to expand...
Click to collapse
Try WPA2 Personal TKIP+AES
Craptain Krunch said:
Try WPA2 Personal TKIP+AES
Click to expand...
Click to collapse
Thanks, forgot to mention the router is already set to TKIP+AES.
However, upon confirming this morning, it is set to auto WAP/WAP2. Will try WAP2-only tonight, unless this won't make a diff?
bo8 said:
Thanks, forgot to mention the router is already set to TKIP+AES.
However, upon confirming this morning, it is set to auto WAP/WAP2. Will try WAP2-only tonight, unless this won't make a diff?
Click to expand...
Click to collapse
WPA/WPA2 decreases the bandwidth of the router. WPA2 will support a full 300Mbps link state. So yea, they are different, but it may not fix it.
I have a Cisco EA6500, so I'm connected to the AC 5Ghz band, and it works flawlessly. WPA2 Personal
My bad on typing WAP instead of WPA.
Doesn't sound like fully opening up the bandwidth will fix it.
Has something to do with how the phone manages the encryption keys?

Categories

Resources