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.
I can't connect to my corporate wifi. The following process worked on my Kindle Fire, and dozens of phones of others in the office:
Add a new connection with hidden SSID
EAP = PEAP
Phase 2 = MSCHAP (not MSCHAPv2)
CA Certificate (got it, installed it, not expired)
domain\usr
pwd
Run WiFi Advanced Configuration Editor
Key Mgmt, uncheck WPA-EAP (IEEE8021X checked)
Enterprise Configuration, re-enter pwd.
Turn WiFi off, back on.
Ignore the SSID secured with WEP.
Done.
This process does not work on my 8GB Nexus 7. I've done the process enough times on my KF and other people's phones to know I'm not doing it differently on the N7. Yet, it doesn't connect. Ever. I sit right across from the AP. Also, I had someone else who's done this a dozen times before also try. No dice there either.
Any idea why I can't get connected?
<noob_shield>I found no (meaningful) results searching this forum for "wifi certificate" and a few other searches.</noob_shield>
Are you in a domain and running through a proxy server? If so try just joining the network normally using your domain\uname letting the cert install automatically then long holding the wifi connection modify connection check advanced then add the proxy settings, worked for me...
Sent from my Nexus 7 using xda app-developers app
_DrG_ said:
Are you in a domain
Click to expand...
Click to collapse
Yes, there's a domain. I'm using my domain acct as the identity/password
and running through a proxy server?
Click to expand...
Click to collapse
No proxy server.
If so try just joining the network normally using your domain\uname letting the cert install automatically
Click to expand...
Click to collapse
The SSID is hidden. I have to start by manually adding the network. Considering that I can't get to connect to that network at all, I'm not sure how to go about "joining the network normally." I'll try it without specifying/bringing my own certificate, and see if one is installed automagically. IIRC, iPad users don't have to manually copy the cert onto their tablet.
I'm having the same issue connecting a Nexus 7" on Jelly Bean to our wifi using a cert. I'm using the exact same settings I use on my Droid Razr Maxx (running ICS) and it connects no problem. If I figure it out I'll post up, but I have a feeling it's a Jelly Bean issue. On ICS when I install a cert it no longer shows in storage, however on Jelly Bean after installing it leaves the cert in storage. Not sure if maybe its not installing it completely, or if that's just how Jelly Bean will do it on all devices. Another thing I noticed is it strips the name of cert, whereas in ICS it leaves the cert name assigned. I'm going to mess around with it now.
This has been discussed and determined to be most likely a jelly bean issue.
Sent from my Nexus 7 using xda app-developers app
Lame answers from Google and ASUS
I tried to get the corporate network connectivity issue resolved through support at Google and ASUS. Google's response was to ask my IT guys to, "use mac filtering on the router". ASUS's response was to reset the tablet, when that did not work, Russell on their support line said that, "the Android OS does NOT support 802.1x EAP on the Nexus 7". This seems like a deal-breaker for the Nexus 7, buyer beware.
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).
I rooted and flashed my phone last night and everything was fine other than 1 thing. The Wi-Fi wouldn't connect on my home router. I tried several different roms and was left with the same problem where it was stuck on either obtaining ip address or authenticating. I then came into work this morning and the phone connected to my Wi-Fi network straight away.
Does anyone know how I can get around this problem, don't want to be using up all my data at home!
Thanks in advance
Dont get me wrong but did you try to restart the Router?
Sent from my HTC using XDA Windows Phone 7 App
Timzter said:
I rooted and flashed my phone last night and everything was fine other than 1 thing. The Wi-Fi wouldn't connect on my home router. I tried several different roms and was left with the same problem where it was stuck on either obtaining ip address or authenticating. I then came into work this morning and the phone connected to my Wi-Fi network straight away.
Does anyone know how I can get around this problem, don't want to be using up all my data at home!
Thanks in advance
Click to expand...
Click to collapse
I second the other suggestion. Those symptoms sound like your router needs a restart if it hangs at getting IP/authenticating.
I'm having the same problem on the network at my university.
I'm having problems with my wifi as well. We have a network here at my office secured with WEP. My galaxy nexus connects to it just fine but my Nexus 4 refuses. It sees the network, show strong signal but it doesn't seem to connect. I did manage to get it to connect once and I downloaded some updates but then the connection dropped and will not reconnect. I've tried various advanced settings (forcing the network to 2.4GHz, changing the power options, etc... No joy. This is particularly frustrating for me as my micro sim has not yet arrived so WiFi is all I have Hopefully it will work at home. At least there I have access to the router so I can make changes if needed. So far not a fan though.
I've got WiFi problems here, too. Roaming between different WiFi networks (home and university) often results in an non functional WiFi connection. Experienced this problem with stock Android 4.2 on Nexus 4 and Galaxy Nexus and latest CM 10.1 nightly on Nexus 4. Even reboot doesn't help every time.
As workaround: If WiFi connection is broken, turn on "flight mode", wait a few seconds and turn it off again. Works for me, maybe it works for your problems too.
I literally just received my nexus 4, and I haven't done anything with the SIM card yet, I just wanted to get things going on WiFi to start. It sees the network I want, let's me type in the password, and lets me click connect. After that it does literally nothing. No thinking, no obtaining IP address, nothing. Any ideas?
dyslexicpenguin said:
I literally just received my nexus 4, and I haven't done anything with the SIM card yet, I just wanted to get things going on WiFi to start. It sees the network I want, let's me type in the password, and lets me click connect. After that it does literally nothing. No thinking, no obtaining IP address, nothing. Any ideas?
Click to expand...
Click to collapse
I have exactly the same problem. Got the phone today and have tried several different access points - no luck. Restart the phone, no change.
Also, system updates screen said I could only download the update to 4.2 from a wifi connection till the 7th, so i set the date to the 7th and did the update successfully over the cell connection. Still no WiFi. Factory reset - no change.
---------- Post added at 09:18 PM ---------- Previous post was at 09:17 PM ----------
Oh, also tried the flight mode "trick" with no success.
Heartbreak said:
I'm having the same problem on the network at my university.
Click to expand...
Click to collapse
Your uni wifi probably is LEAP wifi or PEAP wifi, which is proven broken in Android 4.2
ecsk said:
Your uni wifi probably is LEAP wifi or PEAP wifi, which is proven broken in Android 4.2
Click to expand...
Click to collapse
It's also broken on my campus. Do you have any suggestions to bypass this?
ecsk said:
Your uni wifi probably is LEAP wifi or PEAP wifi, which is proven broken in Android 4.2
Click to expand...
Click to collapse
My university provides both LEAP and PEAP authentication. LEAP doesn't work for me either. But PEAP works. I'm able to connect via PEAP. (Stock 4.2 / 4.2.1 and CM 10.1)
Here is my log. It appears the authentication is timing out.
12-07 10:42:43.863: I/wpa_supplicant(19563): wlan0: Authentication with xx:xx:xx:xx:xx:xx timed out.
12-07 10:42:45.345: I/wpa_supplicant(19563): wlan0: Trying to associate with xx:xx:xx:xx:xx:xx (SSID='XXXXX' freq=2447 MHz)
12-07 10:42:45.385: I/wpa_supplicant(19563): wlan0: CTRL-EVENT-ASSOC-REJECT bssid=xx:xx:xx:xx:xx:xx status_code=1
12-07 10:42:55.346: I/wpa_supplicant(19563): wlan0: Authentication with xx:xx:xx:xx:xx:xx timed out.
All other devices do connect fine and I even restarted the AP to make sure.
This is getting very frustrating. I couldn't connect to wifi at work (WEP, I know...) at all yesterday. I went home, and my WPA2 network at home worked perfectly. I come in this morning and boom, I'm connected just fine to the wifi here at work (the connection was remembered from my tries yesterday). I went to lunch, came back, no wifi. Reboots, reconnections, nothing seems to work. I also have a Galaxy Nexus with 4.2.1 and it connects to the wifi just fine. Grumble grumble....
-Matt
I did a few tests today and it seems to be only when using WPA2 with a pre-shared key. WPA works, as do open AP's.
jim.k.yee said:
It's also broken on my campus. Do you have any suggestions to bypass this?
Click to expand...
Click to collapse
No solution with stock google image AFAIK, because google does not provide 4.1.2 image for Nexus 4. You can try other custom ROM or ask if some one has successful LEAP wifi story about running custom ROM.
BTW I don't own Nexus 4, I am stilling using Galaxy Nexus, as soon as I upgraded to 4.2 LEAP wifi broke, I flash 4.1.2 back then it works fine.
I found that upgrading the access point (MikroTik) to the latest version allows me to connect.
Seems something in this device does not like some older WPA2 versions?
extremewing said:
I found that upgrading the access point (MikroTik) to the latest version allows me to connect.
Seems something in this device does not like some older WPA2 versions?
Click to expand...
Click to collapse
My N4 has been connecting fine to my home router over the past two days. Suddenly, today, it stopped recognizing the network (shown as "not in range" in wifi settings). No amount of router or phone reboots would get it to connect. I read in another forum about going to Displays in the settings menu, scroll to bottom - Wireless Displays. Turn on and search for wireless displays, then turn off. I thought, wtf? Anyway, I tried this and it connected to wifi immediately. Maybe there's a bug in the wireless display function that's interfering with wifi.
I am actually having a similar issue as others here, but I have found another weird work-around. Basically, although the Nexus 4 see's my campus's network, no packets get transfered back and forth, and I am not even sure what is going on (The IP address, tho, is usually "unknown".) However, upon going to the campus's IT help today, they turned off mobile data, and it then seemed to connect fine over Wifi. Any idea what is going on here?
There is no "signing in" to the network at my university, it just connects and verifies your device's MAC address, so I don't think they are doing any fancy authentication. I was thinking about maybe flashing a different ROM and seeing if I get different results.
i got mine yesterday and it connects then stops connecting after a couple seconds
Atrag said:
I am actually having a similar issue as others here, but I have found another weird work-around. Basically, although the Nexus 4 see's my campus's network, no packets get transfered back and forth, and I am not even sure what is going on (The IP address, tho, is usually "unknown".) However, upon going to the campus's IT help today, they turned off mobile data, and it then seemed to connect fine over Wifi. Any idea what is going on here?
There is no "signing in" to the network at my university, it just connects and verifies your device's MAC address, so I don't think they are doing any fancy authentication. I was thinking about maybe flashing a different ROM and seeing if I get different results.
Click to expand...
Click to collapse
I get exactly the same issue in my office. I can connect to school open network, but after a few minutes it lost connection (while still showing connected). I got to wifi setting, it shows that there is only one wifi hotspot and i am connected to it. But actually there should be more than five hotspot! If i switch wifi off and back on it can detect all the networks and get connected again, but then it goes to the weird cycle over and over.
Strangely, if i stayed in another office, it is connected all the time. Seems like the signal problem in my office. But i got no problem in my office when i was using galaxy nexus.
I am driven crazy by this!
Guys, recently bought a Nexus 4 and it normally connects via wifi but can not connect.
I was using the Android 4.2.2 OTA updated to Android 4.3 and the problem persists.
The Nexus 4 connects normally, but the icons of wifi connection and carrier signal are gray instead of blue and even trying to install applications via Google Play or simply access a site via browser do not work and accuse the connection fails.
I was tested and the router's signal is good and other equipment that I usually work (other Android smartphones and notebook).
My router is standard G and I use WPA2.
viamais.net said:
Guys, recently bought a Nexus 4 and it normally connects via wifi but can not connect.
I was using the Android 4.2.2 OTA updated to Android 4.3 and the problem persists.
The Nexus 4 connects normally, but the icons of wifi connection and carrier signal are gray instead of blue and even trying to install applications via Google Play or simply access a site via browser do not work and accuse the connection fails.
I was tested and the router's signal is good and other equipment that I usually work (other Android smartphones and notebook).
My router is standard G and I use WPA2.
Click to expand...
Click to collapse
all routers?
i got the same issue but only on a particular router at home but worked perfectly elsewhere
i ended up changing the router
csara said:
all routers?
i got the same issue but only on a particular router at home but worked perfectly elsewhere
i ended up changing the router
Click to expand...
Click to collapse
Oddly enough, I have the Nexus just 3 days and only had access to the router so far from home, but today I'll look for a router to test the public.
But either way it's frustrating the Nexus 4 have these compatibility issues when connecting to a wifi router.
Before making the switch router, is it not possible to find out which configuration of WLAN could cause this? Does Google do not have this documented?
i feel your pain, been there
it could be your router, from the way it assigns ip addresses to your type of encryption. by any chance is it a linksys G router? that was my problem before until i just decided to get an N router.
did you try switching to WEP or open to see if the problem persists? or changing your gateway ip address? or changing which ch your wifi is on?
never hurts to try
Should factory reset your router and upgrade firmware first, then immediately connect to it without encryption and see if it work.