Related
Hey world,
I'm having trouble with my Roger's branded Samsung Captivate SGH i-896's wifi. The phone is completely stock. When I connect to my wireless AP at home it doesn't seem to always work on the captivate... I had a htc magic before running all sorts of different roms and never had a problem like this before.
What happens is that I would connect to wifi at home and it would work, but if I leave wifi on the phone for an extended period of time and go back to the phone, wifi stops working.
It would show that i've successfully connected to my AP but no data would pass through my phone.
Disconnecting and reconnecting to the AP doesn't seem to work, the only way to fix it is to restart the phone. I'm not experiencing this problem with any of my laptops, netbooks or cellphones at home.
Security type is WPA2.
Is anyone else experiencing this problem? Anyone have an idea what could be causing this problem?
I have had this problem intermittently, So has my wife on her Captivate. No idea what causes it though. It's a pain because if WiFi is on, but not working, 3G doesn't kick in so apps just don't work.
my wife's captivate has this issue as well (but I don't on my captivate). It will work for a short period and then stop. We have a fios wifi router, not sure if that matters at all.
restarting the router and/or phone usually fixes the problem
mine is a linksys... hrnnn
I'm having the same problem on my new Captivate. Tried it on several different networks with the same results (shows connected but no data will transmit) before I took it back to ATT. They scratched their collective heads and rebooted (powered down and removed battery), which is a temporary fix, but its been working for two days now and I turn off WiFi unless I know I'm in range of a working hot spot.
I was having this same problem until I set my wifi policy to never sleep, dont know if it is a fix for everyone but it definitely fixed my problem.
Sent from my SAMSUNG-SGH-I897 using XDA App
Glad to hear I'm not alone!
I've been fighting with this issue for over a week now, it suddenly started occurring. I wonder if it was an app we all loaded that suddenly made this condition occur? If you look the phone is requesting an IP and if the IP given back by the router is the same one it already has the phone doesn't acknowledge that command. If the router is rebooted then a new IP is given, or what is considers new. This is a HUGE problem and I've put in some time looking at it, but one of the problems is that is comes and goes. What your router log and you'll the phone request an IP over and over again, all the while the router saying "here, take the same one you already have back".
If you use the app "Network Info II" you'll see the problem when it displays a "Device IP" at the top of 192.168.1.254 and WiFi IP address will be the correct one, in my case 192.168.1.108. When we have these two IP numbers showing differently the device is hosed. Rebooting will put them back in sync, but that is not the proper solution, we need to get to the bottom of this! I understand the WiFi IP address showing at the bottom but the "Device IP" I do not, why the difference? How can we affect the "Device IP", where does the device get that IP address?
Try the app called WiFi Fixer. That did the trick for me. There seems to be a bug of some sort that causes the phone to not release the IP address. Or you could use static IP but that worked only for a while.
Cheers.
Sent from my SAMSUNG-SGH-I897 using XDA App
the app doesn't seem to work for me.... =(
DKirk said:
How can we affect the "Device IP", where does the device get that IP address?
Click to expand...
Click to collapse
The phone gets the device IP from either the service provider (when using edge/3g), or from the router (when using wifi). If an IP address is not provided, it uses a default IP address, which is always outside of the standard private IP block.
There are two ways to assign an IP address: dynamically and via static IP address. Dynamic = assigned by the router, static = pre-programmed by you. I don't know if you can set a static IP address on a phone, as I've never tried it.
I had a zyxel wireless n router in my house and could never get the wifi to work on my captivate. If it did work it lasted 5 seconds... I was really pissed.
I was thrilled to see that buffalo is now back in the market and with dd-wrt firmwares... So I picked up the most expensive one they had for $89.99.
it has a dlna client built in as well as bit torrent, also lets you use a spare usb hard drive as a nas... things i don't know....
However loaded up the wireless settings in 2 minutes and voila... perfectly working on my captivate... I have also found that this router works flawlessly with G+N devices and it is gigabit. I was able to stream 1080p video from my synology 411+ to my ps3, download on the captivate and be on two other laptops at the same time without any issues... I am very very impressed with the buffalo.
Here is the product info.
buffalo nfiniti wireless n high power router and access point. WZR-HP-G300NH
ohh and my laptops are connected fully at 300 mbps with this router wirelessly...
very very happy with it.... Oh and forgot to mention... once this started working with the buffalo i noticed my batter was much better running on wifi all the time. Also wifi file explorer pro works flawlessly.. I was able to upload a 700 meg movie to my captivate wirelessly in about 2 minutes.
WiFi fixer did not fix my problem as well. After turning WiFi on the device IP remains 192.168.1.254 while the WiFi IP is correctly set at 192.168.1.108. When these two IPs are different WiFi does not work and WiFi Fixer doesn't appear to see any problems here.
The router here is an Asus RT-N16 running Tomato and I'm fairly confident that isn't the problem. This is more like an internal routing issue inside the phone.
I don't think it's brand of router that matters... maybe a setting on our routers can fix this...?
I've searched the internet to find a sol'n but it looks like this wifi problem is a widespread problem for almost all galaxy S devices... ppl have made temporary workarounds (ie. setting a static ip) but ultimately, there is no fix for this problem.... gg...
bigbrotherbear said:
I've searched the internet to find a sol'n but it looks like this wifi problem is a widespread problem for almost all galaxy S devices
Click to expand...
Click to collapse
It appears to go beyond Samsung Galaxy, I've seen the same issue with Nexus and Motorola Droids. VERY frustrating!
tylerdurdin said:
I was having this same problem until I set my wifi policy to never sleep, dont know if it is a fix for everyone but it definitely fixed my problem.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I dont know why nobody even notice that answer !!!!
had same problem on my milestone .. it is not a bug , wifi goes to sleep , its the way your phone is set up ... as its quoted here set it to never sleep and make sure your not using soem kind of app that will overwrite that setting ( like battery manager that for example could turn off wifi to save battery)
very easy to double check once your wifi is not working , go in wifi settings scan and check the wifi access points you normally use you ll see its set to disabled ..
the bug is it doesnt resume like it should. or gets re-enabled however you wanna call it . just re-enable it voila ! no reboot needed .
I got it working!!
This may be my first post here, so be kind...
Running Cognition v2.3b3 and Linksys WRT54G router. WIFI was working fine until I flashed to Cog 2.2 Then I could only use WIFI tethering, no other WIFI connection would work.
I tried setting up static IP and setting sleep to never. Didn't work. Changed router security from WEP to WPA Personal and got it working.
Phone settings: Go to Wi-Fi Settings, click menu, and goto advanced. I don't know if all the settings here are necessary, but I'll post what I have.
Port = 80
Use statis IP = checked
IP address = 192.168.1.103 (check your router assignments for an open address)
Gateway = 192.168.1.1
Netmask = 255.255.255.0
DNS 1 = (check your router config. For my router it's located under the Status, then router tabs.)
Router settings: (Under the Wireless, Wireless Security tab)
Security Mode = WPA Personal
WPA Algorithms = TKIP
WPA Shared Key = (your access key used when you attempt to athenticate from your phone)
Group Key Renewal = 3600 seconds
Write the access key down so you can use it to reconfigure the other wireless devices on your home network.
Good luck,
Glen
changing my router fixed the issue.
I have wifi running on my captivate for 8 hours at a time at work now and at home. Not one hiccup or disconnect, works 100%.
99% of wireless routers are crap. I work in IT and have dealt with most major brands and had been running linksys wireless routers with dd-wrt on them...
if you got a spare 90 bucks.. go to your microcenter or place where they sell buffalo routers and pick one up. If it doesn't work.. you can return it.
This worked for me
Going to a static IP worked for a few hours and then it stopped working as before. WiFi is set to not sleep.
When I ran the router without security I did not have this problem and since adding WPA2 w/AES+TKIP the problem has developed. The iPod Touch doesn't have a problem with it, nor my laptop or wireless ipTV set-top box, only the Android. I'm leaning towards setting up another router without security, on a different channel, and see if the problem disappears again. Here in 2010 we shouldn't be having this issue, but look on other forums and you'll find similar complaints with other brands of Android phones, it's not a Samsung thing.
I have all kinds of computers tablets and gadgets. I have had no problems connecting to my wireless network until the Microsoft Surface came along. My router is the Motorola NVG 510. It doesn't have many settings that can be changed. I am using WPA2 Personal AES and a password. The only way I can Connect My Surface to this network is to turn off encryption. l had the same problem with the Surface RT. .
Tried for 24 hours now to connect... AT & T Says the problem is Microsoft related and Microsoft blames AT & T . l GIVE UP!!. Returning the Surface and going to keep my Samsung Slate 7 . . . has Windows8- WiFi and 3G. . .
how the hell do AT&T come into your wireless settings?
SixSixSevenSeven said:
how the hell do AT&T come into your wireless settings?
Click to expand...
Click to collapse
It is AT&T's router. I have Uverse and this is the one they gave us.Motorola should be who i call if anyone but the problem is Microsoft's ..All others have no problem connecting
shEEEsh said:
I have all kinds of computers tablets and gadgets. I have had no problems connecting to my wireless network until the Microsoft Surface came along. My router is the Motorola NVG 510. It doesn't have many settings that can be changed. I am using WPA2 Personal AES and a password. The only way I can Connect My Surface to this network is to turn off encryption. l had the same problem with the Surface RT. .
Tried for 24 hours now to connect... AT & T Says the problem is Microsoft related and Microsoft blames AT & T . l GIVE UP!!. Returning the Surface and going to keep my Samsung Slate 7 . . . has Windows8- WiFi and 3G. . .
Click to expand...
Click to collapse
Never had an issue with any form of encryption with the Surface RT - it's got the standard windows 8 wifi stack and connects to anything I throw at it, including WPA2/AES.
Not sure why you're having an issue, but you haven't given us much to go on for troubleshooting.
And getting a real router isn't possible?
Talon Pro said:
And getting a real router isn't possible?
Click to expand...
Click to collapse
Apparently this (MOTOROLA NVG510) router is the only one I can use in my area with U-Verse.
Thats bull. Is it a combo router/modem? If so you should still be able to hook up a wireless router off of that if it has at least one ethernet port.
see thats what BT claimed when they installed BT infinity at my grandparents but we dont have the stock router running off of it
Thanks for the suggestions. I returned the Surface. I don't know enough about routers and modems to install anything else or even how to buy something else. On the other hand. Annoys me that every gadget I own (and there are many) connects with no problem EXCEPT the surface.
diane
Your router is old. Something is probably interfering with the Surface Pro's connectivity. Your SP's wifi card isn't busted if it can connect without encryption. It shouldn't have a problem. I'd suggest ditching the modem's wifi and buying a router and using that instead for wifi and leave the modem alone.
99% sure it's a setting in your router that's causing you to not be able to connect a new device through wifi.
First port of call when having wifi issues is to remove all encryption/security settings and have it as a fully open network, if that works then slowly add security/encryption until you find out where it falls over, worse case scenario is a network that appears to be open but uses MAC address filtering to keep people out.
Trig0r said:
First port of call when having wifi issues is to remove all encryption/security settings and have it as a fully open network, if that works then slowly add security/encryption until you find out where it falls over, worse case scenario is a network that appears to be open but uses MAC address filtering to keep people out.
Click to expand...
Click to collapse
the problem was for sure the modem. There are no settings to tweak... It's gotta be the worst modem on the planet-but then U.verse doesn't feel any faster than my old ATT DSL connection. I asked to have my DSL back and ATT said that was not an option. ATT told me this modern is the only one for my area. Maybe it is time I looked into Brighthouse. I am sure there is a way around that modem but in my frustration I returned the Surface. Very sure I will buy another Surface . . I still have my Samsung Slate 7 with Windows 8... Another plus is it has a 3G connection. the more I use Windows 8 the more I like it, wish the Slate was a bit smaller.
Wireless encryption is done router side rather than modem side. You can use the ISP's modem and the connect it to an aftermarket router without issue. Its impossible for the ISP to prevent that. If its a combo modem and router then it is still possible to do.
All routers must have settings, unless you mean it has limited settings.
I've lucked out personally. My ISP's free router isn't the best on the planet but as a freeby is great. Full range of settings. Its a combo modem/router in one but I haven't had issues with that and it is perfectly happy for me to plug other routers into it (which I did once as an ethernet extension cable of sorts, otherwise my other routers are inferior) or according to a friend who used to be on the same ISP it quite happily connects to other modens and acts as a router perfectly fine still.
SixSixSevenSeven said:
Wireless encryption is done router side rather than modem side. You can use the ISP's modem and the connect it to an aftermarket router without issue. Its impossible for the ISP to prevent that. If its a combo modem and router then it is still possible to do.
All routers must have settings, unless you mean it has limited settings.
I've lucked out personally. My ISP's free router isn't the best on the planet but as a freeby is great. Full range of settings. Its a combo modem/router in one but I haven't had issues with that and it is perfectly happy for me to plug other routers into it (which I did once as an ethernet extension cable of sorts, otherwise my other routers are inferior) or according to a friend who used to be on the same ISP it quite happily connects to other modens and acts as a router perfectly fine still.
Click to expand...
Click to collapse
We already tried to tell him that and he wouldnt listen.
>We already tried to tell him that and he wouldnt listen.
OP's name is Diane.
Secondly, as posted in the OP, the device is a Motorola NVG 510. A 10-second lookup would show that it's a combined ADSL2+router, and it's not a simple matter of swapping out a router. Combined-function devices are SOP for leased models, since it saves the company money over having two boxes.
http://google.com/search?q=Motorola+NVG+510
It's a Surface problem. The user shouldn't be expected to mess with things like router settings and learn to be a geek. The device in question is obviously in popular use, and it's up to MS to get it right. The OP did the correct thing in returning the Surface.
However, for those with more tech savvy, the above search produces this help page for the modem+router,
http://www.ron-berman.com/2011/11/24/motorola-nvg510-help-page-for-att-u-verse-users/
which has both the manual and more importantly, a FAQ to troubleshoot connection issues, and links to more appropriate forums to ask further questions on this particular topic.
As I said, even on a combo unit you can use a different router. As long as the new router can recieve internet from any other device via ethernet all you do is connect it to the ISPs router. It will then share that connection. Yes your ISP's router will still be broadcasting but so will the new 3rd party one, you just connect to that. This is a configuration I have tested with a BT homehub and some ****ty Netgear.
To access the new routers settings, unplug it from the ISPs router first and then access the settings in the normal way. or if you can find the new local IP for the additional router you can use that.
>As I said, even on a combo unit you can use a different router. As long as the new router can recieve internet from any other device via ethernet all you do is connect it to the ISPs router. It will then share that connection.
Either the new router has to be reconfig'ed into an AP, or the old router needs to be disabled. Can't have both routers active. Likewise, the old wifi needs to be disabled, or the new one reconfigured that they don't conflict. Regardless, it's not plug and play. Either or both units would need configuration.
The household Internet router is the single most critical piece of equipment there is, because if the user messes up, s/he loses Internet access ENTIRELY and access to any further help. Without local help, that may mean several days' downtime and an expensive bill for onsite repair. I would NEVER, EVER tell a non-tech user to reconfigure his/her router, especially when the person said "I don't know enough about routers and modems to install anything else or even how to buy something else."
Everyone here has good intentions and want to help. Then, the first thing to helping is to listen to what is said, and gauge the person's comfort level with tech. No one even bothered to check up on the OP's router model.
The OP has a stable, working setup. Anything that jeopardizes that setup is bad advice, not unless you are willing to foot the onsite service cost for the person. The preferred solution is to remove the known-problem component, which in this case is the Surface.
PS: A long shot is to go into the Surface's Device Manager, select the Properties tab of the wifi card, and muck around with the advanced settings (if there are any).
You can totally daisy-chain routers using their default settings. Not sure why you would think otherwise...
That said, if you wanted port forwarding and such to work smoothly, it *would* be best to turn off DHCP and NAT on the inner router. However, that's not necessary to simply get Internet access via the router.
GoodDayToDie said:
You can totally daisy-chain routers using their default settings. Not sure why you would think otherwise...
Click to expand...
Click to collapse
Which is precisely what I originally said.
I have daisy chained a cheap as **** netgear router to my BT homehub without any setting changes at all. I was actually using it as an ethernet extension cable pretty much, I didnt have a single cable long enough so I plugged one between the homehub/main router and the netgear and one between the netgear and a raspberry pi. Would you look at that, my laptop can connect to the netgear and get internet access from it, the pi also connects via its ethernet port perfectly.
My grandparents use a set of homeplugs, how do they connect? daisy chaining.
One of my mates has 3 ethernet devices in one room but only one LAN port drilled into the wall (he had an electrician out once to actually have LAN sockets fitted in a few rooms). Solution: cheap wireless router connected to the LAN port in the wall. Other devices connected to the router. Router had 6 ports so he still has 2 left over. Devices connect to it fine. Originally it was default settings but he has since gone and disabled the routers wifi as he doesnt use it.
That said. I came across a linksys unit once which refused to be used as an access point of any kind. But that was only once.
>You can totally daisy-chain routers using their default settings. Not sure why you would think otherwise...
Having nested routers (ie segmenting the network) is a prescription for myriad network problems in the hands of a non-tech user. Again, listen to what the OP said, rather than assume everyone is a geek who knows what DHCP and NAT means, let alone how to change them.
Even if the OP can get the new router configured and running properly, the potential for problem remains. When ISP service goes down, the ISP tech will remote troubleshoot the leased equipment (the old router), since that's the ISP's responsibility. With user equipment attached, troubleshooting responsibility passes on to the user, which the OP has stated in no uncertain terms that she's not capable of.
The point isn't to get Internet access. The OP already has Internet access. The point is to get the Surface to connect to the network, but NOT AT THE EXPENSE of adding networking complications that the OP can't handle.
>I have daisy chained...
This suffices for simple Internet access, until you run into programs or devices that break because of the multiple redirections. I doubt UPNP/DLNA works on nested NATs. Ditto discovery. Devices/periphs on one network segment won't be able to connect to those on another segment.
The wifi will work, but given that most 2.4GHz wifi default to channel 1 or 6, it will likely conflict with the old wifi and work POORLY when both are active.
Hi there, I've had a lot of help through this forum in using my Android tablet without registering, so I thought this could be the best place to ask a question that's beginning to wreck my head.
I have a Versus 7 Touchpad, and while I know it's just a rebranded something or other made in China, it's actually a decent tablet for the price of €100. Anyway, recently I installed the TPlink TL-WA730RE wireless repeater at home and just have had no luck in getting the tablet to connect to the repeater whatsoever. My android phone (Xperia T), my wife's Nokia E5 and my Compaq PC all connect to the repeater fine and can browse the web/network no problem. However, the tablet just says 'connecting' (to the network) but then reverts back to 'saved, secured with WPA' etc. I know it's trying to connect because if I log onto the repeater through my PC every few minutes the MAC address of the tablet appears along with the status of 'STA -ASSOC', which I think means that the unit is trying to associate with the repeater, but then it just disappears. It may be worth noting at this point that the tablet connects to my TPlink TL-WR841N wireless router running DD-WRT no problem.
I've tried almost everything I can think of, like 'forgetting' the network and reconnecting, ensuring MAC address filtering is disabled, trying static instead of DHCP, resetting my router and repeater etc etc. I even tried apps such as 'wifi strongest signal' from the app store which connects you to the strongest access point in your house if you're using a repeater and walking around. The latest thing I did was to install CM10 on the rooted tablet and everything works apart from the wifi with the repeater, so it wasn't a fault with the original image. Also, the tablet was running ICS 4.0.4 I think, which was the same version of Android as my Xperia T, which connects perfectly.
The last thing I can think of trying is updating the repeater firmware, or installing DD-WRT on it also, but I'm loathe to do that seeing as all of my other equipment is working fine. Other than that maybe there is some sort of updated wifi driver I could try for the tablet itself??
Any ideas would be greatly appreciated!
Just incase anyone else has similar problems with this or any other android tablet, I managed to solve the problem after weeks of headaches.
The problem was that my TPLink wifi repeater's channel width was set to 'auto', where I had other options of 20mhz and 40mhz. Once I paired these with my router -i.e- both the router and the repeater were both set to a wireless channel of 20mhz, my tablet worked perfectly fine. Obviously some equipment can handle the difference in channel width, just not the Versus 7 Touchpad wifi.
Hope this helps someone in the future.
This problem happened spontaneously with all the android devices in our house. Router had been set up for a month with great performance and then the day before yesterday things just got crappy on our wifi.
Here's the problem:
There's a significant lag between trying to get data (refresh Facebook app, load a Youtube video, go to a web page in Chrome, whatever) and actually getting the data. This occurs on two Nexus 5 phones running Lollipop and a tablet running Kit Kat. Sometimes it'll be 10 to almost 30 seconds between trying to view, for instance a youtube link, and the video description and video actually starts to load. Sometimes I'll get a network timeout. A laptop running Arch Linux on the same network has no such lag.
Here's the weird thing. When I do a speedtest with the Ookla app, it will take a VERY long time to "find the best server" (it's been a minute so far while I've been writing this post just sitting at that screen) but once it does I'll get really excellent speeds. Basically maxing out the possibility of my home internet connection (40Mbps+). Same with upload (13Mbps). Ping to server was 10ms. When I use a terminal emulator to ping a site like google or facebook it will ping with typical wifi reaction rates, usually under 25ms consistently.
Wifi reception on the 2.4Ghz band is great. throughout the house. Different wifi channels do nothing. Note, my wi-fi signal is not dropping, so it's not that issue that's often reported. Reception is great, there's just major lag between trying to get data, and actually connecting.
And again this isn't just one device, this is three separate devices running two different flavors of android. So I'm guessing my router one day decided it didn't like android. Because like I said, things were great until literally just Thursday, with no change in settings on any devices or the router from us.
Yes, I've done a power cycle on the router, which is a Netgear C3700
Any ideas on what might be happening?
It's possible there is an IP addresses conflict. Do any devices on the network have a static IP?
No IP conflicts that I can see ever have been the issue.
If I reboot the router the problem goes away for a couple hours, but then I get the WiFi lag soon enough. I've seen a lot of reports about lag on WiFi (with bad ping results) on some other google searches I've run, but they all point to problems with IPV6, which my router doesn't support at all, so there's nothing for me to turn off there. I can't find any IPV6 settings for anything anywhere on the phone itself.
I don't see any other problems with my router and android devices specifically mentioned anywhere.
Are your android devices using different DNS servers than that of your laptop?
I have never specifically set up any DNS settings on any device in the house. Not even sure how to see what the settings for that are on the Android devices.
I'll try using a static DNS settings from the router instead of the "let my ISP choose" as I have been having problems possibly related to DNS issues on a wired laptop machine (running Linux as well).
Hooya said:
I have never specifically set up any DNS settings on any device in the house. Not even sure how to see what the settings for that are on the Android devices.
I'll try using a static DNS settings from the router instead of the "let my ISP choose" as I have been having problems possibly related to DNS issues on a wired laptop machine (running Linux as well).
Click to expand...
Click to collapse
Try Google DNS or something
I'm fairly convinced it's not a DNS issue. If it was, rebooting the router would have absolutely no effect at all. But a reboot of the router (unplug and re-plug, a software initiated reboot doesn't seem to work) makes the net fly at great speeds and pings on all devices. For a while. Then it goes bad.
I'm testing a 3rd party app to change the DNS settings to 8.8.8.8 (google) on one android device to see if that one behaves differently. Setting the router to custom DNS settings caused me to get locked out of all internet completely. I couldn't even get into the router software from a wired computer to see the settings anymore. It was like the router didn't exist anymore.
Hooya said:
I'm fairly convinced it's not a DNS issue. If it was, rebooting the router would have absolutely no effect at all. But a reboot of the router (unplug and re-plug, a software initiated reboot doesn't seem to work) makes the net fly at great speeds and pings on all devices. For a while. Then it goes bad.
I'm testing a 3rd party app to change the DNS settings to 8.8.8.8 (google) on one android device to see if that one behaves differently. Setting the router to custom DNS settings caused me to get locked out of all internet completely. I couldn't even get into the router software from a wired computer to see the settings anymore. It was like the router didn't exist anymore.
Click to expand...
Click to collapse
Try setting static IP's for the Mac adresses of the phones in the router and on the phone. Make sure it's outside of DHCP lease boundry of your modem. Sounds like conflicting IPs as already mentioned.
The responders have good intentions but really don't understand the problem entirely. I've faced similar issues.
To quickly dumb down the problem:
Wifi stays connected, but all packets are lost for 10-60 seconds or until wifi is toggled off then on again.
We'll call this Wifi-Connected-No-Connection (WCNC) for the purposes of this thread for easier reading.
Here are my findings...
It may be related to this issue on the google code discussions, there are mentions of complete drop out while remaining connected: https://code.google.com/p/android/issues/detail?id=64706
This has affected both N4 and N5 devices since Jelly Bean. The issue persists in Kitkat but I haven't followed to see if it's entirely been resolved in Lollipop as I refuse to upgrade until certain other issues are worked out with L. If you're good at searching you'll find posts about this drop out issue from a decent time ago.
AP isolation doesn't help.
Modifying most other settings for the router did not help.
What DID help though, is turning the router from N/G mode to B/G mode. I had no WCNC issues with that. Of course, that meant slower speeds, significantly slower speeds. Back on N/G, I find this problem happens pretty frequently.
Packet loss happens at the connection level. Pinging the router means some or all packets are dropped. This is NOT a dns issue.
toastgodsupreme said:
The responders have good intentions but really don't understand the problem entirely. I've faced similar issues.
To quickly dumb down the problem:
Wifi stays connected, but all packets are lost for 10-60 seconds or until wifi is toggled off then on again.
We'll call this Wifi-Connected-No-Connection (WCNC) for the purposes of this thread for easier reading.
Here are my findings...
It may be related to this issue on the google code discussions, there are mentions of complete drop out while remaining connected: https://code.google.com/p/android/issues/detail?id=64706
This has affected both N4 and N5 devices since Jelly Bean. The issue persists in Kitkat but I haven't followed to see if it's entirely been resolved in Lollipop as I refuse to upgrade until certain other issues are worked out with L. If you're good at searching you'll find posts about this drop out issue from a decent time ago.
AP isolation doesn't help.
Modifying most other settings for the router did not help.
What DID help though, is turning the router from N/G mode to B/G mode. I had no WCNC issues with that. Of course, that meant slower speeds, significantly slower speeds. Back on N/G, I find this problem happens pretty frequently.
Packet loss happens at the connection level. Pinging the router means some or all packets are dropped. This is NOT a dns issue.
Click to expand...
Click to collapse
This makes a lot of sense. Wonder why this would happen with one router set to b/g/n and not another set to b/g/n (the a/n settings are only for the 5Ghz band)...
Is anyone else experiencing connection difficulties with wifi since Oreo? Both at work & home with good, strong wifi signals my phone struggles holding onto wifi. Continually drops & struggles to reconnect like I'm on the edge of a signal (but I'm not, mere feet from a router). THen once connected it'll sit with an x through the icon.
Never had this before the update. On bone stock, locked Oreo OPR6.170623.011. Already tried resetting network settings to no avail.
Edit: Been running in safe mode for awhile and it seems to have alleviated the issue. So now it's time to figure out what app isn't playing nice.
I had that. Turned off such to mobile data automatically
I had the exact same issue. I factory reset my phone twice and did not restore any apps and had the same problem. Phone was under warranty so received a replacement which I am keeping on 7.1.2 for now. No issues yet.
I have a Unifi AP lite setup. Maybe I never noticed it before, but I was using a Rasberry Pi as my manager, but now I'm using an actual cloud key.
I've tried messing with all manner of settings and channels and band steering and AP names with no luck. My Pixel XL 8.0.0 will connect stay on for a bit and drop then reconnect. It never misses a beat, to be honest, I don't notice drops in connection. I am also noticing it in my Nexus 7 2013. My laptop seems stable, my girlfriend hasn't said anything about her iPhone or laptop. My Xbox one is stable, as is my switch.
I've reset network settings and tried the safe mode thing with no luck. I may do a factory reset this weekend if I can find the time.
In the mean time, I'm happy to have unlimited data at the moment.
I think I've narrowed it down to using a custom DNS. I was using a RasPi with Pi-Hole and my phone could not stay connected to wifi. I turned off the router pointing to my pi and boom, strong signal.
I tried manually assigning my IP / DNS etc in android 8.0.0 and it would not connect or hold a connection. I tried to connect it to 8.8.8.8 with no luck either. Back to stock DHCP assigned and I have a strong stable connection.
same issue not too sure what to do...is there a way to downgrade wifi driver?
RazorSky said:
I think I've narrowed it down to using a custom DNS. I was using a RasPi with Pi-Hole and my phone could not stay connected to wifi. I turned off the router pointing to my pi and boom, strong signal.
I tried manually assigning my IP / DNS etc in android 8.0.0 and it would not connect or hold a connection. I tried to connect it to 8.8.8.8 with no luck either. Back to stock DHCP assigned and I have a strong stable connection.
Click to expand...
Click to collapse
Same here, time capsule as router and DNS set to pi hole, pixel drops wifi connection - any way to resolve this? I don't want to switch off pi hole
rwanek said:
Same here, time capsule as router and DNS set to pi hole, pixel drops wifi connection - any way to resolve this? I don't want to switch off pi hole
Click to expand...
Click to collapse
So I have a stupid network, I'll try to upload a diagram of it here. My apartment internet only comes in in the kitchen and cannot go anywhere else unless I get a different provider, even then I'm not sure.
I moved the Pi to the router/switch that connects to the AP instead of on the other side of my network bridge and I have had 0 problems since. The attached diagram is my old setup as I was trying to explain it to people. Sorry it's not very pro.