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
Related
My wifi is not working at all after I upgrade the firmware. It kept connecting and then get disconnected. Anyone got this problem?
Sent from my GT-P1000 using XDA App
bubblebob said:
My wifi is not working at all after I upgrade the firmware. It kept connecting and then get disconnected. Anyone got this problem?
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
If it was me, I'd check to make sure you're broadcasting SSID on your router. For some reason, at least this is the way it is for me and I would be really baffled if it wasn't happening to everyone else as well, these android devices (I have an EVO and a GT), have a problem with connecting without it being able to see the SSID broadcast. All of my other devices (laptops, desktops, etc...) have absolutely no problems either way (broadcasting SSID or otherwise) connecting to my WiFi setup. Just the adndroid devices.
I had same problem not sure how i fixed it. But i reflashed everything like 1st time
I think it will b the modem file.
BUT check your wireless setting first
Sent from my GT-P1000 using Tapatalk
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
I just opened my new phone and am trying to get it set up but it will not connect to wifi. It sees all the networks around but it keeps cycling through trying to connect and never gets past the acquiring IP stage. I have tried two different routers and deleted, reentered, and turned the wifi off and on many times. My other phone and all my other devices work just fine on my network. Anyone know of anything else I can try? It was a major hassle to get this phone and I would hate to have to go through a RMA the same day I get it. Thanks
Had the same problem and had to configurate with the inet of sim card. Nexus 4 has some problems with some routers, i couldnt connect my nexus to the router and had to chsnge configuration from router, once connected it was fricking slow. i decided to buy belkin WiFi amplifier and ive connected it to the router. Now it works great, do some research on inet and see if that router is having trouble with n4.
Dont RMA, all have this "issue"
Sent from my Nexus 4 using xda app-developers app
Thanks, will search that.
On my Nexus 10, about 2 weeks old, and running most current version of Android, non-rooted, I can connect to wifi networks, but I do not have access to the internet. It just started today after having no issues whatsoever since I purchased it. It also just happened randomly today out of the blue. For further information, in the top right corner where the wifi "baseball diamond" is, the bars are that grey/white instead of the typical blue. Which I know means that I am connected to the network but without internet access. I have tried restarting my device both powering it off and on, and simply restarting it by holding down the power button. I have tried turning wifi off and on. I have tried the same with airplane mode as well. None of it has worked. I was wondering if anyone knew of any fixes for this issue? Thanks and any help is appreciated.
First I would get the IP of the nexus by long pressing the Wi-Fi network.
Then go on your pc connected to the same router and ping the ip.
For Windows, press Windows, type cmd.exe, enter, then
ping 192.168.1.x
But put in the real address instead.
If you get a reply with a ms value, your tablet is really connected.
If it times out or you get 100% packet loss, then it really isn't connected, or is unresponsive on the network.
Swiped from my Rezound using xda-developers app
When the bars are grey it doesn't necessarily mean that you don't have internet. The bars only turn blue when you are connected to the Google Talk servers. They are blocked at my work but I still have internet access with grey bars.
HillsRider said:
When the bars are grey it doesn't necessarily mean that you don't have internet. The bars only turn blue when you are connected to the Google Talk servers. They are blocked at my work but I still have internet access with grey bars.
Click to expand...
Click to collapse
It just started though and I didn't have problems before. And I am connected to the Google servers on my galaxy s3 just fine on the same wife network. And as for the other poster, how do I ping it on a mac?
mvmacd said:
First I would get the IP of the nexus by long pressing the Wi-Fi network.
Then go on your pc connected to the same router and ping the ip.
For Windows, press Windows, type cmd.exe, enter, then
ping 192.168.1.x
But put in the real address instead.
If you get a reply with a ms value, your tablet is really connected.
If it times out or you get 100% packet loss, then it really isn't connected, or is unresponsive on the network.
Swiped from my Rezound using xda-developers app
Click to expand...
Click to collapse
so i did this on my macbook. and viola it just started working again after I pinged it. It just said "starting ping" on the laptop and never anything else, but hey I am not complaining. so thanks
jscheuner said:
so i did this on my macbook. and viola it just started working again after I pinged it. It just said "starting ping" on the laptop and never anything else, but hey I am not complaining. so thanks
Click to expand...
Click to collapse
So everything worked fine yesterday after doing this. But today it reverted back to what it was doing. Tried pinging the ip again but it didn't work and it gave me 100% packet error or whatever
The ping had nothing to do with it working again, it was just a coincidence. You're having the same wifi problem a lot of us are suffering.
it has to do with the dns settings of the network I am using. And it just seems to come and go in terms of working. Hopefully it is fixable problem within the software
I am having a similar problem, but it happens sporadically and oftentimes fixes itself after about 30 seconds. Is this a known problem and is it hardware? Also, sometimes when I go to open the play store I will get a "No connection" message with the option to retry even when I am fully connected (blue bars and everything). The retry almost always works too. I am curious why this happens and if the two issues are related. Thanks for the forum, folks.
Sent from my Nexus 10 using Tapatalk HD
catfish_stevens said:
I am having a similar problem, but it happens sporadically and oftentimes fixes itself after about 30 seconds. Is this a known problem and is it hardware? Also, sometimes when I go to open the play store I will get a "No connection" message with the option to retry even when I am fully connected (blue bars and everything). The retry almost always works too. I am curious why this happens and if the two issues are related. Thanks for the forum, folks.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Yes, this is a known problem many are experiencing and is most probably software, unfortunately google seems to have a hard time getting their fat fingers off their arse.
Same issue has been driving me crazy. I have to turn Wifi off and on again.
The other, really annoying issue is that when I turn Wifi on in my bedroom, it still connects to the living room router with terrible wifi reception, instead of the nice strong signal from the office router just next door, I have to tell it explicitly connect to the office one.
Alias_neo. Why don't you just rename the network in your room to a different name so the tablet can distinguish between the two
Sent from my Galaxy Nexus using xda app-developers app
surfboard3r said:
Alias_neo. Why don't you just rename the network in your room to a different name so the tablet can distinguish between the two
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
They ARE different names, that's what's bugging me. My SGS3 had no issue, but for some reason the N10 just prefers one once it's set.
Sent from my GT-I9300 using Tapatalk 2
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