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.
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.
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...
I just upgraded my router to a wireless one. Firstly, it's connected via ethernet to a PC and it is happily getting internet access.
On my i5500 I get a strong wifi signal. Wifi Analyser shows the signal at max constantly. I can also connect with Gmote and it works just fine.
The problem is that I can't actually access the net at all from the phone.
So basically I know that my phone is talking to the router with no problem. It's just getting out onto the internet.
Does anyone know of a solution?
try logging into your router and change the broadcast channel to something else and test it again. it should be something like a/b/g mode... define a single channel and see if it works.
I had originally thought that was working. It did for the first few minute where I had connection but then it just dropped.
I have noticed that I have some very small bursts where I can connect.
Do you think that trying the different channels may be the solution?
I have the same problem. Have you found a solution?
Still no solution. I went through every channel and every encryption method.
So far I've found that having the channel set on 'Auto' and then disabling encryption seems to give me internet connection through WIFI for at least the initial period but it eventually drops. But that's also not always.
I've also Googled it to death and found nothing. If you do find the solution please post it here and I'll do the same.
Maybe we can help each other.
make sure you entered the right password of wlan.
use a pc to connect the router and in the wlan you'll find the password.
Ok, just to clarify. My phone connects to the Router via WLAN. In fact I can use Gmote to control my PC. So the WLAN connection is great.
The problem is accessing the internet when using that connection.
I had similar problems with a router last year. I resolved the issues by flashing DD-WRT firmware. The manufacturer's firmware was junk.
Sent from my ADR6300 using XDA App
I had that idea but they don't have firmware for my router yet. I have asked them if they intend to make one.
Any chance the firewall on your phone is blocking your browser from using the Wifi?
Sent from my DInc via XDA App
I have no firewall on my phone.
Ok I've tried some new stuff and they I've had the longest connectivity so far (which is about half an hour).
First I made sure my Wifi wasn't set to turn off when the screen goes to sleep. Second, according to a forum I read, Netgear recommends channel 7. If that channels doesn't work try 1,3,6,9,11,13.
I then disabled encryption.
Fortunately no one near me uses Wifi at all and I've got the kind of walls that stop the signal from getting outside.
Anyway. It's working so far but I'll monitor and report.
[edit] And I forgot. The router was checking for firmware but it wasn't actually finding so I downloaded it myself. Seems that also made a difference.
Ok. I can confirm after 2 and a half hours my internet connection is stable. I even left half way through and when I came back it connected perfectly.
So as a summary here's what I did:
1) Get latest firmware
2) Change channel to 7
3) Disable encryption
I will change encryption and see if it still works
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)...
I own a Wi-Fi repeater to which other smartphones and my wife's MacBook can connect to and have internet access. But on my Pixel 2, while I can connect to repeater wifi network I get the warning "connected, no internet access".
Does anyone know how I can fix this? Thanks In advance.
Cheers
Badelhas said:
I own a Wi-Fi repeater to which other smartphones and my wife's MacBook can connect to and have internet access. But on my Pixel 2, while I can connect to repeater wifi network I get the warning "connected, no internet access".
Does anyone know how I can fix this? Thanks In advance.
Cheers
Click to expand...
Click to collapse
Try this... Turn wifi off and/or unplug everything that has wifi access. Everything. Unplug the repeater and then the main router. Wait thirty seconds and power the router back up. Once it's fully connected, power the repeater on wait for it to connect. Then, turn on your wifi devices. You should be good to go.
Sometimes, DHCP creates conflicts, so this just assigns a new IP address to each device. I have an NAS that I travel with, and every time I connected back to home network, it would cause problems and I would have to do this. Eventually, I just assigned it a static IP address. No more issues.
DuckRuckus said:
Try this... Turn wifi off and/or unplug everything that has wifi access. Everything. Unplug the repeater and then the main router. Wait thirty seconds and power the router back up. Once it's fully connected, power the repeater on wait for it to connect. Then, turn on your wifi devices. You should be good to go.
Sometimes, DHCP creates conflicts, so this just assigns a new IP address to each device. I have an NAS that I travel with, and every time I connected back to home network, it would cause problems and I would have to do this. Eventually, I just assigned it a static IP address. No more issues.
Click to expand...
Click to collapse
Thanks for your answer. I just tried that and it didn't work. I still get the "connected, no internet" warning
Any new ideas, please? Cheers
I have a similar issue with the router of a close relative I visit often. I always have the "connected with no internet" on their router. But if the router is rebooted my pixel 2 will connect fine (initially), then after about 15-30 mins later it's back to saying the WiFi has no internet.
It's rare but bugs with connections and compatibility somewhere can happen between devices. I'm guessing it's some bug in the software causing this. But because the pixel 2 doesn't exactly have a huge market share the users affected are likely not enough for either Google or the manufacturer of the routers experiencing this issue to ever release a fix for this.
My understanding is that Android P fixes a some WiFi issues. Hearing that it's a good daily driver these days, you could load the latest beta.
Is it a "release candidate" at this point?
Sent from my Pixel 2 using Tapatalk