Table of Contents
- The Verdict: Clear Connection History First, Kill Simplink Only If It Comes Back
- What a Failed Handshake Looks Like on an LG OLED Right Now
- Which Sets and Sources Are Affected: C2, G2, C3, C4, G4, C5 and G6
- Fix A: Delete Connection History and Force a Fresh EDID Negotiation
- Fix B: Turning Off Simplink, QMS and Quick Start+
- Head to Head on Speed: How Long Each Fix Takes and How Often You Repeat It
- Head to Head on Reliability: Signal Loss, HDR Switching and eARC Dropouts
- Head to Head on What You Give Up: One-Remote Control, Instant Wake and Seamless Mode Switching
- The PS5 Pro Case: Stopping the 1080p Drop at 40Hz and With VRR Enabled
- PC and AV Receiver Cases: RTX Cards, Denon and Marantz Pass-Through
- RTX Graphics Cards at 4K 120Hz
- Denon and Marantz Pass-Through and eARC
- When Neither Fix Works: Cable Certification, Port Choice and Full Factory Reset
- Who Should Pick Which Fix, and When to Just Wait for LG's Patch
- Limitations of This Guidance and What We Could Not Verify
- Conclusion
- Frequently Asked Questions
- References
Key Takeaway
Clear Delete Connection History first and turn Simplink off only if the fault returns. Deleting connection history wipes the cached EDID that WebOS 26 disturbed, which means the lg oled hdmi handshake renegotiates from scratch and you keep every feature. Turning Simplink off kills HDMI-CEC, so you lose one-remote volume and synced power-on. Budget two minutes for Fix A and about ten minutes of re-labelling inputs afterwards.
An LG OLED that ran a console and a soundbar without complaint for two years drops to “No Signal” on HDMI 2 after the WebOS 26 update. The cable did not change. The source did not change. Owners have been posting this pattern across r/LGOLED through October and November 2026, and the fix is a software one, because a failed lg oled hdmi handshake after a firmware push is a cache problem rather than a hardware problem.
Two settings dominate the discussion. Delete Connection History sits under General and External Devices, and it clears the cached EDID data for every HDMI port at once. Simplink is LG’s name for HDMI-CEC, the command channel that lets your TV and your soundbar control each other, and switching it off severs that channel entirely.
The verdict is Fix A first, because it costs you nothing but input labels, then Fix B, because it costs you features every day you keep it off. Below: the head-to-head comparison, the console and PC cases, and the escalation ladder for when neither works.
About the author
Written by The Tech ABC hardware desk. We test TVs, consoles and AV chains hands-on and report what the settings actually do, not what the marketing says.
Transparency
The symptom patterns and fix outcomes in this article are drawn from owner reports on r/LGOLED, the LGWebOS community forum and AVForums between late 2025 and November 2026, plus LG’s published settings documentation and HDMI Licensing Administrator cable specifications. LG has not published a bug acknowledgement for the WebOS 26 HDMI behaviour as of 21 November 2026.
The Verdict: Clear Connection History First, Kill Simplink Only If It Comes Back
Delete Connection History for video faults. Turn Simplink off for control and audio faults. That split is not arbitrary: black screens, HDR drop-outs and resolution locks are EDID and HDCP problems, therefore clearing the TV’s cached EDID resolves them. Input hijacking, self-powering sets and eARC silence are CEC problems, therefore cutting CEC resolves them.
The cost side decides the order. Fix A takes two minutes and bills you about ten minutes of re-labelling inputs once. Fix B takes thirty seconds and bills you Magic Remote volume control for as long as it stays off. One-time cost beats recurring cost, which is why you run Fix A first even if you suspect CEC.
Check the model table further down if you want to confirm your panel is in the reported population before you change anything.
| Fix | Time to apply | What it costs you | Best for |
|---|---|---|---|
| Delete Connection History | About 2 minutes | Input names, icons, Home Dashboard tiles, per-port Deep Colour | No Signal, HDR drops, resolution locks, PC and console faults |
| Simplink off | About 30 seconds | HDMI-CEC: one-remote volume, synced power, auto input switching | eARC dropouts, input hijacking, TV powering on by itself |
| Both applied together | About 3 minutes | All of the above | Stubborn receiver chains where the fault survives Fix A |
What a Failed Handshake Looks Like on an LG OLED Right Now
A failed handshake shows up in four recognisable ways. The handshake loop is the loudest: HDCP re-authentication never completes, so the panel cycles black every few seconds and sometimes drops into power-saving. HDR drop-out is quieter, where the HDR badge flashes up then vanishes and the set holds SDR with an HDR source attached. eARC silence cuts the audio to a soundbar or receiver after a few minutes. Resolution lock pins a 4K 120Hz source to 1080p or 60Hz and greys out the higher modes in the source’s own menu.
The dates matter here. The r/LGOLED thread Issues with HDMI input/output since WebOS 26 update and a second community thread on WebOS 26 HDMI issues both run through autumn 2026, and owners in both report the same cable and the same source working flawlessly before the update. That consistency is the diagnostic: a cable that was fine on Monday and failing on Tuesday with no physical change points to firmware, which means a lg oled hdmi handshake fault of this kind usually responds to a settings change rather than a parts order.
- Screen flickers black every few seconds on one input while other inputs hold steady
- “No Signal” on an input that worked before the firmware update, with the source powered on
- HDR badge appears then disappears, or the set stays in SDR with an HDR source attached
- eARC audio to a soundbar or receiver drops out after a few minutes, then returns
- A 4K 120Hz source locks to 1080p or 60Hz and the higher mode is greyed out in the source’s menu
- The TV switches input or powers on by itself when another device wakes
Which Sets and Sources Are Affected: C2, G2, C3, C4, G4, C5 and G6
Reports span 2022 through 2025 panels, because WebOS 26 shipped across several firmware lines at once rather than to a single model year. A 2022 C2 produced the same post-update “No Signal” behaviour documented in the r/LGOLED thread LG C2 OLED no signal on HDMI after update, which rules out the theory that this is purely a new-panel problem.
The 2025 sets drew the loudest complaints. Community feedback from October and November 2026 put the 2025 G5 and B5 OLEDs at the centre of it, driven by the update landing alongside UI unresponsiveness on those models, so owners were fighting a slow interface and a dead input in the same session.
Handshake behaviour is panel-brand specific, because each manufacturer implements EDID caching and CEC arbitration differently. Readers weighing an LG against other high-end options can compare the 2026 RGB MiniLED TVs and laser projectors from Hisense, which run an entirely different platform and therefore a different set of quirks.
| Model | Reported symptom | Source device | Fix that worked |
|---|---|---|---|
| C2 | “No Signal” on HDMI after update | Not stated | Delete Connection History |
| G2 | HDMI inputs broken after software update | Not stated | Delete Connection History |
| C3 | Signal loss after WebOS update | Not stated | Delete Connection History |
| C4 / G4 | Handshake failure, 1080p fallback; CEC faults after update | PS5, PS5 Pro | Delete Connection History; Simplink off for CEC cases |
| C5 / B5 / G5 | HDMI signal loss plus UI unresponsiveness after WebOS 26 | Consoles, soundbars | Delete Connection History |
| G6 | Not stated | Not stated | Not stated |
Fix A: Delete Connection History and Force a Fresh EDID Negotiation
The TV caches each source’s EDID on a per-port basis so it does not have to renegotiate from zero every time you switch inputs. That caching is a speed feature in normal use. The problem arrives when a firmware update rewrites the EDID handling, because the stale cached entry no longer matches what the new code expects, resulting in a negotiation that fails at the handshake stage rather than at the bandwidth stage. That distinction explains why a lg oled hdmi handshake fault survives cable swaps: the cable was never the variable. Deleting the history forces a fresh EDID read on the next connect.
- Press the Settings (gear) button on the Magic Remote and open All Settings
- Go to General > Devices > External Devices
- Select Delete Connection History and confirm
- Power the TV off at the remote, then unplug the source device’s HDMI cable
- Reconnect the cable and power the source on first, then the TV
- Re-enable HDMI Deep Colour for that port under General > External Devices > HDMI Settings
- Rename the input and re-add it to the Home Dashboard
The literal path to quote is Settings > General > External Devices > Delete Connection History, and LG’s own support documentation carries the current menu wording for your firmware version.
The cost is real but bounded. Custom input names, device icons and Home Dashboard tiles all reset, and per-port HDMI Deep Colour needs re-enabling, which is the step people forget and then blame for a second round of HDR faults. On a four-device setup that clean-up runs roughly ten minutes. Picture presets, network settings and installed apps are untouched.
Fix B: Turning Off Simplink, QMS and Quick Start+
Simplink is LG’s HDMI-CEC implementation, the protocol that carries power, volume and input-switch commands between devices over the same cable as the video. Three toggles matter rather than one, because they fail in different ways. Simplink carries the commands themselves. QMS changes refresh rate without a full re-handshake and misfires on some sources. Quick Start+ keeps the panel in a low-power standby state, which means a waking source can be handed a half-initialised EDID.
The r/LGOLED thread on CEC handshake issues with a G4 after a firmware update is useful evidence that CEC-layer faults behave differently from EDID-layer faults and respond to Simplink changes specifically.
- Open All Settings > General > External Devices and set SIMPLINK (HDMI-CEC) to Off
- Test the faulty input for ten minutes before changing anything else
- If the fault persists, go to General > System > Additional Settings and set Quick Start+ to Off, then power-cycle the TV
- Test again, then set QMS (Quick Media Switching) to Off under General > External Devices > HDMI Settings for the affected port
- If VRR flicker is the symptom, disable VRR on the source rather than the TV and re-test
- Turn each toggle back on one at a time to identify the culprit and keep the features you can
Test in that order. Flipping all three off at once will sometimes clear the fault, but it tells you nothing about which setting caused it, therefore you end up living without three features to solve one problem.
Head to Head on Speed: How Long Each Fix Takes and How Often You Repeat It
| Fix | Time to apply | Re-setup time afterwards | How often you repeat it |
|---|---|---|---|
| Delete Connection History | About 2 minutes | About 10 minutes on four devices | Owners report repeating after major firmware pushes |
| Simplink off | About 30 seconds | None | One-time until you re-enable CEC |
| Quick Start+ off | About 30 seconds | None | One-time |
| Hard power cycle (fallback) | About 15 minutes including the 10-minute wait | Re-plugging every HDMI cable | Only when software fixes fail |
Fix A applies faster but carries the recurrence, because owners in the WebOS 26 threads report running it again after each significant firmware push. The real cost of Fix A is therefore repetition, not the initial two minutes. Fix B is a single change that holds until you choose to turn CEC back on, which makes it the cheaper option on time and the more expensive option on function.
Head to Head on Reliability: Signal Loss, HDR Switching and eARC Dropouts
The two fixes are not interchangeable, because they act on different layers of the connection. EDID and HDCP faults produce video symptoms and respond to Fix A. CEC faults produce control and audio symptoms and respond to Fix B. Choosing the wrong layer wastes an evening, which is why a lg oled hdmi handshake diagnosis should start with the symptom rather than with the setting. Independent corroboration for the firmware-side origin comes from the LGWebOS community thread Latest software update broke HDMI on my LG OLED G2, where owners traced the failure to the update rather than to hardware.
| Symptom | Fix that resolves it | Underlying cause |
|---|---|---|
| No Signal / handshake loop | Delete Connection History | Stale cached EDID, HDCP re-auth never completes |
| HDR badge dropping to SDR | Delete Connection History, then re-enable Deep Colour | Truncated EDID, port not in full-bandwidth mode |
| eARC audio dropout to soundbar or receiver | Fix A first, then Simplink off | Sits on both EDID and CEC layers |
| TV switching input or powering on by itself | Simplink off | Competing CEC controllers issuing commands |
| VRR flicker in dark scenes | Disable VRR on the source; QMS off | Refresh-rate switching without re-handshake |
eARC is the overlap case. It depends on EDID for the audio format list and on CEC for the control channel, which is why eARC dropouts sometimes clear with a connection-history wipe and sometimes need Simplink off. Test in that order and you keep your one-remote volume whenever the EDID layer was the culprit.
Head to Head on What You Give Up: One-Remote Control, Instant Wake and Seamless Mode Switching
| Feature | After Delete Connection History | After Simplink off | After Quick Start+ off |
|---|---|---|---|
| Magic Remote volume on soundbar or receiver | Kept | Lost | Kept |
| Synced power on/off with source | Kept | Lost | Kept |
| Auto input switching when a source wakes | Kept | Lost | Kept |
| Boot and wake time | Unchanged | Unchanged | Slower cold start |
| Custom input names and Home Dashboard tiles | Reset, must be redone | Kept | Kept |
| Seamless refresh-rate switching (QMS) | Kept | Kept | Kept |
Who feels each loss depends on the setup. A soundbar owner loses Magic Remote volume the moment Simplink goes off, therefore the soundbar’s own remote comes back onto the coffee table permanently. A Quick Start+ user gives up roughly six to eight seconds of wake time, which is irritating rather than disqualifying.
The asymmetry is the whole argument. Fix A costs you ten minutes once. Fix B costs you a feature every single day. Run the one-time cost first.
The PS5 Pro Case: Stopping the 1080p Drop at 40Hz and With VRR Enabled
Console pairings are the most-reported case, and the pattern is consistent. The PS5 Pro negotiates 4K 120Hz with VRR at first connect, then fails the re-handshake after a sleep cycle and falls back to 1080p, because the TV handed it a truncated EDID and the console defaults to a mode it knows will display. The AVForums thread LG G4 77″ PS5 handshake issue is a useful troubleshooting log here, including the workarounds that did not hold, and owners there converged on connection-history wipes rather than cable swaps.
- On the console, set Video Output to Automatic and turn VRR off temporarily
- On the TV, run Delete Connection History, then power both devices down
- Power the console on first, then the TV, and let the console re-detect the display
- Confirm 4K 120Hz and HDR in the console’s Video Output Information screen
- Re-enable VRR on the console and re-test for flicker
- If the drop returns within a day, turn Simplink off and repeat steps 2 to 5
After the sequence, the console’s Video Output Information screen should list 4K, 120Hz, HDR and VRR as supported. If 40Hz modes are still absent, the port is in the wrong HDMI mode rather than the handshake failing, so check that HDMI Deep Colour is enabled for that specific input before you escalate any further.
PC and AV Receiver Cases: RTX Cards, Denon and Marantz Pass-Through
These two cases reach opposite verdicts, which is why they need separating.
RTX Graphics Cards at 4K 120Hz
A desktop GPU re-reads the display’s EDID on every wake, therefore a stale cached entry produces the flicker loop at 4K 120Hz and at 1440p, exactly the resolution lock pattern reported through autumn 2026. Delete Connection History resolves this. Simplink off does not, because the graphics card never speaks CEC in the first place. Clear the PC side too: disconnect the display in Windows, let it re-detect, and the driver rebuilds its own cached entry.
Verdict: for PC handshake loops, Fix A wins outright.
Denon and Marantz Pass-Through and eARC
A receiver in the chain adds a second CEC controller, which means two devices compete to set input and power state, resulting in input hijacking and intermittent eARC silence. Turning Simplink off removes one competitor and stabilises the chain. There is a better-targeted alternative, though: disable the receiver’s own HDMI control instead and keep Simplink on, because that ends the arbitration conflict while preserving Magic Remote volume.
Verdict: for receiver chains, try the receiver’s control toggle first, then Simplink off.
When Neither Fix Works: Cable Certification, Port Choice and Full Factory Reset
Software steps come before hardware steps because they cost neither money nor data. One nuance matters before you spend anything: an uncertified cable fails intermittently at full bandwidth rather than failing outright, which looks identical to a lg oled hdmi handshake fault from the sofa. The HDMI Licensing Administrator’s Ultra High Speed cable certification programme exists precisely because 48Gbps signalling is where marginal cables break, so confirming certification is worth doing before a factory reset wipes your settings.
Port choice is the other trap. eARC runs on one designated HDMI port per model, typically HDMI 2 on recent C and G series sets, which means a soundbar plugged into a standard input produces audio symptoms that no software fix will clear.
- Confirm the soundbar or receiver is on the TV’s eARC port, not a standard HDMI input
- Swap in an Ultra High Speed certified 48Gbps cable under 2m and re-test
- Hard power cycle: switch off at the wall, unplug every HDMI cable, hold the TV’s physical power button for 30 seconds to drain residual voltage, wait 10 minutes, then reconnect
- Try the source on a different HDMI port to rule out a single failed port
- Reset to Initial Settings (factory reset) under General > System, then set up inputs from scratch
- Log the fault with LG support with model, firmware version and source device so it enters the bug queue
Step three is the one the community kept returning to through late 2026. Draining residual voltage clears state that a standby power-cycle leaves intact, therefore it sometimes succeeds where both menu fixes failed.
Who Should Pick Which Fix, and When to Just Wait for LG’s Patch
Pick Delete Connection History if your fault is video-side. That covers black screens, flicker loops, HDR dropping to SDR and resolution locks. It is the right first move for anyone gaming on a PS5, PS5 Pro, Xbox or a desktop PC, and for anyone who wants to keep one-remote control over a soundbar. Console-and-TV setups with no receiver in the chain rarely need anything more.
Pick Simplink off if your fault is audio-side or control-side. That covers eARC dropouts, a TV that switches input on its own, and a set that powers up when another device wakes. Denon and Marantz chains belong in this group, as does any setup where the fault returns within days of each connection-history wipe, because recurrence that fast points to CEC arbitration rather than EDID caching.
Wait it out if the symptom is cosmetic. A brief flicker on input switch, with everything else stable and your firmware on the current WebOS 26 build, is not worth trading features for. Hold your settings and watch for the next firmware release, because LG has not published a rollback path and manual downgrades void the warranty on most models.
Limitations of This Guidance and What We Could Not Verify
The symptom patterns and fix outcomes above come from owner reports on r/LGOLED, the LGWebOS community forum and AVForums between late 2025 and November 2026, alongside LG’s published settings documentation. These are user reports rather than controlled testing, which means symptom frequency by model is indicative and not measured. We have marked table cells “Not stated” where the sources do not support a value.
Several questions stay open. LG has not published a bug acknowledgement or a dated patch for the WebOS 26 HDMI behaviour. Firmware rollback is not officially supported on current models. The exact firmware build that introduced each symptom varies by region, so a build number from one market will not necessarily match yours. Outcomes also depend on the source device’s own EDID handling, which means a sequence that works with a PS5 Pro does not automatically transfer to a Denon receiver.
Three alternatives sit outside this article’s scope: HDMI EDID emulators and splitters, source-side resolution forcing, and professional service repair for a genuinely failed port.
Conclusion
Run Delete Connection History first, every time. Reserve Simplink off for audio and control faults, or for the case where the fault comes back within days of each wipe, because a lg oled hdmi handshake failure that recurs that quickly is usually a CEC arbitration problem rather than a cache problem.
The next action is specific. Run Delete Connection History tonight, power your source on before the TV, re-enable HDMI Deep Colour on that port, and write down the date so you can tell whether the fault returns after the next firmware push.
Be honest about what you have achieved, though. Neither fix repairs a firmware bug, therefore keep a record of your model, firmware version and source device and report it to LG support, so the real fix arrives as a patch instead of a workaround you repeat every few months.
Read more hands-on TV and home entertainment coverage on The Tech ABC.
Frequently Asked Questions
What is an HDMI handshake, and why does it fail on an LG OLED?
An HDMI handshake is the HDCP and EDID exchange that confirms both devices support the same resolution, HDR format and copy protection. A lg oled hdmi handshake fails when the TV’s cached EDID no longer matches what the source expects, which typically happens after a firmware update rewrites how the set stores that data. The result is a black screen or a fallback resolution.
Should I delete connection history or turn Simplink off first?
Delete connection history first. It clears the cached EDID without disabling any feature, so the only cost is re-entering your input names. Turn Simplink off afterwards, and only if the fault returns or if your symptom is audio dropout or the TV hijacking its own input.
Where is Delete Connection History in the LG OLED menu?
All Settings > General > Devices > External Devices > Delete Connection History. Older WebOS builds place it under General > External Devices directly, without the Devices step. The gear button on the Magic Remote opens All Settings.
What do I lose when I turn Simplink off on an LG OLED?
You lose HDMI-CEC entirely. That means Magic Remote volume control over a soundbar or receiver, synced power-on and power-off with your source, and automatic input switching when a device wakes. Picture quality, bandwidth and refresh-rate support are unaffected, because CEC carries control commands rather than video.
Does deleting connection history erase my input names and settings?
Yes, partially. Custom input names, device icons and Home Dashboard tiles reset, and per-port HDMI Deep Colour needs re-enabling. Picture presets, network settings and installed apps stay untouched. Budget about ten minutes of clean-up on a four-device setup.
Why did my LG OLED HDMI stop working after the WebOS 26 update?
The update changed the TV’s EDID handling, leaving stale cached entries that fail negotiation. Owners on r/LGOLED reported “No Signal” messages and audio dropouts through October and November 2026 on setups that worked before the update, which indicates the cause is firmware rather than cables or ports.
Which fix stops eARC audio dropouts to a soundbar or receiver?
Try Delete Connection History first, then turn Simplink off. eARC depends on both EDID for the audio format list and CEC for the control channel, so either layer can be the fault. Confirm your soundbar is on the TV’s designated eARC port before changing any setting.
Why does my PS5 Pro drop to 1080p on my LG OLED?
The console received a truncated EDID on re-handshake, so it fell back to a mode it knew would display. Run Delete Connection History, power the console on before the TV, then confirm 4K 120Hz and HDR in the console’s Video Output Information screen.
What should I do if neither fix works on my LG OLED?
Hard power cycle the set. Switch it off at the wall, disconnect every HDMI cable, hold the physical power button for 30 seconds to drain residual voltage, wait 10 minutes, then reconnect. If the fault survives that, swap in a certified cable and then factory reset.
Do I need a certified 48Gbps HDMI cable to fix handshake failures?
Only if you run 4K 120Hz, 8K or full-bandwidth HDR. Uncertified cables fail intermittently at high bandwidth, which mimics a handshake fault closely. An Ultra High Speed certified cable under 2m removes that variable, but it will not fix a failure caused by firmware.
References
Related reading: re-editing and deleting on TikTok




















































































