Palettes shared by the people who made them.
Every theme here was built in ColorBlendr and reviewed by a person before it went live. Browse them, vote, and apply one to your whole device from the app.
Trending right now.
Ranked by votes and applies, weighted toward newer themes. Hover a card and the page wears it. Tap a card to open it.
From your phone to this page.
Themes come out of the app, go through a person, and come back to everyone else's app.
-
Build it
Make a palette in ColorBlendr: seed colors, Monet styles, saturation, per-shade overrides.
-
Share it
Submit it anonymously from the Community screen. A person reviews every submission before it goes live.
-
Apply it
One tap in the app themes the whole device with any theme from the catalog.
What happens when you tap apply.
Android 12 introduced Monet: the system derives a tonal
palette from your wallpaper and locks you out of the rest.
ColorBlendr works at the layer underneath. It builds its
palettes on-device (six tonal rows, thirteen shades each)
and injects them at runtime through the
FabricatedOverlay API or the system's theme
customization settings. No APK overlays are compiled and no
system partition is touched. Removing a theme is the same
operation as applying one.
Every change previews live inside the app before anything reaches the system. A staged preferences layer holds your edits in memory; commit applies the overlay, discard drops it. The engine re-applies your configuration on boot, wallpaper change, and dark-mode switches through event-driven broadcast receivers. Nothing polls.
Root
The full engine. Fabricated overlays register directly with the system's overlay service, so palette changes land instantly, without a reboot. Per-shade overrides on every palette row, saturation and lightness sliders from 0 to 200%, per-app theming, and one-tap community themes.
Grant root once
Shizuku
No root required. A helper process at shell privilege writes the system's theme customization settings directly. Any seed color and Monet style; settings persist across reboots.
Start Shizuku after each boot
Wireless ADB
The same shell-privilege path, negotiated on-device over the ADB TLS protocol. Pair once with your own device; no computer involved afterward.
Pair once over Wi-Fi
Next to what Android already offers.
| Capability | ColorBlendr | Stock Android 12+ | OEM theming | Substratum (legacy) |
|---|---|---|---|---|
| Apply speed | Instant, runtime | Wallpaper change + regeneration | Instant, preset-bound | Reboot or SystemUI restart |
| Works without root | Yes, via Shizuku or Wireless ADB | Yes | Yes | Mostly no1 |
| Custom seed color | Any color, any source | Wallpaper-derived only | Preset packs | Per-overlay, precompiled |
| Per-shade manual overriding | Yes, 11 editable shades per row2 | No | No | Only if the overlay author shipped it |
| Saturation and lightness control | Sliders, 0 to 200%, per mode2 | No | Limited presets | No |
| Pitch-black AMOLED rendering | Yes, one switch2 | No | Partial3 | Per-overlay |
| Storage footprint | None; overlays are fabricated in memory | None | None | APK per overlay, accumulates |
| Survives OS updates | Yes, re-applies from saved config | Yes | Yes | Frequently breaks, needs rebuilds |
| Community sharing | Anonymous, human-reviewed, in-app | No | Locked to OEM stores | Third-party packs, unreviewed |
1. Substratum's rootless "Andromeda" mode required a PC tether per boot and died with Android 10.
2. Root mode only; Shizuku and Wireless ADB modes cover seed color and style selection.
3. OEM dark modes darken surfaces but rarely reach true #000000 across system UI.
Questions from power users.
- How does ColorBlendr change system colors without permanently modifying the system?
-
Through
FabricatedOverlay, an Android 12+ API that registers resource overlays with the OverlayManagerService at runtime. Nothing is written to/systemor/vendor, no APK is installed, and no partition is remounted. Unregistering the overlay restores stock behavior in the same second.In Shizuku and Wireless ADB modes, ColorBlendr instead writes the documented
theme_customization_overlay_packagessecure setting, the same mechanism the stock wallpaper picker uses, with more of its fields filled in. - Why don't Samsung OneUI system apps change color?
-
OneUI's system apps read from Samsung's own palette pipeline, not Monet. ColorBlendr replaces the Monet palette, so every app that honors Material You (Google apps, most modern third-party apps) follows it. Samsung's own UI ignores Monet by design, and no overlay-based tool can change that without modifying Samsung's framework itself.
- Do the background service and live previews drain battery?
-
The service exists to keep broadcast receivers alive; it reacts to wallpaper changes, boot, and dark-mode switches. There is no polling, and between events it is idle.
Live preview never touches the system at all: it loads the candidate palette into the app's own process through
ResourcesLoader, so previewing costs the same as rendering any app screen. The palette math (the CAM16 color appearance model) runs once per change, in milliseconds, then is cached. - What happens to my overrides after a reboot or ROM update?
-
Your configuration is the source of truth, stored in app data rather than in the overlay. After boot, once you unlock, a receiver re-registers the overlay from that configuration. ROM updates that clear registered overlays are handled the same way: the next boot re-applies everything.
Per-shade overrides, sliders, and saved styles also travel inside backup files you can export and restore.
- How does anonymous sharing work without accounts?
-
Submitting a theme uploads only the color specification plus the name and description you type. A person reviews it as a public pull request before it appears. Voting needs duplicate protection, so the app sends a one-way SHA-256 hash of the device identifier with an app-specific salt. It cannot be reversed, cannot be correlated across apps, and is stored only to enforce one vote per device.
No accounts, no analytics, no advertising identifiers. The whole pipeline is public: repository, review process, and serving infrastructure.
Share what you made
Every theme here came out of the app. Build a palette you like, share it from the Community screen, and it shows up once a person has reviewed it.