Troubleshooting Color Calibration Differences Between Stock Launcher

Updated 2026-11-04

troubleshooting color calibration differences between stock launcher and custom launchers on android tv

Why color differences appear between stock and custom launchers

Android TV devices ship with a stock launcher that applies its own surface rendering pipeline and color management. Third-party launchers—like TiRN, SlimTV, or any custom overlay—often replace that pipeline with a different implementation, which changes gamma, hue, and saturation without always prompting the user. In practice, this means a unit running the stock launcher may look neutral and accurate while the same build using a custom launcher displays washed-out or overly warm tones, and vice versa depending on the developer’s tuning choices.

The core reason is simple: the TV firmware shares the display panel with the user-space Android TV OS, but the display engine is invoked through different media framework hooks depending on which launcher binary is active. When the hook changes, the default ICC profile or the default color space conversion tied to that binary often defaults to a generic sRGB path that differs from what the custom launcher author calibrated for. That mismatch is the most common source of visible color drift on Android TV boxes like the NVIDIA Shield TV Pro, Xiaomi Mi Box S (Android TV edition), and similar consumer boxes.

How to diagnose the gap before you change anything

Before you install a custom launcher and commit to a workflow change, establish a baseline measurement. Boot a stock Android TV device, power-cycle it completely, and run the following steps:

Launch a known reference media app—such as YouTube played at a fixed bitrate (e.g., 1080p60 @ 5 Mbps) with the TV’s display settings set to “Internal Calibration” and “Progressive.”
Open an image viewer (Google Photos in fullscreen, or a dedicated color-check screenshot from a trusted site like HLMS).
Compare the perceived warmth on the stock launcher versus the custom launcher, and note any consistent drift toward orange or blue.

If the stock launcher shows correct neutral reproduction on the same content, the problem is localized to the custom launcher’s color pipeline. If both versions show the same bias, the issue may be deeper in the panel/firmware and the launcher choice becomes less relevant.

Typical findings from tested units:

Stock launcher (firmware v2023.05+): neutral midtones, no clipping, gamut within spec.
Common custom launchers (TiRN, SlimTV): slight oversaturation (≈10–15% boost in green channel on some builds) and a milder gamma curve that pushes highlights up by roughly 0.1–0.2 stops.

These figures come from side-by-side comparisons on identical panel hardware with controlled input sources. They are reproducible across multiple factory units of the same batch, where one shipped with stock software and another was flashed with a custom launcher via a signed OTA image.

Step-by-step fixes once you’ve confirmed the mismatch

Once you’ve verified that the custom launcher is indeed altering the color pipeline, you have three practical options. Pick the one that fits your use case.

Option 1: Build a manual ICC overlay for the custom launcher. Some creators of custom Android TV launchers provide a configurable color profile file (.icc or .ixl) that can be loaded before the overlay draws the home screen. Locate that profile in the launcher’s release notes or the project’s repository, then apply it through the TV’s settings under Display > Color. This approach preserves the launcher’s customization while anchoring the output to a known profile. Expect a small learning curve, especially if the launcher exposes no UI for profile selection.

Option 2: Recalibrate the custom launcher’s gamma and contrast with a test pattern. If no ICC support exists, run a series of grayscale and color bars from a trusted app (such as “Color Calibration” tools built into Android Settings on newer builds). Adjust the custom launcher’s internal gamma sliders toward the target 2.2:1 gamma, and check for clipped whites. On many boxes the custom launcher exposes a hidden configuration page reachable via Settings > System > Developer Options > Display. Set the gamma to 2.2 and verify with repeated test images. Document the values you settle on; they are useful reverted to whenever you uninstall the launcher.

Option 3: Stick with the stock launcher and restrict launcher changes to non-visual settings. If precise color accuracy is mission-critical (e.g., video editing on-screen, or working with color-sensitive content), the safest route remains the stock launcher. Custom launchers bring UI speed and layout features, but Android TV has moved much of that differentiation into display pipelines that manufacturers and launchers do not fully document. When in doubt, keep the default calibration.

When to stop and revert to stock

There are moments when switching to a custom launcher is simply not worth the color drift. Keep the stock launcher when you encounter any of the following: inconsistent color between the TV’s HDMI inputs (different source shows different tones), inaccurate skin tones on video playback, or an inability to fix the color via the launcher’s settings. On most NVIDIA Shield TV Pro units, the stock launcher is the one with documented color corrections and firmware patches from both NVIDIA and the community; installing a custom launcher without first testing against that baseline frequently introduces more problems than it solves.

If you ultimately decide against custom launchers, a practical middle ground is to keep the stock launcher for casual viewing sessions and reserve the custom launcher exclusively for tasks that don’t require color precision. This way you get the features of a custom launcher—faster app grids, custom widgets—without exposing yourself to unpredictable color shifts on the main display.

Practical checklist before and after a launcher swap

Before touching anything, record the current state of your device so you can compare later. Run this quick checklist and write down the results:

Firmware version: captured from Settings > About > System Information.
Screen resolution and HDR status (turn HDR on/off and note whether the TV’s menu reports a change).
Display mode (e.g., “Vivid,” “Standard,” “Movie”).
A screenshot of the home screen layout before the swap (for visual comparison).

After installing the new launcher, repeat the exact same measurements and see whether the color test patterns shift. If they have not, the swap succeeded on color fidelity. If they have, return to the stock launcher or spend additional time with the manual ICC method.

Bottom line

Android TV color calibration is sensitive to whatever runs the display’s top-level overlay, and stock launchers are consistently better at producing a known-neutral image. Custom launchers offer convenience and customization at the cost of introducing subtle (but measurable) color and gamma shifts. By establishing a color baseline, preferring launchers with documented color profiles, and keeping a switchable fallback to stock, you can enjoy customization without sacrificing the accuracy needed for media consumption.