So, I'm deployed right now and I got the N7 3G specifically so I could tether to my computer and phone. After getting the device and realizing that it did not have native tether I rooted it and flashed it with the image(?) I found here.
http://forum.xda-developers.com/showthread.php?t=1995737
Everything went smoothly and I thought I was good 2 go. When I attempt to log on with my devices I get a IP address conflict. My computer (WIN7) is smart enough to manually assign itself an IP and connect to the internet but nothing else will. It's driving me nuts. Obviously, I can only imagine that it is something to do with the DHCP. I would have posed this question on that thread but based on not having posted before I did not have the permissions. Thank anyone ahead of time for any help.
Still no luck. I've reapplied everything multiple times and nothing. I've also flashed the monoco(?) rom hoping that their tether would work but nothing. Only thing I haven't done is factory restore and start from scratch. This is really sucking. I'm looking for any suggestions. I'm sure 90% are more experienced then I am with this. I have absolutely no programing knowledge.
Sent from my Nexus 7 using xda app-developers app
Hmmm. Yea its DHCP from your Nexus handing out IPs. I'm not sure what your DHCP RANGE is but it should be a pool of about 10 IPs. If your Range is only set to 1, then it will only hand out one.
Oddly there aren't any options on my Galaxy Nexus (I don't have a 3G N7).
What I would do is take your other devices and tap and hold on your tethered WiFi network and select forget. Disconnect everything completely and forget all settings. Change your WiFi Tethered name.
Try to connect one at a time before moving to the next. The devices keep the connection settings in memory and will try to use the old IP address they used before.
This could also be a bug with the tether section also. Most roms share the same development features.
Sent from my Nexus 7 using XDA Premium HD app
No luck
Sent from my Nexus 7 using xda app-developers app
Related
I rooted my phone the other day and I'm loving it but signal sucks at my girls house so I need wifi but it won't connect. It picks up the network and lets me ebert the password but that's it. I know it's not a computer problem because my itouch and laptop connect fine. Can someone give some advice please?
-------------------------------------
Sent via the XDA Tapatalk App
Put in...not ebert sorry.
-------------------------------------
Sent via the XDA Tapatalk App
money226 said:
I rooted my phone the other day and I'm loving it but signal sucks at my girls house so I need wifi but it won't connect. It picks up the network and lets me ebert the password but that's it. I know it's not a computer problem because my itouch and laptop connect fine. Can someone give some advice please?
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Still most likely a router problem, wifi works fine with root installed, try connecting to a different wifi access point (at your home, or work, etc.) if you still have problems then troubleshoot the phone, before then...
Often times Routers will have issues with one device and not another, I've had plenty instances where my computer connected fine to my wifi, and then my laptop could not. Usually hard reset on the router works (unplug the router and plug it back in). Often times it has to do with a corrupt cache, (your mac address for devices connected is stored temporarily on the router, there are times when this caching gets corrupted and actually prevents you from reconnecting) The same applies to devices connected. If you have the access point saved on your phone, delete the saved access point, and reconnect.
As a side note, I think this was a better post for Q&A and not development thread.
i'm an idiot. thought this was in reference to the wifi tethering thread. my bad.
Thank you, resetting the router worked and now I'm connected. I agree this would have been better in another section but I posted here since I thought it may have been related to root since it was fine before but thanks again.
-------------------------------------
Sent via the XDA Tapatalk App
So I have noticed that as of late, when connecting to some access points, my xoom takes an excessivly long time scanning and authenticating the network, and will not connect. Other times it will connect in the correct fashion. I have verified pass code and IP settings. Anyone have advice?
Sent from my Xoom using XDA Premium App
I have seen the same thing on exactly one other wifi hotspot, while traveling. I thought it might be something in the way that the AP was configured due to the fact that my 1.6 phone would not connect either while my wife's Win7 netbook connected immediately. I thought that they must not ike Android.
Its possible the routers were out of IPs to assign. A common problem I find in hotels is that they set really long, or indefinate lease times and people come and go and they run out of IPs to assign.
Sent from my HTC Desire using Tapatalk
I think you may be on to it there.... the times I notice odd behavior is when a significant number of devices are connected...
Sent from my Xoom using XDA Premium App
Hi All:
I recently bought a Nexus 7 in addition to my year old TF101. I am having problems accessing the internet (via wifi) on both devices at the same time. For example, if I were using the TF101 while turning on the Nexus, the Nexus would not be able to access the internet (all connections would time out). The LAN works on both devices at the same time so it is not a problem with the router. Internet access would start working on the Nexus a few minutes after I turn off the TF101. I am using the same Google account on both devices. Could that be causing the problem? Any suggestions to resolve the issue would be much appreciated.
Thanks. .. KS
Its a not the Google account. I am currently in logged in on 3 devices. Chances are your router is set to only allow you one wifi device at a time, Some are like a that. Try Google your router's, make to find instructions how to change it.
Sent from my GT-P6210 using xda premium
Thanks. It was indeed related to the router... somehow the 2 tablets were using the same static IP but they were shown to have been assigned different IPs when I checked inside the router. Now resolved and working well.
OK this is really pissing me off. Everyone time I go on my nexus device it doesn't automatically connect to the WiFi.. I have to either disable the WiFi and reenable it. Or just click on my network and click connect (it says its saved but doesn't automatically connect when I turn on my device), i tried everything from forgetting every saved network, restarting me device, ect, and its not my routers problem, my DNA connects automatically when I turn it on. Any of you guys had this problem? If so what did you do to fix it?
Sent from my Nexus 7 using xda app-developers app
what router? My nexus 7 is fine and so is my sgs1.
No idea what router I have but that's not the problem, problem is that when I turn on my nexus and get passed the lockscreen, the WiFi would normaly automatically connect. It for some reason stopped doing that and it gets really annoying manually connecting
Sent from my Nexus 7 using xda app-developers app
kernel
PhantomsWay said:
No idea what router I have but that's not the problem, problem is that when I turn on my nexus and get passed the lockscreen, the WiFi would normaly automatically connect. It for some reason stopped doing that and it gets really annoying manually connecting
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
try to change your kernel. the wifi drivers are in the kernel...
Running stock, never changed my ROM or kernel
Sent from my Nexus 7 using xda app-developers app
You could try a different channel on your router
Sent from my Nexus 7 using xda premium
PhantomsWay said:
OK this is really pissing me off. Everyone time I go on my nexus device it doesn't automatically connect to the WiFi.. I have to either disable the WiFi and reenable it. Or just click on my network and click connect (it says its saved but doesn't automatically connect when I turn on my device), i tried everything from forgetting every saved network, restarting me device, ect, and its not my routers problem, my DNA connects automatically when I turn it on. Any of you guys had this problem? If so what did you do to fix it?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hi,
I share the same problem. Upon a reboot, it will work normally for a while.
Once they symptoms starts, it will refuse to connect most of the time. When it does connect, it will disconnect within a couple of minutes. WPS wont respond either. toggle wifi/airplane mode does not work either.
The only way is to reboot.
However, I did have some findings but couldnt get it fixed! Do this and test if it works for you as well:
Go to terminal (needs to be rooted device):
Simply select the "Take wifilock/B]" option and it will stay connected!
Release it and it will get disconnected and back to the same issue.
Hopefully some experts can give us some pointers?
Temporary fix
I have the same problem. This is what i did to fix it: Settings- Wifi settings- advanced- switch always on to Never, reboot in recovery, clear cache, reboot your device and go back and turn Wifi back to Always on. this is a temporary fix because if you reboot or shutdown your device, you will need to redo the steps. this is a known problem with google's 4.2 jellybean. we need an update soon!
hope it helps you.
Thanks for your help
Sent from my Nexus 7 using xda app-developers app
It won't be much comfort to you, but remember that "it takes two to tango".
Yeah, there's IEEE standards for all of this stuff. Do interop problems still happen? All the frigging time, every day. Sure it is maddening.
And sometimes the problems only manifest themselves with an exact pair of firmware(s) releases between the AP and the client device. I had a WiFi router that would gladly talk to four or five unique types of devices; on the sixth - an Android phone - it would associate & authenticate successfully, but the client device would never get an IP address.
That sure sounds like a problem with the phone, doesn't it?
How did I fix the problem? I upgraded the firmware ... on the router !
Sometimes problems with intermittent connections can be rectified by fooling with things that you might think have no bearing on the problem. For instance, some routers will accept connections in A/B/G/N mode. Do you need all of those? If not, simplify your router's behaviors by disabling non-essential features, e.g. select G-only or N-only.
That's just an example - but the point is that the fewer behaviors either of the devices engage in, the lower the probability that the bug which is shared between them will get expressed.
So, you can either fool around with both devices, only one of them - changing one setting at a time to see if that alters the behavior you observe, or you can throw one device away and start all over with new combinations of devices. The router probably has more knobs which can be turned than the phone does (unless it's not your router, or you don't control it).
Good luck
Just got the phone today (upgraded from a Sensation 4G).
This phone connects to my home WIFI fine.....and then once it sleeps for around 10 minutes and I wake it up, the wifi connection is gray (instead of blue) and I cannot access anything on the internet. I have to disable WIFI on the phone and re-enable it and it's fully functional again.
What's going on? Fully stock, 4.2.2
I do notice the IP it's pulling is a 172.27.35.x.....whereas my network is configured as 192.168.0.x
What's going on here???
cybertlc said:
Just got the phone today (upgraded from a Sensation 4G).
This phone connects to my home WIFI fine.....and then once it sleeps for around 10 minutes and I wake it up, the wifi connection is gray (instead of blue) and I cannot access anything on the internet. I have to disable WIFI on the phone and re-enable it and it's fully functional again.
What's going on? Fully stock, 4.2.2
I do notice the IP it's pulling is a 172.27.35.x.....whereas my network is configured as 192.168.0.x
What's going on here???
Click to expand...
Click to collapse
When I manually enter in my network settings (rather than DHCP) and set it as a 192.168.0.x value......everything is fine.
What's going on where it's pulling these 172 values? Never had an issue like this. Thanks!!!
Have you unlocked the Developer Options yet? If not, goto Settings -> About Phone then tap build number 10 times to unlock. Enable "Stay Awake" in the Developer Options and connect your phone via your PC. Observe your wifi connection and get back to me
EDIT: How complicated is your home network? Are you using your router as a straight forward access point?
BluDRed said:
Have you unlocked the Developer Options yet? If not, goto Settings -> About Phone then tap build number 10 times to unlock. Enable "Stay Awake" in the Developer Options and connect your phone via your PC. Observe your wifi connection and get back to me
EDIT: How complicated is your home network? Are you using your router as a straight forward access point?
Click to expand...
Click to collapse
Running DDWRT.....very straightforward. Nothing complicated. I have Kindle Fire HD's......HTPCs.....etc running without an issue. All DHCP. This Nexus 4 is the only thing that has ever had issues.
The thing that I'm not understanding.......why is it being thrown a 172 IP address unless I turn DHCP off on the phone? Cuz as soon as I set it static (to a 192) it works fine.
Hmm DD-WRT, I'm going to hazard at a guess and say you know what you're doing when it comes to networking so I won't insult your intelligence or anything. But, if you're willing, try playing around with your router's DHCP setup before doing anything else and see how your phone goes by trial and error.
Come to think of it, unless anyone on these forums has experienced this before, trial and error is the best way of understanding. My best guess is the issue resides within the code of 4.2.2 FW. Hypothetically and possibly inadvertantly it has already been debugged for use on a custom rom. Some of the apk's found on the app store may shed some light onto the issue. WIFI Fixer apk may be help
https://play.google.com/store/apps/details?id=org.wahtod.wififixer&hl=en
i too have an issue on my newly bought nexus 4, every device connected to our router except the n4 is working fine. tried flashing a kernel and the problem still persists.
Sent from my LG-P500 using xda premium
roi14 said:
i too have an issue on my newly bought nexus 4, every device connected to our router except the n4 is working fine. tried flashing a kernel and the problem still persists.
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Right, so surely it is an issue with the phone, which firmware are you using Roi? If it's 4.2.2, nandroid backup then flash a custom rom of your choice and see what happens with your wifi issue
BluDRed said:
Right, so surely it is an issue with the phone, which firmware are you using Roi? If it's 4.2.2, nandroid backup then flash a custom rom of your choice and see what happens with your wifi issue
Click to expand...
Click to collapse
hey bludred. I have stock, unlocked and rooted 4.2.2 running Franco's r111. I seem to connect to the Wi-Fi but the connection drop still persists.
Sent from my Nexus 4 using xda premium
If you are receiving IP address that's not defined by your router then you are getting it from somewhere else.
Sent from my Nexus 4 using xda premium
roi14 said:
hey bludred. I have stock, unlocked and rooted 4.2.2 running Franco's r111. I seem to connect to the Wi-Fi but the connection drop still persists.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Do you have your "keep wifi on during sleep" setting at always? If you've already eliminated that as the issue, try wiping the delvik cache in CWM. I had a similar problem once when I used CM9.1, wiping delvik cache solved it.
If there's no joy, copy and post up a logcat or consider a custom rom like aokp 4.2.2 build 4 :good: