CarPlay and Android Auto on Mazda Connect
Apple CarPlay and Android Auto arrived on MZD Connect as a dealer-installed retrofit in 2018, not a factory feature. A Gen 6 Mazda Connect car can run it once the CMU is on firmware 70.00.021A or later and the right USB hub and cables are in place. Factory fitment varies by model year, trim, market, and whether a prior owner already did the retrofit, so do not assume every 2019+ car ships with the same CarPlay hardware.
For every path side by side (OEM kit, dongle, aftermarket head unit), see CarPlay and Android Auto options. If it pairs but the projection screen never loads, go to CarPlay won’t connect.
Requirements
Section titled “Requirements”- Firmware:
70.00.021Aminimum; later region-correct firmware is recommended - Hardware: a USB hub kit, OEM (TK78-66-9U0C) or an aftermarket equivalent
- Order: update firmware first, install the hub second
The firmware must go on before the new hub. Once the hub is connected, the normal update path may refuse to run. Remove the navigation SD card before updating and reinsert it after. Full steps are in Update procedure.
Official retrofit kit
Section titled “Official retrofit kit”Part numbers:
- USB hub: TK78-66-9U0C
- USB data cables: C922-V6-605A
- Accessory kit: 00008FZ34
| Route | Cost |
|---|---|
| Dealer-installed (parts + labor) | $350–550 |
| DIY (parts only) | $150–200 |
| Aftermarket clone (Amazon/AliExpress) | $30–100 |
The OEM kit is wired-only. Its USB port delivers 2.1A charging, up from 0.5A on the pre-retrofit hub.
Installation
Section titled “Installation”- Update CMU firmware to v70+
- Remove the center console trim panels (Phillips screws plus plastic clips)
- Disconnect the old USB hub
- Run the new USB cables from the hub location to the CMU
- Connect the new hub (CarPlay uses the USB1 port)
- Reassemble the trim
Plan on 1–3 hours depending on how comfortable you are with interior trim.
Aftermarket hubs (P-series)
Section titled “Aftermarket hubs (P-series)”Third-party hubs in the OEM form factor:
| Version | Wireless | Notes | Price |
|---|---|---|---|
| P1 | No | Basic OEM clone | $30–60 |
| P2 | No | Better build quality | $40–80 |
| P2 PRO | No | Adds USB-C PD fast charging | $50–100 |
| P3 | CarPlay only | Built-in WiFi for wireless CP | $60–120 |
| P3B | Both | Wireless CP + AA, wired fallback | $80–150 |
| P3 PRO | Both | Best reported compatibility | $100–150 |
P3B and P3 PRO are the commonly recommended wireless boxes, but documentation and firmware quality vary by seller. Confirm the exact model, its wired-fallback behavior, and the return policy before buying. Moving from P2 to P3 usually means swapping only the hub box; the cables stay.
Wireless CarPlay
Section titled “Wireless CarPlay”There is no firmware mod or tweak that turns a wired hub into a wireless one. Wireless needs a WiFi radio in the hub. Three ways to get it:
- External dongle (Carlinkit, Ottocast, or another dual-mode adapter): $50–100, plugs into the existing USB port, adds latency
- P3-series hub: $60–150, same form factor, radio built in
- OEM wireless CMU swap: part TC3N-66-9C0, not well documented for retrofits
Check the adapter category before you buy. The Motorola MA1, Carsifi, and older AAWireless units are Android Auto adapters, not Apple CarPlay. Newer dual-mode products can behave differently from older ones with near-identical names.
Wireless trades wire-free convenience for some friction. Owner reports cluster around:
- 1–2 second input lag
- 20–35 second connection time
- A coin-flip on connecting to the wrong phone when more than one is in the car
- Higher phone battery drain than wired
To trim the startup delay and clean up the Bluetooth/WiFi handoff, see Make wireless CarPlay connect faster.
Hardware limitations and separate options
Section titled “Hardware limitations and separate options”Stock Android Auto disables the touchscreen. This is Mazda’s Android Auto behavior, separate from the speed lock the native UI uses. AA Touch is the ScreenTune option that supplies the missing input path and works while parked or moving. Apple CarPlay accepts touch on stock software while parked.
Display resolution is fixed. The 7-inch panel is 800×480. CarPlay and Android Auto stream H.264 at 800×480 @ 160 DPI. No mod raises it; it’s the display hardware.
No HUD integration. CarPlay and Android Auto turn-by-turn does not appear on the Active Driving Display. Only Mazda’s native navigation reaches the HUD, and there is no workaround.
Knob navigation is clumsy. Both projection systems were built for touch. The commander knob is workable but awkward, especially for map zoom and text entry.
Tweaks that improve the experience
Section titled “Tweaks that improve the experience”A few CMU-side changes make CarPlay quicker to reach and easier to use:
| Tweak | Effect |
|---|---|
| Touch while driving | Keeps CarPlay touch live at all speeds (CarPlay only; does not affect Android Auto) |
| AA Touch | Adds tap, swipe, drag, and on-screen keyboard input to Android Auto while parked or moving; commander controls remain available |
| No disclaimer screen | Removes the startup splash, so you reach CarPlay sooner |
| Optional wireless CarPlay startup | Gets the head-unit side ready sooner when the ScreenTune intake says the car uses wireless CarPlay |
| Earlier Wi-Fi initialization | Brings the unit’s wireless network and CarPlay startup up instead of leaving it in the busy first-core queue |
Wireless CarPlay connected ~16–20 seconds sooner in the test configuration
Section titled “Wireless CarPlay connected ~16–20 seconds sooner in the test configuration”When the order intake says the car uses wireless CarPlay, ScreenTune includes its wireless network and CarPlay startup changes. On the test CMU, a typical stock boot reached wireless CarPlay around 71 seconds and the ScreenTune configuration reached it around 55 seconds. The improvement was about 16 seconds typically and up to about 20 seconds on a good boot. The unit also became touch-ready about 16 seconds sooner, from roughly 48 seconds to 32 seconds.
The main reason is the CMU’s two-core startup behavior. Stock software places almost all startup work on the first core while the second retains capacity. The wireless CarPlay configuration moves Wi-Fi and CarPlay startup onto the less-busy core.
A few things to keep in mind:
- This does not add wireless CarPlay, convert a wired hub to wireless, or change Apple’s CarPlay protocol. It only makes the head-unit side ready sooner.
- The last stretch before CarPlay actually connects is partly your phone’s own Wi-Fi and CarPlay handshake, which the car doesn’t control, so that part of the wait can still vary boot to boot.
- These are config and boot-order changes, not new hardware. They shorten the wait and unlock touch, but they can’t add a radio or raise the resolution.
ScreenTune includes the notice and touch changes. The wireless CarPlay startup path is included only when selected in the intake. Features and options lists the current product configuration.
Bugs worth knowing
Section titled “Bugs worth knowing”Drops and reconnects. Usually the cable. Use a short, high-quality USB cable, turn off “Enhanced Integration” in the iPhone’s CarPlay settings, clean the USB port contacts, and re-pair (forget, then re-add).
Audio from one speaker. Sound only from the driver-side speaker during CarPlay. Fixed in the v74 firmware series.
Siri must be on. CarPlay won’t connect if Siri is disabled on the iPhone.
Phone set to “Never Enabled.” Mazda Connect can block CarPlay per phone. With a phone set to Never Enabled, Bluetooth still pairs and the phone still charges, but CarPlay never activates. Re-enable it in Mazda Connect’s Apple CarPlay device settings, or run the clean re-pair flow in CarPlay won’t connect.
Ghost touch. Mostly 2014–2016 Mazda3 and some CX-5 units. ITO-film corrosion from moisture causes phantom presses. The usual repair is a digitizer replacement, around $50–100 in parts. The Duffy v. Mazda settlement received final approval on February 26, 2026 and covers specified infotainment defects for listed U.S. vehicles.
v74 note
Section titled “v74 note”Do not run legacy AIO tweaks on a v74 unit with wireless CarPlay; AIO replaces system files with pre-v74 copies, and owners on 74.00.324 and 74.00.331 report lost wireless CarPlay afterward. If you’re on v331, confirm your exact build and recovery path before applying anything v74-specific. See Version history and AIO on v74.
References
Section titled “References”| Resource | Link |
|---|---|
| Mazda CarPlay support | connect.mazda.com |
| Mazda Android Auto support | connect.mazda.com |
| NHTSA CarPlay retrofit bulletin | MC-10144323-9999 |
| Mazda3Revolution retrofit comparison | mazda3revolution.com |
| Mazda retrofit announcement | Mazda USA News |
| Class action settlement | mazdainfotainmentsettlement.com |