BMW head units / reviewed 11 Nov 2026
AI Box on BMW iDrive: Wireless CarPlay Boxes Only
AI box on BMW iDrive 6, 7 or 8: wired boxes do not connect, TBox Ultra 3 pairing order, Mstick4 BMW mode, video sound lag, no touchscreen, OEM GPS.
Which boxes owners run on these cars, with current listings
What works
BMWs with iDrive 6 (NBT Evo), 7 and 8 take CarPlay wirelessly, and owners report that the wired connection most AI boxes rely on does nothing there: wired CarPlay does not work on a 2021 X5 (G05), a TBox Ambient was never seen by a 5 Series (G30) on iDrive 7, and a Carlinkit dealer told a TBox Plus owner that none of their wired boxes work on a BMW. Two more owners never got a box paired: one on an M2 Competition with iDrive 6, who had it refunded although the same box starts up in his other car, and one with an Ottocast Picasou 3 on a 2024 X4. The cable from the box still goes into a USB port, but only for power.
What does connect is a box that joins the car over wireless CarPlay and starts the connection itself. A reply from Carlinkit support, quoted by an owner, says these BMWs accept only devices that actively search for the car, and that the TBox Ultra 3 does this while the Ultra 2 and Ultra 4 do not. Owners use:
- Carlinkit TBox Ultra 3. Two owners report it working after an older BMW-specific box: much faster, navigation that keeps up with turns, track names on the head-up display. One of them notes the sound delay in video is small. One owner reports an Ultra 3 working over wireless Android Auto instead, on a 2026 540i (G60, iDrive 8.5): video streaming works, but maps do not reach the head-up display, he found no split-screen layout, and calls are unreliable. See the TBox Ultra hub.
- MGears Mstick4 in BMW mode, over wireless Android Auto (quirk below). See the Mstick4 hub.
- BMW-specific boxes such as the Ottocast i3 and MMB 2.0. One owner found his i3 connected only to his BMW’s NBT head unit and not to the other cars he tried, a Volvo among them; another got an i3 running on a non-BMW car with wireless CarPlay. A 2019 BMW i3 owner with the small screen reports the Ottocast i3 connecting over the car’s built-in wireless CarPlay. Three MMB owners report lag, glitches or freezes, and two of them returned the box. Details on the i3 are on the Picasou 3 hub.
Internet on the box. The box’s Wi-Fi is busy with the car. The Ultra 3 and the MMB carry two Wi-Fi modules, so owners run them on the car’s Wi-Fi and the phone’s hotspot at once; one Ultra 3 owner also keeps a second phone on the car’s Bluetooth at the same time. The Mstick4 has one module and needs a SIM (SIM card not working if it is not detected).
Known quirks
TBox Ultra 3 on iDrive 6: no confirmation code ever appears
What owners saw: the box does not show up as a CarPlay device; iDrive waits and no pairing code appears, while other boxes confirm by themselves within seconds.
What fixed it: starting the pairing from the Ultra 3’s own screen, in this order:
- Plug the box in with its bundled cable and wait for the clock on its screen.
- On iDrive, add a new device and choose CarPlay, nothing else.
- On the Ultra 3, swipe the clock up and tap the Bluetooth icon; check the switch is on.
- Swipe that screen to the left to start the device search.
- Tap the car’s name (BMW followed by five digits, the end of the VIN).
- Confirm the code on the box first, then on iDrive.
It worked for 3 of 5 owners who reported trying it, on an X6 (F16), an X3 (G01) and a 6 Series (F06), all with NBT Evo. After that the box connected by itself; one owner re-paired it after a firmware update with no trouble. It failed on an X4 (G02) and on a China-market BMW, where the code appeared on the car but never on the box. One Ultra 3 owner had connection trouble on the 28 Jun 2026 firmware, with the box not even trying to connect; the seller sent a 5 Jul 2026 build, and the owner had not reported back on it. An owner on iDrive 8.5 found the opposite on that 28 Jun 2026 build, which connects well for him; his trouble began with a later update (see “Still open” below).
With another box, one owner got past the same wait a different way: he held the voice-command button on the steering wheel while the car’s screen asked him to confirm the Bluetooth passkey, and the box connected. He was answering an iDrive 6 owner whose box never paired and did not name his own box or car; nobody else has reported trying it.
If the box pairs once but has to be paired again after every restart, see car doesn’t detect the AI box, where a BMW owner’s attempt is described.
MGears Mstick4: BMW mode and a SIM
What owners saw: the Mstick4 speaks only Android Auto, so it has nothing to connect to on a BMW that offers CarPlay alone.
What fixed it: BMW mode, under MGears settings → Device settings → Vehicle connection role, on a BMW with wireless Android Auto. Two owners report it working, on a China-market X1 (U12) and an X7 after its facelift; an owner quoting the MGears compatibility list names iDrive 8.5 or newer. It failed for 2 others: one G05 owner had constant drop-outs of the wireless link, and another found the stick did not work on his older BMW. In BMW mode the stick talks to the car over Wi-Fi, so it cannot take internet from your phone’s hotspot; owners fit a SIM.
Video: the sound runs behind the picture
What owners saw: over wireless CarPlay, video sound lags the picture, by a second or more in some apps.
What fixed it: a player with an audio-delay setting. A 5 Series (G30) owner set the audio delay in SmartTube, an alternative YouTube client, and wrote that it helped; he set it in VLC as well. Apps with no such setting stay out of sync. The box’s own sync setting helped 1 of 6 owners: on an MMB 2.0 the newer firmware’s audio/video and frame-rate adjustment made video “quite watchable” for one owner, but not for another MMB owner on an X7, and the three sync modes on an iHeylinkit-type box made no difference on a G05. Three more owners of BMW-specific boxes report the same of their sync modes; one of them, with an Ottocast i3, still measures the sound about 700 ms late. An i3 owner on a 4 Series (G22, iDrive 7) puts the delay at about one second and has not said what he tried. YouTube errors that are not about sync are in YouTube playback error.
No touchscreen: use the iDrive controller or a remote
What owners saw: many iDrive screens do not take touch, so the box’s Android screens cannot be tapped.
What fixed it: the iDrive controller and a Bluetooth remote. Three owners report working set-ups: turning the iDrive knob moves a selection frame over the box’s widgets and a long press edits them; a Bluetooth remote handles everything else for an owner without a touchscreen; and newer CarCar Launcher builds (4.0.1) on NBT Evo follow the controller, with a second press needed inside a window. The Ultra 3’s own touchscreen is another way in for owners whose car has none.
The controller alone does not suit every box. On a 2019 BMW i3 with the small screen, an Ottocast i3 owner found the dial works only partly and ordered a Bluetooth remote; he has not reported back on it. An MMB owner on iDrive 6 returned his box because the iDrive wheel kept moving the MMB’s own menu instead of scrolling the app in front. More ways to drive a box are in control an AI box without a touchscreen.
TBox Ultra 3: the picture looks grainy
What owners saw: an Ultra 3 owner on an M340i saw grain that the car’s own CarPlay does not show.
What fixed it: raising the picture-quality value near the top of the box’s display settings to 10. One owner reported it looked much better. App scaling, where apps lay out as if on a tablet, stayed unsolved.
Ottocast i3: music stutters
What owners saw: constant split-second freezes in music from every source on an i3, unchanged by phone Wi-Fi or three different cables.
What fixed it: a factory reset, reinstalling the apps and installing the March 2025 firmware update. One owner reported it running normally afterwards, after an hour and a half of driving. Back up your logins before you reset. If the i3’s settings lack the menu you are looking for, owners found it differs from the P3’s; see keyboard flickers or vanishes for the side-bar case.
OEM GPS freezes or is missing over wireless CarPlay
What owners saw: with the box set to use the car’s GPS, the position on an MMB 2.0 sometimes stayed put in a city centre while the car’s own navigation kept moving. On a BMW with an Ultra 3, OEM GPS gave no position at all over wireless CarPlay.
What fixed it: turning OEM GPS off and using the box’s own receiver. One owner explains the car’s navigation also uses wheel speed and steering angle from the car, which the box never gets, and found the box’s own GPS regains a fix faster after losing it. The setting and placement tips are in inaccurate GPS on the AI box.
Calls: a second phone on iDrive
Owners who want their phone on iDrive for calls while the box holds the CarPlay connection had the head unit coded to accept two devices. Coding changes the car’s configuration; leave it to a dealer or a coding specialist.
Two owners describe the problem from the other side. An Ottocast i3 owner found he could not use his phone hands-free while the box is connected. The owner of another BMW-specific box, whose phone Android Auto through the box crashed at every track change, connects his phone to iDrive as a secondary phone for calls only; he does not mention coding. The general set-up is in car Bluetooth calls with an AI box.
Still open on these cars
- iDrive 6 and the Ultra 3: navigation prompts crackle while the box’s music is paused. It is on crackling or muffled sound; no fix yet.
- iDrive 8.5 and the Ultra 3 on the 22 Jul 2026 firmware: one owner reports that the 28 Jun 2026 build connects to iDrive 8.5 without trouble, and that after the 22 Jul 2026 update the option to switch to wireless CarPlay is gone. Nobody has reported a fix. Dated builds are listed in the firmware tracker.
- Ottocast i3: slow or lost connection. On a 2023 5 Series Touring (G31, iDrive 7) one owner’s i3 often loses the connection at power-on and can take minutes to connect, though his apps run well. A 2021 M440i owner got it connected once and never again. An i4 owner says his early glitches went after he installed all updates over home Wi-Fi before moving to the phone’s hotspot; he did not say which updates. Another i3 owner’s Waze map is never centred, and Apple Music and Tidal never fill the screen.
- Phone Android Auto through a BMW-specific box: the G31 owner lost it on his i3, an MMB owner says it does not run on the MMB for iDrive 6, and a third owner’s box crashed at every track change.
- iDrive 9 (X3 G48): one owner’s wireless box showed a black screen instead of its interface, even after the seller’s firmware. Some wireless-CarPlay BMWs need a newer box firmware, according to a reply on TBox Ultra black screen after boot.
- TBox Ultra 4: an owner got no pairing with iDrive 6 in any mode, which matches Carlinkit’s reply above; another owner uses one in a BMW but reports inaccurate GPS and no sound, without a fix yet. The Ultra 4 is sold for these cars, but no owner has confirmed a working set-up, so plan on an Ultra 3.
Before you connect a box
- Check what your iDrive offers. If CarPlay appears only as a wireless connection, a wired box will not work; plan on an Ultra 3 or a BMW-specific box. For an Mstick4 you need wireless Android Auto. If the car has no CarPlay at all, one M3 (F80, iDrive 6) owner had a Wi-Fi antenna fitted and CarPlay activated by coding; a wireless AI box then connected and runs his phone’s Android Auto, with the car’s own functions intact. That changes the car’s configuration, so it is a job for a coding specialist.
- Have the box’s screen within reach the first time an Ultra 3 pairs, and use the bundled cable on a 2 A supply, as one owner recommends.
- Decide how the box gets internet. Two-Wi-Fi boxes take the phone’s hotspot; an Mstick4 in BMW mode needs a SIM.
- Plan for heat. Two owners saw BMW boxes overheat, one in an armrest in summer and an MMB at 85 °C (185 °F), and added cooling; see AI box overheating and shutting down.
- Plan the controls if your screen is not a touchscreen: a Bluetooth remote, or a launcher that follows the iDrive controller.
If something breaks
Write down the box model and firmware date (Settings → About), the car model and year, the iDrive version, whether the box is paired as a CarPlay or Android Auto device, and whether a phone connects wirelessly in the same mode. Note the car’s Bluetooth name the box shows, and whether a code appeared on the car, the box, or neither. A short video of the pairing helps.
Send that to the box maker’s support (Carlinkit: [email protected]; Ottocast: [email protected]); how to report a bug has a template. If iDrive refuses every wireless device, phones included, ask the dealer. If no box pairs with your iDrive, the car’s own wireless CarPlay or Android Auto with your phone may be the honest answer; start here covers whether a car supports a box at all.
Boxes owners run on these cars
Among Carlinkit boxes, owners and a Carlinkit support reply name the TBox Ultra 3 as the one that connects to these BMWs over wireless CarPlay; the Ultra 2 and Ultra 4 do not. The pairing order and the quirks above still apply.
Carlinkit TBox Ultra 3 (Android 15, QCM6350, 1.8-inch screen on the case)
Check that the title says Ultra3, the model with the small screen on its case, then pick the EAU or JP option for your region. Seller: Loadkey Carplay 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.