I flashed Calkulin's GB ROM and flashed the latest FD19 modem. It wouldn't connect, so I flashed back to the EL29. Still no luck. So I figured, what the heck? I'll go ahead and flash an ICS ROM. So I flashed Calkulin's ICS and still no luck.
But wait, there's more!
I don't think this is a problem with the ROM. Why, you ask? Because I can connect to my neighbor's unsecured Belkin router no problem! Also, it's happened over two ROMs and three modems. And doubly also, I had the same problem with my Transformer. And tripply also, the thread for neither ROM is lighting up with people having this problem.
I'm using an AT&T 2Wire, so to fix this, I have tried the following:
Change the broadcast channel on the router (this is what solved the problem on the Transformer).
Change the IP range on the router.
Restart the router from a browser.
Physically unplug the router for a few minutes.
Disable and then re-enable wireless from the router.
Someone suggested clearing the DHCP table, but I don't think you can do that on a 2Wire.
And... still no luck. I have to believe that this is not all that uncommon.
Has anyone else dealt with something like this?
For the record:
Calkulin's E4g 2 v1.4
Modem: EL29
Kernel: 3.0.15-SPH-D710.FD02-CL336391
Again, I don't think t's the ROM.
Is your network password protected with WEP or WPA? If it is then delete the network from your phone and add it back. Should connect after a minute or two. I have to do this pretty often when flashing between roms.
If you've already done this then I'm at a loss.
Loremonger said:
I flashed Calkulin's GB ROM and flashed the latest FD19 modem. It wouldn't connect, so I flashed back to the EL29. Still no luck. So I figured, what the heck? I'll go ahead and flash an ICS ROM. So I flashed Calkulin's ICS and still no luck.
But wait, there's more!
I don't think this is a problem with the ROM. Why, you ask? Because I can connect to my neighbor's unsecured Belkin router no problem! Also, it's happened over two ROMs and three modems. And doubly also, I had the same problem with my Transformer. And tripply also, the thread for neither ROM is lighting up with people having this problem.
I'm using an AT&T 2Wire, so to fix this, I have tried the following:
Change the broadcast channel on the router (this is what solved the problem on the Transformer).
Change the IP range on the router.
Restart the router from a browser.
Physically unplug the router for a few minutes.
Disable and then re-enable wireless from the router.
Someone suggested clearing the DHCP table, but I don't think you can do that on a 2Wire.
And... still no luck. I have to believe that this is not all that uncommon.
Has anyone else dealt with something like this?
For the record:
Calkulin's E4g 2 v1.4
Modem: EL29
Kernel: 3.0.15-SPH-D710.FD02-CL336391
Again, I don't think t's the ROM.
Click to expand...
Click to collapse
This may be a silly question but have you setup the connection again? Every time I flash a new ROM I always have to search for the network again and re-enter my password.
Verify the Password
Well, I decided to try one more thing and disabled network security. Voila! Connected in less than a second. So then, when I turned network security back on, I remembered that I had recently changed the password.
So here's my word to the wise today. If you're having trouble connecting to a Wi-Fi network, make sure you're using the correct password.
Thanks for the replies, though.
Related
Moved from Development section and added more information.
I have a Desire with customized Rom with Data2Ext. I can connect my WiFi. But when I go to somewhere (let's the WiFi disconnect) and come back, my Desire can connect to WiFi without any problem but I can't access my network.
More information is as below:
1. from my pc, I can't ping to my phone.
2. the configuration seems good in my phone(busybox ifconfig).
3. from phone, can't ping to the net gate.
Andriod 2.2
Baseband: 32.54.00.32U_5.14.05.17
Kernel: 2.6.32.15
Internal Version: 2.29.405.5
I tried to shutdown the network interface and to bring it up again to see if some issue happens during starting up. But I couldn't shutdown that interface.
Everything is ok if I turned off my WiFi and turned on again.
Looks like some settings were not reseted when connection was back.
Anybody can help me in this case?
Try a diffrent rom. One without D2EXT etc. Use a almost stock i.e. Leedroid.
So you can be sure that its not about your hardware.
Flashmaniac said:
Try a diffrent rom. One without D2EXT etc. Use a almost stock i.e. Leedroid.
So you can be sure that its not about your hardware.
Click to expand...
Click to collapse
Actually, this version is a almost stock ROM. Maybe it's something related to router definition.
I will try another router to see if the problem still exists.
does your phone acquire an address from the router? could be a lease-time issue, or DHCP issue
EranSa said:
does your phone acquire an address from the router? could be a lease-time issue, or DHCP issue
Click to expand...
Click to collapse
For the 1st question, my answer is yes. I could see the address and I also could see the route via terminal. But from my phone, I could not able ping to the network gate.
Lease-time issue, it could be. Don't know, how to confirm that?
DHCP issue, seems not.
Today I updated my ROM from LeeDroid v2.5 to v3.0.8.2. I wiped my phone first. After this I rebooted, then rebooted again into recovery and installed the recommended radio (32.56.00.32U_5.17.05.08). Then I restored my apps+dat with Titanium back up and rebooted again.
It soon became apparent that whilst mobile internet was working fine, WIFI wasn't. While my phone will connect to the router it won't connect to the internet. If I enter the local IP of my router I can browse the settings fine. I tried "forgetting" the network and re-entering security code but this still didn't work.
I restored my v2.5 nandroid backup and the internet worked fine, the radio is still 32.56.00.32U_5.17.05.08.
So I did a fresh install of the v3.0.8.2 ROM and tried connecting to WIFI again and again the same problem.
So my question is, is this an inherent problem with the ROM, and if so why does no one else seem to have this problem, or is it a setting issue?
Any help would be much appreciated.
Also I tried changing the WIFI channel as suggested in another WIFI thread, and this didn't change anything. Except the WIFI channel obviously.
And I tried a static IP address and that didn't work either.
Ben81 said:
Today I updated my ROM from LeeDroid v2.5 to v3.0.8.2. I wiped my phone first. After this I rebooted, then rebooted again into recovery and installed the recommended radio (32.56.00.32U_5.17.05.08). Then I restored my apps+dat with Titanium back up and rebooted again.
It soon became apparent that whilst mobile internet was working fine, WIFI wasn't. While my phone will connect to the router it won't connect to the internet. If I enter the local IP of my router I can browse the settings fine. I tried "forgetting" the network and re-entering security code but this still didn't work.
I restored my v2.5 nandroid backup and the internet worked fine, the radio is still 32.56.00.32U_5.17.05.08.
So I did a fresh install of the v3.0.8.2 ROM and tried connecting to WIFI again and again the same problem.
So my question is, is this an inherent problem with the ROM, and if so why does no one else seem to have this problem, or is it a setting issue?
Any help would be much appreciated.
Also I tried changing the WIFI channel as suggested in another WIFI thread, and this didn't change anything. Except the WIFI channel obviously.
And I tried a static IP address and that didn't work either.
Click to expand...
Click to collapse
You try turning off router and putting back on again? I sometime's get that in my network.
Yes I tried turning my router off for a couple of minutes then switching it back on. Didn't change anything.
Ben81 said:
Yes I tried turning my router off for a couple of minutes then switching it back on. Didn't change anything.
Click to expand...
Click to collapse
Did you sort it?
I think you need to wait before the router give your router assign an ip for your phone, btw, some router donot fit all phone model
Yes thanks I managed to sort it today by following this thread
Apparently the fault is inherent to Android 2.3.3 and seems to present itself mainly with Thompson routers. It was a static IP I needed, I'd not entered the details properly the first time.
Thanks for the replies!
Ben81 said:
Yes thanks I managed to sort it today by following this thread
Apparently the fault is inherent to Android 2.3.3 and seems to present itself mainly with Thompson routers. It was a static IP I needed, I'd not entered the details properly the first time.
Thanks for the replies!
Click to expand...
Click to collapse
Thats good
Hi all. I have searched and nothing pertains to my problem.
I upgraded to a new rom (coredroid 7.1), and even going back a rom version my wireless keeps logging in and then disconnects for no apparent reason. It doesn't even pick up the IP address. Show's 'connecting' then 'disconnected' straight after. The one radio i have used has worked flawlessly.
Any ideas on what is going on?
Philosofical said:
Hi all. I have searched and nothing pertains to my problem.
I upgraded to a new rom (coredroid 7.1), and even going back a rom version my wireless keeps logging in and then disconnects for no apparent reason. It doesn't even pick up the IP address. Show's 'connecting' then 'disconnected' straight after. The one radio i have used has worked flawlessly.
Any ideas on what is going on?
Click to expand...
Click to collapse
It can be a kernel issue... some kernels are not compatible with certain routers to get info from them to connect. Try flashing a different kernel and see the results.
Ah I tried a new radio and Kernel but it still does the same thing. Rebooted the router and reinstalled my phone rom as well and nothing changes with the problem.
try flashing a rooted stock rom. if still cannot connect, i hope you're still under warranty and send it back to htc
Ah well after flashing a new radio and kernel then reflashing the rom, it decided to work again after I changed the channel on the router....... Confused yet? I was. So thanks for your help it's now working fine.
I just unbricked my phone by following the newest directions I found, you may remove that topic if reading this (sorry). Wifi was the issue I was trying to resolve when I did brick it. Ever since EH17, I downgraded (or tried to) to EC05 and get back on Syndicate, and now Wifi will not work except with DI18. Any update through Sprint, done from files from here, etc will result in non-working wifi. It always worked before, even with EC05. I have a Linksys E3200 with WPA2 security. Anyone have any ideas how to fix that? It always sits at "obtaining IP address"
I just got the phone back on EH17 in Syndicate, was still no luck (wasn't working in stock EC05 either). Now I go to EH17 Hurricane (where it last worked other than DI18 stock) low and behold, wifi works again! So how come now I can't downgrade to EC05 and still have it? What could be causing this?
Damn so many ppl are having this problem
I had a help req on this fourm with 2 weeks of bumping and no luck
But i figured how to fix it
Step 1 find your windows computers ip through cmd prompt
Type ipconfig
Your ip should be accross from gateway ip or something like that
Step 2 copy and paste ip into web browser
Step 3 login
Default password is admin
Leave username blank
Step 4 play with options till you can find factory reset or something like that
Step 5 press it
Step 6 ????
Step 7 profit
Sent from my SPH-D700 using xda premium
Im putting the last 2 steps in respect to noobnl
Plus i thought it was cool
Sent from my SPH-D700 using xda premium
You are saying to reset the router. Unfortunately the router really is not the issue considering the phone can and will connect, but only with DI18 or EH17. Not even a stock (unroot start from scratch) EC05 will make the wireless work right. It just sits at obtaining IP.
Chilinmichael said:
You are saying to reset the router. Unfortunately the router really is not the issue considering the phone can and will connect, but only with DI18 or EH17. Not even a stock (unroot start from scratch) EC05 will make the wireless work right. It just sits at obtaining IP.
Click to expand...
Click to collapse
Instead of doing a factory reset on the router, you could try just unplugging for 30 seconds and plugging it back in for a soft reset. It is possible an ip address is locked up or something in the router. Also for the changing of the modem, did you just Odin the modem.bin file? Can you explain the steps you did when upgrading/downgrading, etc...
Sure. I'll even go back to when I first rooted.
Was at Stock EC05, everything worked perfectly.
Rooted with Clockwork mod Purple, Added SyndicateROM Frozen 1.2 and Genocide 2.0 Kernel, everything worked great.
Saw ACS EH17Plus Kernel and Hurricane 1.5, decided to give that a shot, worked great.
Decided to upgrade the modem to EH17, used ODIN, did successfully. The only issue I had was the very seldom "random" reboot once going to EH17.
After trying for a while, missed a few features of Genocide/SyndicateROM Frozen. (Voodoo control, GalaxyTuner, etc etc). Wiped Data x3, Wipe Dalvik x3. Went back to that and noticed no wireless IP obtained.
ODIN modem to EC05, since I knew that worked, but no luck, still same.
Factory reset (after a brick somewhere along the lines, forgot where after) to DI18, wireless worked again!
Let Sprint auto-update to EC05 OTA, wireless stops working right again once at EC05.
Flashed up to EH17/EH17PLUS Kernel/Hurricane 1.5, wireless works right again.
I tried for the hell of it, to go back to SyndicateROM Frozen 1.2 and Genocide 2.0 but still, wireless will not work right.
So the only options that work for me are DI18 stock or EH17. Strange eh?
*Edit: I'm not even removing the above due to my own stupidity. I took your advice and soft rebooted the router, I don't even know how it would allow connection with certain software and not with others, but the phone is connected fine now on stock EC05. I have a COMPTIA A+ certification to boot. Sad day for me lol.
Chilinmichael said:
Sure. I'll even go back to when I first rooted.
Was at Stock EC05, everything worked perfectly.
Rooted with Clockwork mod Purple, Added SyndicateROM Frozen 1.2 and Genocide 2.0 Kernel, everything worked great.
Saw ACS EH17Plus Kernel and Hurricane 1.5, decided to give that a shot, worked great.
Decided to upgrade the modem to EH17, used ODIN, did successfully. The only issue I had was the very seldom "random" reboot once going to EH17.
After trying for a while, missed a few features of Genocide/SyndicateROM Frozen. (Voodoo control, GalaxyTuner, etc etc). Wiped Data x3, Wipe Dalvik x3. Went back to that and noticed no wireless IP obtained.
ODIN modem to EC05, since I knew that worked, but no luck, still same.
Factory reset (after a brick somewhere along the lines, forgot where after) to DI18, wireless worked again!
Let Sprint auto-update to EC05 OTA, wireless stops working right again once at EC05.
Flashed up to EH17/EH17PLUS Kernel/Hurricane 1.5, wireless works right again.
I tried for the hell of it, to go back to SyndicateROM Frozen 1.2 and Genocide 2.0 but still, wireless will not work right.
So the only options that work for me are DI18 stock or EH17. Strange eh?
*Edit: I'm not even removing the above due to my own stupidity. I took your advice and soft rebooted the router, I don't even know how it would allow connection with certain software and not with others, but the phone is connected fine now on stock EC05. I have a COMPTIA A+ certification to boot. Sad day for me lol.
Click to expand...
Click to collapse
I am glad it worked for you!! It was probably just a simple IP conflict! And we ALL have days like this!
Yes, but the funny thing was I went into my Router's DHCP reservation before this and cleared out the lease for the MAC of the phone and it still hadn't worked! Once I noticed my printer was having an issue as well I figured something just got messed up in the router's memory or what have you. Once I did the soft reboot, everything worked thank god. It was just the strangest thing that the phone would connect using Gingerbread or it's original DI18 but no other setup. Guess I'll never have an answer better than a (at the time) dysfunctional router.
my phone did hang on the obtaining ip and on every build but other devices would connect
give it a shot
it worked for others too
I've searched far and wide for an answer and I can't find anything conclusive. I'm trying to use a PPTP VPN connection on my phone SGS II. The connection requires MPPE encryption and I can connect but afterwards the connection fails/drops/timeout after about 3-4 minutes. I am on ICS 4.0.4 (darkside). Does anyone have a conclusive answer to why the VPN connection will drop when I am in an area with full service? I have tested all the radio's available and deduced it is not a service/radio issue. It seems to be possible an issue with the kernel, or ROM, but again I am not sure. I'm at wits end trying to get this to work.
shatterpoints said:
I've searched far and wide for an answer and I can't find anything conclusive. I'm trying to use a PPTP VPN connection on my phone SGS II. The connection requires MPPE encryption and I can connect but afterwards the connection fails/drops/timeout after about 3-4 minutes. I am on ICS 4.0.4 (darkside). Does anyone have a conclusive answer to why the VPN connection will drop when I am in an area with full service? I have tested all the radio's available and deduced it is not a service/radio issue. It seems to be possible an issue with the kernel, or ROM, but again I am not sure. I'm at wits end trying to get this to work.
Click to expand...
Click to collapse
Here is an update incase anyone experiences the same issue.
In my testing I re flashed the darkside ROM I had a few times to be sure it was not a dirty flash. I also switched Kernel's from tdj's to faux. Neither step worked. So I flashed a new ROM (infamous resurrection) it comes with its own Kernel as well. After flashing IR I have been able to maintain VPN connections via PPTP w/ MPPE encryption. I can't conclusively say if it was ROM or Kernel related but my issue is resolved. If anyone is ok with ICS and needs to use a VPN connection the Infamous Resurrection ROM is the one I'd pick.