Skip to content
Miatafy
Search Miatafy

Find something for your Miata.

Good places to start

    Buy ScreenTune
    Menu

    How ScreenTune Fixes Mazda Connect Message Ordering

    ScreenTune corrects a message-ordering defect present throughout the Gen 6 Mazda Connect firmware line.

    Websocket message ordering (GUI framework)

    Section titled “Websocket message ordering (GUI framework)”

    Affected firmware: all Gen 6 MZD Connect versions, v55 through v74.

    Symptoms: stale screens, missed transitions, or the wrong view after rapid interaction such as switching audio sources or dismissing an alert.

    Root cause: the MMUI, Mazda Connect’s main UI controller, sends commands to the GUI over an internal websocket, each with a sequence number. The GUI framework’s Websockets.js holds a reorder queue meant to catch messages that arrive out of order and replay them in sequence. The queue doesn’t work:

    • _isStack and _delStack are written as standalone JavaScript functions but called as object methods via this._isStack(). They were never attached to the Websockets prototype, so every call throws a TypeError. Logs recorded it 225 times in one boot cycle.
    • With those two repaired, the queue still never matches a queued focus-stack or transition message, and its flush hands the JSON parser a value it can’t read.

    The messages it loses are the ones that change the screen. After the GUI restarts, for example when Mazda Connect restarts it after a stall, the MMUI’s sequence counter has already moved on, so focus-stack and transition messages go into the queue and are dropped. Focus moves but the matching screen never draws, or CarPlay or Android Auto stays behind. A car log from October 2026 shows CarPlay’s focus change lost this way.

    What ScreenTune changes: it replaces the block of Websockets.js that handles MMUI messages (its onmessage handler) with one that delivers every message in the order it arrives. The MMUI numbers and sends each message under one lock, so they already arrive in order and need no queue. The rest of the file, _isStack and _delStack included, stays as Mazda shipped it. The option is Fix message ordering, on by default (reliability fixes).

    A modified file stops the install. ScreenTune replaces the block only when it matches Mazda’s original exactly. If something else already changed Websockets.js, the install stops and rolls back every change instead of patching it (an action that failed).

    Before ScreenTune 1.3.1, the fix only turned _isStack and _delStack into prototype methods:

    function _isStack( → Websockets.prototype._isStack = function(
    function _delStack( → Websockets.prototype._delStack = function(

    That stopped the TypeError but left the queue dropping messages after a GUI restart.

    This patch fixes a software defect in the UI layer. It does not address hardware faults: a failing touch digitizer (ghost touch), a CMU that black-screens and reboots, or a dying 12V battery are separate problems with separate causes. If your screen issue is physical, the firmware fix won’t reach it.