Hi all
I rooted my NC a few days back, and it's working great. I'm able to connect to and use any wifi I find, (tried 3 unique locations successfully; 2 for 15 minutes a pop, 1 for about 2 or 3 hours) except for my home wifi It works about... 30% of the time. It seems to be totally random as to when it works. I use a DIR 615 at home, running WPA/WPA2 PSK.
It's not a problem with too many devices. I've run two laptops, a wireless 360, and 2 iphones all at once with no problems. Even when I power off the 360 and laptops and put the iphones on 3G I have the same issues with the NC.
Signal strength is also not an issue.
I've had it work for between 2 and 60 minutes at home, but most of the time it reads "Connected, but no internet."
Has anyone encountered this? Or have any idea what might be causing it?
swapdotavi said:
Hi all
I rooted my NC a few days back, and it's working great. I'm able to connect to and use any wifi I find, (tried 3 unique locations successfully; 2 for 15 minutes a pop, 1 for about 2 or 3 hours) except for my home wifi It works about... 30% of the time. It seems to be totally random as to when it works. I use a DIR 615 at home, running WPA/WPA2 PSK.
It's not a problem with too many devices. I've run two laptops, a wireless 360, and 2 iphones all at once with no problems. Even when I power off the 360 and laptops and put the iphones on 3G I have the same issues with the NC.
Signal strength is also not an issue.
I've had it work for between 2 and 60 minutes at home, but most of the time it reads "Connected, but no internet."
Has anyone encountered this? Or have any idea what might be causing it?
Click to expand...
Click to collapse
I had a friend that had the same problem. He called bn support and they suggested they turn off n on the router and use b/g wireless only and it fixed his problem. I know not having n enabled maybe annoying but it was the only fix he colud find. Might be a router issue since he has the exact same router as you.
What version of the Nook Color firmware are you running? v1.0.1 has some wifi improvements, so it could potentially help.
doomstalk said:
What version of the Nook Color firmware are you running? v1.0.1 has some wifi improvements, so it could potentially help.
Click to expand...
Click to collapse
I am on 1.0. To upgrade I just do a wipe of /system and /data via an 8 failed boots reboot, then update, then reroot with autonooter for 1.01 right?
jameswei said:
I had a friend that had the same problem. He called bn support and they suggested they turn off n on the router and use b/g wireless only and it fixed his problem. I know not having n enabled maybe annoying but it was the only fix he colud find. Might be a router issue since he has the exact same router as you.
Click to expand...
Click to collapse
On the router or on the nook?
Edit: And is this for all N routers, or just mine?
I also have a DIR-615 using N with wpa2 and I have no problems. My NC is 1.0.1 rooted with Autonooter..
I can say that the NC had a very decent wireless reception...
Maybe try another channel? Does your DIR-615 have the latest firmware?
I'm sorry, forgive my ignorance; how do I change channels?
The first thought that comes to my mind is: have you checked to see if there is upgraded firmware for your router?
I had no problems with a DIR614 at my sister's or either of the netgears I have at my own home.
The ONLY time I have had problems is when I was using the ad-hox fix script- something went slightly wrong for me and the infrastructure mode wouldn't stay connected to any wifi signal for long.
My solution has been to manually switch between wpa_supplicant files.
I also have the DIR-615, hw rev B2, fw 2.25 and ended up having to run WEP & b/g only as I found that with b/g/n enabled a b device would kick n devices off.
I didn't miss having n functionality, and had to have WEP as I have several devices that do not/cannot support WPA and are b only.
Also IIRC some hw variation of the 615 had various problems. I don't recall what they were offhand but a quick web search should turn something up. I only got this as I got it for a good price and ATT IIRC rev B2 hw was supposed to be OK...
I've run into a similar situation, running dd-wrt. I noticed that when a dhcp lease is created for my nook I get connected, no internet. I delete the lease and it works again.
enfox said:
I've run into a similar situation, running dd-wrt. I noticed that when a dhcp lease is created for my nook I get connected, no internet. I delete the lease and it works again.
Click to expand...
Click to collapse
I will try this next time it craps out. It's working ATM.
cutterjohn said:
I also have the DIR-615, hw rev B2, fw 2.25 and ended up having to run WEP & b/g only as I found that with b/g/n enabled a b device would kick n devices off.
I didn't miss having n functionality, and had to have WEP as I have several devices that do not/cannot support WPA and are b only.
Also IIRC some hw variation of the 615 had various problems. I don't recall what they were offhand but a quick web search should turn something up. I only got this as I got it for a good price and ATT IIRC rev B2 hw was supposed to be OK...
Click to expand...
Click to collapse
I'd miss N for sure. I need N to stream 720p MKVs to my 360 Just in case I want to test that though, how would I go about disabling N on the DIR 615?
As a previous poster mentioned, i changed the settings on my router to b/g only and it fixed the connnectivity issues right away. I wasn't 100% keen on losing n to fix it, but it will do for now. I do get on to the wifi at my work and other places which i wouldn't be diabling n for any reason.
I am on 1.0.1 already and will try putting n back onto the router settings and see when i have some spare time.
I had "DIR-615" problems with WiFi for my Pandigital Novel. Until it just burn out. Well it was a $24.99 gamble of "open box" merchandize at Fry's 2 years ago, and it did work fine as is, just reflashed to the latest firmware. But it was before 615 become DD-WRT-able, and it didn't work for my PDN half the time anyway. So, I got me a Fry's FR-300RTR which is $29.99 rebrand of 615 (open boxes should be like around $15 or so, but there were none at the time.)
Long story short, I put DD-WRT on it, procedure is in the regular DD-WRT forum for Fry's router 95% of the way. The remaining and quite important 5% is in my blog http://fineoils.blogspot.com, enjoy.
For both PDN and Fry's routers to work stable on 802.11n, I used (it's also quite important, as I didn't find anybody else mentioned these) wireless basic settings like:
AP (don't use the "Router" unless you have another "gaming" router for $180 or so in your network(s), but then you don't need this cheapo device in the first place, right?)
NG-Mixed (I'd be working on pure N, but have couple of ancient b/g laptops, plus throaway dumb phone, I'm a cheap skate, as you can see, lol)
Full (20 MHz) (don't go for 40/20, or Turbo, or whatever if you have too many phones around -- which is usually the case today)
Auto (but the actual channel is "1", as it's less crowded in my area; so first scan your area and choose whatever you like more, 3 or 4 APs on your best channel compared to 8-10 on a default channel)
[whatever]
[whatever]
[Advanced Settings] should be left default, OFF, without mark in the box (one may spend a lot of time trying to improve something instead of reading one's nookbooks; I tried a little, had some problems, turned it OFF, and everything goes OK.
Replace all "regular" 2.4 GHz "wireless" phones in your household for the 5GHz ones, as long as you don't use BT/tethering, don't use your cell phone too close to your NC.
Use default 20db gain, it's just fine. This cheap piece starts to overheat even on default signal level, so consider voiding the warranty on your 615 or Fry's and set some heat sink like it's shown in my article. The picture shows a different router (and with some other weird mods), but you get the idea.
On less than 15% of battery charge, there might be some problems with WiFi (and I yet to see someone finding what is a default NC transmission level, and if it's 100%, I'd rather play with 20....40% instead and see what happens).
However, on a deplete battery there's lots of other things that may become dysfunctional.
Firmware did not help. Looks like I've fixed it by replacing my router. Thanks, boxing day! Using a DIR 825 now.
swapdotavi said:
Hi all
I rooted my NC a few days back, and it's working great. I'm able to connect to and use any wifi I find, (tried 3 unique locations successfully; 2 for 15 minutes a pop, 1 for about 2 or 3 hours) except for my home wifi It works about... 30% of the time. It seems to be totally random as to when it works. I use a DIR 615 at home, running WPA/WPA2 PSK.
It's not a problem with too many devices. I've run two laptops, a wireless 360, and 2 iphones all at once with no problems. Even when I power off the 360 and laptops and put the iphones on 3G I have the same issues with the NC.
Signal strength is also not an issue.
I've had it work for between 2 and 60 minutes at home, but most of the time it reads "Connected, but no internet."
Has anyone encountered this? Or have any idea what might be causing it?
Click to expand...
Click to collapse
I can confirm this.... though this was on a friend's tmobile dlink router (for uma support).
Sent from my SGH-T959 using XDA App
Look. What I proposed is using DD-WRT on DD-WRT-able D-Links. Which, in their original form (firmware), are either lower than average, or barely average routers in terms of throughput/throughput stability, stress under the load of multiple hosts/DNS/wired&wireless combinations/wireless signal attenuation, and overall QoS/load balancing, or lack of it. Then, many ISPs tend to shape traffic dynamically and drastically when observing some bursts of traffic on some ports (think P2P). D-Link devices do not like that. So no wonder they are cheapest on the market (seems like TRENDnet junk might be cheaper, but these just don't work stably even under low loads).
DD-WRT on 615 helps to alleviate many of most acute problems described above. Sure, one can decide like swapdotavi to put up extra $80...$100 and buy DIR-825 with twice RAM and 60 % faster processor, but guess what: it has a commercial version of DD-WRT as its firmware
aludal said:
Look. What I proposed is using DD-WRT on DD-WRT-able D-Links. Which, in their original form (firmware), are either lower than average, or barely average routers in terms of throughput/throughput stability, stress under the load of multiple hosts/DNS/wired&wireless combinations/wireless signal attenuation, and overall QoS/load balancing, or lack of it. Then, many ISPs tend to shape traffic dynamically and drastically when observing some bursts of traffic on some ports (think P2P). D-Link devices do not like that. So no wonder they are cheapest on the market (seems like TRENDnet junk might be cheaper, but these just don't work stably even under low loads).
DD-WRT on 615 helps to alleviate many of most acute problems described above. Sure, one can decide like swapdotavi to put up extra $80...$100 and buy DIR-825 with twice RAM and 60 % faster processor, but guess what: it has a commercial version of DD-WRT as its firmware
Click to expand...
Click to collapse
Your advice seems very applicable. I wanted to test the easy fix (firmware upgrade) first before I started deciphering your post which, honestly, went way over my head. I didnt mean to overlook your post or anything; your advice seems valuable.
By the time I found out my lazy firmware upgrade didnt work my girlfriend was so fed up with the outages I was causing by constantly rebooting and playing with the router that she dragged me out to look at boxing week sales and bought the 825 herself. I wasnt about to stop her
I was simply presented with an easier option is all.
swapdotavi said:
Your advice seems very applicable. I wanted to test the easy fix (firmware upgrade) first before I started deciphering your post which, honestly, went way over my head. I didnt mean to overlook your post or anything; your advice seems valuable.
By the time I found out my lazy firmware upgrade didnt work my girlfriend was so fed up with the outages I was causing by constantly rebooting and playing with the router that she dragged me out to look at boxing week sales and bought the 825 herself. I wasnt about to stop her
I was simply presented with an easier option is all.
Click to expand...
Click to collapse
Ever tried to reboot your GF?
Jokes aside, your brand spank new 825 should have a commercial DD-WRT distro on it, and for it to show best possible wireless performance (like in: overall throughput, load balancing, QoS, filtering of cell and other parasite interference/frequencies), you may want to look at my first post for 6 or so basic wireless parameters that I have found useful for use 2 tablets, 2 laptops, and 2 wired PCs in my household, porch, and backyard.
Sure it should work fine out of the box (unlike 615), but it takes some effort and play with a router when tuning your NookColor for predominant usage of 802.11n
If problems arise still, try to touch your router at its different outer body parts and check their temperatures. These should be mildly warm, anything hotter requres a trip to the shop for the replacement.
Not yet rooted Nook would refuse to stay connected, but dropping wireless N worked like a charm. All of the devices in the house are using G anyhow, side for a laptop, so this worked great.
aludal said:
Look. What I proposed is using DD-WRT on DD-WRT-able D-Links. Which, in their original form (firmware), are either lower than average, or barely average routers in terms of throughput/throughput stability, stress under the load of multiple hosts/DNS/wired&wireless combinations/wireless signal attenuation, and overall QoS/load balancing, or lack of it. Then, many ISPs tend to shape traffic dynamically and drastically when observing some bursts of traffic on some ports (think P2P). D-Link devices do not like that. So no wonder they are cheapest on the market (seems like TRENDnet junk might be cheaper, but these just don't work stably even under low loads).
DD-WRT on 615 helps to alleviate many of most acute problems described above. Sure, one can decide like swapdotavi to put up extra $80...$100 and buy DIR-825 with twice RAM and 60 % faster processor, but guess what: it has a commercial version of DD-WRT as its firmware
Click to expand...
Click to collapse
I have the impression that Dlink don't actually make their own hw, and possibly even their own firmware as IIRC even with the 6XX series of routers they went through SEVERAL various CPUs and fw variants in those routers. e.g. IIRC the 615 had 3 different hw variations and 3 different fw families...
Back when I got it there was no choice other than stock fw and possibly one of their betas, and at that time it was one of the better performing routers in that price range overall, or more specifically the rev B2 hw variant...
Disabling N: it's in one of the router setup pages... probably have to use the manual setup rather than their "wizard", which is what I always do anyways...
Related
So ever since I've gotten my Nexus One I've been noticing it drops out of a WiFi way too often. It does it both at home and at work on Wireless routers using the latest firmware. I've set the sleep policy to never go to sleep but most of the times I wake my phone up, I'll find it on 3G instead of the full strength WiFi it should be on. On 2.1 when I'd go into WiFi settings it would show the connection and say something along the lines of "Connection unsuccessful, tap to try again" and on 2.2 it just says "Disabled, Secured by blah blah blah". If I retry, it ALWAYS connects and WiFi will stay active for a short period of time before falling back to 3G.
Is there some way I can tell Android to retry the WiFi connection if it fails instead of just giving up? I've been looking through the WiFi API's on the Android Developer site and I'm this close to writing an application that will attempt to mitigate this issue for me.
If I'm within range of one of my pre configured networks, I want the phone to try it's hardest to stay on WiFi. If it loses connection, retry. It it can't get it after 5 retries, wait five minutes and try it again, don't just give up and mark the connection as disabled.
I've read tons of threads about people with WiFi issues and people always say "it's the router, it's the channel, etc, etc" but my WiFi works perfectly fine as long as there is a human to reconnect it if it drops.
Anyone else in the same boat as me?
ok so apparently I'm the only one with an N1 and a WiFi issue.......
I have the same exact issues.
I have the same issue as well and if it stays on I have to turn wifi off and back on so it will connect properly
-------------------------------------
Sent via the XDA Tapatalk App
same issue here. i had been looking for an app that would force the connectivity, but the market doesn't seem to have it. just a bunch of crappy wifi on/off switcher management apps. i'm surprised that no one has hacked this function or built an app for it.
It's certainly a very annoying problem. Mine will go to known good wifi networks, at work, at home and at other locations where my other devices work flawlessly. I have a coworker with the exact same firmware (we updated using the same file) on a nexus one that has never seen this problem, which I find odd, but I'm fairly new to Android. It looks like a software or driver issue to me, but as I said, I'm new to Android.
My device shows the known networks as "Disabled", but I can connect manually.
Looks like it's worth me coding up an App to fix this then.
what kernel are you using? i used to have that problem but that has gone away with newer kernels. unfortunately a new problem has arisen where after being in standby for a while, wifi shows as connected but doesn't have an outside ip. wondering if its my rogers modem or not.
y2whisper said:
what kernel are you using? i used to have that problem but that has gone away with newer kernels. unfortunately a new problem has arisen where after being in standby for a while, wifi shows as connected but doesn't have an outside ip. wondering if its my rogers modem or not.
Click to expand...
Click to collapse
2.6.32.9-27220-g328f560
android-[email protected]#1
I've never tried a new kernel.. Is this something I should look into?
I'm running the same kernel.
BootsSiR said:
Looks like it's worth me coding up an App to fix this then.
Click to expand...
Click to collapse
Personally I wouldn't do any work towards writing an app to fix this since it looks to me to be an OS or driver issue that should be resolved in a future release (hopefully in very short order).
An app would really just be a band-aid, but I'm the lazy type and I can deal with using my cell ular data when I don't feel like reconnecting my wifi.
Full disclosure: I'm a crummy programmer and it takes me forever to write stuff so I'm usually less inclined to do it.
w9ndb said:
Personally I wouldn't do any work towards writing an app to fix this since it looks to me to be an OS or driver issue that should be resolved in a future release (hopefully in very short order).
An app would really just be a band-aid, but I'm the lazy type and I can deal with using my cell ular data when I don't feel like reconnecting my wifi.
Full disclosure: I'm a crummy programmer and it takes me forever to write stuff so I'm usually less inclined to do it.
Click to expand...
Click to collapse
I'd rather take the time to fix it then wait for an update that may never arrive. Always fun digging into the API anyways
That's cool. I still find it a bit troubling, though, that some devices see it and some don't, using the same firmware, on the same wireless networks.
I guess it could be a board rev. difference or an app conflict or something. ::shrugs::
I have a similar problem. I use APNdroid to keep cellular data off and use wifi, but I continually have to reconnect wifi no matter what if I am not actively using it. Defeats the purpose of push email.
I downloaded APNdroid after checking data usage and finding that with wifi on there was still significant 3G leakage. Especially confusing with wifi set to never sleep and plugged in overnight.
On the plus side, APNdroid has netted me a lot more battery life, I can almost get two days and one night. I almost never use my spare battery anymore.
Just as an additional data point, I am having the exact same issue with 2.2 FRF83 (I had been on FRF50).
It looks to me like it is simply scanning all of the time and never associating with a known network. I'm not sure why it flags them as "Disabled", however.
Have you guys tried to set the "wi-fi sleep policy" to "never"
if not, try this:
Wifi settings->menu->advanced->wifi sleep policy->Never
safeplayer22 said:
Have you guys tried to set the "wi-fi sleep policy" to "never"
if not, try this:
Wifi settings->menu->advanced->wifi sleep policy->Never
Click to expand...
Click to collapse
Yeah, it doesn't help, that was one of the first things I tried. Any time I leave and come back, the networks show as "Disabled". It's a frustrating issue in that it isn't consistant. It's 80% fail, 20% work.
I had my g1 for a year now and just now got my n1. I havent rooted it b/c of this bug. At first i couldnt listen online radio b/c as soon the display went out it would buffer the whole time. I played with the wifi router and the n1 wifi settings an managed to fix it somehow, BUT when i wake up in the morning for some od reason it lost connection and never reconnected again. So i can hear online radio with the display out but after some hours w/o online radio and just in standby it loses wifi connection and never connects again
This issue is not new. There is a thread on the google forum many pages long. Nobody hase even a clue where it could come from. Some1 on the forum said if u call support they will tell its ur routers fault.
The n1 completly ignores the sleep policy settings.
I have rooted two g1s with goldcard and still using one w/o a problem.
-------------------------------------
Sent via the XDA Tapatalk App
Zapo said:
I had my g1 for a year now and just now got my n1. I havent rooted it b/c of this bug. At first i couldnt listen online radio b/c as soon the display went out it would buffer the whole time. I played with the wifi router and the n1 wifi settings an managed to fix it somehow, BUT when i wake up in the morning for some od reason it lost connection and never reconnected again. So i can hear online radio with the display out but after some hours w/o online radio and just in standby it loses wifi connection and never connects again
This issue is not new. There is a thread on the google forum many pages long. Nobody hase even a clue where it could come from. Some1 on the forum said if u call support they will tell its ur routers fault.
The n1 completly ignores the sleep policy settings.
I have rooted two g1s with goldcard and still using one w/o a problem.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Well, I know fore a fact it's not my access point. I am a network engineer and worked on wireless systems for years and debugging these types of problems is something I'm a bit obsessive about. This stinks of a software or driver problem to me. It could potentially be a hardware revision issue since we have a N1 that works perfectly in all scanerios.
I've tested this with the following access points:
Apple Airport Extreme
Apple Airport Express
Meru
Cisco 1231
Cisco 350
Belkin pre-n
Linksys WRT54G stock
Linksys WRT54G dd-wrt (I forget the build number)
Soekris Engineering running pfSense
All exhibit the same behavior, while my control devices (Apple iPhone 3g, Apple Macbook Pro and a MyTouch 3g running Cyanogen 2.1).
I wasn't aware that this was related to rooting, I'd be more than happy to move back to a stock ROM if that solved my problem. Maybe I'll try that today if I get some time.
Could you possibly post a link to the google forum you're referencing?
I'm currently digging through the alogcat output to see if there is anything interesting in there.
This issue is worse since I upgraded to 83. I'm actually holding off to try CM6 when it comes out to see if there is any better performance there. I'm not sure if he uses updated drivers or kernel that may give better wifi performance.
hi there i am having a problem with my sgt p1000 wifi just upgrade to 7 series 4.1.0 i noticed that my wifi connection is not stable...
Think is an hardware problem.because i have installed this rom and i have any problem with the wifi.
Galaxy Tab P1000-OVERCOME 7 SERIES 4.1.0
icy25 said:
hi there i am having a problem with my sgt p1000 wifi just upgrade to 7 series 4.1.0 i noticed that my wifi connection is not stable...
Click to expand...
Click to collapse
Get yourself over to the Overcome thread and READ through it. Your answer lies within...
No offense phlooke, but you've told a few people that, and I've already become a bit lost in the over 100 pages of posts in that overcome 4.1 thread. Unless you're gonna post a link to the page in that thread where the solution begins, how is your above post helpful?
I'm going back into that thread now, but I swear, it's full of a lot of duplicate commentary, side discussions, and very little of the content is useful. A mod should clean up that thread.
maybe this one?
http://forum.xda-developers.com/showpost.php?p=21180574&postcount=770
Overcome 4.1 wifi fix attached there by Alterbridge himself.
Well the reason the thread is so congested is because of the same questions being asked over and over again.
People are too damn lazy to do there own investigation.
If you can't be bothered to read the whole thread there's a search function.
Check the forum rules.
Lastly the post I made is helpful in pointing the op to the place containing the answer? Duh.
Sent from my GT-P1000 using XDA App
Overcome Series ROM's are awesome but I always have a screen problems on my TMO Tab. I get these little brownie prickles on my screen like a twinkling stars at night. I am not sure why, maybe it's because the LCD and RAM are under voltage. Normally, every time I flash a new ROM, I always flash back my modem.bin just to make sure that I get all the benefits of my carrier's. Right now, I use Chromed JQ8 Stock ROM with Dip7 Kernel. It's pretty much stable and fast. Chromed JQ8 and Dip7 Kernel combo works furiously fast and stable. No bugs and everything works wonderfully.
Actually not really, because if you read through the conversations on the Overcome 4.1.0 thread, that wifi fix doesn't work for many people. And now, as a new Overcome user (as of four hours ago), it doesn't work for me, either. I flashed the fix file from CWM and I still get an up, down, up, down and so on with the wifi connection. There needs to continue to be people asking some of the same questions about this, so that people like yourself don't give the mistaken impression that this problem is somehow "solved". I'm not putting you down, because I can tell from your posts on XDA that you really want to help when and where you can (as do most people on XDA including myself), but the fact remains that this wifi problem is NOT fixed, and at least for the time being, the more people who squawk about it on here or in the official Overcome thread, the more likely a true solution will present itself.
Because right now, there isn't one. The flash fix doesn't work for a lot of us, and I shouldn't have to tweak my router. That's a ridiculous notion. That, and I find myself moving from location to location, relying in a variety of wireless networks to connect to, and I certainly can't go and tweak every single router I come into contact with. It's unrealistic, and it's a *software* issue on the ROM. So a fix is possible. But isn't available just yet.
So this thread, and any other new ones... at least for the short term, they have the latent function of keeping the issue current and visible to the developer or others who might have the tech savvy to truly fix the issue.
personally, if I don't feel like helping, I will just move on.
I just don't understand why some people feel like policing the threads while not offering valuable info.
Take a deep breath and ignore the post.
As for the wifi problem, I wonder if it is modem related? It has to be either that or hardware related (batch issue with chipset?)
There is a small number of users with unstable wifi issue.
Small number of reported people with this issue. Who knows how many it actually affects, but more than three is too many. I can't see why it would be hardware related, since the devices in question work fine prior to flashing Overcome 4.1.0. Some people have switched to Overcome 4.0 and seen the problem go away (as have those who switched to other Chefs' ROMs). Of those who install 4.1.0 and see no problems, it suggests that whatever change happened between 4.0 and 4.1.0 affects only certain routers. Maybe some kind of optimization done has rendered a number of router models affected. ???
Suleeto said:
Of those who install 4.1.0 and see no problems, it suggests that whatever change happened between 4.0 and 4.1.0 affects only certain routers. Maybe some kind of optimization done has rendered a number of router models affected. ???
Click to expand...
Click to collapse
It has nothing to do with what router you have. Any router set to have no lease expiration will cause the bug. MOST routers don't even allow you to do such an asinine things. I couldn't force my router to have no lease expiration if I wanted to (which I wouldn't, because it would be stupid).
Search google for "Netgear No Lease Expiration". This is a GENERAL problem. It is not confined to Gingerbread Overcome ROM 4.1.
The bug is a combination of some routers' fault for shoddy programming and a gingerbread wifi config fault for not handling a fringe (and borderline retarded) but technically acceptable setting.
Change (FIX) your router's setting.
---
See for details: http://www.ietf.org/rfc/rfc2131.txt
According to the RFC SPEC:
The client may ask for a permanent assignment by asking for an infinite lease. Even when assigning "permanent" addresses, a server may choose to give out lengthy but non-infinite leases to allow detection of the fact that the client has been retired.
Nowhere in the spec does it say the server should give out Infinite Leases to clients that do not ask for them. If your router gives infinite leases to clients that can not or do not handle them, THE ROUTER IS THE BROKEN PART.
So you're saying that Froyo, WinMo, and other more powerful computing devices have additional functionality to deal with "fringe" features on select routers?
I am considering your explanation but you can understand how the explanation itself also might sound asinine to a layperson. I understand what DHCP servers do and how IP leases work.
My router is a newer Belkin model only a couple years old.
Edit: Because I am curious, I'll be looking into the router settings to see just what it is actually set at.
Edit 2: Yep, it's set to forever. Then again, I still can't understand why that is in your assessment considered a "bad" thing. And in my experience, it has never, NEVER been a problem with previous tech, over the years and years of wifi router use.
None of this explains or justifies why Gingerbread-based ROMs should suddenly lose this functionality. It is not like Android clients are going to change the face of what is a very common DHCP configuration among routers past and present (despite your sentiments). To me, moving from Froyo builds that can handle this to Gingerbread builds that cannot seems counterproductive for Google, as most consumers WILL NOT want to tweak their three to five year old routers that otherwise connect fine to every other computing device they can bother to try to connect with.
And like I said previously in this very thread... you can't exactly go into the back room of a Starbucks, the town library, or of local businesses, and demand they make a change to their DHCP lease configurations that for everyone else (oh! oh! oh! Including the well loved iPhone!) works without any issues whatsoever.
So I'm sorry, I'm not being a **** here, but what you're suggesting is an extremely large pill you are asking me to swallow, and it just seems like a prescription for a disease I do not possess.
LOL, checked the router and found the problem.
Was that not covered in the thread as one of the issues/fixes?
Jeez.
you can't exactly go into the back room of a Starbucks, the town library, or of local businesses, and demand they make a change to their DHCP lease configurations
Click to expand...
Click to collapse
And you'll almost never have to, because 99.5% of routers are made to the spec I linked and won't give the type of lease that your router does. Surprising that there isn't a firmware upgrade available that changes the default on the router to not be infinite - may just be because you can do it yourself in the router setup, so they didn't bother.
The "infinite-lease" by router without client request situation is not specifically defined in the spec, which means it is not necessarily defined in all clients. What makes other devices work with this router is either
a) the other clients can/do request infinite-leases
b) the other clients happen to have a lease handler that accepts an infinite lease
But nothing in the spec says the client should handle an infinite lease if it did not request one. In the case of this particular gingerbread ROM, that handler is left out, which is a case of not coding defensively enough. -Great- code would handle that in a different way than re-scanning constantly. However, there is a difference between "great code" and "meeting specs". By specification technicality it is the router that is on the wrong side of this argument.
All it means is that both sides kind-of suck. And in this situation the sucky part you have control over is the router, unless Alterbridge releases a modified wifi config that can handle this case gracefully that it shouldn't have had to handle in the first place (but honestly should have anyway, because that's what great code does).
phlooke said:
LOL, checked the router and found the problem.
Was that not covered in the thread as one of the issues/fixes?
Jeez.
Click to expand...
Click to collapse
Um I only mentioned that out of rhetoric, I am not questioning what I can do to resolve the tablet connection process AT MY HOME, I'm questioning the logic of defining the router as a "problem", which the other gentleman (darkmatter) is discussing with me. Or did you miss the point I was actually making? Jeez
darkmattar said:
And you'll almost never have to, because 99.5% of routers are made to the spec I linked and won't give the type of lease that your router does. Surprising that there isn't a firmware upgrade available that changes the default on the router to not be infinite - may just be because you can do it yourself in the router setup, so they didn't bother.
The "infinite-lease" by router without client request situation is not specifically defined in the spec, which means it is not necessarily defined in all clients. What makes other devices work with this router is either
a) the other clients can/do request infinite-leases
b) the other clients happen to have a lease handler that accepts an infinite lease
But nothing in the spec says the client should handle an infinite lease if it did not request one. In the case of this particular gingerbread ROM, that handler is left out, which is a case of not coding defensively enough. -Great- code would handle that in a different way than re-scanning constantly. However, there is a difference between "great code" and "meeting specs". By specification technicality it is the router that is on the wrong side of this argument.
All it means is that both sides kind-of suck. And in this situation the sucky part you have control over is the router, unless Alterbridge releases a modified wifi config that can handle this case gracefully that it shouldn't have had to handle in the first place (but honestly should have anyway, because that's what great code does).
Click to expand...
Click to collapse
I am not really concerned with "great code" vs. "poor code" here, I'm concerned with consumer use. I am more and more convinced this was a decision of the ROM chef and less that it's "Gingerbread" design. I can't imagine Google taking a risk of alienating even a small percentage of consumers who find themselves trying to connect to routers with default infinite leases. You claim that most new routers don't even allow that. This would mean that "infinite lease" is a legacy configuration, but again, every other device seems to have no trouble with that, because companies making these devices and their ROMs understand that the average consumer DOES NOT always know how (or have the option to) go in and change the config of a given router.
And btw... using the term "code" to criticize router design is a bit sloppy. How cleanly it's "coded" isn't at all what you're describing. It's "design philosophy" that is at work here. Not "code". Sometimes amateur programmers haven't spent enough time in the corporate development world and do not understand that the deciding factor in features and function is the COMSUMER end. Code is the guts, not the result. The result is designed based on need.
Also, you have some devices (recent ones, like my HP wireless printer for instance) that do not have an easy way to be assigned a fixed IP, and do not like frequent DHCP reassignment because the driver end on the client PC retains the IP as the pointer for the print queue. An infinite lease allows the initial assignment process to happen, and allows the client PC driver assigned IP to keep consistent with the IP assignment of the printer. This is not the only device that has this issue, but it is an increasingly common problem among a few wireless printer manufacturers in the way they set up client software connections to wireless printers.
So are you saying I should change my router config and cause printing problems in order to satisfy my apparently gutted, less-than-full featured network functionality of my custom flashed Android device?
Does that sound reasonable? Does that even address the concern that I have no control over public and other private wireless networks that I might try to connect to (and have infinite lease enabled)?
Tell you what: I will be going to not one, but three different wireless networks today. One at my local college, one at Starbucks, and believe it or not, the Denny's down the street has a brand new wifi setup installed (only about six months old). I will tell you what happens.
Even still, if I have this situation at home, then inevitably it exists elsewhere. And I would wager it's not a 1% experience, either.
I'm all for streamlining custom ROM's and trimming the fat, but not at the expense of such particularly important functionality. You call it "fringe", but from a product development point of view, we would consider it "comprehensive".
I like my "comprehensive" term a lot better than your "fringe" one. Maybe dropping this kind of functionality will happen eventually in devices, but I feel that doing so now is premature.
And I'm hoping that the chef reads this and at least offers the code in a subsequent version.
---------- Post added at 10:06 AM ---------- Previous post was at 09:50 AM ----------
From the Overcome 4.1.0 thread:
absolutab said:
Not every GB ROM. Only on 2.3.6 JQ8. Had no issues with wi-fi on previous GB versions.
OTOH, on previous versions I had market issues (even at 240 dpi and with the 60Mb cache hack) and everything's working great on 2.3.6. Go figure... If I could have overcome 7 4.0 with overcome 7 4.1 market behavior I'd be more than happy.
I've tried ICS CM9 and wi-fi seemed stable.
Click to expand...
Click to collapse
So Google may have indeed been the one to F' things up... Still, my sentiments stay the same, and it means that I might be switching to Overcome 4.0 until the situation is resolved. At least if this is the case, it's not the Chef's fault.
It has been a good discussion - I feel it is definitely clearing up the details, and I've learned a few things myself while researching to make sure my dhcp knowledge is up-to-date and at least mostly factually correct.
Also, you have some devices (recent ones, like my HP wireless printer for instance) that do not have an easy way to be assigned a fixed IP, and do not like frequent DHCP reassignment because the driver end on the client PC retains the IP as the pointer for the print queue. An infinite lease allows the initial assignment process to happen, and allows the client PC driver assigned IP to keep consistent with the IP assignment of the printer.
Click to expand...
Click to collapse
The infinite lease merely stops the Lease Handshake from occurring. The lease handshake is a different communication altogether from DHCP [re]assignment. About the only time a DHCP assignment will happen is if DHCP settings change on the router between leases, and on the rare occasion it could happen that the Lease Handshake fails (like if one of the devices is unplugged or loses power momentarily) and a different device is connected and takes the IP, requiring a new one to be given to the other device. However, on your mostly stable/unchanging home network, this should happen pretty much never. The only case worth worrying about is if a power outage lasts long enough to span the lease expiring on multiple devices, they could reconnect and get different IPs each
less-than-full featured
Click to expand...
Click to collapse
I have been quoting from the RFC on DHCP. What your router is doing is not "full featured", it's "extra featured", which means not every device is going to support it, nor does it have to support it to be approved. If you look up "infinite lease" on google, you will see that essentially all documentation recommends against it. Another humorous link is to microsoft DHCP server software, which allows setting infinite leases (it is nowhere close to the default) but then begs you not to in the documentation!
However, since the spec does not explicitly state that a device should fail and retry the connection when an infinite lease is given, there really is no wrong method.
There is certainly a "more-appealing-to-users-desiring-full-compatibility" method. But again, when one device does something not explicitly defined in the specifications for ALL DHCP devices, it is just asking for other devices to be unable to connect to it.
Does that sound reasonable? Does that even address the concern that I have no control over public and other private wireless networks that I might try to connect to (and have infinite lease enabled)?
Click to expand...
Click to collapse
As for this concern, I may be wrong, but I believe any public wifi with infinite leases will be broken 1/2 the time due to the allocated IP space being used up by devices that aren't even connected anymore. They'll be rebooting their router every few hours/days depending on how heavy their traffic is.
Almost all documentation warns against even setting your client to request infinite leases, or allowing your router to grant them
See: http://technet.microsoft.com/en-us/library/dd183602(WS.10).aspx
or: http://www.tcpipguide.com/free/t_DHCPLeasesLeaseLengthPoliciesandManagement-4.htm
or: http://blogs.technet.com/b/teamdhcp/archive/2007/02/07/configuring-lease-time.aspx
Important Excerpts from above links:
Although it is possible to configure a client with infinite lease duration, use infinite lease durations with caution. Even relatively stable environments have a certain amount of client turnover. At a minimum, computers might be added and removed, moved from one office to another, or network adapters might be replaced. If a client with an infinite lease is removed from the network without releasing its lease, the DHCP server is not notified, and the IP address is not automatically reused. Also, when using an infinite lease, options set on the DHCP server are not automatically updated on the DHCP client, because the client is never required to renew its lease and obtain the new options. We recommend that you use reservations, rather than infinite lease durations.
Click to expand...
Click to collapse
Perhaps the most relevant one of all is here:
Should I have INFINITE lease time?
It’s technically possible and most of the devices support it but the recommendation is never to have infinite lease time. The main reason is that any change in network configuration on dhcp server will not be updated on the client as the client will not trigger renew. Also it’s reported on some site that few devices don’t behave properly with INFINITE lease time and result in service crash and other issues. So if you are dhcp admin and want to avoid unnecessary issues it’s recommended not to have INFINITE lease time
Neelmani
Windows Enterprise Networking
Click to expand...
Click to collapse
See quotes above. It is way more of a router problem than a client problem.
But, in the end, I do agree that a well-designed wifi driver -should- be capable of handling an infinite lease without failing and reconnecting endlessly.
After reading all that the morning you posted it, I agree with you even before the edit. I see your point.
And I'm glad you also seem to agree with me that it could have been more comprehensive.
I've since turned my lease to two weeks (the maximum increment other than infinite). Hopefully my printer will continue to sync up to the client software later on. I will admit that I partly blame HP and other printer manufacturers for using such a LAZY workaround for their wifi printing solutions.
I suppose in a few years from now it won't matter. I still haven't visited those three other networks I wanted to try Overcome's Gingerbread on. Not yet. Been extremely busy. In a few minutes I'll be heading to a Starbucks in another town, so it might happen.
Connection problems either WiFi or physical cable have all the same similarity, Manufacturer's problem and not the OS. If I remember it correctly, way back in the 90's, Modem manufacturer's would just produce hardware and doesn't even think about the end user that will use it. We used to trash WinMo for having so many hardware problem's without realizing that some of the hardware manufacturer's doesn't go by the standards when designing and writing device drivers.They'll just re-use the same design hardware and hoping that they could just re-write the device coding to make it work whatever OS the end user would be using.A well designed hardware makes a coder job fairly easy and would work easily with the end user without a hitch. Sadly, I have to admit that until to these days some manufacturers still have problems catching up every time we have a new OS and merging two OS on a router to make a connection is still a ***** for them.I hate to say it, but "Belkin" should join the club properly .
Sometimes happens only !
I flashed overcome 4.1 over 20 times (while trying other roms and CM9 releases) and return back to it.
on 50% of the cases wifi caused problems. So wonder was about cache - wiping issue.
P.S. Yes i do use same file everytime and re-stock.
Try it.. Simple
i can smile use this because wifi easy connect... use this
1. Install Wifi Static (download from Android Market)
2. Make sure your wifi is connect.
3. Open Wifi Static, and click all box.
4. Click (add configuration) and press button option at your tablet.
5. Now u can see Generate click it.
6. Now click at IP Address change it. example:
192.168.2.1 to 192.168.2.100
7. Restart wifi.
it simple because can save configure and know
ip address/gateway/netmask/dns1/dns2
just changed ip address because you should use ip address no people take already.
easy to use at McD... or any Wifi
Just received my One in the mail today. After connecting to my home WIFI I started experiencing connectivity issues with all devices on my network. This thing is constantly pinging I/O. Screen shot of my bandwidth monitoring graphs from DDWRT'd router attached. When I turn it off I get great speedtest.net results and a quiet flat line on my monitor graphs. Turn WIFI on the phone back on and the graph lights up and speed tests take a dump. Any ideas?
my roommate's iphone5 does this, but it's intermittent. I'll be playing BF3 and notice lag spikes all of sudden. That's how I always know he's either home or connected to Wifi. Doesn't always happen though.
this has been constant since I turned it on at 3 PM today
My LTE did this to my network too, fixed it by putting in a $1200 Checkpoint security appliance lol, been running this way for about 3 months no issues. Somewhat of temp solution, but one of the benefits of working It, have to return to company. Still have not had time to dig deeper, just needed fixed ASAP due to fiancé getting frustrated that Internet always going down.
Sent from Taptalk on EVO LTE soff on some awesome custom Rom!
I had same issues we have 10 devices here and while playing Halo4 noticed lag. We upgraded our Router to Netgear 5g and havent had troubles since.
Sent from my HTCONE using xda premium
Need a better router and also check your channels for a temporary solution too.
Sent from my HTC One
not a router issue. as of this morning I have powered off all other connected devices and was able to produce the same issue. Having constant I/O activity from a particular device is not indicative of a router issue. Something in the phone, service or app, is constantly pinging.
I haven't experienced this issue with mine. Been running the One along with my laptop, PS3 and Xbox without any problems. Using a Linksys routing running DD-WRT, fwiw.
onefstfoknv6 said:
not a router issue. as of this morning I have powered off all other connected devices and was able to produce the same issue. Having constant I/O activity from a particular device is not indicative of a router issue. Something in the phone, service or app, is constantly pinging.
Click to expand...
Click to collapse
It may be an app trying to lock. I have two Ones with various apps and haven't had any ping issues. Just was online with computer and our device activities are medium in use and nonexistent at idle.
Sent from my HTCONE using xda premium
just went out and bought a Linksys EA6500 HD Video Pro AC1750. Issue remains. As I suspected, not a network infrastructure issue. Now I need some input as to what phone services might be the culprit. Installed a data monitor app and have no fruitful information to share from that either.:crying::crying::crying::crying::crying::crying::crying::crying:
I bet if you have the Asus RT-AC66U you wont have any problems. It's $200 but man is it a beast. Plus it has AC and so does your new phone so I suggest it. I bought mine about 2 weeks ago and I love it. Allows me to have a network printer now and my repeater for my PS3 doesn't lose any signal strength at all. I get 45mbps from LAN and 45mbps from wifi and 45mbps from my repeater on LAN and wifi. Everything is at max.
Great router and I am always happy to promote a great product.
Just grab a copy of wireshark, install on a laptop or pc and filter out your cell to determine what its doing. Shouldn't frame you more than 5 mins.
Sent from my EVO using xda app-developers app
I did a hard reset and am now working properly.
I apologize for not diagnosing the issue to find the root of the problem. I know that would have been useful. For now, the fix is HARD RESET.
Idk... I made sure my home internet would be able to keep up with me... Avg 115mbps
Sent from my PG86100 using xda premium
***UPDATE***
After the initial WIFI issues I had were inexplicably resolved with a hard reset, I ended up having a dead pixel and had the device replaced.
The replacement device was great out of the box, from approximately April 25th to May 6th. Yesterday, May 7 2013, I had a notification for an update to "Sprint Zone." I allowed the update. Upon the completed installation of the Sprint update my WIFI issues returned. I uninstalled all Sprint related services I could and stopped the ones I could not. Still the WIFI issue remained. I once again was only able to remedy the problem with a hard reset. There is obviously an issue with the relationship between Sprint software and the WIFI hardware, and it is not isolated to a particular device. The device was brand new at the time of my original post and has since fallen off the first few pages that get trolled. We are nearing one month in service of this device and I can't believe that I am the only one to have experienced it.
I want to know....
I am having this issue as well.
Really shouldn't have switched to Sprint as I am in LA and wow, the network is trash compared to Verizon over here. Unusable in most areas.
Anyway, rooted, on d3rpone , 4 different releases of it, same wifi issue.
I was getting the issue stock as well.
Still trying to analyze when it takes place.
A couple of quick ideas: First, you might want to see if whether it's specific to 2.4 or 5 gHz bands. I expect not, but worth looking. Also, maybe try disabling notifications in Sprint Zone -- maybe the stupid thing is phoning home a lot? Once you're sure you don't have a hardware problem, you might also want to consider unlocking and running Viper - that decruds a lot.
scottegos2 said:
A couple of quick ideas: First, you might want to see if whether it's specific to 2.4 or 5 gHz bands. I expect not, but worth looking. Also, maybe try disabling notifications in Sprint Zone -- maybe the stupid thing is phoning home a lot? Once you're sure you don't have a hardware problem, you might also want to consider unlocking and running Viper - that decruds a lot.
Click to expand...
Click to collapse
Thanks for the input. I will be switching to Viper if I have the issue again.
I did try selecting specific WIFi bands, as well as using the "auto" option. No change.
My phone never caused any issues with my DD-WRT router (Linksys e3000). Can't even replicate now.
Vincent Law said:
My phone never caused any issues with my DD-WRT router (Linksys e3000). Can't even replicate now.
Click to expand...
Click to collapse
not a router issue. problem persists in any wifi environment i log in to.
I've seen all the problems about Lollipop and Wifi not connecting. However, my problem is different. I connect just fine AND I'm getting 31 ms ping, 60mbps down and 12mbps up. However, my internet browsing is slow, Facebook is slow, you tube is slow. Pretty much anything I need is slow except that my e-mail comes in, although if I need to synch anything, but my inbox (because that's pushed) it's slow as well. Even the speed test takes a while to load up, but when it does these are the results I get. The only solutions I find are about problems not connecting to the internet. Even that being the case I tried those remedies with no luck. Also my wife who just got a Moto X has the same problems. Hmmm both phones are made by Motorola I'm wondering is this is a coincidence. I should say I wasn't having these problems a few weeks ago they just kind of started and my wife had a Moto G that didn't have these problems. This combined with bluetooth issues is making it very hard for me to keep believing in Android as much as I want to. Any thoughts or help on this is greatly appreciated.
jdekoven said:
I've seen all the problems about Lollipop and Wifi not connecting. However, my problem is different. I connect just fine AND I'm getting 31 ms ping, 60mbps down and 12mbps up. However, my internet browsing is slow, Facebook is slow, you tube is slow. Pretty much anything I need is slow except that my e-mail comes in, although if I need to synch anything, but my inbox (because that's pushed) it's slow as well. Even the speed test takes a while to load up, but when it does these are the results I get. The only solutions I find are about problems not connecting to the internet. Even that being the case I tried those remedies with no luck. Also my wife who just got a Moto X has the same problems. Hmmm both phones are made by Motorola I'm wondering is this is a coincidence. I should say I wasn't having these problems a few weeks ago they just kind of started and my wife had a Moto G that didn't have these problems. This combined with bluetooth issues is making it very hard for me to keep believing in Android as much as I want to. Any thoughts or help on this is greatly appreciated.
Click to expand...
Click to collapse
maybe the issue is your wifi or router, not the phones. have you tried using a different wifi?
simms22 said:
maybe the issue is your wifi or router, not the phones. have you tried using a different wifi?
Click to expand...
Click to collapse
All other devices such as my laptop, roku box and other smartphones don't have these same issues on my wifi. As far as using other wifi' with my smartphone it varies - some are good and some are not. Which makes me think it's having trouble with certain routers or their settings.
jdekoven said:
All other devices such as my laptop, roku box and other smartphones don't have these same issues on my wifi. As far as using other wifi' with my smartphone it varies - some are good and some are not. Which makes me think it's having trouble with certain routers or their settings.
Click to expand...
Click to collapse
thats what im thinking as well. try messing with settings from both device and router.
simms22 said:
thats what im thinking as well. try messing with settings from both device and router.
Click to expand...
Click to collapse
I've already tried all the suggestions. However, I can't adjust other routers that I don't have control over. So it's frustrating that it doesn't work better on more routers.
btw, what kind/brand of router are you using? maybe someone is using the same or similar that can give some advice.
I am seeing the exact same thing on a used Nexus 6 that I just picked up. It seems to only happen (so far) on my work's WiFi, although even that just started within the past couple of days. It works fine on the WiFi at home.
Since I purchased the N6 to use with Project Fi which relies heavily on WiFi, this is putting a serious damper on things.
I'm looking for any suggestions or even just confirmation that me and jdekoven aren't the only ones.
I have the same problem with my Nexus 6, Nexus 4 and Nexus 10, all on either 5.1 or 5.1.1. It happens on my home Comcast X1 router/cable modem. It is not a problem with my Chromebook or Windows 7 PC.
It is not a problem at my office which has an Asus router and Cox cable modem.
This problem appeared recently, definately since 5.0, but maybe more recently (especially the Nexus 6, which I have only noticed the problem for a week or 2), and is only a problem for me on my home Comcast network.
I've had this same issue for a few days now. Just plugged my Asus router into the Xfinity box and once setup, WiFi is perfect using the other router. I'm assuming its due to background updates in the Xfinity box not playing nice with the phone. Dunno. But swap routers if you can.
jdekoven said:
I've already tried all the suggestions. However, I can't adjust other routers that I don't have control over. So it's frustrating that it doesn't work better on more routers.
Click to expand...
Click to collapse
Maybe this will help >http://phandroid.com/2015/05/13/comcast-wireless-gateway-lollipop-bug/
Hey,
So I am having serious wifi issues since I installed my Google Home. I use a chromecast too, but I think it's safe to say that it's the Home device that f-ed up wifi network.
I did read all the articles back i January/February that I was not alone with the issue, and as far as I understand - Google rolled out a fix about a month ago.
However, I am still having issues. My wifi drops for no reason (on all devices at the same time, phones included) for a few seconds and then comes back up. I've tried rebooting the router, and updating firmware on the router but no help. Today I pulled the plug to the Google Home until this has been fully resolved.
I love my Home and would like to have it connected. Did the correction that Google rolled out solve it for everyone else here or does anyone still have issues - or is it just me?
How can I see what firmware/software I am running on the Home? I have obviously tried to ask it, but it responds "this is not supported yet".
Any ideas?
Vol
I had the same problem on my main router, so I tried connecting it to my secondary router, and it worked, but since that one was supposed to be for the other part of the house, I got a cheapest used router I could (doesn't even support n standard) and created a separate network with different SSID, now I use it only to connect google home devices, chromecasts and other smart home wifi devices, and it works (it still uses my main router's DHCP server, and network, it is just AP with a different SSID), oh and I use channel 6 on that router btw.
Volatyle said:
Hey,
So I am having serious wifi issues since I installed my Google Home. I use a chromecast too, but I think it's safe to say that it's the Home device that f-ed up wifi network.
I did read all the articles back i January/February that I was not alone with the issue, and as far as I understand - Google rolled out a fix about a month ago.
However, I am still having issues. My wifi drops for no reason (on all devices at the same time, phones included) for a few seconds and then comes back up. I've tried rebooting the router, and updating firmware on the router but no help. Today I pulled the plug to the Google Home until this has been fully resolved.
I love my Home and would like to have it connected. Did the correction that Google rolled out solve it for everyone else here or does anyone still have issues - or is it just me?
How can I see what firmware/software I am running on the Home? I have obviously tried to ask it, but it responds "this is not supported yet".
Any ideas?
Vol
Click to expand...
Click to collapse
Ok, i feel my networking knowledge can come handy here! Lol. Home,three chromcasts, firetv, firestick x2; Nghthawk x8000->asusrtac68u->lan2wanWNR1000(for old 2nd gen sony bluray dlna and one roomstreaming)+wirelessLinksysEA6350->asusrtac88u. Yes, intriguing network! 6bdrm 3300sqft house. Biggest ever afforded! So, needless to say i pay TWC for 100Mbps, capping at 230mbps on the rtac68u ethernet bridge to wired desktop! All running my own modified compiled tomatousb. Linksysea6350 is ddwrt, kongbuild and a PIA so thats w/e stock kong wanted. Well safe to say ive been at making all this work!! What i need from you is topology and setup, running broadcoms or others? I find broadcom way easier to mess with. Second, you running custom or boxed units? And third is the google products subnetted (more of a b***h if you ask me!) And connected 2.4 or 5? N or AC? And how are you allocating resources? IE using QOS or similar? If you can't answer those im need (if unboxed and freed) "logcats", iptables, etc.. more than safe to say, the home not the culprit in sense to it "drowning" out the wifi band, but could for drown resources, IE low grade hardware, hardware beginning stages of failure and one extra workhorse did it, RAM, eMMC, getting the gist? Im gonna say w/slight certainty you might be rebooting not wifi actually cutting out. You also could if custom firmware corrupted something that the home doesnt like. But wont know w/out the numbers to look at. All i got from you is, either a LAN2LAN or bridge as i read your main hib is the DHCP, and is the SSID you "created" a subnet? And your "30" dollar router also could not be up to task.
And sorry if the reply is anything not right, first post ever here! Years of only reading lol. And something wrong with my cheap phone cracked screen phone replacement everytime keyboard is opened! Doubt its this website. my pixel xl tried to drive on the interstate outside of my car...so sad.. just know im gonna punch this phone or throw from the anger ive gained trying to type and the sign-in to post.. thank you.
Similar solution worked for me
I use a dedicated connection for all things GH related. This stopped the wifi dropout.