Skip to content
Miatafy Miatafy

Where the ScreenTune Log Is and What It Records

Zip the entire contents of the ScreenTune USB and email the ZIP to support. That one file holds everything support reads. Get help shows how to zip the drive on Windows or a Mac.

Where the files are on the USB

Section titled “Where the files are on the USB”
USB drive
├── screentune.log          every run, appended in order
├── logs/
│   ├── run-2026-10-12_18-04-51/
│   │   ├── screentune.log  this run only
│   │   └── ...             system snapshot files
│   └── run-1970-01-01_00-02-13/
└── (package files)
  • screentune.log at the top level collects every run on this USB, one after another.
  • logs/run-…/ holds one folder per run, with that run’s own screentune.log. A run that passed the firmware, VIN, and media checks also holds a system snapshot taken before any change.
  • A support bundle exported from the Miatafy app goes into its own timestamped folder under logs/. Get help shows how to export one.

Folder dates can read 1970

Section titled “Folder dates can read 1970”

The CMU’s clock can start at January 1, 1970 before it gets the time, so run folders can be named run-1970-01-01_…. The newest-looking folder name may not be the newest run, so send the whole USB, not one folder.

A log exists only when a prompt appeared

Section titled “A log exists only when a prompt appeared”

ScreenTune writes a log on every run that reaches the SCREENTUNE prompt, including runs where you chose CANCEL. No log means the firmware or package check stopped the run first. See no prompt appears.

What the log records

Section titled “What the log records”
  • Versions. The ScreenTune version and the car’s firmware version.
  • The action. INSTALL, UPDATE, REPAIR, REMOVE, or CANCEL.
  • The changes. The internal ID of every change in the package, and whether each applied or failed.
  • The outcome. Any rollback, and how the run finished.
  • The VIN. The VIN read from the car, for actions that check it.
  • The system snapshot. Version details, running processes, memory and storage use, network interfaces, and Mazda Connect’s own system logs and configuration files.

The snapshot leaves out Wi-Fi credentials, hotspot profiles, and network address leases, and a privacy.txt file in the run folder lists what was omitted. The rest includes your car’s system state and VIN, so send the ZIP to support rather than posting it publicly.