BananaBender

I gave up. I exchanged it for a Sony. Fortunately I bought the LG from John Lewis in the UK and they allowed me to exchange it after 2 months.

You say cabled, so I'm assuming that you've connected the TV to your network via ethernet rather than WiFi? If you're using ethernet, I suggest you try WiFi. My TV is much more responsive since only connecting via WiFi. I've been asking myself how this can be. And the only answer I've come up with is that WebOS wouldn't originally have had an ethernet driver as it was intended to run on mobile devices. So I'm guessing that LG added an ethernet driver and they've botched it. Either way, I'm sending my TV back and buying an alternative brand. It's still pretty terrible (but less so since I'm on Wifi).

I talked to an operative at LG today on the telephone. They gave me a number of diagnostics to try. Initially it was suggested that it was the remote control rather than the television. I.e. check the batteries. They're okay. The useful test seems to be using the little joystick underneath the screen. So when the tv has become sluggish, try adjusting the volume by moving the joystick left and right. If it fails to respond then it's not the remote (which I know I'm certain it isn't). I shall do that test this evening and report back, although I suspect the result will be the same as if I was using the remote.

I have a 42LB650V purchased in the last 6 weeks. After about an hour of use the television becomes completely unresponsive. A change in volume takes about 10 seconds to register. Changing channel takes 5-10 seconds to respond. Switching between inputs can take up to 30 seconds. The settings page can take up to 30 seconds to respond too. It becomes almost impossible to page through the guide. Is this normal, are other folks experiencing this? I'm sure this shouldn't be happening. I got a firmware update at the end of October and that has not made much difference. From a software perspective, it feels like a memory leak and the resulting poor performance is the OS itself trying to survive the resulting memory pressure. Any guidance is most welcome.