Detect Magazine logo Detect MagazineFind what others miss
Tech Notes

HDMI Handshake Failures and How to Find the Cause

The console was on. The television said no signal. Ten seconds later the picture arrived, held for four seconds, went black again, and the sound carried on playing underneath the blank screen as if nothing were wrong.

A television showing a no signal message above a shelf of stacked devices with several HDMI cables unplugged and laid out in front

The console was on. The television said no signal. Ten seconds later the picture arrived, held for four seconds, went black again, and the sound carried on playing underneath the blank screen as if nothing were wrong. I spent a Saturday on that one in my own living room, and the cable I replaced twice was never the problem.

A handshake failure is the most misdiagnosed fault in home video, because it presents as a dead connection and is almost always a negotiation that went wrong. Two devices have to agree on resolution, refresh rate, colour depth, audio format and copy protection before a single frame appears. Any one of those can fail, and the only thing the television tells you is that there is nothing to show.

What the two devices are actually agreeing on

Plug a source into a display and three separate conversations happen in the first second or two.

The display sends its EDID, a small block of data describing which resolutions and refresh rates it accepts. The source reads it and picks a mode. Then, for protected content, the two run an HDCP authentication, currently HDCP 2.2 or 2.3 for 4K material, which involves exchanging keys and confirming that nothing in the chain is untrusted. Separately, a 5 volt line and a hot plug detect pin tell the source that something is physically there and awake.

The failure modes map onto those three conversations neatly. An EDID problem gives you the wrong resolution, or a mode the display cannot show. An HDCP failure gives you a black picture with working audio, which is the single most diagnostic symptom in the whole field. A hot plug or 5 volt problem gives you nothing at all until you unplug and replug.

Audio continuing under a black screen means the devices are talking. That narrows it to copy protection or bandwidth, and it rules out the cable being severed, which is where most people start.

Read the symptom before you touch anything

I now write the symptom down before I move a single lead, because the symptom is most of the diagnosis and it changes the moment you start swapping parts.

What you seeMost likely causeFirst test
Black picture, audio playing normallyHDCP authentication failing somewhere in the chainRemove the soundbar or receiver and go source to display directly
No signal at all, fixed by repluggingHot plug detect or power on orderPower the display first, wait ten seconds, then the source
Picture flickers to black every few secondsBandwidth marginal for the selected modeDrop from 4K120 to 4K60, or turn off deep colour
Wrong resolution, will not offer 4KStale EDID cached by the source or a switchUnplug the display at the mains for 60 seconds
Works on one input, fails on anotherThat input not configured for full bandwidthEnable the enhanced or deep colour setting on that input
Fails only after the display sleepsRenegotiation on wake, often a firmware issueDisable the display's power saving, then check for updates

The fourth row deserves a note. Sources and switches cache EDID, sometimes for weeks. If you ever had the box connected to a 1080p display, or through a splitter, the source may still believe that is what it is talking to. A full mains disconnection of the display for a minute, with the source off, clears most of these. It is the fix that sounds like superstition and works more often than any cable swap.

The device in the middle is usually the liar

Every extra box in the chain has to pass the handshake through, and each one is a place where the negotiation can quietly degrade.

A soundbar or receiver from 2017 may support HDCP 2.2 on some inputs and not others, and the labelling on the back panel is often wrong. A cheap switch may claim 4K and mean 4K at 30Hz with 8 bit colour. A splitter may present an EDID that is a crude average of the two displays attached to it, which can leave a perfectly capable television offering 1080p.

So the test that settles arguments is to strip the chain. Source, cable, display. Nothing else. If it works, add one box back at a time and retest. I have never had this method fail to identify the culprit, and in four of the last five cases the culprit was a receiver or soundbar rather than a cable or a console.

While you have the chain apart, it is worth checking whether the box in the middle was also adding delay, since the same devices are the usual suspects there. The method for that is in TV input lag in games and how to find the cause.

The counter take on buying a better cable

The first reply in every forum thread about this is to buy a better HDMI cable. It is the advice I followed twice on that Saturday, and for handshake failures specifically it is usually wrong.

