Volkswagen, Škoda and Audi head units / reviewed 11 Nov 2026
AI Box on VW, Škoda and Audi MIB: CarPlay vs Android Auto
AI box on a VW, Škoda or Audi MIB 2.5 or MIB3: calls need Android Auto, AA is slow on some MIB 2.5 units, Audi runs CarPlay only, OEM GPS, multitouch.
Which boxes owners run on these cars, with current listings
What works
The Volkswagen, Škoda and Audi head units owners report on are MIB 2.5 units (Composition Media, Discover Pro, Bolero, Columbus, MIB2 Entry) and MIB3 units, in the Tiguan, Polo, Passat, Teramont, Touareg, Octavia, Karoq, Kodiaq, Rapid, Audi A4, Q7 and others. They take an AI box over a USB cable in wired CarPlay and, on most units, wired Android Auto. Many MIB3 units also connect phones wirelessly; the box still uses the cable.
Two single owner reports come from cars outside that list. A 2023 VW ID.4 S owner runs a Carlinkit TBox Plus (Android 13, 6225 chip) as his everyday interface and calls it fluid; he fitted the box’s extra-power cable from the start because the ID.4’s USB-C ports supply little power, and had not tried the plain cable. A 2020 VW Polo owner says his TBox Ultra works very well.
On these cars the protocol decides more than the connection. Owners describe the trade-off this way:
- Android Auto mode lets many MIB units keep your phone on the car’s own Bluetooth for calls, with the wheel buttons and the instrument cluster showing the call. It is also the only mode with two-finger multitouch.
- CarPlay mode gives the box the car’s GPS position (OEM GPS), connects much faster on some MIB 2.5 units, and on a Škoda Karoq it was the only mode in which the instrument cluster showed music track titles. A Discover Pro owner adds that the box runs cooler with OEM GPS, and he heard no sound difference between the two modes.
- Ignition. One Škoda owner notes that on these cars CarPlay connects with the ignition off, but Android Auto only once the ignition is on.
Carlinkit TBox models change protocol with a 2–3 second press of the recessed mode button next to the LED: green for CarPlay, blue for Android Auto. Switch the CarPlay / Android Auto protocol has the steps and the fallbacks. Which mode to pick depends on your head unit, as the quirks below show.
Known quirks
Calls: the head unit drops your phone while the box is in CarPlay
What owners saw: with the box connected in CarPlay mode, the MIB unit closes the phone’s own Bluetooth connection, so calls can only go through the box. A VW owner who had moved his phone from the car to the box hit exactly that.
What fixed it: switching the box to Android Auto. A Škoda Rapid owner with a MIB2 Entry unit reports that in Android Auto mode the head unit keeps the phone’s Bluetooth and handles calls itself, while a CarPlay device breaks the phone connection. One VW MIB2 owner could not get his phone onto the head unit even in Android Auto, so it worked for 1 of 2 owners here. The VW owner who fixed it by switching protocol, a Tiguan MIB 2.5 owner whose phone stayed on the car in Android Auto, and the failures on a 2019 Teramont and an Audi Q7 are counted in keep your phone on the car’s Bluetooth while the box runs, which has the full set-up.
Some units allow both at once. A Kodiaq MIB3 owner keeps the phone on the head unit even with the box in CarPlay, and a VW Tayron owner reports the same after the head unit’s coding was changed to allow a second phone. Coding changes the car’s configuration, so leave it to a dealer or a coding specialist. If your calls through the box have no microphone, see microphone not working on calls.
On MIB2 and MIB 2.5 units that drop the phone even in Android Auto, two MIB 2.5 owners (a Columbus and a 2018 Kodiaq with a Bolero) kept it by pairing in a set order and then force-restarting the head unit; the order is in Step 2 of the same guide.
The switch to Android Auto also fixed a voice problem. A Škoda Octavia A8 owner’s voice assistant on the box could not hear him while his phone was on the head unit; after he changed the box to Android Auto, everything worked. The owner who asked about the same fault had not reported back.
MIB 2.5 Composition Media and Bolero: Android Auto connects slowly, so owners stay in CarPlay
What owners saw: on a Tiguan with a MIB 2.5 Composition Media unit, a TBox Ambient (6225 chip) took many times longer to connect in Android Auto than in CarPlay; the October 2024 firmware did not change it. Once connected, both modes ran equally well. A Kodiaq owner with MIB 2.5 saw the same delay after trying three head-unit firmware versions, although phones connect quickly in Android Auto. The Tiguan owner suspects the head unit first tries to read the box as a USB drive before it starts Android Auto.
What fixed it: going back to CarPlay. Two owners did: the Tiguan owner stayed on CarPlay although he had bought the box for Android Auto, and the Kodiaq owner, whose TBoxes also ran badly in Android Auto on a Bolero unit, switched them back.
The delay is not universal: a Discover Pro (Harman) MIB 2.5 owner sees none with the same TBox Ambient. An owner of a China-built Kodiaq reports that only CarPlay works there. Staying in CarPlay means giving up the phone on the car’s Bluetooth from the quirk above.
Audi A4 B9, Q7 and e-tron: the box will not connect in Android Auto
What owners saw: on an Audi A4 B9 with MIB3, a TBox Ambient in Android Auto mode rebooted in a loop. A Y-cable with extra power from the 12 V socket stopped the reboots, but the head unit still showed a connection error, although Android Auto is enabled in the car and works with a phone. A Q7 owner reported the same, with the box running very hot.
What fixed it: nothing in Android Auto mode; the A4 owner runs the box in CarPlay, where it works. A TBox Plus on a Q7 with MIB3 and a TBox Ultra 2 on an e-tron would not connect in Android Auto either (counted in car Bluetooth calls and steering-wheel call buttons not working), so plan on CarPlay for an Audi. On the A4’s virtual cockpit, the caller’s photo and album art appear only with a phone connected directly, not through the box.
Multitouch: Android Auto only, and not on every MIB3
What owners saw: pinch-zoom in a navigation app needs the box in Android Auto mode, and MIB3 cars differ in whether it works without changes.
What fixed it: on a 2022 VW Polo with MIB3, switching to Android Auto was enough: one owner has two-finger zoom in navigation with an Ottocast Picasou 3 and a TBox UHD (6225 chip), without root. On a 2022 Karoq with MIB3 and a TBox Ambient 6225 it did not work out of the box. On a 2021 Kodiaq with MIB3, one owner needed the multitouch patch Brick risk on his TBox Ambient and TBox UHD (6225 chip), and with it multitouch works. Enable multitouch on a TBox has the methods, including routes without root, and their undo steps.
The Karoq owner noticed a cost of Android Auto mode: the instrument cluster stopped showing the track titles from his music app, which it had shown in CarPlay.
OEM GPS works even without factory navigation
What owners saw: a Tiguan with a MIB 2.5 Composition Media unit has no navigation and no NAV key, so its owner did not expect the car to share a GPS position. With OEM GPS on, a GPS test app on the box shows no satellites at all.
What fixed it: turning on OEM GPS in the box anyway and judging it by the navigation app, not the test app. Three owners report it working: the first Tiguan owner, a second Tiguan owner whose navigation runs normally while the test app sees no satellites, and a Škoda Octavia owner. Owners explain that cars without navigation still carry a GPS module, used to set the clock, and that the head unit passes on a processed position, which is why test apps see no satellites. On these boxes OEM GPS works in CarPlay mode. Where the switch is and how to undo it is in inaccurate GPS on the AI box.
Working is not always better. A Škoda Karoq owner with MIB3 and a TBox Ambient (6225 chip) tested OEM GPS in town and on the motorway: the speed readout lagged and the car sometimes jumped to a neighbouring road, and with OEM GPS off both improved. A MIB 2.5 owner tried the car’s GPS twice, saw the navigation move in jerks both times, and stayed on the box’s own receiver. Compare the two on a route you know before you settle on one.
China-built Teramont Pro: turn OEM GPS off
What owners saw: a TBox Ultra in CarPlay mode on a VW Teramont Pro, with OEM GPS on, made the navigation hang and then catch up, or show the car moving while it stood still.
What fixed it: turning OEM GPS off, so the box uses its own receiver. One owner reported it seemed fine afterwards, though he also blamed signal jamming on his route and maps that had not been downloaded. Another owner warned that VW group cars built for China are the exception to OEM GPS working.
The box’s firmware plays a part as well. An owner of a China-built car on the MQB-Evo platform with MIB3 and a TBox Ultra got no position from OEM GPS on the August 2025 build his box arrived with; it worked after he updated to the October 2025 build, and stopped again on an unofficial build he tried afterwards.
MGears Mstick4: you have to tap Android Auto at every start
What owners saw: an MGears Mstick4 in a VW group car does not start Android Auto by itself; the owner has to tap the tile after each start, or the stick shows its desktop for half a second and drops.
What fixed it: deleting the phone from the stick’s list of paired Bluetooth devices. One MIB3 owner reported the stick then connected without a tap three times in a row and has had no start-up problem since; the owner who asked had already tried it without success, so it worked for 1 of 2. The same MIB3 owner finds a good third-party cable even a little more stable than the bundled one. Owners report MIB 2.5 support arrived in Mstick4 firmware 1.8.3 (Mstick4 page), and a Tiguan owner’s “connection interrupted” morning is in Mstick4 connection interrupted.
Škoda Karoq (Columbus): the box reboots when the mobile signal changes
What owners saw: a Karoq owner’s TBox Ambient in CarPlay mode rebooted now and then, mostly on country drives. Network-mode settings, LTE only included, made no difference.
What fixed it: running the box without its mobile data, either on Wi-Fi shared from the phone or with mobile data turned off; one owner found it stable that way. He later stopped the reboots with a second power feed, a report counted in AI box keeps rebooting, but on the third day the extra-power cable burned out his car’s USB hub. A Kodiaq owner ran the same box on a single cable in the Android Auto socket with no trouble.
Crackling sound after the switch to Android Auto
What owners saw: in a discussion among MIB3 owners, one found that after moving the box from CarPlay to Android Auto music crackled and rattled; in CarPlay it was clean.
What fixed it: a factory reset of the box after the switch, for 1 of 2 owners: one said the full reset fixed his rattling sound, the other had reset several times with no change. Back up your logins first; the background is in noise after switching to Android Auto.
On a Škoda Karoq with a Swing unit it ran the other way. That owner’s TBox Ambient (6225 chip) in CarPlay started to crackle in his music player after about ten minutes, on top of GPS dropouts and jumps that had begun on his older TBox, and an update changed nothing. Switching the box from CarPlay to Android Auto ended the crackle and made GPS almost perfect. So neither mode is the clean one on every unit: MIB3 owners heard the crackle in Android Auto, the Swing owner in CarPlay, and trying the other protocol costs less than a reset.
Box will not start or restarts in a loop: force-restart the head unit
What owners saw: now and then the fault sits in the head unit, not the box. A MIB2 owner’s box failed to come up, twice. A TBox Plus owner on MIB 2.5 had occasional stuttering, distorted sound, mostly with the box hot. A Columbus MIB3 owner with an MGears Mstick4 hit a glitch two or three times in six months, and on a couple of occasions the stick restarted in a loop right after he plugged it in.
What fixed it: a forced restart of the head unit: press and hold its power button until the unit restarts, 10–15 seconds on the Columbus MIB3; the MIB2 owner lets go when the speakers click. All three owners reported that it cleared the fault, and the TBox Plus owner said a MIB 2.5 restart was often the only thing that helped. It changes no settings. If the box restarts while you drive, see AI box keeps rebooting.
MIB 2.5: taps land off-target on a TBox Plus with Android 12
What owners saw: on a Carlinkit TBox Plus 8/128 running Android 12, touches on a MIB 2.5 screen landed offset from where the owner tapped; he lived with it for a year.
What fixed it: the box’s Android 13 firmware, installed with the box’s standard updater. One owner confirmed the offset was gone; the first attempt showed “Update failed” before the update went through. He found sound unchanged, with the 44.1 kHz audio setting kept, and start-up a few seconds faster. Check Settings → About for your version, and see update TBox firmware with FOTA and touchscreen not responding for the rest.
Still open on these cars
- Audi A5L: a TBox Ambient (6225 chip) that works in another car is not accepted, although the head unit has wired CarPlay; the owner says a TBox Plus did connect in the same model.
Before you connect a box
- Know your head unit. Note whether it is MIB 2.5 or MIB3 and its name (Composition Media, Discover Pro, Bolero, Columbus). The Android Auto delay was reported on Composition Media and Bolero, not on Discover Pro.
- Decide how you will take calls. If you want the phone on the car’s Bluetooth, the box has to run in Android Auto on most units, unless a dealer or coding specialist enables a second phone.
- On an Audi, plan on CarPlay. Owners of an A4, two Q7s and an e-tron never got Android Auto mode to connect.
- Turn the ignition on before you judge Android Auto mode; one owner found it connects only with the ignition on.
- Be careful with extra power. On these cars the box usually runs on one cable; one Karoq owner’s extra-power cable destroyed the car’s USB hub.
- Know your box. Which TBox do I have shows how to read the model and chip in Settings → About.
If something breaks
Write down the box model and firmware date (Settings → About), the car model and year, the MIB generation and head-unit name, the protocol the box is in, and whether a phone on a cable works in the same mode. Note whether the ignition was on. A short video of the screen helps.
Send that to the box maker’s support (Carlinkit: [email protected]); how to report a bug has a template. If something on the head unit stopped working after a coding change, ask whoever coded it to set it back first. If the head unit refuses the box in both protocols, the car’s own phone projection may be the honest answer; start here covers whether a car supports a box at all and how the box families compare.
Boxes owners run on these cars
The boxes that come up in the owner reports behind this page, most often first. More reports means more owners run that box in these cars, not that it works better or worse: the quirks above apply to all of them. To choose between them, see which AI box to buy.
Carlinkit TBox Ambient
Comes up in 7 confirmed problems owners reported on these cars.
Listing: Carlinkit TBox Ambient / TBox Plus (Android 13). The listing sells both boxes: pick a Tbox-Ambient option, EAU, NA or JP for your region. Seller: Carlinkit Official Store.
Carlinkit TBox Plus
Comes up in 3 confirmed problems owners reported on these cars.
Listing: Carlinkit TBox Plus / TBox Ambient (Android 13). The listing sells both boxes: pick a Tbox-Plus option, EAU, NA or JP for your region. Seller: Carlinkit Official Store.
Carlinkit TBox UHD
Comes up in 3 confirmed problems owners reported on these cars.
Listing: Carlinkit TBox UHD (HDMI, Android 13). Pick SM6225 or SDM660 (the SDM660 has the extra USB port), EAU or NA for your region. Seller: Carlinkit Official Store.
Carlinkit TBox Ultra (1–4)
Comes up in 1 confirmed problem owners reported on these cars.
Listing: Carlinkit TBox Ultra (Android 15, QCM6350). Pick the EAU or NA colour option for your region. Seller: Loadkey Carplay Store.
Ottocast Picasou 3 family
Comes up in 1 confirmed problem owners reported on these cars.
Listing: Ottocast P3 Pro (Picasou 3 Pro, Android 13). The listing opens on a cheaper Mini adapter option: pick P3 Pro, then North American or Eurasian. Seller: OttoPlay Store.
Affiliate links: we may earn a commission at no extra cost to you. We have not tested these boxes; check that the listing names the exact model and the variant for your region before you buy. Disclosure.