LG OLED C1/C2 Logo Brightness Dimming: Test the Real Trigger

Quick Answer

To test whether LG's Logo Luminance/Adjust Logo Brightness feature is involved, compare the same moving content with a stationary logo or game HUD present, then with that overlay absent while picture mode, average brightness and source remain unchanged. Photograph or measure the logo region and a nearby moving region separately. LG describes the feature as detecting static logos and reducing brightness to help limit image-retention risk; RTINGS describes it as dimming the area around a detected logo.

Do not assume every whole-screen brightness change is logo protection. An immediate change when a bright field fills the screen is more consistent with ABL. Gradual dimming of an almost unchanged whole scene may involve static-scene behavior. Energy Saving/AI Brightness, broadcast camera cuts, HDR mapping and firmware variation are separate branches. Keep protection enabled while diagnosing.

Symptoms That Need Different Explanations

A fixed score bug or game HUD becomes less bright while nearby motion stays similar: logo protection is plausible.

The entire hockey rink dims immediately on a wide shot: bright-area ABL is more likely.

The whole picture fades only after a long low-motion scene: time-based static recognition is possible.

Brightness follows room lighting: Energy Saving/AI Brightness is involved.

The screen changes exactly at a commercial, replay or camera cut: source production may explain it.

One app dims but the same channel through another device does not: app/output processing matters.

A logo-shaped dark mark remains after changing content: possible retention/wear, not active dimming.

A permanent patch appears in LG Home with no logo: panel/service diagnosis.

Owner reports disagree about whether a given event looks localized or global. That disagreement is why a region-based comparison and controlled overlay test are more useful than naming the behavior by sight.

Causes: What Logo Luminance Is—and Is Not

Detection of persistent graphics

Channel logos, scoreboards, news tickers and game HUDs can remain in one place while the background changes. LG's consumer reliability guidance says Logo Luminance Adjustment can detect static logos and reduce brightness. This is intended to reduce cumulative differential wear from repeated fixed bright elements.

Local perception can look global

A large ticker, HUD frame or several static graphics can cover a meaningful portion of the screen. Human vision adapts to the graphic and nearby content, so local reduction may be perceived as a whole-image shift. Some community reports claim global changes; others report localized behavior. Without measurement or a controlled mask comparison, do not attribute internal scope with certainty.

ABL follows bright area/load

RTINGS measures the C2 as significantly dimmer for large bright scenes than small highlights. If the whole picture changes immediately as a white field or menu expands, logo detection is not required to explain it. Logo on/off tests must keep average picture level similar.

Static-scene and energy behavior

TPC/ASBL terminology commonly refers to dimming over elapsed low-motion time, whereas Logo Luminance targets persistent graphics. Energy Saving and AI Brightness operate through supported user settings and may alter the entire screen. These mechanisms can overlap during news, sports or a game pause.

Firmware and model-year variation

C1/G1 and C2/G2 use different webOS generations, and firmware can alter menu wording or detection behavior. A timing reported for another model/build is not a specification. Record firmware and repeat after official updates rather than promising one fixed delay or region.

Step-by-Step Localized Logo Test

1. Choose a reproducible source

Use a recorded sports segment, news clip or game training scene where a fixed graphic can be shown and hidden without changing camera content substantially. Record signal type, app, input, picture mode, firmware and Logo Brightness setting. Avoid a live-only test whose production changes cannot be replayed.

2. Establish a neutral picture baseline

Begin in SDR when possible. Use Cinema, Filmmaker or another neutral supported mode, set room-appropriate OLED Pixel Brightness, and hold room light constant. Record Energy Saving, AI Brightness, Peak Brightness and Dynamic Contrast. Do not copy calibration values.

3. Mark two comparison regions

Select one small region containing the static logo and a nearby region with continuing motion and similar initial luminance. A camera on manual exposure, colorimeter if available, or careful side-by-side screenshots from the same TV session can document relative change. Automatic phone exposure can invent a global brightness shift, so lock exposure where possible.

4. Compare overlay present versus absent

Run the segment with the logo/HUD visible long enough to observe normal behavior, then hide the HUD through a documented game option or compare a replay package where the broadcaster removes its score bug. Keep content and mode as close as possible. Do not edit the feed or leave a static test logo for hours.

5. Run the area test separately

Resize a bright window or compare wide versus close sports shots for immediate whole-screen change. If the change tracks bright area within seconds, classify ABL separately. This prevents falsely crediting Logo Brightness for an area/power response.

6. Run the time test separately

At constant area, observe whether the whole scene gradually dims with limited motion and recovers after a large menu or scene cut. Record elapsed time. That behavior belongs in static-scene diagnosis even if a logo is also present.

7. Neutralize energy automation

Temporarily disable Energy Saving/AI Brightness in normal menus and maintain constant room light. Repeat only the controlled sequence. Restore preferred supported settings later. If brightness tracks ambient light, logo protection was not the sole trigger.

8. Compare source and firmware paths

Test an internal app and an external source with similar content. Confirm SDR, HDR10 or HLG. After an official firmware update, verify that the active mode/settings were not reset and repeat the same recording. Do not use unofficial firmware or assume rollback is supported.

Safe Responses by Result

If only a logo/HUD region changes, leave Logo Luminance enabled, vary content, use HUD opacity/hide options supplied by the game and reduce sustained SDR brightness. If ABL dominates, manage large bright area and ambient light. If the whole low-motion scene dims over time, update officially, use display sleep for pauses and report repeatable false positives to LG. If only one broadcast changes, compare provider/device output before changing the TV.

Cautions

Do not disable logo protection, TPC or GSR through service menus. Cumulative OLED wear depends on brightness, duration and repeated static placement; a short clean-panel anecdote does not establish long-term safety. Do not run manual Pixel Cleaning for active dimming, and do not raise black level or use Dynamic Contrast to conceal it. Persistent logo retention across varied normal content should be documented for LG support.