Related
I've had the captivate about 24 hours now and dig it. I've rooted it and remove the att bloatware (per titanium backup), I've also performed a backup using Rom Manager.
I'm having trouble getting it up and running on an enterprise wireless what uses 802.1x PEAP authentication. I can get through all the auth. steps, and the device is assigned an IP, but I am unable to do anything that requires an internet connection; browser, market, etc.
Has anyone else ran into this issue?
*****EDIT*****
sigh i just realized that this is in the wrong area, it should have been over in development...i'm an idiot
I had a similar problem on a WEP-encrypted network, which I fixed by setting a static IP on the phone and then setting it back to DHCP (the correct setting). However, your problem could be entirely different than mine (not that I even am sure what my problem was, just that I fixed it!)
Best of luck!
Having the same problem on enterprise access points regardless of encryption. Home wifi netwroks work great (open and WPA2). Enterprise APs (open and WEP) connect and give me an IP, but will not transfer data. Think its a driver issue with the Wifi, it happens on every captivate ive tested, and seems to be more widespread than the GPS issue.
I have had the same issue with my work at work. I can get it to connect and get a ip but can not pass any data.
Sent from my SAMSUNG-SGH-I897 using XDA App
Had the same problem at work. Luckily I'm an admin and figured mine out. Our monowall portal was the issue. I can give a detailed answer for my problem tomorrow when I get to work.
I actually had the cap wiped to go back, then I literally figured out the problem. Thanks go out to my team mate for helping me talk through this.
Sent from my SAMSUNG-SGH-I897 using XDA App
can't wait to hear what your fix was!
Sent from my SAMSUNG-SGH-I897 using XDA App
This sounds more like your network not being allowing your device rather then the device having an issue.
it's been frustrating as I know two other guys with android devices that didn't have an issue. one is a droid eris running 2.1 and the other is a nexus one running 2.2.
Sent from my SAMSUNG-SGH-I897 using XDA App
designgears said:
This sounds more like your network not being allowing your device rather then the device having an issue.
Click to expand...
Click to collapse
Worked closely with my highly experienced network admin in my dept. for an afternoon (we had some time to kill). He checked the firewall and dhcp servers, ran packet traces, etc.
With what I'm experiencing, its the device. These wifi networks we use with Cisco APs are completely wide-open. All other phones and mobile devices have always worked great for years. We rely on this network for many custom applications and mobile tools.
Once the dhcp server leases an address, it seems like the radio stack hangs, and the device ceases communication. Here's an older thread on the exact issue over at androidfouroms: http://androidforums.com/samsung-captivate/130403-wifi-terrible.html
I have tested multiple new unmodified captivates and the issue is identical accross the board.
Now that I am at work, and have coffee in me and not beer, I will go through the problem I had with miCap and works wireless. Due to my skeptical ways, I will be semi vague for security purposes. On with it.
When I originally got miCap (pet name for it) I was able to access our public wifi. It allowed me into the public portal to agree to terms. I played a little bit on it, but wanted to see if I could access our private wifi. I got in the private no problem. But after that I never was able to get back on to our public. It did the same thing as I've read. It got an ip no problem (via dhcp) and acted like all was well. No browser, or ap could get a connection. The phone would not switch over to 3g to get info.
Armed with ip and mac address, my co-worker and I started to did through our monowall. ( He also has a cap that had no issues on public or private). We try tried reserving the ip for miCap, didn't work. We tried static ip, didn't work. I spent the morning completely wiping miCap to get it back to return worthy.
This was when I decided on last ditch effort.
Our ap's are cisco's that connect into monowall. I got into monowall and dug around. I found that with in the captive portal (how fitting) that the ip/mac associated with my phone hadn't checked in for 8 days. Even though I tried everyday. I deleted the entry to the phone there and suddenly my phone was getting access again.
Now I understand that this may not help everyone, because setups vary from place to place. But digging deeper into configurations at the access points may be what is needed. Do I think the phone had nothing to do with it? No, I think it helped aggravate the problem.
We have had problems with the Intel 3945abg chipsets with the same exact setup. That problem was fixed with driver updates on the laptops.
sorry for the long winded reply.
So in a nut shell you deleted the DNS entry for that ip/mac in the firewall and you are working.
Pmac25 said:
So in a nut shell you deleted the DNS entry for that ip/mac in the firewall and you are working.
Click to expand...
Click to collapse
Essentially yes. But it is not listed like that in the portal. Hmmm. I wonder about the combo of dhcp/dns being the culprit.
I was able to resolve this issue by changing my connection settings from DHCP to static for the Cisco APs.
Installing WiFi Buddy from the market allowed me to access these connection settings.
I just used an address from our static IP pool.
Manually set IP, subnet, gateway, and DNS, and now im finally rolling on our enterprise wifi network
I sent a help ticket into samsung; maybe if enough folks do we can get it on their radar.
jhannaman82 said:
I was able to resolve this issue by changing my connection settings from DHCP to static for the Cisco APs.
Installing WiFi Buddy from the market allowed me to access these connection settings.
I just used an address from our static IP pool.
Manually set IP, subnet, gateway, and DNS, and now im finally rolling on our enterprise wifi network
Click to expand...
Click to collapse
you can set the ip manually with out an app. When on the wifi screen, hit menu-advanced. This is a good time to set the wi-fi sleep policy also.
phlunkie said:
you can set the ip manually with out an app. When on the wifi screen, hit menu-advanced. This is a good time to set the wi-fi sleep policy also.
Click to expand...
Click to collapse
Thanks for that, i figured the menu was built in somewhere just never found it.
:thumbsup:
UPDATE
So I flashed the i9000 Eclair rom last night, and when I got into work today I can connect and use the wifi here. So looks like something AT&T buggered up, big surprise there, when they "customized" the captivate.
As much as I normally love blaming AT&T for problems, that can't be done here. My Captivate (running Stock Firmware) connects just fine to my work network. We use 802.1x with PEAP/MSCHAPv2 for authentication.
Anyone been able to connect at over 802.11b speeds while connected to an 802.1x network? I show connections at G and N speeds on my WPA2 network but nothing over 11Mbps on 802.1x.
Sent from my SAMSUNG-SGH-I897 using XDA App
Hi,
I am also having problems with my work wifi network.
It is 802.1x, on TTLS/PAP it also requires a thawte premium server ca certificate insalled.
Is there any way to connect this kind of networks?
With my previous iphone 3g it was taking only 4-5 seconds.
Hi, in case this has been already solved I apologize in advance, however I searched all the post on this and could't find real solution to my problem and from what I have read I am not alone...
The think is that if I install any build of Androud to my Leo everything works perfect except the WiFi connection - after enabling WiFi and pointing it to my router it recognizes it, accepts the password (WPA-PSK protection) and then after some time of getting IP it never connects and it goes on and on.
I tried every single thing I have found all around this forum and many others, unfortunatelly nothing could make it work (forcing static IP, opening the network without protection, changing networks SSID, leaving WiFi on and restarting, etc.)
It is really pitty as I really like the way Androind moves on HD2, but as I use the Wifi a lot to unload a bit my data plan I cannot stick with it at the moment. So, is there any real solution to this problem?
Thank you in advance.
I have the same problem. But the connection is fine when I was under Winmo.
The only time I've experienced a similar issue was when I upgraded to a new kernel, without pushing the new modules. What builds and kernel are you using?
Sincerely,
Mac
Try updating your builds or just modifying the mac adresses
I already have this issue when upgrading or changing build. I resolved the problem with Airplane Mode. switch on/switch off. Let us know the result. ^^
I was having the same problem. It wouldnt connect to my home network, but it would connect to every other network. Turns out my router was too old. I recently got a new router and it works fine. Also, when I had my G1, it also wouldnt connect to my home network via wifi, but it does with the new router.
wangshuokevn said:
I have the same problem. But the connection is fine when I was under Winmo.
Click to expand...
Click to collapse
On WinMo no problem.
white-energy said:
Try updating your builds or just modifying the mac adresses
Click to expand...
Click to collapse
As I wrote before, I tried many different builds with no succes. At the moment I installed MCCM SE V3.4(FroyoStone Sense)[kernel hastarin r8.5]. As I have nothing to save I do everytime clean install on reformated card.
lamario said:
I was having the same problem. It wouldnt connect to my home network, but it would connect to every other network. Turns out my router was too old. I recently got a new router and it works fine. Also, when I had my G1, it also wouldnt connect to my home network via wifi, but it does with the new router.
Click to expand...
Click to collapse
IMHO the router is not the problem even it's a bit outdated - Linksys WRT54GL - as I tried to connect to friend's network, I also created AP from my notebook - with the same result.
hatchy77 said:
I already have this issue when upgrading or changing build. I resolved the problem with Airplane Mode. switch on/switch off. Let us know the result. ^^
Click to expand...
Click to collapse
The Airplane mode you toggle in WinMo or Android? I tried it in WinMo - no success.
oh yes...
... I know this kind of problem.
Tried so many builds of Froyo. Most wlan-stable was indeed MCCM SE V3.4(FroyoStone Sense)[kernel hastarin r8.5] - with this build I had no wifi drops or hsdpa drops.
From today on I try the MDJ FroYo HD v.4.1[kernel:MDJ S7.3HD]. Most time it holds the connection, but sometimes when waking up from stand-by I have to disconnect and reconnect wifi.
Router: Linksys WRT54G.
mac-nukem said:
... I know this kind of problem.
Tried so many builds of Froyo. Most wlan-stable was indeed MCCM SE V3.4(FroyoStone Sense)[kernel hastarin r8.5] - with this build I had no wifi drops or hsdpa drops.
From today on I try the MDJ FroYo HD v.4.1[kernel:MDJ S7.3HD]. Most time it holds the connection, but sometimes when waking up from stand-by I have to disconnect and reconnect wifi.
Router: Linksys WRT54G.
Click to expand...
Click to collapse
Thanks for the answer, unfortunatelly I have nothing to drop as I cannot connect. On the other hand either EDGE and HSDPA works like charm - solid connection.
snekoza said:
The Airplane mode you toggle in WinMo or Android? I tried it in WinMo - no success.
Click to expand...
Click to collapse
Into Android my friend
I also had this problem. It's easily solved by loging into your router and setting up the access list (under adv wireless settings on mine). You can add the device in with its specific mac address and by doing this I was instantly able to use wifi.
It's not an issue with mac address filtering. I know this issue because I have the same problem with the wifi router at the office. I can connect without any problem at home but It just won't work at the office.
DHCP server assigns an IP, but if you try to ping any IP outside LAN you'll get network unreachable.
I didn't have time to test a bit more, but I'll try to change the mac address of my wlan in order to test if the problem relies in there. The idea is to assign the same MAC Adress I have on WinMo. This will be very useful also to people with 2 HTC HD2 using the same ROM and Kernel.
BTW, I'm not using MAC Address filtering, this issue has nothing to do with it.
I have the same problem here ..
Please help me buddy!
thank you in advance
hassohd2
I tried this switching in and out of Airplane mode in Android with varying degrees of success. The problem itself seems intermittent for me - sometimes I get a decent amount of time with successful access and sometimes I don't. Similarly a reboot (of Android) may or may not work for me. I am using kernel version 2.6.32.15-gd09adbb gcc version 4.4.0 and is dated Thu Dec 30 19:14:35 CET 2010 for me. I notice I am more inclined to have an issue with Market even than with Firefox. Also it is more of a problem now than with a previous kernel version (but it had problems too if I recall correctly). I upgraded because I am having difficulties with getting the USB link to work under Android (but that problem is still there). It did seem to work well for the first few hours after the upgrade, but since then...
I did notice that under MS WM, the MAC address is quite different to that recorded by my DHCP server (a unix box the other side of my wireless router) for Android. The Android one looked like it was a stock standard number sequence, so fabricated. I wonder where that is set on the phone?
I also noticed that the phone does not have the usual (for Linux) resolv.conf file that often gets configured by the DHCP connection process. Further, entering a host IP in the /etc/hosts file does not necessarily mean that a command like ping will find it every time. Of recent I have not been checking that - I have been using the IP address of my unix box to do ping tests to. The network does (of course) shut down when the phone goes into sleep mode, but does wake up, even responding to a ping from the unix box. Running up Market, though, seems to kill the connection every time now (but a weather update won't).
A further observation: if I get the Wi-Fi network connection to reset itself (straight forward when the lease expires), it is hard to get it to reset itself until after the next lease expiry for some reason.
I did some further tests. I don't have a pipe (|) key on my HTC HD2 that works so the following commands are a little long winded.
localhost / # getprop > /data/tmp/props
localhost / # grep dns /data/tmp/props
[net.change]: [net.dnschange]
[dhccp.eth0.dns1]: [192.168.10.1]
[dhccp.eth0.dns2]: []
[dhccp.eth0.dns3]: []
[dhccp.eth0.dns4]: []
[net.dns1]: [192.168.10.1]
[net.dnschange]: [49]
localhost / #
Now 192.168.10.1 is my (Unix) DNS server.
When I do the following on the phone
localhost / # nslookup 192.168.10.1
(or even localhost / # nslookup cicada or even the fqdn of the server)
and I tail -f /var/tmp/named.log on the server (where I set up logging for queries and resolver categories for this test)
I see no action at all on the server and on the phone I get
localhost / # nslookup 192.168.10.1
Server: 192.168.10.1
Address 1: 192.168.10.1
Name: 192.168.10.1
Address 1: 192.168.10.1
localhost / #
localhost / # nslookup cicada
Server: 192.168.10.1
Address 1: 192.168.10.1
nslookup: can't resolve 'cicada'
localhost / #
and the same for the FQDN.
The DNS server does not even see the request for forward or reverse lookup, strangely enough. But it is seeing the requests from other machines with logs to the reverse lookup from those other machines looking like:
10-Jan-2011 22:21:57.953 queries: info: client 192.168.10.20#38971: query: 1.10.168.192.in-addr.arpa IN PTR +
So, not only does the wi-fi link drop when Market is run, the DNS is behaving strangely to terminal based testing. Further, an update of the weather does not show any traffic in the DNS server log (at least for the logging level I have set up) even though the weather does get updated. It makes me wonder what DNS it is really using.
The other avenue I want to check is DHCP time-out, which I have been keeping an eye on (it does seem to time out and not update, but there are also other issues that suggest the problem is not a time-out one). That will have to be another day at this stage, though.
what channel is the router using for wifi?
My Wifi connected to my home router perfectly until I flashed the custom rom.
Now it wont work. the phone recognizes my network, then tries to connect but it pauses at the obtaining ip address bit and doesn't connect?
I tried to restart the router. It doesn't work.
I tried to reflash the rom or offical rom (KE7). It doesn't work.
I also tried to delete the file /data/misc/dhcp/dhcp_list, but there are no "dhcp_list" file inside 'dhcp'
Do anyone have another way to solve this problem?
Thanks
Could be a problem with the router, are other devices able to acquire IP addresses from it correctly?
Perhaps you should assign a static IP to see if that makes a difference.
I am on KE7 stock rom with root and had this problem too. It just started yesterday and got stuck at obtaining ip adress. So I switched WIFI off and flight mode on and after some seconds wifi on and flight mode off and it connected. I also noticed that now sometimes when it is in standby it disconnects from the wifi network (but wifi is still ON) and when I wake it up it connects to my network.
Me too, same problem.
If wifi is ruled on "sleep when screen turn off", it don't wake when screen turn on.
It stay on " searching for IP adress...".
For the moment, I'm forced to leave wifi on "never" and I use Juice defender for disabling wifi on screen off.
I really think it's a common pb with SGS 2. May be it will be fixed with 2.3.4.
Same problem. I 'fix' it by turning off wifi then turning it back on and it gets an IP address immediately.
same problem here with a dlink dir-615 router. from time to time the phone can't get an ip, and it only works if i reboot the router. didn't try with another router yet ( well, i connected to a few more but not frequent so i can see if there are problems), but i ordered a new one anyways since the dlink also crushes my battery too.
try posting the brand/model of the router you have problems with, maybe there's some specific ones that are troublesome.
d-link dir-615 here / ke7 stock - rooted
I also have a dlink router. But I get the same problem with a Belkin.
With my first SGS, no problem. I really think it's a specific issue on SGS2.
I'd read in some place that 2.3.4 will fix some wifi problem known for the moment on 2.3.3...
Let's see...
I'm seeing this with both my home router (Netgear WNDR3700) and my office router. Disabling & re-enabling WiFi on the SGS2 solves it -- fortunately, it's easily accessible on the notifications panel.
Same thing with Dlink dir 815.
Sent from my GT-I9100 using XDA Premium App
Same thing here with Draytek 2820 router, all other devices (PC's Phones, PDA's etc) have no problem. SGS2 however needs WiFi turning off when waking from sleep to get it to obtain an IP address again. However my HD2 also running Gingerbread 2.3.3 works faultlessly.
KF2 seems, for me and some others, fix the problem...
hi
lucky me, i thought im the only 1 having problem with wifi
my problem, same as the others
the wifi try to connect (obtaining IP) and then disconnected
it will scan again, same thing will happened
try with all type of protocols, wifi b,g,n wep, wpa, no passwd
results still same
try to connect wifi at my office, results also the same
im on KF1 using dlink 615
hopefully someone can help us
tq
Just got my Galaxy S2 today. Cannot connect to wifi network on G or mixed mode, with or without security - just tries to obtain an IP address. Ridiculous.
Any help ? Quick search on Google doesn't bring up too much. There does seem to be an app called "FXR Wifi" but I don't expect to use that on a brand new phone.
Update: Upgraded my router's firmware (WRT54GS) and it works !
I have the same problem with my SGS 2. I can't connect to an AP - NETGEAR DG834G.
I found a partial solution to use my phone with my AP until I solve the problem. In the Wi-Fi settings menu enter Advanced mod and set the IP address, Gateway, Netmask, DNS1 manualy (by touching <Use static IP>). If you don't know what IPs you have to set for IP address, Gateway, etc. just connect with you laptop or desktop and use the settings from your computer. Just make sure you type a different IP address in your mobile (not the one from your computer - for example in you computer you'll find something like this: 192.168.0.3, you'll have to type in your mobile something like this: 192.168.0.10). The rest of the settings have to be identical.
Good luck!
To solve this "obtaining ip address problem". Set the following manually in the advanced configuration and save it.
1. ip address(your choice).
2. subnet mask(255.255.255.0).
3. default gateway(192.168.1.1).
4. dns servers(8.8.8.8,8.8.4.4)
Note: The above given values are the most commonly used, you change it if you want so.
After entering these values manually(and correctly), it will connect to the networ in 1 or 2 seconds.
like mine SG s2, wifi connects works perfectly at home and friends place,
but stucks at obtaining ipaddress for wifi, at the mall and college, ( where it needs first login page for authentication) ( or to agree user terms and regulation),
any idea, how to fix this issue.
Thanks
mine also does this where it doesn't get an ip. Reboot your router or just disable and re-enable the access point feature on the router and it should work without having to reboot it
Sent from my GT-I9100 using Tapatalk
but at university?college or mall, we dont have access to router.
any other idea to fix this
Thanks
Hey guys! Did you find a fix for this problem? I have the same thing happening right now. I tried at different places, home and country house with Zyxel P660HN and Cisco E4200 respectively. Stuck at obtaining IP address...
XSCounter said:
Hey guys! Did you find a fix for this problem? I have the same thing happening right now. I tried at different places, home and country house with Zyxel P660HN and Cisco E4200 respectively. Stuck at obtaining IP address...
Click to expand...
Click to collapse
Search xda with 'wifi rare' and 's2 wifi not working'.. U can find few threads dealing with wifi problem..
Sent from my GT-I9100 using XDA Premium App
hi everyone, some days ago I installed the virtuous 1.6, than replaced with a rooted stock 3.1. Since then, when I disconnect from my wifi for a while, getting far away from my router, it happens that coming back into the wifi field the tablet tries to reconnect but after 4 or 5 times it stops trying and tells me the connection is disabled. I see the dhcp service bouncing, no ip assigned. The only solution I've found googlin' around is to rename/delete the file dhcpcd-wlan0.lease in /data/misc/dhcp. It worked. but the issue got back again and again. I wanted to find out the cause and solve the problem once and forever, if possible. It's a pain in the... you know
Here is my topic. There is also one solution to it apart from the one you've found in google (which was probably my topic anyway ).
You're right, it'was your post. I've read it againg but I can't find out which could be the alternatrive solution. Keep in mind that when I got this wrong behaviour the first time obviously I invesitgated the possible causes, and I discovered the inability to retrieve a dhcp IP address either with my wifi router, with my wifi access point 3g and with a tethered connection via Iphone (all of them I normally use when I'm not at office). None of these would work until the uplisted file deletion). Would you be so kind as to suggest me, if you can, the possible solution in more detail (apart from performing a global reset that would be as annoying than deleting the file)
In any case, many tnx for your answer
Currently the common solution is to abandon the leaked 3.1 rom or put up with the bug.
Manually setting DHCP also works but it's usefull only if you'll use the tablet on one wifi. Else it's just a big pain in the arse.
I have same issue with the stock 3.1 rom.
At the end what I did was manually assign IP address for my iPhone's MyWi connection.
It seems mine has no trouble to connect to my home wi-fi network as well as work...
I also get that problem. But now, seems to have fixed it. I have done the followings:
- delete the dhcp lease file
- change the channel of my wifi router to 9 or below
- download the ad-hoc supported wpa_supplicant
Please try if above help you
Honestly I have no idea why this is happening on my android 4.0+ devices. I will get stuck on obtaining IP address connecting to certain networks and the only thing that worked for my home network is static IP. But for instances when I don't have access to the router to know what the static IP should be, is there a way to get this working? This happened on my phone as well. I was at a local cafe which had wifi and before I upgraded my samsung galaxy s2 to ICS, I could connect to their wifi no problem, now it has the same issue, and so does my Nexus 7. I don't know what to enter for static IP, I entered some random IP, it connected but internet still didn't work. Why is this problem plaguing ICS onward, and does anyone have a workaround when static IP is not an option?
This is definitely not a universal problem (I've never heard of it before). Are you running stock roms? If not, then do you have these problems with stock roms?
C2Q
Why are you posting this to multiple threads?
There is no "proper way" to use a static IP for a router that is setup for DHCP only. For routers that use both, many times the static IP's are reserved for specific devices.
Sent from my Nexus 7
Because I didn't notice the other thread before I posted this one. Anyway then why is this obtaining IP address loop a problem on ICS? As I said, my phone on GB would manage to connect/obtain an IP address just fine before I upgraded to ICS. This happened with my home router and other areas as well. The solution that worked for me at home was to assign a random static IP within my routers IP range. But if I don't know the gateway IP this won't work. So what gives? I'm kind of confused what you mean by routers set up for DCHP only. If I use static or DCHP options on the android device to connect, they will both work (this was before ICS).
I ran into similar issues with my nexus 7 and my work open wifi. It needs you to connect to a web login page where you accept a use policy before you can surf. My nexus would connect but never redirect to that login page.
The issue was resolved by using static IP instead of DHCP and also by changing the DNS values to DNS1 8.8.8.8 and DNS2 4.4.8.8
Changing those settings lets me finally use my work wifi. My phone also has the same issue (its an ICS phone, whilst the nexus is jelly bean) but is not resolved with this change.
Sunburn74 said:
the issue was resolved by using static IP instead of DHCP and also by changing the DNS values to DNS1 8.8.8.8 and DNS2 4.4.8.8
Click to expand...
Click to collapse
Sure that is not 8.8.4.4 ?
Thanks for posting this question. I have exactly the same problem with my Samsung S3 (ICS) and Nexus 7 (Jellybean). My old Samsung S2 (Gingerbread) worked fine.
I am trying to connect to a hotel open network. When I try I get the looping "Obtaining IP..." message. I have a strong network signal.
What gives? How come earlier versions of Android worked but later ones don't?
As the OP stated, the static option works insofar as I can then connect to the network but the made up static IP numbers do not actually let me download (or upload) data. As the OP wrote, you need to know some valid values for the static IP setting.
Does anyone have a solution for this (apart from downgrading to Gingerbread)?
Ive always had this issue but my home router has dhcp off. A majority of routers start with 192.168.1.1 or 192.168.1.2 so its not hard to work it out.
BT routers always start with 192.168.1.254 so there's another option dunno why my devices do it but im used to it. My Wifes Xoom 2 and wildfire S are stock and do not have the issues my rooted ones do but i have just put it down to coincidence
First off. Is your modem in service? Do other devices connect? Have your restarted your tab? Does it connect to other networks? Meaning going to another WiFi hotspot If you can answer yes to all of these questions we move on....
What modem/router are you connecting to?
What type of WiFi encryption are you using? Wep-open, WPA, wpa2-psk
On the tab does it fail to obtain the IP address? Meaning it says "remembered"?
Not going to lie more the 3/4ths of the time you have the wrong WIFI PASSWORD. CHECK IT AGAIN usually its on the modem/router or if you have no clue here is a hint: on windows vista and windows 7 under control panel>network and sharing center>manage WiFi networks if your right click on the network name such as "Ilovepancakes"and go to properties it will have a security tab that you can click on and show password.
Sent from my Nexus 7 using XDA Premium HD app
bonesy said:
Ive always had this issue but my home router has dhcp off. A majority of routers start with 192.168.1.1 or 192.168.1.2 so its not hard to work it out.
Click to expand...
Click to collapse
I don't know what you mean. Do you mean that I should try these numbers to see if they work? You need a number of values to set up static IP addressing to work.
Did you dirty-flash your Nexus? A while back my Gnex wifi connections would take longer to complete the handshake. I did a factory reset/fresh install & it has been much faster.
strongergravity said:
Did you dirty-flash your Nexus?
Click to expand...
Click to collapse
My Nexus (and GS3) is completely stock (I have only added a launcher).
This problem seems to be caused by older routers, which don't seem to like something about newer versions of Android.
I'm not sure if it's something Google can fix, but the combination of old router and new Android seems to make logging onto wi-fi networks a problem.
Bump.
Ive been struggling with this problem for a week now since getting a transformer infinity. My s3 gets stuck when I try to connect to it. The tab cycles through connecting, obtain a valid address and saved.
I bought a new 32gb nexus yday and had this issue. I entered advanced settings, changed dhcp to static. Changed IP addy to 192.168.1.1 and it worked fine. Only had to do it once. After that it connected to every network fine without changing settings again.
Sent from my Nexus 7 using xda app-developers app
Warrior1975 said:
I bought a new 32gb nexus yday and had this issue. I entered advanced settings, changed dhcp to static. Changed IP addy to 192.168.1.1 and it worked fine. Only had to do it once. After that it connected to every network fine without changing settings again.
Click to expand...
Click to collapse
This worked for me also (Infuse 4G on JB), but it seems like this is only a problem on WiFi AP's that have marginal signal strength, even though they appear to have full bars. I personally have never have seen this issue on a network that was performing properly.
Same here!
Same thing is happening to me! Im using he htc desire c running ics.. my phone detects the wifi network, shows that it has excellent strength, but it gets stuck at "Obtaining IP Address"! My friend and I both bought the same model a couple of weeks earlier and till now neither of us have been able to connect to a wifi network! Please Help!!!
its a DHCP bug
This is probably not a problem with your network configuration unless it works everywhere else; im having the same problem as well as other people i know and its definitely a bug with DHCP, so the only way to work around this is by using a static ip as far as i know
bobbyelliott said:
I don't know what you mean. Do you mean that I should try these numbers to see if they work? You need a number of values to set up static IP addressing to work.
Click to expand...
Click to collapse
What he's saying is that most routers will begin assigning addresses starting with 192.168.1.1 or 192.168.2.1 for itself (you can access the router configuration page by typing in this address into a web browser), and then increment upwards afterwards. If you knew that the router started its DHCP addressing with 192.168.1.1, for example, you could try 192.168.1.2, and so on and soforth.
If you did a "dirty" upgrade, I'd recommend doing a factory wipe (after an appropriate backup-- there are some good apps out there that can handle this). In-place OS upgrades have a bad habit of being finicky. Android is also generally less tolerant of network "misconfigurations" than, say, Windows, OS X, or iOS. Many networks that use captive portals (your standard coffeeshop Wi-Fi) deliberately use an altered network setup to support their access policies, such as a captive portal.
However, with the exception of corporate/enterprise networks (which may require fine-tuning because of increased security), you really shouldn't be messing around with this if you don't have at least a rudimentary understanding of how networking works. That's not meant to be insulting, but when people plug in random values and find it doesn't work, it tends to lead to more frustration than utility.
(fyi: The reason you can "connect" by tossing in a random set of octets your your IP and DNS is because you've properly authenticated against your router, but you'll never be able to receive data unless your router's DHCP lease lines up with your self-assigned IP, because the router never handed that address out to you. It's the digital equivalent of building a mailbox in front of your house without registering with the post office, and wondering why you never get mail).