ATV 4K Problem Powering TV On/Off

[krawfo]

Here's the scenario with my ATV 4K w/Siri remote and Samsung TV:
- TV has been off overnight. Using Siri remote I power everything on. ATV powers on but TV doesn't. I finally have to power the TV on with the Samsung remote.
- After watching TV for a while I power off the Samsung and ATV with the Siri remote. Everything shuts down. If I use the Siri remote right away, it will power both units back on with no problem. If everything sits overnight, only the ATV will power up with the Siri remote.
The Samsung has CeC and the Siri remote controls the TV volume with no problem.
Any idea why the Siri remote fails to power the TV on after it's been sitting off for a while but works fine powering on and off once I use the TV remote to power the TV on after sitting off for a while?
Thanks for your input.

 

[Juicy Box]

I've been having similar issues, but with a sound bar. The Apple TV turns on the sound bar turns on the TV turns on, but it doesn't go to the correct HDMI when everything power is on.


This only started happening recently.

It's not really a fix, more of a work around, but it works 100% of the time. I press the TV button, otherwise known as the home button, three times in a row. And then it switches the HDMI.

It is probably a long shot, but you can try that and see if it works.

 

[-Gonzo-]

The Siri Remote itself doesn’t actually power on your tv, it’s the HDMI CEC link that activates the TV when the Apple TV is powered on.

 

[w5jck]

@krawfo, Exactly how is your ATV connected to the TV and the soundbar.

Is the TV the main control device with audio out to the soundbar and an HDMI CEC connection between the ATV and the TV? This is more or less the ideal way to have things set up.

 

[krawfo]

My Samsung TV has a stand alone device with 3 HDMI ports, a port labeled MASTER CONNECT and an ARC port (NOT a CeC port as I wrongly assumed). My Sonos Beam soundbar plugs into the ARC port and the ATV into the HDMI 1 port.
Could the CEC port be my problem?

 

[HobeSoundDarryl]

A simple first test could be to try switching ATV in to the unused port. ARC to soundbar should be right.

Have you checked the menus of the TV to be sure you are using CEC (that is is ON). Is it still called Anynet on Samsung? If so, look for that.

Another simple test since it seems to be working when you turn it off: cable? Have you tried swapping HDMI cable in for the ATV to Samsung cable? Maybe you've got a borderline HDMI that is barely working with CEC commands only some of the time?

 

[MegaBlue]

My Samsung TV has a stand alone device with 3 HDMI ports, a port labeled MASTER CONNECT and an ARC port (NOT a CeC port as I wrongly assumed). My Sonos Beam soundbar plugs into the ARC port and the ATV into the HDMI 1 port.
Could the CEC port be my problem?

I believe the "MASTER CONNECT" port is for when you use one of Samsung's One Connect boxes.

I wish I could offer you advice, but unfortunately I've gone through the same struggle you currently are with every Samsung TV I've owned, newer or older. It seems as though Samsung just can't properly implement HDMI-CEC correctly, as I've had CEC issues with the Apple TV and the Xbox Series on Samsung TVs, but they work exactly as expected on LG, Roku, and Sony TVs. 🤷‍♂️

 

[HobeSoundDarryl]

I have a Samsung with a One Connect box and have no trouble with CEC working just fine. The change for me is in setup:

AppleTV to Receiver, Receiver to Master Connect Box.​

However, I have experimented with a direct connect bypassing the receiver and that works just fine too.

I suspect OP is going to find that maybe "Anynet" is not "on" and/or a swap in port or HDMI cable will resolve this problem. It's almost working now (it can turn everything off). My best gut guess is new HDMI cable.

 

[waw74]

Try unplugging and replugging the HDMI cable, And if that doesn't work a good old fashioned hard reboot (unplug/replug) of both the aTV and TV might.

Both of these should cause the HDMI handshake to happen again, and might sort out anything that got squirrelly

The Siri Remote itself doesn’t actually power on your tv, it’s the HDMI CEC link that activates the TV when the Apple TV is powered on.

no 💩 Sherlock,
They even said the remote powered on the aTV, but the TV didn't come on.
Day 2, and you're already going for least helpful comment of the year award.

 

[neutrino17]

This worked fine with our 10 year old Sony TV. We just recently got an LG OLED. It is great, but we have similar issues turning it on. I long press on the Apple Remote (ATV 4K) power button. Both devices come on. After a few seconds the TV turns off. I have to use the TV remote to power it back on. Sometimes I just use the LG remote to turn on the TV. If ATV was the last device used then the TV will turn on ATV. Usually I have to turn on the LG TV at least twice to get it to stay on, even when viewing over-the-air content.

On my hierarchy of problems this is quite low so I haven’t invested any time to troubleshoot this.

 

[-Gonzo-]

no 💩 Sherlock,
They even said the remote powered on the aTV, but the TV didn't come on.
Day 2, and you're already going for least helpful comment of the year award.

Wow, and a Happy New Year to you too 🫣

My comment was more in response to the last paragraph of the OP.

Any idea why the Siri remote fails to power the TV on after it's been sitting off for a while but works fine powering on and off once I use the TV remote to power the TV on after sitting off for a while?

But fine as long as you’re happy passing out the insults then I’m good 😊🥳

 

[krawfo]

First, thanks everyone for your suggestions. Much appreciated.
I swapped out a new HDMI cable and plugged the new one into a different HDMI port - No Joy.
Anynet is on. It's labeled Anynet + if that matters.
I unplugged the power cords to the soundbar, Samsung and ATV. Plugged everything back in but No Joy.
Something else weird I've now noticed. It takes 2 key presses to power the TV on via the Samsung remote. Even weirder, following the second key press, both the TV and the ATV turn via the Samsung remote. I'm stumped.

 

[cotxia]

I just stumbled across this thread after searching for answers to the exact same issue. I have tried everything listed in this thread on my Samsung that had been working fine for years until the past few weeks. I can't say exactly when the issue started for me but it would have been around the time of the 16.2 update. I am starting to wonder if it's a software issue at this point? Hopefully 16.2.1 comes out soon and resolves this for us if that is the case.