Custom Boot Animations and Themes for Mazda Connect
The Gen 6 Mazda Connect splash and home screen are just files on the CMU’s filesystem — a boot animation video, a background image, and a handful of color values the UI reads at startup. ScreenTune swaps those files for ones you provide. We change what the system displays; we don’t touch how it runs.
That distinction is the whole point of this page. Visual customization is the lowest-risk thing you can do to a CMU, because none of it sits in the boot chain or the driving systems. The worst outcome is a black splash or an ugly home screen — and you fix that by reverting one file.
What you can change
Section titled “What you can change”| Element | Customizable | What it is |
|---|---|---|
| Boot animation | Yes | The splash video that plays after the Mazda logo, before the home screen |
| Home screen background | Yes | The static image behind the home tiles; rotation through multiple images is available |
| System accent color | Yes | The highlight color on progress bars, active indicators, and selections |
| Off-screen / standby background | Yes | The image shown when the display is dimmed or idle |
| Background overlay opacity | Yes | How much the background is darkened under the UI |
| Button / icon styling | Limited | Some icon swaps are possible; the layout grid is fixed |
| Font | Limited | Constrained by the CMU’s installed font handling |
| Screen layout / tile arrangement | No | The home grid and menu structure are compiled into the UI, not configurable |
Boot animation
Section titled “Boot animation”The boot animation is a video that plays during startup, after the Mazda logo and before the home screen becomes interactive. A custom animation replaces the stock Mazda Connect clip with your own.
What matters in practice:
- The file has to match your display’s resolution and the system’s expected format. A 7-inch unit and an 8.8-inch unit have different native resolutions; an animation built for the wrong one will letterbox or stretch.
- A corrupt or unplayable file doesn’t brick anything. The system shows a black screen for the animation phase, then loads the home screen normally. It’s a cosmetic failure, not a boot failure.
- A firmware reinstall overwrites the custom animation with the factory one. Reapply afterward if you re-flash.
If you mainly want a faster startup rather than a different-looking one, the animation isn’t where the time goes — see boot optimization, which gets you CarPlay about 16–20 seconds sooner (and full responsiveness about 16 seconds sooner) every start by making smarter use of the CMU’s two processor cores.
Backgrounds and color
Section titled “Backgrounds and color”Home screen background. The home background is a static image the UI draws behind the tiles. It can be replaced with your own, and a rotation option cycles through several. Off-screen/standby uses a separate image, so the idle display and the active home screen can differ.
Overlay opacity. The UI darkens the background slightly so white text stays legible. That darkening is adjustable — lighter if your image is already dim, heavier if it’s busy.
Accent color. A single accent value drives highlights, progress bars, and active-selection indicators across the system. Changing it recolors those elements system-wide without touching text color or layout. It’s one value, not a per-screen theme.
Why visual changes are the safe end of the risk scale
Section titled “Why visual changes are the safe end of the risk scale”Nothing here lives in the boot chain or talks to the vehicle. Boot animations, backgrounds, and color values are read by the UI layer well after the CMU has started; they have no path to the systems that matter for driving. The failure mode for every item above is the same: a screen that looks wrong but still works, fully operable from the commander knob.
That’s the honest pitch — not that themes make the car faster or better, but that they’re cosmetic and reversible, with a known and trivial worst case. For how ScreenTune writes to the CMU in general and what it deliberately leaves alone, see how it works and the safety FAQ.
Reverting
Section titled “Reverting”Every visual change reverses cleanly:
- Miatafy app → Uninstall restores the appearance ScreenTune captured before it changed it — swapped boot animations, backgrounds, and accent colors back to what was there when you installed.
- Full firmware reflash reinstalls factory firmware and the default appearance — the fallback if you’ve also re-flashed or want a guaranteed clean slate. The firmware image is owner-obtained, not supplied by Miatafy.
Full procedures are in revert / uninstall and backup and recovery.
Coming from MZD-AIO themes
Section titled “Coming from MZD-AIO themes”If your CMU already has legacy MZD-AIO theme packs on it, remove them before applying new visuals. AIO themes were not built for clean uninstall the way ScreenTune changes are, so the cleanest path is a firmware reinstall first, then a fresh theme. See AIO on v74 for what carries over and what doesn’t.
Getting custom visuals
Section titled “Getting custom visuals”Custom boot animations and themes are handled as an add-on alongside the core tweaks. They pair naturally with a ScreenTune install; contact support with your vehicle details and what you want changed, and we’ll confirm format requirements for your display before anything is applied.