Skip to content

Audio, UI, System & Boot Tweaks for Mazda Connect

These are individual changes ScreenTune applies to a factory Gen 6 Mazda Connect unit running v74.00.324A. Each one edits the CMU’s own configuration or UI assets — there is no added hardware and no replacement head unit. Tweaks are bundled on the product USB; you select which to enable. Every change is reversible by reverting (see Revert & Uninstall).

The MZD-AIO README catalogs the older community-tweak era and is a useful historical reference, but legacy AIO payloads do not run on v74 — the file layout and signing changed. Where a tweak below has a v74-specific implementation, that is what ships.

These modify media playback and the sound environment. None of them touch the amplifier or speaker tuning; they change what the head unit displays and how it routes playback control.

Enlarges the album artwork shown during media playback. The factory layout renders a small thumbnail; this expands the displayed image.

Substitutes a default image for the gray placeholder the CMU shows when a track has no embedded artwork.

Removes the Gracenote branding text overlaid on the media playback screen.

The stock v74.00.324A mute button silences the speakers but lets the track keep playing. This tweak makes mute send a pause command to the active media source instead. In development; not yet shipping.

Silences system notification sounds — button-press feedback, warning chimes, navigation prompts. Media audio and phone call audio are unaffected.

Adjusts USB audio handling for better behavior with USB storage devices. The older-firmware version documented by MZD-AIO added folder controls, corrected list icons, trimmed some UI clutter, and added track-change notifications.

Shows an overlay when the playing track changes, displaying the new track name and artist.

Reorders the audio source list in the media menu so frequently used sources (USB, Bluetooth) sit ahead of rarely used ones.

These change the layout and navigation of the CMU interface. MZD-AIO documents the original older-firmware versions of the menu loop, list loop, status-bar date, background, and color-scheme changes.

Wraps the main menu: scrolling past the last item returns to the first, and vice versa. Removes the dead stop at each end.

Applies the same wrap-around to all scrollable lists (contacts, media, settings), not just the main menu.

Adds the date next to the clock in the top status bar, with a configurable format (e.g. YYYY-MM-DD).

Conflict: Cannot run alongside Status Bar Speedometer — both write to the same status-bar region. The installer enforces this as a mutual exclusion.

Shows current vehicle speed in the top status bar, so you can read it without opening a dedicated speedometer app.

Conflict: Cannot run alongside Date in Status Bar.

Known issue: May not display correctly while CarPlay is active.

Sets a custom accent color applied across the interface.

Cycles through a folder of wallpaper images as the CMU background. Custom images are copied onto the USB drive during install.

System tweaks change CMU configuration to enable functionality the stock unit does not expose.

Creates additional swap space on the CMU’s writable partition. This is a dependency for the Video Player app — video decoding exceeds the CMU’s limited RAM without swap. MZD-AIO documents the same swap requirement for older firmware.

These are the changes you actually feel day to day: the whole system runs faster and more responsive, with no spots of lag, and CarPlay is ready about 16–20 seconds sooner every single time you start the car. On the same unit and firmware, the system becomes fully responsive (touch-ready) at roughly 32 seconds instead of about 48 (~16 s sooner), and CarPlay connects at roughly 55 seconds instead of about 71 — about 16 s sooner on a typical start, up to ~20 s on a good boot. For the full back-to-back measurements and the honest per-boot ranges, see Boot Optimization and Boot Benchmarks.

The main reason CarPlay is ready about 16–20 seconds sooner. The CMU has a dual-core processor, but from a cold start the stock software piles almost all of its startup work onto the first core (which sits pinned at 100%) while the second core has spare capacity. Bringing up Wi-Fi and CarPlay has to wait its turn in that traffic jam. ScreenTune moves the Wi-Fi and CarPlay startup onto the second, less-busy core, so it runs right away instead of waiting in line.

The stock unit starts up services for hardware many cars never had (TV tuner, DVD/CD changer, DAB radio) and for online services that have since been shut down. ScreenTune skips those, which frees memory and processor time. That is part of why the system becomes fully responsive sooner, and why menus stay smooth afterward instead of competing with background tasks. SiriusXM stays on by default so it keeps working if you subscribe; it can be turned off if you do not use it.

The Mazda Connect menus and screens are drawn by a built-in browser engine. ScreenTune gives it a larger cache, so a screen it has already shown snaps back instantly instead of being rebuilt from scratch each time. That means less momentary lag as you move around the interface.

A supporting change: ScreenTune replaces the unit’s long sequence of small network setup steps with a single combined step, plus reduced background logging and CPU governor tuning. Together these shave a bit more off boot and leave more processing headroom so you stop hitting the random lag spots.

Boot tweaks change what the CMU shows during startup — the displayed assets only. They are separate from the performance work above that makes startup faster; for that, see Boot Optimization.

Replaces the factory Mazda loop animation with a custom VP8/IVF video. See Custom Boot Animations & Themes for format requirements.

Replaces the static Mazda logo shown during early boot with a custom image. See Custom Boot Animations & Themes for format requirements.

Every change here is a configuration or asset edit inside the factory software. They do not add CarPlay where the hardware lacks it, do not upgrade the amplifier, and do not run on Gen 7 units. For the full picture of what is and isn’t possible on the platform, see What’s Possible and How It Works.