HDMI is a digital link. A cable that is inadequate for the mode fails loudly, with sparkle, dropouts or a picture that never appears, not with a negotiation that completes and then collapses four seconds later. And the bandwidth thresholds are specific rather than vague. 4K at 60Hz with 8 bit colour needs under 18Gbps and runs over almost any High Speed cable. 4K at 120Hz with 10 bit colour wants the full 48Gbps of HDMI 2.1, which is where cable quality genuinely starts to matter, particularly past about three metres.

So there is a real case for a certified Ultra High Speed cable, and it is narrow: you are running 4K120 or higher, or your run is longer than three metres, or you are using a passive cable near the five metre mark where passive copper starts to struggle. Outside those conditions, a new cable is a twelve pound placebo and it costs you the diagnostic step you should have taken instead.

I would put it this way. If the audio works and the picture is black, the cable is carrying data perfectly well. Something in the chain is refusing to authorise the picture, and no amount of copper will change its mind.

Where the fault often turns out to live

Three causes account for most of what I see. Power on order, where a source that boots before the display never gets a valid EDID and settles on a safe mode or nothing. Firmware, because televisions and receivers both ship HDMI fixes in updates and people rarely install them. And input configuration, where a television has a setting per port, named something like enhanced format or input signal plus, that must be switched on before that port will accept anything above 4K60.

That last one caught me on a set where only port two had the setting available at all, and nothing in the menu said so. Fifteen minutes of reading the manual would have saved the afternoon. It is the same kind of undocumented behaviour that makes old hardware fail on new displays for reasons nobody wrote down, which is the story in why light gun games stopped working on modern TVs. More of these teardowns sit in the tech notes section.

FAQ

Why does my screen go black but the sound keeps playing?

That is the signature of an HDCP authentication failure. The data link is fine, which is why audio survives, but something in the chain will not authorise protected video. Take the receiver or soundbar out of the path and test source straight to display.

Does a more expensive HDMI cable fix a handshake problem?

Rarely. Cables matter when you are pushing 4K120 or running longer than about three metres. A handshake that completes and then drops is a negotiation fault, not a signal integrity fault, and a new cable will not change the negotiation.

What does unplugging the TV from the mains actually do?

It clears stored state, including EDID the source may have cached and any stuck authentication. Sixty seconds with the source powered off is enough. It is the cheapest first step and it resolves a surprising share of no signal faults.

Why does the problem only appear after the TV sleeps?

Waking triggers a fresh handshake, and some firmware handles that badly. Turn off the display's own power saving, check for a firmware update for both the display and any receiver, and if it persists, set the source to output 4K60 rather than the highest mode available.

RQ
Rosamund Quist

Rosamund spent years writing about game culture for print magazines before moving online. She edits Detect Magazine's features and has a soft spot for games that hide their best ideas in plain sight.

More posts by Rosamund

More in Tech Notes

01doorganico 084goad 3hot8 4465456 after5internprogram ahandfulofblessings ahmadpc ahomcybersecurity allodialresources annodex antiquesandperiodcollectibles aotc asianworldkashmir beedlectrics bloggertemplatefree bluefeatheragency bodyweightsolution campaign08blog carfixadvisor catstreetcollective cbstvsports cnfanspurchasing committeeof500yearsofdignityandresistance covertopsdjs cs-kaiyuangame cuestacomunicaciontotal cxoutlet dancebetgame deskgearhub destinyvillastay di33 diamondsteelbuildings donmo dyanadropship emarsysfinance emimattl escapechan eskitarih evautoplay everythingweddings-orlando farmzone feedviewerapp foxstudiosscratch gamevui123 gleasongrade greetingsday hacklabasu haskell iw-kaiyun jagoanproperti jilidskripsi joltbusinessfinance juegodepokergratis juegospucca kaeru-festival latestmehndidesigns lestanzediottaviano litemagazines localcommunityhero lustrsazan mariashebets menswheels newwebstechs1 nikkit ootheday oxigenvpn plurfitness prefetial probudgetcarpetcleaning psychicmrsmartin pyaten qvantor rejoignezlogis rexzbot riselayouts ruchin rwxqsgd5 sakaltime shibiaowang shop-bot skrtips spotlesshaven strcoding tetapatrium topselller uneplanteartificielle vipertechcr webtech1223411 wo-kygaming yamaha-mekar yeknava yoybuysheets zenunwa yamaha-mekar jilidskripsi ankertoto ankertoto ankertoto