Bravia 49XE8004 won't detect pc hdmi connection

[davetherave98]

I have a Sony Bravia 49XE8004 Android TV and when I try to connect to my pc in any hdmi port I receive no signal. It isn't until I have to force shutdown my computer (which will eventually kill the Hardrive) that when I turn it back on the signal is detected. Sometimes this takes two or three attempts.

The pc is using GPU AMD Radeon HD 7800 Series on Windows 10. The resolution is 1920x1080 60HZ and the pc is detecting a SonyTV. I originally believed it to be related to ARC as when I turned the AV Receiver off it appeared to work almost every time for a few days however the issue is now presenting itself again.

I've tried the sony help guide on the problem which didn't work and have changed cables to a high speed hdmi but still not detecting the signal straight away. I have also unplugged all cables and removed TV plug and held power button for 30 secs to try reset the hdmi connections but still this hasn't worked.

Can anyone advise why this keeps happening as force shutdown on pc will eventually cause other issues. My very old samsung smart TV can pick the signal up straight away so this is very disappointing.

[royabrown2]

@davetherave98 

HDMI ports are not guaranteed to be hot-pluggable (though they usually are, and no damage will occur even if you do this), but it can disrupt the HDMI handshake, and it looks like this is affecting your connection here.Instead of restarting the computer though, try power cycling the Sony TV.

You are, of course, quite wrong that power-cycling your computer will eventually kill your hard drive, at least in your lifetime; in fact leaving it on all the time may shorten it more drastically.

But in these circumstances, it doesn’t  matter which device you restart, as long as you restart one of them, and thus initiate the HDMI handshake afresh.

[Joe_Dohn]

I agree with @royabrown2, except for the force shutdown part, a shutdown is safe, no matter how many times you do it, but a force shutdown is a terrible idea, especially with hard drives since it can result in the read header stopping abruptly, which can result in a tiny hole in the platter which then results in bad sectors among other very fun things. 😂 Though, knowing you, you probably know all of this already and just missed the "force" part in the OP. 😛

@davetherave98

All that said, I think there's a slightly easier way of either preventing this or avoiding a restart even for the TV.

If you don't already have the PC connected to a port that has Enhanced signal format enabled, you should. And I believe that switching back and forth between Enhanced and Standard would force-reset that specific port and thus re-doing the handshake.

Hope this helps!

- JD

[royabrown2]

@Joe_Dohn @davetherave98 

ACPI came in over 20 years ago, with Windows 98, and every PC and laptop made since then, pretty much, has supported it. So when you shut the machine down by pressing the power button, it has a think, and shuts down the hardware in an orderly fashion, including giving any hard disc the chance to retract its heads. It can’t shut down the software in an orderly fashion, true, so you may still get software corruption, but you won’t get physical damage.

But quite separately from this, even in the case of a sudden power cut to a running PC, any modern disc drive has enough stored energy to carry out an orderly head retraction - has to have, if you think about it, both for third-world countries and modern-day Britain.

But are we even really talking about this sort of in extremis forced shutdown here, or just an ordinary user-initiated power down? 

@davetherave98  are you really saying that the only way to reset the HDMI port on your PC so that it will reinitiate making the handshake, is a forced shutdown? An ordinary controlled shutdown won’t do it?

[Joe_Dohn]

@royabrown2

You're absolutely right, I forgot about that, but I did have a physical damage issue with a laptop's internal drive, which has now become a mystery to me. 😅😂

@davetherave98

Are you still facing the same issue or is it resolved now?

- JD