ASBL and TPC on LG OLED: Static-Scene Dimming Explained

Quick Answer

ASBL is a community term for gradual OLED dimming during content the TV judges to be static. TPC is a service-menu label associated with this behavior on some LG OLED generations. Neither term should be treated as a complete public specification of LG's detection algorithm.

You may notice the effect during a paused movie, a dark scene with little movement, a game menu, a desktop or a calibration pattern. Model year, firmware, picture mode and the content itself can change when—or whether—it occurs.

How it differs from ABL

• ABL manages luminance when a large part of the screen is bright.
• Static-scene dimming develops when the picture changes too little for the TV's protection logic.
• Logo or static-region reduction can target persistent screen elements rather than the whole image.

These behaviors can overlap, which is why changing one undocumented service option does not guarantee a particular result.

Safer checks before advanced changes

1. Confirm the source has not enabled its own screen dimmer or power-saving mode.
2. Compare moving content with a paused image.
3. Lower sustained SDR brightness for desktop use and enable display sleep.
4. Install current production firmware, but expect menus and behavior to change.
5. Read the protection-features guide before considering service access.

Disabling a protection control can increase permanent image-retention risk and may affect support or warranty decisions. OLED Control can expose only controls supported by a particular TV and firmware; it cannot rewrite the panel's protection firmware.

What TPC means—and what ASBL does not mean

LG professional material expands TPC as Temporal Peak Luminance Control. “ASBL” is owner/community vocabulary rather than one complete LG consumer specification. It is useful shorthand for gradual whole-image dimming when the television believes content is static, but forum timing claims should not be generalized to every firmware.

GSR, Logo Brightness, Screen Move, energy saving and ABL can all change luminance for different reasons. Calling every change “ASBL” produces unsafe advice.

A timeline-based identification

A paused game menu that fades after a delay and recovers when navigation moves is consistent with static protection. A low-motion dark movie can create a false positive. A white page that dims immediately as it expands is ABL. A screen that follows room lighting suggests ambient automation. A source screen saver belongs to the source.

To verify, replay one timestamp, keep room and mode fixed, time the fade, and briefly display a normal playback overlay. Rapid recovery after new on-screen movement supports static detection. Compare an internal app and HDMI player to exclude source behavior.

C1/C2 and later firmware

Owners frequently discuss C1/G1 behavior because dark cinematography could be misclassified. Later generations and firmware revisions may change thresholds or remove service-menu access. A menu path reported on a C1 is not evidence that a C2, C3 or G-series set exposes the same entry.

LG does not publish engineering notes for every algorithm revision. Treat a verified before/after scene as evidence and a forum update date as a lead.

Safe responses

Keep supported protection enabled. Update via LG's public channel, turn off source screen dimmers only when diagnosing, use reasonable SDR output and display sleep for desktop use, and report reproducible false positives to LG with firmware and timestamp.

Do not enter IN-START/EZ-Adjust to change TPC. Service interfaces contain factory values unrelated to picture preference; errors can affect operation and warranty. Manual Pixel Cleaning does not disable active dimming and is not a remedy.

ASBL/TPC FAQ

Can subtitles prevent dimming?

Bright changing subtitles may alter detection, but they are not a reliable fix. Use them according to viewing needs.

Why do dark scenes trigger protection?

Low-motion photography can resemble an unchanged frame to an algorithm that cannot know the director's intent.

Is the fade permanent?

No. Protection-based luminance normally recovers when content changes. Persistent image damage is a different diagnosis.

Can OLED Control safely override it?

The app should not be represented as rewriting or bypassing LG panel-protection firmware.

Dark-film example

Imagine a five-minute night conversation with a locked camera and mostly black background. If it starts readable, fades gradually and immediately returns when the playback bar appears, that pattern supports a false static-scene classification. If it is equally dark from the first frame, mastering, Dolby Vision mode, room reflections or source output are more likely.

Repeat the timestamp instead of relying on memory. Keep subtitles, picture mode and room light constant. This produces evidence suitable for LG and avoids sacrificing protection across every other use case.

Desktop example

A code editor or news dashboard is genuinely static for long periods. In that case protection is responding to the exposure pattern it was designed for. Moderate SDR output, screen sleep, hidden taskbar and varied windows are safer than trying to make the panel ignore an all-day interface.

When to involve support

Report dimming that repeatedly affects normal moving content across internal apps and direct HDMI sources after supported firmware updates. Supply the exact model suffix, firmware, picture mode, title, timestamp, elapsed time and a fixed-exposure video. This gives LG a reproducible false-positive case. A statement that “ASBL is aggressive” without the signal and timing cannot distinguish protection from energy saving or source behavior.

• LG professional OLED specification naming TPC
• LG — TV software update guidance

Sources

• LG — How to prevent image retention or burn-in
• RTINGS — Real-life OLED burn-in test (secondary)