Leaderboard

My router is literally next to the TV next to the inlet on the wall, constant 50mps , the wireless button is faded so cannot use but I literally cannot get nearer the router and I still have this problem!

@PhylipR That is an innovative and interesting fix, although a bit expensive at around AUD$150 + usb Ethernet adaptor. I guess it seems to prove that the Ethernet chip Driver, and the API (software layers) on top of that have big issues, or at least "timer" issues. By that, I mean inside a lot of software, there are "timers" for "waiting" for an event. With IP (TCP/IP, Internet protocol), The Internet is a very large and variable "data space" where data packets can come and go unreliably, mainly because of bottlenecks, and routing issues, as well as web-server performance variabilities. Many of the "timer values" recommended for the TCP/IP protocol were documented years ago, when the hardware (servers, routers, DNS servers etc) were very much slower and less powerful than todays systems. Plus of course the VAST increase in both user number and device numbers that are now "connected" over time, has tended to dlute that technology shift, where gains are now negated by sheer vast numbers and far higher complexity. Even my new Fridge has an IP adress!! All that raises the chance that those "old spec" timer values (see the RFC docs - started in around 1974 for TCP-/P), being totally unrealistic in todays high-speed internet requirements. What makes the problem even worse, is that many Software Developers rely on "Libraries" of standard "routines" (Object code libraries) to perform specific tasks within a large API/Driver/Interface, or collectivley an "APP". I suspect that MANY devices (including Smart TV's) are still running on outdated "library" code inside the Drivers and API's and "APPS". Now those libraries might not have been updated to the latest software, but the "company servers" still provide them, and they work, and they "link" to make a viable and workable "APP" or driver. However, it may contain an untold amout of "bugs", or even "vulerabilities", until said developer company updates their "software libraries". As many are finding on this forum "There is no such thing as perfect software"!! Going back to the thread points - someone quoted an LG engineer saying that "The WiFi card module has a design fault, and is kicking in when it should not". That may well be part of the issue, BUT, with a properly written Software Driver, both on THAT AND the Ethernet interface side, they should NOT be getting in the way of each other, when ONE SIDE is still active. All operating systems that I have worked with, have had the ability to "ignore" or "defer" interrupts from unwanted sources or data lines. That SHOULD include WebOS!!