For years the answer on every BMW forum was the same: "NBT EVO only does CarPlay. If you have an Android phone, buy an MMI box or replace the screen." That answer is now out of date.
OEMNAVIGATIONS has developed native wireless Android Auto for NBT EVO ID5 and ID6 head units in BMW, MINI and Rolls-Royce. It runs inside the factory iDrive system. There is no extra box behind the dash, no AUX audio, and no aftermarket screen. And unlike remote-only services, you install it yourself with an ENET cable and a laptop.
Why NBT EVO never had Android Auto
BMW launched NBT EVO (iDrive 5 and iDrive 6) around 2016–2017. BMW added Apple CarPlay to these units but never Android Auto. Native Android Auto only arrived with iDrive 7 (MGU) in 2019–2020 cars.
That left millions of F-series and early G-series BMWs, MINI F5x models and Rolls-Royce cars with a modern screen and no way to use Android Auto. Android owners had three options, and none were great.
The old options: MMI box, Android screen, or screen mirroring
| Option | How it works | Downsides |
|---|---|---|
| MMI / CarPlay box | Separate module spliced into the screen cable (LVDS) | Extra hardware, often AUX audio, separate menus, switching between systems |
| Aftermarket Android screen | Replaces the factory display | Loses the OEM look, quality varies, can affect resale value |
| Screen mirroring | Mirrors the phone over USB | Not Android Auto, unsafe to use while driving, limited apps |
| Native Android Auto (OEMNAVIGATIONS) | Software inside the factory head unit | No hardware, factory audio, iDrive controller and touch |
What "native" Android Auto on NBT EVO means
- Runs on the factory head unit. Android Auto appears as part of iDrive, not as an external video input.
- Wireless or wired. Your phone connects automatically over Wi-Fi, or you plug it in with a USB cable. The connection type is a setting in iDrive.
- Factory audio path. Sound goes through the car's own audio system, not an AUX input.
- Factory controls. Use the iDrive controller, the touchscreen (where fitted), and steering wheel buttons.
- Full-screen apps. Google Maps, Waze, Spotify, YouTube Music, WhatsApp, calls and Google Assistant.
- Keeps everything else. BMW navigation, radio, DAB, Bluetooth and settings work as before.
DIY installation: no booking, no remote technician
Some vendors only activate through a booked remote session, with a technician controlling your laptop. We built OEMNAVIGATIONS' DIY Android Auto activation for iDrive 6 to be simple:
- Buy the activation and enter your VIN.
- We check your VIN and email your activation code.
- Connect your laptop to the car with an ENET (OBD-to-Ethernet) cable.
- Run our DIY installer app, enter your code and follow the on-screen steps.
- Restart the head unit and pair your phone.
You choose when to do it — evening, weekend, in your own garage. No waiting for a free slot.
What you need:
- ENET cable (around £15–£25 online)
- Laptop running Windows (10 or 11) or macOS — the installer works on both
- A car with original BMW NBT EVO ID5 or ID6
- An Android phone — Android 11 or newer for the wireless connection
Which cars are compatible?
Compatibility depends on the head unit and its software version, not just the model or year. As a guide:
| Brand | Models (with NBT EVO ID5/ID6) |
|---|---|
| BMW 1–4 Series | F20/F21, F22/F23, F30/F31/F34, F32/F33/F36, F80/F82/F87 M |
| BMW 5–7 Series | G30/G31, G32 GT, F06/F12/F13, G11/G12 |
| BMW X models | F15/F16, F85/F86, F25/F26, G01/G02, F48/F39 |
| BMW i | i3, i8 |
| MINI | F54, F55, F56, F57, F60 (NBT EVO with 8.8" screen) |
| Rolls-Royce | Models fitted with NBT EVO ID5/ID6 |
Not sure which head unit your car has? Check your VIN with our free BMW VIN decoder — it reports the head unit fitted to your exact car.
NBT EVO ID4, older NBT and CIC units are different hardware and are not compatible. Third-party and aftermarket head units are not supported.
No WiFi antenna? It now works over USB too
Wireless Android Auto uses the head unit's WiFi antenna, and not every NBT EVO ID5/ID6 has one fitted. Until now that was the end of the road: the right head unit, but no way to connect, and fitting an antenna means taking the unit out of the dash.
Not any more. The activation now includes a connection type setting in the iDrive menu — wireless, or a USB cable. Plug the phone into the car's USB port and Android Auto starts on the same factory screen, with the same iDrive controller and steering wheel buttons. Everything else is unchanged: the firewall stays on, ConnectedDrive and live traffic keep working, and your settings stay where you put them.
So if your car has an original NBT EVO ID5 or ID6, it can run Android Auto — antenna or no antenna.
How this compares to other NBT EVO Android Auto solutions
Other teams have tried to make Android Auto work on NBT EVO, and forum threads show how hard it is. We tested several of those solutions from other developers and sellers. Below are the problems we found, next to what our version does and why it matters.
We built and tested ours across multiple head units and software versions before launch, with three goals: fast reconnection, no freezes, and no conflicts with CarPlay or BMW functions. Some of the others are developed continuously and keep patching their holes; ours is already here and does all of this today. We keep developing too, but we are adding features rather than closing gaps.
Security
| OEMNAVIGATIONS | Other versions |
|---|---|
| The car's firewall stays on, and its protection and routing table stay as BMW made them. Android Auto connects without opening anything up or touching the car's network rules. | Some simply switch the firewall off to get the phone connected. The head unit is then wide open on the car's network, and the built-in modem's internet stops. |
| ConnectedDrive, RTTI, weather and all online services keep working. Live traffic, weather, online search and the other BMW services run exactly as before, next to Android Auto. | With the firewall off, these services go dead: no live traffic information, no online services, and often nobody tells you why. |
| No system files touched. Nothing in the iDrive system is modified or written, so an install or an update cannot damage it. No boot loops, no head unit stuck on the boot screen. | Some remount the system partition and change system files. A power cut or one wrong file during that can leave the head unit unable to boot. If you are lucky, a reflash brings it back. |
Music and alerts
| OEMNAVIGATIONS | Other versions |
|---|---|
| Waze directions and speed camera alerts over FM radio or any other source. You hear every turn instruction and every speed camera warning, whatever you are listening to. The radio is lowered for the announcement and comes back after it. | Announcements usually go only through the phone's Bluetooth audio. With the radio on you hear nothing: missed turns and missed speed camera warnings. |
| No blasting music after a phone call. Music that was playing comes back; music you had paused stays silent, just like in a factory system. | After you hang up, the head unit can start the music by itself, even when it was paused, sometimes at full volume. |
| The same after navigation announcements and Google Assistant. After a voice prompt or a question to the Assistant, everything continues exactly as it was before. | Paused music can suddenly start after a prompt, or the radio gets switched away to Bluetooth. |
| Uncompressed 48 kHz / 16-bit audio over WiFi, with Bluetooth if you prefer it. Full-quality sound straight from the phone, and Bluetooth audio can be selected in the menu. | Bluetooth only: compressed sound, and every Bluetooth hiccup is heard in the music. |
Its own settings menu in iDrive
| OEMNAVIGATIONS | Other versions |
|---|---|
| Everything is set in the car, with the iDrive controller. Switch Android Auto on or off, choose a wireless or USB connection, pick WiFi or Bluetooth audio, set the music and announcement volume separately, and choose the start screen — Android Auto, iDrive, or the last one used. No laptop, no app, no files. | Settings need a laptop and command-line edits, or there are no settings at all. |
| Remove it with one press, and your settings are kept on update. If you ever need to, the whole system can be removed from the menu, and an update leaves your settings as you set them. | Removal means a workshop or a laptop session, and an update often resets everything. |
Installation and updates
| OEMNAVIGATIONS | Other versions |
|---|---|
| One click with a Windows or macOS app, verified steps, rollback. Anyone can install it in minutes. Every step is checked, and if anything goes wrong it goes back to the previous state. Updates run any time with the same app. | Manual installation over a command line, with root passwords and system changes. One typo can break the head unit, and every update means doing it all again. |
Everyday use
| OEMNAVIGATIONS | Other versions |
|---|---|
| Starts with the car. Get in, the phone connects, Android Auto is there. | It has to be started by hand, every time. |
| The reverse camera always comes to the front. When you reverse, the camera view is on screen and the controller works it, as it should. | If Android Auto keeps the screen or the controller while reversing, the camera view is hidden or the controller acts on the phone instead. |
| The steering-wheel voice button starts Google Assistant. Hands on the wheel: call, navigate or play music by voice. | Often missing, so you have to reach for the phone or the screen. |
| MyBMW and the AAIdrive apps work alongside it. Android Auto and the BMW apps share the car's Bluetooth connection without getting in each other's way. | Android Auto and the BMW apps fight for the same Bluetooth link: MyBMW drops, or Android Auto does not connect at all. |
| Apple CarPlay stays untouched. If the car has CarPlay, iPhone users keep it exactly as before. | Some reuse CarPlay's video system. After Android Auto has run, CarPlay can stay black until the head unit is restarted. |
Support
| OEMNAVIGATIONS | Other versions |
|---|---|
| Continuous development, every version tested, help when you need it. New versions come regularly, and each one is tested on real head units before release. If something is not right, we help. | One-off releases, builds released without testing on real head units, and no one to ask when something goes wrong. |
Available now
Native wireless Android Auto for NBT EVO ID5/ID6 is on sale. Enter your VIN on the NBT EVO ID5/ID6 Android Auto activation page and the compatibility check tells you straight away whether your car has the right head unit.
FAQ
Does NBT EVO support Android Auto from the factory?
No. BMW only offered Apple CarPlay on NBT EVO ID5/ID6. Factory Android Auto started with iDrive 7.
Is this wireless or wired?
Both. Your phone connects automatically over Wi-Fi, or you can use a USB cable — the connection type is a setting in iDrive. That means a car without a WiFi antenna can run it too.
Do I need an MMI box or extra hardware?
No. It runs natively inside the factory head unit. You only need an ENET cable and a laptop to install it.
Will Apple CarPlay still work?
Yes. Apple CarPlay and Android Auto can both be used on the same car.
Can I install it myself?
Yes. The installer guides you step by step. No coding experience is needed.
Does it work on MINI and Rolls-Royce?
Yes, on MINI and Rolls-Royce models with NBT EVO ID5/ID6. Check your VIN to confirm.
What if my car has NBT EVO ID4?
ID4 units are not compatible with this activation.
BMW, MINI and Rolls-Royce are registered trademarks of BMW AG. Android Auto is a trademark of Google LLC. OEMNAVIGATIONS is not affiliated with or endorsed by BMW AG or Google.