[jader201]

I was actually pleasantly surprised to see the "just don't connect it to the internet" comments, as most of these smart TV threads are usually full of comments complaining about them on principle, even though most of the world doesn't care (connected to the internet or not), and in this case, I think it does solve most of the issues.

It's more common for HN to argue against something on principle, even when there's a relatively simple solution/workaround.

Not saying there's something inherently wrong with arguing against something on principle, but just saying that it seems more common on HN, and saying that the inverse is "such a typical HN response" is not my experience at all.

> It should turn on in seconds, not minutes.

I'm assuming this is hyperbole, but if not, I think there are other issues if it's taking minutes for even the smartest, most connected and loaded TV to turn on. Every smart TV I've owned has barely taken seconds to turn on, and I usually don't go out of my way to keep it disconnected from WiFi (unless, for example, I'm trying to avoid an update).

[derefr]

I have a smart TV (in fact, the very one recommended in the article), connected to a Sony sound bar, and an Apple TV. I wake the whole assemblage from sleep by prodding the Apple TV remote — and then it takes fully 60 seconds before I can use it, because it seemingly

1. Wakes the TV up in SDR, syncs with the Apple TV;

2. Starts playing audio;

3. Which wakes the soundbar up;

4. Which forces a re-sync as the TV switches to eARC mode;

5. And then the TV notices that the Apple TV is offering to negotiate Dolby Vision, so it does so, and re-syncs again;

6. Which kicks it out of eARC mode, so it needs to re-sync another time to get back into it…

And that’s all just if I left it on the Apple TV’s input when putting it to sleep. If I sleep the TV by sleeping a game console when it’s the only thing awake, and then wake it up later with the Apple TV remote, then there at least two more resyncs involved, and also seemingly ten seconds of complete blackness where it’s doing literally nothing.

Also, this one’s not the TV’s fault, but YouTube for tVOS gets so confused by these repeated mode-switch re-syncs, that if it’s what would be playing on resume from sleep, then instead the audio will play from the YouTube video, with the first frame of the video frozen on the display and the event loop stalled for another ~60s (I.e. my prompting to go into the task manager to kill the app is ignored, and then 60s later it suddenly happens, but at that point the video resumes so I don’t need to do it any more.) Doesn’t happen with any other app waking from sleep.

Oh, and sometimes the TV will just wake to its home menu despite being woken up by the Apple TV remote, and while the system apps will be responsive (once I grab the TV’s remote), it will refuse to open the input switcher, or the device preferences (in order to gracefully reboot it.) when it does this, I have to get up and unplug the damned thing to get it working again.

[kalleboo]

None of those things have anything to do with the TV being "smart" though, it's all up to the crappiness of modern HDMI.

Removing app support from the TV would not fix it. Actually, it sounds like using the smart features of your TV to watch video instead of an Apple TV would actually reduce the bugginess?

I have a 10 year old non-smart TV. It predates HDR, but just basic ARC and CEC still regularly trips it up. To the point my 5 year old knows how to re-select the sound bar output to fix when the audio breaks.

[derefr]

Ah, but most of the slowdown from this messiness is due to all these mode changes being handled at the application layer in sandboxed userland daemons on a non-real-time OS. Before smart TVs with application processors “fast enough” to (barely, slowly) do these things, the “control-plane logic” for a TV’s DSPs was handled effectively instantly by purpose-designed ASICs.

[kelnos]

I suspect if you fully unplugged many smart TVs on the market, and then plugged them back in and turned them on, they'd take a minute or two (or more) to fully turn back on.

When you turn off a smart TV, it doesn't actually turn off. It's similar to a laptop when you close the lid and it goes into standby. Consumers wouldn't tolerate a several-minute power-up sequence every time they want to watch TV -- and rightly so -- so instead, they sit there, wasting power and money in a standby state.

[chillfox]

I should turn on in seconds (and be ready to use) from having the power switched off at the wall. Dumb TVs can do this.

[Gigachad]

Most of the world does care, they want their TV connected to the internet. They want to install apps and stream content. They don’t want to have to run a plex server and set up a raspberry pi hanging out the back of their TV.