LG OLED C2/G2 Auto-Dimming After Firmware: Test Before and After

Quick Answer

If C2/G2 auto-dimming seems different after firmware, do not infer causation from timing alone. Record the exact firmware, input, SDR/HDR/Dolby Vision context, picture mode, Energy Saving/AI settings, Peak Brightness and a reproducible scene with timestamps. Restart the TV, verify whether the update reset or migrated settings, then compare the same content and mode. Install only LG's current public firmware for the exact regional model and do not promise or attempt an unsupported rollback.

A firmware change can alter behavior, but an update may also reset Energy Saving, change the selected picture mode, leave a stale HDMI/HDR state or coincide with a source/app update. Community reports conflict across sizes and installations. The safe outcome is documented reproduction and an LG service case—not a claimed universal firmware cure.

Symptoms Worth Separating

The whole picture gradually darkens during a long dark movie scene and recovers on a bright cut.

A desktop dims when static and brightens after scrolling or toggling HDR.

Full-screen white immediately dims compared with a small window: that is ABL behavior.

Brightness follows room lighting: inspect AI Brightness/Energy Saving.

Only one HDMI input or HDR mode changed after update.

The active picture mode reverted to Standard/Auto Power Save.

One app changed while other internal and HDMI sources remain stable.

A fixed dark patch remains across menus and sources: not ordinary firmware auto-dimming.

Capture the behavior on video with the TV menu briefly showing mode and firmware. A subjective memory from before the update is weak evidence unless the same scene/settings were recorded.

Causes to Audit Before Blaming Firmware

Settings migration or reset

Major webOS/firmware changes can preserve, move or reset controls. SDR, HDR10, Dolby Vision and each input store separate contexts. A user may compare pre-update HDR Cinema with post-update Standard or an Energy Saving mode without realizing the mode changed.

Energy and ambient-light controls

Energy Saving, Auto Power Save and AI Brightness can reduce output or adapt it to light. If a brightness control is grayed out, the selected energy/picture mode may own it. Test with constant room lighting and record these values.

Static-scene protection

OLED protection can reduce brightness when the image changes too little. Long dark shots, static game HUDs and desktop windows may trigger different observations. LG documents Logo Luminance and screen-protection functions, but user labels such as ASBL often combine several mechanisms.

Area-based ABL

Firmware reports about “auto dimming” often confuse ABL with static detection. ABL responds quickly when bright area changes and remains part of OLED power management. A firmware version that adjusts static-scene recognition should not be advertised as removing ABL.

Source or application state

Windows HDR mapping, a console's HDR calibration, a streaming-app release or an HDMI handshake can change around the same date. Internal-app versus HDMI comparison is essential.

Step-by-Step Before/After Protocol

1. Record the installed build and model suffix

Open TV information and write down full C2/G2 model, region suffix and firmware. Do not install a file from another regional support page based on forum reassurance. Photograph relevant settings before any change.

2. Choose two reproducible tests

Use one legally available movie scene known to dim and one desktop/static test. Record timestamps, source, app version, input, room light and playback state. Add a short window-area test to identify ABL separately. Avoid hours-long static stress patterns.

3. Audit every active picture context

With SDR playing, record mode, OLED Pixel Brightness, Peak Brightness, Energy Saving and AI settings. Repeat while genuine HDR10 and Dolby Vision are active if those paths matter. Settings stored in one context do not prove another remained unchanged.

4. Restart before changing values

Use a normal restart/power cycle after the update and allow the TV to complete startup. Restart the source/app too. If toggling Windows HDR alone restores brightness, investigate the source state before altering OLED protection.

5. Reproduce with constant conditions

Run the same scene from the same timestamp and measure the time until dimming. Note what restores it: scene cut, menu overlay, pointer movement, input switch or power cycle. Compare internal playback with an external source where possible.

6. Neutralize user-facing automation

Temporarily disable Energy Saving/AI Brightness in normal menus and select a known picture mode, while keeping room lighting fixed. Re-run only the affected context. Restore preferred settings afterward. Do not enter service menus or disable TPC/GSR.

7. Check LG's official update channel

Use the TV's update function or the exact model's LG support page. Read release information where available. Install a newer stable public build if offered, then repeat the documented protocol. Absence of a listed dimming note does not prove no internal change; a forum claim does not prove one either.

8. Escalate with evidence

If multiple sources reproduce abnormal dimming after settings audit and restart, contact LG with model, firmware, before/after videos, scene timestamp and mode table. Ask for supported service action. Do not promise downgrade availability: consumer LG firmware normally does not expose a supported rollback path.

How to Interpret Results

Immediate area-linked changes indicate ABL and call for lower sustained SDR output/workload mitigation. Delayed dimming at constant area that recovers on motion suggests static-scene logic. Room-light correlation identifies ambient automation. One-app behavior points to that app/source. Persistent darkness across boot screens or a fixed patch warrants hardware support.

An update followed by improvement is still correlation unless the same controlled test changes while settings remain matched. Likewise, one owner's regression does not establish a generation-wide defect. Record uncertainty explicitly.

Cautions

Do not download unofficial firmware, alter region/model identifiers, block power during update or attempt hidden rollback procedures. Do not factory-reset before documenting settings; reset can erase the comparison. Do not use service-menu TPC/GSR changes as a firmware test, and do not run Pixel Cleaning for global dimming.