There is an issue I'm having with the Kindle fire & 3rd party roms which also happens to be a LONGstanding issue with wifi connectivity I've had in the past.
Specifically, devices I've owned, like the kindle here will not connect to a wifi router in our house. It has wpa2 which I am not about to remove. The kindle in stock form will connect to it, running energy rom & Miui will not. Now I know their are caveats with these roms and I accept that but I would like to know what specifically is causing the issue. The device will see the router and get stuck at the "obtaining IP address" part. Each time, without fail, gets stuck in the same place. Ive used 3rd party utilities in the past to try and connect but no luck.
FWIW: I have a router in the basement, also with wpa2 security and devices NEVER have a problem connecting to that, I repeat NEVER! I have a phone, LG Thrill which has never been able to connect to the problematic wifi spot, even with stock firmware.
The problematic router is a Airport Time Capsule, latest gen. The one in the basement is an older gen airport extreme.
Have you tried connecting with static IP, netmask, etc settings? Have you tried turning off encryption for troubleshooting purposes? Do you know what channels the two access points are using?
Sent from my Kindle Fire (CM7) using xda premium
No guarantees, but something you could try is:
Make sure IPv6 is disabled on the AirPort Time Capsule. IPv6 uses multicast instead of broadcast for DHCP addresses and as seen in the UPnP thread, multicast breaks all the cm9 based KF roms at the moment.
jd
Related
Just picked up my TF today, updated to 3.1
I have a main router at my house and two bridged repeaters (dd-wrt) sending the signal everywhere so I have coverage. Here is the strange issue:
I can connect via wifi just fine to my main router, but I can't to either repeater. The TF says I am connected, but the wifi symbols stays gray, and doesn't connect to the internet. Other devices connect fine to the routers, even my droid 2 global has no issues.
Anyone else experiencing anything like this? Strangest wifi bug I've ever experienced, i'm stumped.
I've tried the following:
Channel Changes
Open security
Router Reboots
Any advice would be appreciated!!!
just tried connecting to my dd-wrt for the first time reading your post, and it worked fine... I am running prime 1.4 if that happens to have anything to do with it.
Have you tried static IP on your TF?
dan-htc-touch said:
just tried connecting to my dd-wrt for the first time reading your post, and it worked fine... I am running prime 1.4 if that happens to have anything to do with it.
Click to expand...
Click to collapse
A repeater? Or direct router?
I have tried static ip, no avail.
I also have an annoying wifi issue as well. When my transformer comes out of sleep it seems to be connected to the wifi but I can't surf the net. I need to turn-off wifi and turn it back on to make it properly work.
Using Prime ROM v1.4 and the wifi uses WPA.
I should have also mentioned, that despite being "connected" I still cannot visit the router gui via the TF's browser...
alansgabriel said:
I also have an annoying wifi issue as well. When my transformer comes out of sleep it seems to be connected to the wifi but I can't surf the net. I need to turn-off wifi and turn it back on to make it properly work.
Using Prime ROM v1.4 and the wifi uses WPA.
Click to expand...
Click to collapse
+1... I am annoyed with this as well...
mine is a bridge, with it's own ssid
still can't figure it out
I'm considering flashing to prime 1.4 to see if that will help. does anyone know if there are different wifi drivers on prime 1.4 vs stock 3.1?
thx
Have you tried flashing the latest firmware to you repeaters?
alansgabriel said:
I also have an annoying wifi issue as well. When my transformer comes out of sleep it seems to be connected to the wifi but I can't surf the net. I need to turn-off wifi and turn it back on to make it properly work.
Using Prime ROM v1.4 and the wifi uses WPA.
Click to expand...
Click to collapse
Same issue was happening to me on stock rom. I changed WiFi disconnect policy from "Never when plugged in" to "Never". The issue is now gone but battery goes a little quicker now...
Do you know if you have an access list setup on your router? Your access list maybe bllocking your tf from connecting
The first thing I would do in your case, OP, is to disable all security, mac filtering, passwords, etc and see if the Asus will connect or not.
I'm using Prime 1.4 and have no problems connecting to my wifi network using WPA2.
I have...
(1) - Verizon Fios - Main router - no wireless broadcast - DHCP on
(2) - Linksys E2000 - DD-WRT - wired ethernet to main router - broadcasting SSID - DHCP off
(3) - Linksys E2000 - DD-WRT - wired ethernet to main router - broadcasting SSID - DHCP off
Unfortunately, I'm not doing the wireless bridge repeater mode but I haven't noticed anything particularly different about the Asus's wifi.
My wifi is always on, I don't use any of the battery saving modes.
figured it out
After trying a bunch of various resets and google searches, it turns out that the only way for me to connect to a bridged router is by using static ip's and making sure the dns was set to find my main AP.
Its strange that i would have to go through so much manual setup, when all other devices work just fine.
I know there has been wifi problems with others, but I think my problem is diffrent. For me it is only one router and it works for a while but then wont connect and displays an error. If I reboot the router it will work again. It may work for an hour, it may work for 5 minutes, it may work for several hours before I need to reboot again. I have connected my fire to many other routers and all work fine, even my phones tether works fine.
Router is a Netgear 3G Router (MBR624GU). The firmware is up to date.
Side issue: The XDA App crashes ALOT on my fire, does it on anyone elses?
zenopzz said:
I know there has been wifi problems with others, but I think my problem is diffrent. For me it is only one router and it works for a while but then wont connect and displays an error. If I reboot the router it will work again. It may work for an hour, it may work for 5 minutes, it may work for several hours before I need to reboot again. I have connected my fire to many other routers and all work fine, even my phones tether works fine.
Router is a Netgear 3G Router (MBR624GU). The firmware is up to date.
Side issue: The XDA App crashes ALOT on my fire, does it on anyone elses?
Click to expand...
Click to collapse
Do the other devices that are connected to the router drop connection? what is your network config ?
your problem seems not to be involving the b/g/n mix mode so i could only guess that your ip is dynamic. many people resolved this problem by making their ip's static.
I don't have a kindle yet, i was about to buy it but the wifi problems are freaking me out
i don't want to go to a hotel with a b/g/n router or dynamic IP and my kindles wifi stop working.
Sounds like this is a router problem, not a Fire problem. It should probably be moved to a another forum.
The only time I have ever seen this problem was when the router was on its way out and needed to be replaced.
I've been using home routers for about 10 years now and I have had this problem with three of them. Two were linksys and one was a netgear.
I think the best way to test this out is to try a different device on the router, but from the symptoms it sounds like it's going to happen despite it being a kindle or some other device.
michaelkourlas said:
Sounds like this is a router problem, not a Fire problem. It should probably be moved to a another forum.
Click to expand...
Click to collapse
no its a kindle fire problem , had mine for 6 weeks, we instalied a new wi fi router all other devices work on router , kf is erratic , some days better than others now has gone off all together will not connect to wi fi , my son is a computer engineer we have been on to amazon website there are hundreds of people with same problem ,tomorrow am going to various wi fi hotspots to see if it connects there , we live in south africa ,i joined this site as i am considering rooting the kf and this looked like best site , i just dont know now i was hoping to find a thread on the problem or hoping rooting the kf would solve it, its now a choice of returning it to the 3rd party on line store for warranty or rooting it , any help or advice would be appreciated
If you are on stock you need to go to advenced settings and set it to 14 channel (Japan) or on the router you switch to a channel below 12
Sent from my Nexus S using XDA App
Currently trying to use my motorola droid as a wifi tether for my kindle fire. Kindle has CM7 installed and connects perfectly to my belkin router with WPA/WPA2. I am using Barnacle Wifi Tether app. If I am persistent I might get it connected every so often but for the most part the kindle is stuck trying to obtain an IP address over and over again. Slightly more luck if I have no encryption present but it is still spotty at best. Have searched forum for related thread but have had no luck. Would appreciate any help or a nod in the right direction.
Fixed by switching to wireless tether app and changed channel to 6. Kindle needs a reboot every so often but it is not required as frequently.
Have same problem on CM7 and CM9, nothing helps, only static ip using, but this is not oprion for me
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've seen some chatter about this buried in other threads, but I wasn't able to locate a dedicated thread...so if there is one, sorry about a duplicate post.
So I have a Nexus 7 and a Galaxy Nexus phone and both have this issue. The issue has occurred in multiple environments with multiple routers/networks.
Basically, the wireless on the N7 and both the wireless & cell on the Galaxy Nexus go gray but show as connected with a strong signal. However, there is no IP traffic being routed. The devices have an IP address, and show correct DNS and default route locations and the wireless symbols even show data moving (the little bidirectional arrow deal) but nothing actually happens on the device.
Some have said this means you are not connected to Google's services like Gmail and what-not, but that isn't the case either as you can't ping from the device nor can you go to any websites in the browser, get new mail, get web data for other web enabled apps, or in the case of the phone, get text messages or phone calls.
The only *fix* I've found is to turn off wireless, wait a minute, and turn it back on. This can be really annoying when you have to do it 5-10 times a day on the tablet and it really sucks when you find you miss calls, texts and emails on the phone.
I notice this has never occurred with any of my other Android based devices or iOS devices. This would lead one to believe it has something to do with Jelly Bean and perhaps some background task crashing or something.
Does anyone else experience this? If it were just my phone or just the N7 I would think I had a defective device, but since they both display similar behaviors at different times with different routers on completely different networks, it seems more software related since the only thing in common is that they are both Android 4.1.x devices (it happened on 4.1.1 and now 4.1.2).
I would love to know if there is a real fix for this somewhere!
I fixed mine by getting a new Netgear router...
Sent from my Nexus 7 using xda app-developers app
rmm200 said:
I fixed mine by getting a new Netgear router...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Again, it happens with multiple routers from the lowly Linksys to Netgear to D-Link to Checkpoint and several more. This is NOT a router issue.
I was having to power off my Linksys router several times a day to allow dropped devices to reconnect again. What happens when you power cycle your router?
Sent from my Nexus 7 using xda app-developers app
What router settings and security method are you using? WEP, WPA? try changing the channels on your router or something
From what I experienced, it is connected to the router but somehow the router has lost net connection. Rebooting DSL modem fixes it for me. I have DSL connection here in Philippines, the telco provided a zyxel dsl modem. From the DSL modem I have Tomato flashed router. Rebooting the DLS modem fixes without rebooting router or the n7. In N7 from gray it turns blue and i can see the up / down arrows, net access is working.
I get the impression that my request/question was too long as it seems people are not really reading. Either that or they are not getting it because they either never experienced the problem, or because they don't take their N7 around like I do so they think it's connected to their home router.
This problem happens at about 8 different sites. Every site has a different router and a different internet connection from DSL to cable to T1.
This problem happens with both my N7 & my Galaxy Nexus and not at the same time at the same site.
I do appreciate people trying to help, but this clearly isn't a router issue but rather it is an Android issue. Focusing on the router really isn't helpful because there is nothing in common. Even the encryption varies from open networks like at a coffee shop, to WEP (yeah...seriously) to WPA to WPA2.