Old T-UI habits should remain useful, not become a cage.
RETUI still begins with a prompt, commands, and configuration you can inspect. The difference is that the project now gives modern Android, safer workflows, and visual discovery a proper place beside them.
The prompt is still home
If you are returning from the original T-UI Launcher, the important part has not been replaced. Commands remain the quickest path through the app. Configuration files remain real. Themes still change the character of the whole screen.
I did not want modernisation to mean covering the terminal with conventional Android screens. I also did not want loyalty to the old architecture to make every new user hunt through XML before changing a colour.
RETUI keeps both doors open. Type when you know what you want. Open a visible surface when you need to discover what is possible.
Start with settings
The current settings hub is the best place to reorient yourself. It groups appearance, behaviour, modules, app organisation, integrations, backup, and diagnostics without hiding the underlying configuration model.
settings help apps -ls module -ls preset -ls
The older themer command still opens the settings surface for compatibility. I would teach settings now because the screen has grown beyond theming.
Save a preset before you experiment
Presets are now the useful unit for a complete RETUI look. They can hold the state you actually want to return to instead of leaving theme sharing as a loose sequence of manual edits.
preset -save my-current-look wallpaper -auto preset -save wallpaper-test preset -ls preset -apply my-current-look
wallpaper -auto asks for confirmation because enabling wallpaper-derived colour can replace a look you have already tuned. Save first. Experiment second. Returning should be boring.
The visual surfaces do not replace the commands
The app drawer can now show alphabetical tabs, groups, and hidden-app organisation. Modules can stay visible as terminal panels. Notifications and music can live in dedicated surfaces instead of turning every update into another line in command history.
None of that makes the prompt ornamental. The drawer reflects the app organisation managed by apps. The settings hub edits the same system the Launcher reads. The visual pieces are there to make state easier to understand and repeated actions easier to reach.
Some responsibilities moved out of Launcher
The biggest conceptual change is larger than a command rename. RETUI now includes separate Files and Keys applications.
Use files in Launcher to hand the current directory and visual context to RETUI Files. Use RETUI Keys as a normal Android keyboard when you want terminal controls and local suggestions beyond the home screen.
This separation is deliberate. Modern Android storage permission belongs in the file manager. Keyboard data belongs in the keyboard. Launcher can connect the experience without collecting every responsibility into one process.
A practical return path
- Open
settingsand check the font, colours, wallpaper, layout, and gesture choices. - Save that starting state with
preset -save <name>. - Run
apps -ls, then rebuild groups and hidden-app choices as needed. - Open
module -lsand add only the panels you actually want on screen. - Grant notification access only if you want notification surfaces.
- Run
wallpaper -autoafter the safe preset exists, then keep or revert the result. - Open Files and Keys as their own apps and decide whether each belongs in your setup.
Next release ยท local build
Keep a recovery point while the next build settles
The local Launcher build records a durable restore journal before replacing configuration files. If the process stops during activation, recovery can restore the previous files and preferences; completed restores keep their new configuration. Cancelling during preparation preserves the current setup. Once the final commit begins, it must finish or recover.
Frame settings have their own recoverable draft, and module library updates require an explicit replacement choice while keeping saved module settings and data. These safeguards concern Launcher; they are not a new release announcement for the standalone Files app.
Basic calculation remains built in. Advanced Qalculate calculation moves to an optional engine pack, so an upgraded user who needs units or exact results must install that pack. The public pack catalogue is not available yet; local import works independently. Calculator preferences are retained in backups, while downloaded engine packs must be installed again after a restore.
Focused local checks and recovery mechanisms do not replace testing the final release as an upgrade from your installed version. Export a backup before trying a development build, and keep the released app until the release candidate has completed that verification.
RETUI should reward the muscle memory you already earned. It just should not require the whole project to stand still around it.