Need a little help. My G-tab is running current VEGAn-TAB rom. I am having problems getting the wifi to actually connect. My icon shows a good signal, and inside the wireless settings I am showing connected to my wireless network. I also went to advance settings and made sure wifi never sleeps. All apps that need internet connection (market, browser, etc.) show no data connection.
Used yesterday with no problems. My laptop is running on same network and working fine.
Any ideas?
have you restarted? Sometimes happens to me too but it's nothing a simple restart can't fix.
Yes. Restarted several times. Didn't work.
Oddly enough I have a Airave from Sprint to boost my cell phone signal, and it may have been the problem. When I unplugged it and returned to my G-Tab later the Wifi was working. Not sure why.
TexasZac said:
Yes. Restarted several times. Didn't work.
Oddly enough I have a Airave from Sprint to boost my cell phone signal, and it may have been the problem. When I unplugged it and returned to my G-Tab later the Wifi was working. Not sure why.
Click to expand...
Click to collapse
Could be competition on the 2.4 GHz frequencies. Some wireless phones and even microwave ovens can trash a wifi connection.
Moved to general
Anyone else having WiFi problems with Vegan? Since installing this mod, I can only connect to a WEP signal and not a WPA-secured network.
I can't connect either. Trying to connect to a wep wifi and it stays on "obtaining ip address from ..." but never completes the connection. Any help?
LittleBirds said:
Anyone else having WiFi problems with Vegan? Since installing this mod, I can only connect to a WEP signal and not a WPA-secured network.
Click to expand...
Click to collapse
No problems with home WEP, office WPA2-PSK and several wide open public ones. I just wish the damn thing would auto-connect to the ones I have been to before.
outofoffice said:
I can't connect either. Trying to connect to a wep wifi and it stays on "obtaining ip address from ..." but never completes the connection. Any help?
Click to expand...
Click to collapse
My only guess is, if its a 5Ghz N Router you should check to see if it allows
2.4Ghz signals and not just 5Ghz. The GTAB doesn't seem to support connections at 5Ghz.
I just changed over from TNT Lite(latest version) and was able to connect fine but I didn't like the interface and some of the features. I've loaded Vegan tab 7.0.0 and I was able to connect at work (802.1 EAP) network but I can't connect to a wep wifi at home (were several other pc's are connected and working fine) and it stays on "obtaining ip address from ..." but never completes the connection. Any help?
I have a Linksys wrt300n router and have confirmed that it configured to accept 2.4Ghz & 5Ghz signal and have rebooted several times with no luck.
I don't have a lot to add to help you troubleshoot, but I can say that I am running VEGAn Gingerbread RC1 with pershoot's latest kernel. I am able to connect at home on a WAP2-PSK (Linksys Linux based G/N) at home, WAP2-PSK at the cabin (Linksys's cheapest G/N), and at work on a 802.1 EAP network (Cisco).
I has some unexplained issue mounting the internal storage on a computer. After a little head scratching, I started to wonder if it had something to do with the custom kernel I was running. I flashed Pershoot's latest kernel and my problems went away.
I mention all that to suggest that you might try flashing a different kernel and see if you get different results.
I have an issue with vegan where when i reboot the device (or turn off and turn on) wifi is off even if left on when turning off, i have to manually turn on wifi after every boot.
Sent from my DROIDX using XDA Premium App
fajordan said:
I just changed over from TNT Lite(latest version) and was able to connect fine but I didn't like the interface and some of the features. I've loaded Vegan tab 7.0.0 and I was able to connect at work (802.1 EAP) network but I can't connect to a wep wifi at home (were several other pc's are connected and working fine) and it stays on "obtaining ip address from ..." but never completes the connection. Any help?
I have a Linksys wrt300n router and have confirmed that it configured to accept 2.4Ghz & 5Ghz signal and have rebooted several times with no luck.
Click to expand...
Click to collapse
Have you checked to see if you're using MAC address filtering, and if so, that your gTab's MAC address has been added to the whitelist on the router? I get the feeling that that may be the issue. You have the WEP key on your device, but your router's still blocking it. I'm running the same ROM you are, and have had absolutely no troubles connecting to my work network with 802.1 PEAP, WPA/WPA2-TKIP and AES at home, and multiple makes/models of access points/routers.
Hmmm. Just reread your original. Now I'm wondering if you have enough DHCP leases available on your router. If you're out, you'll have to wait until a lease expires or add some more to your scope of addresses.
Hope some of that helped in some way...
First of all may I say I have searched for this problem on google, as well as xda forum. I did find several threads about this problem, but none of the solutions presented appear to be my case.
So, basically the problem is: I cannot connect to my home router, a Linksys WRT300N N-router. I could not connect with a N1, HTC Desire, nor with my actual NS. My previous Galaxy S was connecting fine though. I'm talking here about stock ROM, no rooting, no custom kernel etc. Also, using static IP address works like a charm, but then WiFi cannot be used on other outside routers, since Static Ip setting is not setup PER router, but rather per WiFi connection, meaning the phone will try to use the static IP defined for any WiFi I run into.
From My experience, it seems it could be related to wireless N router as opposed to b/g. This happened since I replaced my router with the actual one. Ever since this happened, my phone would not connect to my router. Also, this problem seems to be presentfor any N-router, since I cannot connect to WiFi in other locations as well (which might have N-routers as well).
Assuming that it is a problem with N-routers, I don't understand why the Galaxy S would connect, but NS not, since they are almost the same hw.
Does anyone have a clue on this? But please skip solutions like reset router, reset phone, reset modem, use different ROM etc. I am talking stock ROM for all the examples above.
Thanks.
I use my NS with three 802.11N routers without issue (D-Link, Belkin and Netgear).
Have you checked if MAC filtering on the router is active? What security mode are you using? Who makes yr router and does it have latest fw?
Sent from my Nexus S using XDA App
Just seen you use Linksys, I have a wag160n and I find it unsusable on terms of wifi, dreadful hardware, despite the parent company being Cisco
Check Linksys forums for problems.
Try another router for whether it's that or phone at fault.
Sent from my Nexus S using XDA App
MikhailCompo said:
I use my NS with three 802.11N routers without issue (D-Link, Belkin and Netgear).
Have you checked if MAC filtering on the router is active? What security mode are you using? Who makes yr router and does it have latest fw?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
MAC filtering is disabled, I've checked it. Security is, on the router, PSK-Personal with TKIP encryption. Key renewal: 7200 sec. Not sure if this can influence anything.
I've checked on linksys page for fw upgrade, they only have pdf manuals.
ionutz6 said:
First of all may I say I have searched for this problem on google, as well as xda forum. I did find several threads about this problem, but none of the solutions presented appear to be my case.
So, basically the problem is: I cannot connect to my home router, a Linksys WRT300N N-router. I could not connect with a N1, HTC Desire, nor with my actual NS. My previous Galaxy S was connecting fine though. I'm talking here about stock ROM, no rooting, no custom kernel etc. Also, using static IP address works like a charm, but then WiFi cannot be used on other outside routers, since Static Ip setting is not setup PER router, but rather per WiFi connection, meaning the phone will try to use the static IP defined for any WiFi I run into.
From My experience, it seems it could be related to wireless N router as opposed to b/g. This happened since I replaced my router with the actual one. Ever since this happened, my phone would not connect to my router. Also, this problem seems to be presentfor any N-router, since I cannot connect to WiFi in other locations as well (which might have N-routers as well).
Assuming that it is a problem with N-routers, I don't understand why the Galaxy S would connect, but NS not, since they are almost the same hw.
Does anyone have a clue on this? But please skip solutions like reset router, reset phone, reset modem, use different ROM etc. I am talking stock ROM for all the examples above.
Thanks.
Click to expand...
Click to collapse
Have you checked that you set up the router with b/g/n protocols? not only N..
Try to change the password encrypting method, to WPA or WPA2 or WEP, try also to change the default password.
Have you tried to disable the firewall (DMZ)?
I have exactly the same issue on my stock Desire.....
I have recently upgraded my router from a Belkin G+ to a Belkin N+ and using the b/g/n setting the desire WILL see the connection but will NOT connect to it, NO MATTER WHAT settings you try. Changing it to b/g and it will connect without any issues.
It is my understanding that the Desire/Nexus et al doesnt have the access to the N ability enabled (it has the correct chipset but for some reason it is not active).
Maybe when broadcasting the tri-band the chipset only sees the stronger N connection, therefore tries to connect but gets conflicted (due to lack of N firmware) and instead of switching to b/g it just loops to the stronger signal. IF that makes any sense
Riki1kenobi said:
I have exactly the same issue on my stock Desire.....
I have recently upgraded my router from a Belkin G+ to a Belkin N+ and using the b/g/n setting the desire WILL see the connection but will NOT connect to it, NO MATTER WHAT settings you try. Changing it to b/g and it will connect without any issues.
It is my understanding that the Desire/Nexus et al doesnt have the access to the N ability enabled (it has the correct chipset but for some reason it is not active).
Maybe when broadcasting the tri-band the chipset only sees the stronger N connection, therefore tries to connect but gets conflicted (due to lack of N firmware) and instead of switching to b/g it just loops to the stronger signal. IF that makes any sense
Click to expand...
Click to collapse
Well, the funny part is that I don't even know how to disable the N range to my Linksys 300N.
Anyway, it is weird that the Samsung Galaxy S had no issues with this, while Nexus S (still Samsung made, brother-in-law to SGS) has this issue. For HTC, all have had this problem, including Desire, Desire HD, Wildfire.
Still no explanation or resolution to this matter.
I may have fixed this issue (well I have for me anyway, so yay).
After posting this I decided to apply some weird logic to it. So I reset the router back to b/g, to do this you need to log into the router IP settings, for Belkin it is 192.168.2.1. On linksys routers I think it is 192.168.1.1 but check to be sure.
Once you are logged in there you can change the broadcast settings from N, b/g/n or b/g etc.
Okay, so here is what I did. I reset the router to broadcast b/g only, my Desire would connect. So I decided to try resetting the router to broadcast b/g/n (because I use N on other devices) and then switched the wifi on the desire off and back on again. Low and behold it connects.......Tried it loads of times now and connects everytime!
Might be worth a try?
You guys should just check the logs on the router and see what they say. Should give you a much better idea of what the issue is. You can then Google the error line.
Mine is fixed now, been connecting to various N routers with NO probs since I did the workaround.
My guess would be a protocol conflict (wireless handshake if you prefer) when N routers are broadcasting (based on the fact that the Desire/Nexus etc dont have N protocol enabled in the chipset firmware).
To get around the conflict connect to an N router using the b/g only setting in the routers IP settings and then check you can connect okay and switch the b/g/n back on in the router. I've done this twice today (different N routers, a Linksys and a D-Link) and it works on both where it wouldnt before, so it wasnt just my router.
hum... i am having the exact same problem as described only my router is already using
802.11g&802.11b
i have no idea why it keeps trying to obtain ip address
then it scans agains because it can't connect and tries to obtain the ip again
after trying for a minute or 2, the home ssid becomes:
"disabled, secured with..."
(device = motorola atrix)
I have tried everything and still not working... do routers block Mac addresses if it doesn't connect right away?
Sent from my MB860 using XDA App
Did you reboot your router? Mine does that sometimes but a reboot always fixes it.
Sent from my Nexus S using XDA App
Hum. Tried restarting the router... no go
Sent from my MB860 using XDA App
My modem broke down a few days ago, so I got a replacement. I don't remember the previous WiFi settings, but the network in use previously was probably WPA2 TKIP secured, because every device in the house was able to connect to it. I set up the new one on WPA2 AES, but the phone fails to connect to it. It is visible in the WiFi list, but it doesn't work. I went back to TKIP, because there was also a laptop and a Blackberry in the house that couldn't connect because of the AES encryption, but it bugs me that I can't connect to a whole range of networks out there. A friend's Samsung Galaxy S i9000 (GB 2.3.5 stock) connects just fine, and since it's older, and I also doubt LG would be cutting costs on WiFi chips at this level, I assume it's a software issue, but I can't be sure.
Has anyone been able to connect to AES-encrypted wireless networks? I tried on v10d, v21a and v21b, with the same result.
So, after browsing a bit about this I'm still unable to connect to my work wifi network. Every other network I'm able to connect just fine.
I put the wifi password, authenticates, goes to "obtaining ip address", goes back to authenticate.. and doesn't connect.
Forcing (using manual IP configuration) connects but doesn't open websites, even tho I'm using the connect gateway / dns servers. (even used 1st dns same as gateway).
Got a LG 4x next to me connecting just fine, problem is only on my nexus 5.
So far happens on 4.4.2 and 4.4.3.
Tried some tips that I saw around the web like disabing nfc or turning on and off airplane mode (although there isn't much logic in these), but still nothing.
Wifi password is correct.
Problem it seems is somewhere obtaining the ip from the router or something, as it goes back when it reaches this point, but then again forcing it allows me to connect but doesn't open websites.
Any tips? I'm suing WPA2 PSK at home and it's fine.
The network is in a 2ghz range channel 10.
Any help is appreciated.
PS - Router is a linksys WAP54G.
Thanks a lot!
Hi. Recentlly I bought a Samsung S7(G930A - AT&T version) as refurbished one. I found a big issue what hurts me a lot. Here are some issues with wifi:
I could not really connect to a lot of WIFI networks, it says "connecting" after that it drops and cycle begins once again infinitly.
On several networks it shows "authentication error occured" , although wifi is public and another devices connects to than one.
On several networks, it connects but connection is very slow(0).. only way to make a better connection, is to put phone on router...awful...
On one networks which i tried, it worked ok..it's an 5ghz wifi. although, not for a long distance from router.
I installed all updates, tried troubleshots from internet with bluetooth, reset and everything..but no success at all... Now I think that problem is really in hardware... Had anyone such issues ? Any solutions to fix ?
Please help...
maxiannicu said:
Hi. Recentlly I bought a Samsung S7(G930A - AT&T version) as refurbished one. I found a big issue what hurts me a lot. Here are some issues with wifi:
I could not really connect to a lot of WIFI networks, it says "connecting" after that it drops and cycle begins once again infinitly.
On several networks it shows "authentication error occured" , although wifi is public and another devices connects to than one.
On several networks, it connects but connection is very slow(0).. only way to make a better connection, is to put phone on router...awful...
On one networks which i tried, it worked ok..it's an 5ghz wifi. although, not for a long distance from router.
I installed all updates, tried troubleshots from internet with bluetooth, reset and everything..but no success at all... Now I think that problem is really in hardware... Had anyone such issues ? Any solutions to fix ?
Please help...
Click to expand...
Click to collapse
I had frequent wifi connection authentication errors when connecting with my home wifi and slow Internet loading speeds with my Galaxy tablet, but all my other wifi devices connect consistently without errors.
The steps below solved a similar problem with my Samsung Galxy Note 10.1, and it might help with your Galaxy 7. Some of the steps may vary with your device, but the goal is to set wifi Poxy Settings to NONE, and IP Settings to DHCP. It completely resolved my home wifi authentication error and slow spped when browsing.
For the Galaxy Note 10.1: Settings> WiFi> long press the SSID/router name(the wifi you want to connect to)> Modify Network Config> check the box "Show Advanced Options">set proxy settings to "None" -- set IP settings to "DHCP"> Save.
Now my wifi connection with the Galaxy note 10.1 are quick, consistent, and Internet pages load fast.
I hope this is helpful.