Android Auto on BMW NBT EVO (iDrive 5 and 6): Options, Compatibility and Native Activation
If you drive a BMW from roughly 2016–2019 with the NBT EVO head unit and an Android phone, you have probably noticed the gap. iPhone owners could get Apple CarPlay on these cars, but BMW never offered Android Auto for NBT EVO. Wireless Android Auto only arrived in 2020, and only for newer cars with iDrive 7. This guide explains what is possible on an NBT EVO car today, how the main routes compare and what decides whether native activation will work on your software.
The key point first: on compatible software builds, Android Auto can be activated as a software change on the original head unit – wireless, full-screen on the factory iDrive display, with no MMI box and no replacement screen. Compatibility is decided by the head-unit software build, not by the model year, so it has to be checked by VIN before anything is bought. Our remote service is BMW NBT EVO Native Android Auto.
An honest note: this is an unofficial modification. BMW did not offer Android Auto for NBT EVO, and the feature is independent of BMW AG and Google LLC. The sections below explain what that means for software updates, warranty and everyday use.
The short answer
- Does BMW offer Android Auto on NBT EVO? No. Native activation by software is possible on compatible software builds.
- Wired or wireless? Wireless. The phone pairs over Bluetooth and projects over Wi-Fi, so there is no cable to plug in.
- Extra hardware? None. It runs on the original head unit and appears on the original iDrive display.
- Which head units? NBT EVO with iDrive 5 or 6. iDrive 4 units need the ID4 → ID6 upgrade first; older NBT and CIC systems are not supported.
- What decides compatibility? The exact head-unit software build – checked from your VIN and a photo of the software information page.
- How is it done? A remote session with an ENET cable, a Windows laptop and a remote-access tool, usually 30 to 60 minutes.
- What does it cost? €120 (regular price €200) for the service, including the compatibility check and help with the first pairing. An ENET cable costs around €20 if you do not have one.
Why NBT EVO cars never got Android Auto
BMW’s smartphone integration arrived in two steps. Apple CarPlay came first and is closely linked to the NBT EVO generation, which is why that head unit is often called “the CarPlay generation”. Android Auto came much later: BMW announced it in late 2019 and began rolling it out in 2020 as an over-the-air update for cars with iDrive 7 (BMW Operating System 7), wireless only. NBT EVO cars were not part of that rollout.
BMW has not published its reasons, but the practical result is easy to see. Android owners with a 2016–2019 BMW were left with Bluetooth audio and a phone holder, an add-on interface box or an aftermarket head unit – none of which gives the factory look and feel. That gap is exactly what a native software activation is meant to close.
Your options on an NBT EVO car
| Option | Extra hardware | What you get on the screen | Worth knowing |
|---|---|---|---|
| Native software activation (this guide) | None | Android Auto full-screen on the original iDrive display | Depends on the software build, so it is checked first. A later software update can overwrite it |
| MMI / Android interface box | A box wired into the car | The box’s own interface shown through the original screen | Something to fit, power and keep working; menus differ from the factory ones |
| Aftermarket Android head unit | Replaces the factory unit | An aftermarket screen | Loses factory integration and often the original look |
| Community “Connected Apps” workaround | A phone app plus BMW’s own Connected Apps feature | App-style screens inside the iDrive menu – not full Android Auto | Needs the BMW Apps option and an active subscription; only some features |
| Bluetooth audio and a phone mount | A holder and a charging cable | The phone’s own screen | Simple, but nothing is integrated and the phone needs attention while driving |
None of these is best for everybody. Native activation is the only route that adds nothing to the car, but it is also the only one whose availability depends on the head-unit software build. That is why a serious provider checks compatibility before taking payment instead of after.
Which BMWs have NBT EVO?
NBT EVO was fitted to many BMW and MINI models from about 2016 until the MGU generation took over. The table is a guide, not a guarantee – two cars of the same model and year can carry different head units.
| Model family | Chassis codes that commonly have NBT EVO | Notes |
|---|---|---|
| 1 and 2 Series | F20, F21, F22, F23 | Check the home screen and software information page |
| 3 and 4 Series | F30, F31, F34, F32, F33, F36 | Very common; many have iDrive 5 or 6 on later builds |
| 5 Series | Early G30, G31 | Early G-series cars still used NBT EVO before the MGU generation arrived |
| 6 and 7 Series | F06, F12, F13, G11, G12 | Early G11/G12 cars belong here as well |
| X models | F15, F16, F25, F26, early G01, G02 | Later G01/G02 cars have the MGU generation |
| i3 and i8 | I01, I12 | Confirm by VIN |
| MINI | F54, F55, F56, F60 | Only units with the larger NBT EVO screen |
If you are not sure which generation you have, read Which BMW iDrive do I have? CIC, NBT, NBT EVO and MGU explained first. A tile-based home screen on a car from this period usually points to NBT EVO.
iDrive 5, iDrive 6 and the software build
iDrive 5 and iDrive 6 are two interface generations of the same NBT EVO family. For Android Auto, the label matters less than the exact software build installed in the head unit. The build is a long string that starts with “NBTevo” and sits on the system or software information page in the iDrive settings. Two cars with the same label can carry builds that behave differently, and an older build may not accept the activation at all.
That is why a model badge or production year is never enough. A proper compatibility check reads the build, compares it with the builds known to work and gives a clear yes or no.
How to check your head unit and software version
- Look at the iDrive home screen. A grid of large tiles on a car from this period points to NBT EVO.
- Open the iDrive settings and find the system or software information page. The wording differs a little between builds.
- Photograph that page so the whole “NBTevo” software string is readable.
- Send the photo together with your VIN. You get a clear answer on the head unit, the software build and the route before you book.
There are three possible outcomes. If your build is compatible, the activation can go ahead. If you have iDrive 4, the head unit first needs the NBT EVO iDrive 4 – iDrive 6 upgrade. If the system is an older NBT or CIC, or the build cannot take the feature, you are told before any work starts.
What you get on the iDrive screen
| Feature | What it means in the car |
|---|---|
| Wireless connection | The phone connects over the car’s Bluetooth and Wi-Fi when you get in |
| Full-screen picture | Android Auto uses the wide NBT EVO display instead of a small window |
| Controls | The iDrive controller, the touchscreen where fitted and the BACK button |
| Navigation | Google Maps, Waze and other Android Auto navigation apps on the factory display |
| Music and media | Spotify, YouTube Music and other media apps through the factory speakers |
| Calls and messages | Hands-free calls and spoken messages through the car’s audio system and Google Assistant |
How the car’s own voice control and Android Auto hand over to each other can differ slightly between software builds. Extras such as navigation prompts in the instrument cluster or head-up display also depend on the build and on the equipment of the car, so ask about them before you book instead of assuming.
What you need before the session
- ENET cable (OBD2 → Ethernet), usually around €20.
- Windows laptop with a stable internet connection.
- Remote tool: TeamViewer, UltraViewer or AnyDesk.
- An Android phone with wireless Android Auto support. Google’s published requirement for wireless Android Auto has been Android 11 on a phone that supports 5 GHz Wi-Fi. Some older phones also work, and local rules can differ, so check Google’s current Android Auto help page for your phone and country.
- Car parked with the ignition on, and a battery charger connected if you have one. Coding should never run on a weak battery.
How the remote session works
- Pre-check: send your VIN and the photo of the software information page. The head unit, build and price are confirmed.
- Connection: connect the car to your laptop with the ENET cable and switch the ignition on.
- Remote access: start the remote tool and let the technician join your laptop.
- Activation: the technician reads the head unit’s current state, then activates Android Auto in the software.
- Pairing and test: the head unit restarts, your phone is paired and navigation, music and calls are tested together.
Plan on 30 to 60 minutes including the connection and the first pairing. If you live near Vilnius, ask about a workshop visit instead.
Android Auto or Apple CarPlay – which should you choose?
The phone in your pocket decides. Android Auto works only with Android phones, and Apple CarPlay works only with iPhones.
| Your situation | Best route | Why |
|---|---|---|
| You use an Android phone and your build is compatible | Native Android Auto | Wireless, full-screen, no extra hardware |
| You use an iPhone | BMW Apple CarPlay activation | CarPlay is the matching system for iPhone; see our Apple CarPlay activation guide |
| Household with both an iPhone and an Android phone | Often both | Tell us before the session if CarPlay is already active so we can check that both work on your build |
| You have iDrive 4 | Upgrade first | The ID4 → ID6 upgrade makes the unit eligible for the NBT EVO features |
If the phone does not connect after activation
Most connection problems come from the phone side rather than the car. Work through these in order:
- Make sure Bluetooth and Wi-Fi are switched on and that the phone supports 5 GHz Wi-Fi.
- Remove the car from the phone’s Bluetooth list and from Android Auto’s list of connected cars, then pair again.
- Update the Android Auto app and Google Play services on the phone.
- Switch off battery-saver modes that may stop background connections.
- Restart the phone and restart the iDrive system, then try again.
If the connection still fails, tell the technician which phone model and Android version you use. Wireless Android Auto behaviour differs between phones, and a quick check usually shows whether it is the phone or the head unit.
Read this before you book
- Unofficial modification. The activation changes the head unit’s software. It is independent of BMW AG and Google LLC. Android Auto is a trademark of Google LLC.
- Compatibility is not guaranteed. Not every NBT EVO software build can take the feature. If yours cannot, you are told before any work starts and shown an alternative where one exists.
- Software updates. A dealer or over-the-air software update can remove or overwrite the activation. Ask before you update the head unit.
- Warranty. A modified infotainment system can affect warranty claims related to it. Discuss this with your dealer if the car is still covered.
- Safe use. Use Android Auto in line with the traffic rules where you drive and keep your attention on the road.
- Reversible. The head unit’s original state is recorded before anything is changed, so the original configuration can be restored on request.
Price
Native Android Auto for BMW NBT EVO costs €120 (regular price €200). The price covers the compatibility check, the remote activation and help with the first pairing. It is a single price with no subscription. The only extra you may need is an ENET cable.
Frequently asked questions
Does BMW NBT EVO support Android Auto?
BMW did not offer Android Auto as a factory feature on NBT EVO head units. It can be enabled through a software change on compatible builds, which is why every car is checked by VIN and software version before booking.
Is Android Auto on NBT EVO wired or wireless?
The service is set up for a wireless connection over the car’s Bluetooth and Wi-Fi. If you need something different, say so before booking and the technician will confirm what your software build allows.
Do I need an MMI box or a new screen?
No. Android Auto runs on the original head unit and appears on the original iDrive display. Nothing is added to the car.
Does it work on iDrive 4?
Not directly. iDrive 4 units need the ID4 → ID6 upgrade first. Older NBT and CIC systems are not supported.
Can I have Android Auto and Apple CarPlay on the same car?
Often yes. Tell us before the session if CarPlay is already activated, so we can check that both work on your software build.
Which phones work?
You need an Android phone with wireless Android Auto support. Google’s published requirement has been Android 11 with 5 GHz Wi-Fi, and some older phones also work. Check Google’s current help page for your phone and country.
Will a software update remove it?
It can. A dealer or over-the-air update may overwrite the activation. Ask before you update the head unit.
Can it be undone?
Yes. The head unit’s original state is recorded before anything is changed, so the original configuration can be restored on request.
How long does the session take?
Usually 30 to 60 minutes including the connection, the activation and the first pairing.
What happens if my car is not compatible?
You are told before any work begins, and an alternative is suggested where one exists – for example Apple CarPlay or the NBT EVO upgrade.
Final checklist before booking
Check that your car has NBT EVO, photograph the software information page, make sure your phone supports wireless Android Auto, and have an ENET cable, a Windows laptop and a stable internet connection ready. If you already have Apple CarPlay activated, mention it. Do not update the head unit until the activation is done and you have asked whether an update could remove it.
Ready to check your car? Open BMW NBT EVO Native Android Auto, send your VIN and the photo of the software page, and you get a clear yes or no before you pay anything. To see everything else that can be done remotely, browse all BMW remote services, or contact us directly.
BMW, iDrive and MINI are trademarks of their respective owners. Android Auto is a trademark of Google LLC. They are used only to identify compatible vehicles and features. TempaDrive is not affiliated with or endorsed by BMW AG or Google LLC. Modifying infotainment software is unofficial; follow the traffic rules and the warranty terms that apply to your vehicle.