Hi guys! I seem to be having a problem to connecting to the WiFi Hotspot that my Nexus 4 makes. When I use my laptop to connect to it, it always shows limited connectivity. However, when I use USB tethering it works. Is this a hardware problem on the part of my Nexus?
Any help would he appreciated.
Sent from my Nexus 4 using Tapatalk 4 Beta
I've sometimes noticed it can take 30-60 seconds for Windows to realize it has a connection via a WiFi tether. Assume you've checked the obvious like that your TCP/IP settings in wireless are all correct? Should be set to obtain DNS and IP automatically. Also, do you normally have a proxy configured?
toxicbubble said:
I've sometimes noticed it can take 30-60 seconds for Windows to realize it has a connection via a WiFi tether. Assume you've checked the obvious like that your TCP/IP settings in wireless are all correct? Should be set to obtain DNS and IP automatically. Also, do you normally have a proxy configured?
Click to expand...
Click to collapse
Yeah they're all correct. My laptop has no problem connecting to other phones. I also don't have a proxy.
Sent from my Nexus 4 using Tapatalk 4 Beta
It takes a while and I find that windows want to create a new location profile upon each new tethering session.
Sent from my Nexus 4 using xda app-developers app
Related
Does anyone have wifi tether working on windows 7x64? I have tried that and barnacle and my comp can see them both but times out while trying to connect. Sits there for several minutes and says it can't connect.
Sent from my SPH-D700 using XDA App
Mine works like a champ as does my wifes. Both are Win7x64.
Sent from my SPH-D700 using Tapatalk
Shoot! Did you do anything special or just use the defaults?
Sent from my SPH-D700 using XDA App
I had an problem connecting once, but realized that when i was doing some work with vpn's and ports i decided to disable adhoc on my personal wireless card.
To see if it may be disabled on your machine click on start menu, right click computer and go to manage, then click device manager, under network adapters find your wireless adapter and right click and go to properties. Now go to the advanced tab to see if there is anything in there that says adhoc and if it is possible to enable it....
Like I said, I managed to disable mine and all it took was a re-enable to get it back working correctly.
Good luck either way.
Mine works fine too...make sure you are running the latest version of Android Wifi Tether (pre9 - pre13 generally work)..also try running the Internet browser on the phone after you connect.
Also if you are not on Froyo there is the Mobile AP option for Infer-structure tethering.
Working here too. I'm using the SyndicateROM 1.02. It comes with wifi tethering pre11.
The steps I took:
1) Renamed my wifi SSID
2) Added a security key, 13 characters exactly
3) In Win7x64, I manually added the wifi and for the security key, I chose WEP and entered the key.
I could be on 3G or 4G and wifi tethering works without a hitch.
crawrj said:
Does anyone have wifi tether working on windows 7x64? I have tried that and barnacle and my comp can see them both but times out while trying to connect. Sits there for several minutes and says it can't connect.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Does your laptop have an Intel card? I am unable to connect with my Intel 6200-based WiFi adapter on my Sony Z. It worked ONCE a while back, but updates seem to have messed this up rather permanently. Other machines that aren't based on Intel seem to work quite peachily.
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
No one at work with an android phone/tablet can connect to the WiFi. IPhone/pad Windows p8 and laptops. Connect fine. It gets stuck at authentication error or can't authenticate at least on my phones/tablets. I don't know if there is an firewall issue but I find it hard to believe as other devices can. Is it an android issue? We have like 10 or so access points or extenders all under the same name. I don't know if maybe I need to find the main router and try connecting to that... any ideas?
Sent from my SCH-I605 using Tapatalk 2
Are you sure it's WEP? It sounds like you're using a flavor of 802.1x WPA like EAP-FAST which isn't really supported on Androids.
It shows up as WEP secured.
From what I've gathered. Some android phones used to work but there was a lot of people that couldn't connect. So they called our IT guy and he called our network guy and they got it opened up so everyone was able to connect. Then a short time later android stopped connecting
Sent from my SCH-I605 using Tapatalk 2
Long time ago but still an issue. Anyone know the issue?
Sent from my SCH-I545 using Tapatalk 2
First of all, WEP is highly insecure, but I don't know why you would have problems. I would upgrade the security to WPA/WPA2 to prevent people from "stealing" your internet.
Sent from my LePanII using xda app-developers app
Usually it's an issue with the router/AP, not the phone. No idea why either.
Normally the security protocol is WEP ,its ok..the problem is not with your phone maybe they adopted for MAC filtering..you should try to check with the network admin..or try connecting a laptop and see if it works with the same protocol..or try to check with the network admin to move on to wpa or wpa2..maybe things can sort out
Hi after updating to 4.3 connecting to my WiFi seems to just keep looping obtaining, authenticating, obtaining. This didn't happen in 4.2.2. Anyone know a fix?
Sent from my Nexus 4 using Tapatalk 2
Try another network. Maybe it has a problem with your network. Hit thanks
Sent from my Nexus 4 using xda premium
Try forgetting the access point and redo it.
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Try forgetting the access point and redo it.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Hey man i tried this but did not work.
davinnwilliam said:
Try another network. Maybe it has a problem with your network. Hit thanks
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yes it works on other WiFi networks but does not mean the one I am having problems with is faulty cause other devices connect to it just fine. Not to mention it worked perfect on 4.2.2
Sent from my Nexus 4 using Tapatalk 2
JamesInsights said:
Hey man i tried this but did not work.
Yes it works on other WiFi networks but does not mean the one I am having problems with is faulty cause other devices connect to it just fine. Not to mention it worked perfect on 4.2.2
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Alright, what security type does the access point use?
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Alright, what security type does the access point use?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
WPA2 PSK. Also I want to note that this is a second router connected to the main one by ethernet and used as an access point
Sent from my Nexus 4 using Tapatalk 2
JamesInsights said:
WPA2 PSK. Also I want to note that this is a second router connected to the main one by ethernet and used as an access point
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Have you tried checking the router settings?
Sent from my Nexus 4 using xda app-developers app
I had the same issue before 4.3 update. It was working fine after the update but today it happened again. I switched to static ip in my nexus wifi settings and its working fine. So i guess DHCP has the problem and im blaming nexus because everything else in the same network works fine.
nikolas7gr said:
I had the same issue before 4.3 update. It was working fine after the update but today it happened again. I switched to static ip in my nexus wifi settings and its working fine. So i guess DHCP has the problem and im blaming nexus because everything else in the same network works fine.
Click to expand...
Click to collapse
I have the same problem with my old generation nexus 7. New one works just fine, galaxy nexus - just fine, xperia s - also fine, macbook pro - fine. I can't blame the network. Something is messed up. I tried a factory reset (as I'm selling this one) and it didn't help. also after quite some time of trying it wrote "Avoided poor connection" under the name of my network, but I can't alter the "Avoid poor connections setting" from the setup wizard.
Any help is greatly appreciated.
I think the problem is DHCP too. I used to use WPA2 for my LAN. My Nexus 4 appears to not connect to those networks anymore.
macropp said:
I have the same problem with my old generation nexus 7. New one works just fine, galaxy nexus - just fine, xperia s - also fine, macbook pro - fine. I can't blame the network. Something is messed up. I tried a factory reset (as I'm selling this one) and it didn't help. also after quite some time of trying it wrote "Avoided poor connection" under the name of my network, but I can't alter the "Avoid poor connections setting" from the setup wizard.
Any help is greatly appreciated.
Click to expand...
Click to collapse
Tried to set a static IP address? And you could also playing with the WiFi frequency bands. Some reported they can't connect to WiFi on 5 GHz band. Could try the 2.4 GHz one instead.
In cases of weak signal, DHCP may fail when connecting. If this happens, move closer to the AP (stronger signal).
If you have 2 routers and use 1 as an access point, use the LAN (not WAN) port on the second router and disable the DHCP server on the same router. You can use the same SSID and float between them if the other settings match (encryption and password). Use 2 different channels as far apart as possible (like 1 and 11). On 2.4 GHz, only use channels 1 to 11. On 5 GHz, only use 36, 40, 44, 48, 149, 153, 157, 161, or 165. The other channels have FCC limitations in the US. Use WPA-2 only with CCMP (AES) encryption. WPA should only be used with TKIP, while WPA-2 should only be used with CCPM (AES). I have seen a lot of issues when mixed is used.
Hope this helps...
Thanks for the suggestions. While testing I was standing just beside my router, so no weak signal problem. What I did after many tries to connect was reinstall stock 4.3 but version which ended with the letter 'V'. I was unable to see my problematic android build version, because I was stuck at welcome screen. So the reinstall fixed it.
One very irritating "feature" on my note 3 is it's automatic network disconnect when it thinks the internet connection speed is poor. Is there any way to override this automatic disconnect? Particularly since there seems to be a well known bug with the galaxy range wifi network which thinks the connection speed is poor even if there is nothing wrong with the wifi signal or Internet connection speed.
Try this.
Sent from Note 3 (The beauty & beast)
Unfortunately the wifi connection dropping issue seems to be highly dependant on your router.
Most people with the problem (including me) solved it with a different/newer router.
If you have spare time you could waste it ticking/unticking boxes in the wifi menu .. & THEN change your router lol
Sent from my SM-N9005 using xda app-developers app
No it is os bug. I have the same issue on newest update
Sent from my SM-N9005 using XDA Premium 4 mobile app
I am having the same issue on a corporate wireless network behind a proxy. It will connect, perform the connection speed test and then disable the network due to the connection speed being slow.
I am able to connect to a WiFi network on a secondary connection which does not go through the proxy. Both connections are on the same network.
GramiFIN said:
No it is os bug. I have the same issue on newest update
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes.... obviously an OS bug but we are stuck with it currently.
The information people need is how to COPE with the bug. I changed my router & no more problems so there's router's that will stop the issue occurring.
Sent from my SM-N9005 using xda app-developers app
is there a way to disable this stupid thing yet?
Neo3D said:
is there a way to disable this stupid thing yet?
Click to expand...
Click to collapse
Turnoff wifi power saving mode. This should work.
Sent from Note 3 (The beauty & beast)