Teal / Launcher

A wallpaper can start the theme. A preset lets you keep it.

I like the idea that RETUI can look at the wallpaper you already chose and find a palette inside it. I do not like the idea that an automatic choice should quietly become permanent. Those are two different jobs.

Auto-colour is a beginning

Run `wallpaper -auto` and RETUI enables wallpaper-derived colours. The launcher uses the current wallpaper to calculate the effective palette for text, backgrounds, borders, suggestions, modules, and the shared terminal chrome.

Before it enables that mode, RETUI asks whether you have saved your preset. That little interruption is intentional. A wallpaper can change, and a generated palette can replace a visual state you spent time adjusting.

wallpaper -auto
Please confirm if you have saved your preset (Yes/No)

The system wallpaper controls are still there

The `wallpaper` command is also the quickest route to Android's wallpaper pickers. This part does not need a new RETUI abstraction.

wallpaper

Open the normal static wallpaper picker.

wallpaper -static

Open the same static picker explicitly.

wallpaper -live

Open Android's live wallpaper chooser.

wallpaper -auto

Enable or refresh the colours RETUI derives from the current wallpaper.

The RETUI WALLPAPER entry in Settings is a separate project surface. The command above deals with the Android wallpaper and the Launcher palette built from it.

A preset is the decision to keep something

Once the generated palette feels close, I can adjust the details and save the result under a name. That saved preset contains the current colour values from `theme.xml` and `suggestions.xml`.

wallpaper -auto
# adjust the colours you care about
preset -save night-train

Saving also applies the new preset. Applying a preset copies its two colour files into the active RETUI configuration and disables wallpaper auto-colour. From that point, the saved values are in charge again.

The command stays small

preset -save <name>

Save the current theme and suggestion colours. Saving an existing name updates that preset.

preset -apply <name>

Apply a saved or built-in palette and turn auto-colour off.

preset -ls

List your saved presets alongside the palettes included with RETUI.

The built-in choices are `blue`, `red`, `green`, `pink`, `bw`, and `cyberpunk`. Saved and built-in names also appear in command suggestions, because remembering the look should not require remembering the exact spelling.

My practical route

1. Choose a wallpaper

Start with the image you actually want to live behind the launcher.

2. Run wallpaper -auto

Let RETUI find a first palette instead of choosing every colour from nothing.

3. Make it yours

Adjust the colours that need more contrast, less noise, or simply better taste.

4. Save the decision

Use `preset -save <name>` when the experiment has become a look worth returning to.

If I change the wallpaper later, I can run auto-colour again and begin another variation. If it goes somewhere I do not like, the previous preset is still one command away.

Sharing is deliberately separate

A local preset and a shareable configuration solve different problems. The preset is the quick personal snapshot. Settings can package a configuration for another person when the point is to move a look between devices.

That separation keeps a simple command simple. I can collect several moods for my own phone without turning every experiment into an export format.

read the Preset Sharing post

Automatic colour gives RETUI somewhere interesting to begin. A preset marks the moment when the machine's suggestion finally feels like mine.