NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Android devices keep getting thrown off the Orbi WiFi
(This was also an issue before the latest firmware)
Our Android devices (tablets and phones) keep experincing the same issue. They are all sporadically thrown off WiFi and re-connected again a few seconds later.
What could the reason for this, and any recommended way of fixing this issue? I've done no changes to the basic Orbi setup, other then enabling Ipv6 and changing the DNS (issue was also present before doing those two changes).
I previously had a Nightahwk X8 where this never was an issue, so I'm worried either a setting or the Orbi system itself is flawed. In general I feel like the X8 has been superior in terms of speed, range and stability. Is that supposed to be correct?
152 Replies
Wonder if the two are related?
https://community.netgear.com/t5/Orbi/iOS-devices/td-p/1189718
Looking at the thread at a glance, I don't think so. I've never had issues with the iOS devices in the house and this was before the latest firmware hit, it's also present on the latest firmware. But the root of the issue might be the same.
I have the same problem with two android phones. My IOS products work fine but the android ones keep ketting disconnected en reconnected. Very very annoying. I am honestly thinking about returning this product because its faulty in my opinion.
- Those options are off and Intried every channel available. No luck. Its really an issue with android and this router. I will bring it back after the holidays.
- And the router and sattelite are two floors apart. The next would have been to put the sattelite on the roof and I guess thats not the idea. Its just not as greatbas I expected from the ads. I had a apple network (much slower) but that was stable.
My android devices and Sony Xperia z4 tablet and phones also experience random WiFi drops frequently, have tried factory resets many times, different channels disabled beamforming nothing works this issue was a lot less frequent on old 16 Firmware with the 18 Firmware it happens constantly
I ran into the same issue holding a connection for a Samsung Galaxy Tab 3. I opened the orbilogin.com site on my desktop when I tried to connect the tab3 and noticed that the ip addresses did not match. The orbi assigned 192.168.1.5 but the tab noted the address of 192.168.1.125. I went into the tab3 advanced setup under the orbi connection and changed the dhcp setting to manual and entered the 192.168.1.5 with the other settings left alone.
Once I restarted the tab it connected quickly and so far seems to be working. I know its not the perfect solution, but it'll work while you're in your home.
Good luck.
- I've actually used wifi analyzer and we do have other signals. The bands I'm using are ones that have the least interference from others actually.
The modem really has nothing to do with the issues here. It's an Arris cm820. I've set the 2.4 to 9 and since I only had I believe 3 or 4 channels to select from on the 5ghz I left it at 48.Try and set the secuirty option on Orbi to none and do a quick test.
In some instances WPA2-PSK [AES] have been known to cause problems, a long shot but give it a try.
Has this issue been solved? Im having the same problem with my samsung galaxy s6.. I get dropped out from the wifi connection and then it reconnects right away...
I'll try that later when I get home from work.
Thanks for the tip..
Issue seems to persist for me, and the router itself is now acting up. Came into the living room this morning and saw it was a solid magenta/purple and no idea why.
- Any update killabandit?
This is happening to me as well. I have an android tv (Samsung smart tv) and if I have beamforming enabled, it stutters and can't stream my local DLNA movies. When I disable beam forming it works just fine.
Hope netgear is looking into it. - Ok, based on what I've read in other threads, implicit beam forming can cause incompatibilities, this is because there is no official spec on it. probably best to leave this option off, these incompatibilities aren't netgear specific, other vendors would have similar problems.
