BMW Apple CarPlay Upgrade: Which Retrofit’s Worth It?

Straight-six snarling, iDrive glowing, but Maps, messages, and audio feel frozen in time. Power’s modern. The dash? Not so much. That’s where Apple CarPlay enters the picture.

But can your BMW handle it, and what’s the cleanest way in? It’s more than just the model year. Firmware, Wi-Fi hardware, and how much risk you’ll take all matter. Some owners unlock CarPlay with $100 coding tweaks. Others shell out $1,200 for a full Android screen.

This guide cuts through the noise. We’ll ID your head unit and iDrive version, trace BMW’s shifting CarPlay rules, and lay out the three upgrade paths: coding, MMI box, or Android screen.

Each brings its own quirks, installation hiccups, audio limitations, and possible warranty fallout. By the end, you’ll know what fits your VIN, your budget, and your appetite for compromise.

1. Compatibility comes down to your head unit, not just the badge

Why build dates mislead so many owners

“Mine’s a 2017, so I’m good.” That’s where a lot of folks trip. CarPlay doesn’t live in your model year; it lives in your head unit.

A late 2016 3-Series with the right NBT Evo setup might unlock CarPlay with a simple flash. But a 2017 running ID4? That’s a hardware wall. VIN decoding or checking the iDrive software version always beats guessing by year.

The real minimum for factory CarPlay

To even qualify, your BMW needs the NBT Evo (HU-H2) head unit with ID5 or ID6. Newer setups like MGU ID7 and ID8/8.5 come ready with wireless CarPlay baked in.

But here’s the catch: without option code S6CPA, a Wi-Fi antenna, and updated firmware, CarPlay won’t work. No antenna means no wireless link, even if the CarPlay menu appears.

Fast Compatibility Grid

Why BMW pulled the subscription stunt

CarPlay started as a $300 option. Then, in 2019, BMW decided to charge $80 per year through ConnectedDrive. The excuse? Ongoing wireless support. No one bought it.

Forums lit up. Car and Driver dragged them. Audi and Mercedes gave CarPlay away. By late 2019, BMW folded, making CarPlay free on cars with factory nav. The quick U-turn said it all: this was never about tech costs, just a failed cash grab.

2. Factory CarPlay runs wirelessly, set it up the right way

Wireless only, no USB fallback

CarPlay in BMWs runs strictly over Wi-Fi. Bluetooth just kicks things off. Plugging into USB? That won’t trigger CarPlay in any factory setup. Think of Bluetooth as the greeter; Wi-Fi does the heavy lifting.

How to pair on ID7 (and make it stick)

1. On iDrive: go to COM → Mobile Devices → New Device → Phone calls and audio

2. On iPhone: open Bluetooth, pick your BMW, confirm the PIN

3. Accept Apple CarPlay when prompted, and keep your iPhone screen on while it finishes

4. Wipe any old BMW pairings from both phone and car before starting

How to pair on ID8 (and avoid Siri hang-ups)

1. On iDrive: TEL → Connect new telephone, then tap your iPhone when it appears

2. Confirm the PIN and accept CarPlay

3. Siri must be turned on; no Siri, no CarPlay

4. If setup hangs, toggle Wi-Fi and Bluetooth off/on, then accept again

Setup fails when these are missing

You’ll need an iPhone 5 or newer, running at least iOS 9.3, with Siri, Bluetooth, Wi-Fi, and a live data plan. On the car’s side: NBT Evo with ID5 or ID6, S6CPA option, and a working Wi-Fi antenna. Even if the menus show CarPlay, a missing antenna or unsupported head unit will block it cold.

3. Three upgrade paths when factory CarPlay’s off the table

Flip the software switch if NBT Evo’s already under the hood

Running NBT Evo with ID5 or ID6 and have S6CPA on your build sheet? You’re a software unlock away from full wireless CarPlay, no screen swap, no head-unit surgery.

Just one tweak behind the scenes. For full-screen support, your firmware needs to be from the NBTEvo N to Y series, and a Wi-Fi antenna must be wired behind the dash. Skip the antenna, and pairing won’t even start.

Remote coding is the safest move. A proper vendor can handle it in 30–60 minutes, no E-Sys digging or bricking risks. Some coders use USB sticks, others rely on an ENET cable and desktop app.

Expect to pay $90 to $400, usually with instructions, tech support, and a way to roll back. As for warranty concerns? BMW would need to prove the coding caused the failure. Still, keep a backup of your stock firmware, just in case.

Go with an MMI box if you want to keep the factory feel

Got a CIC or NBT ID4 system? An MMI retrofit box adds CarPlay or Android Auto while keeping your original screen, iDrive knob, and steering controls.

It intercepts the video signal, layers in CarPlay, and passes commands back to the stock system. Brands like BimmerTech offer polished kits, while cheaper options like Andream or CarlinKit focus on the basics. Hardware costs run $200 to $700; install ranges from free to $300, depending on your skills.

Audio routing matters here. Basic AUX output technically works, but it’s analog, expect hiss, distortion, and dull tone. Bluetooth routing improves sound on most setups.

But if your BMW has a MOST fiber-optic audio bus, go that route. Kits like Mr12Volt send digital audio straight to the amp, keeping dynamics crisp and distortion low, especially important with Hi-Fi or Harman Kardon packages. Always calibrate input gain, or you’ll get EQ distortion even at low volume.

Installing an MMI box is more than plugging in a phone charger. You’ll need to remove trim, unbolt the head unit, daisy-chain wiring, and tuck the module somewhere behind the dash.

Clip breakage and bad mic placement can ruin the job if you rush. A careful DIY install takes 40 to 180 minutes. Want factory fit and no hassle? Pay a pro and be done with it.

Go full Android if touch and screen size matter more than factory look

If you’re chasing a modern dash with touch control, app support, and a big screen, an Android head unit does it all. It replaces your factory display with a 10–12″ screen offering native CarPlay, Google Maps, YouTube, and more if you want. Expect $600 to $1,200 for the screen, and $100 to $300 for install.

You’ll keep your steering wheel buttons and iDrive knob, but not everything carries over. System alerts sometimes stay locked in OEM mode. Audio handoff can lag. You may need to pair your phone to the new screen, not the car.

Fit and finish ranges wildly. Cheap kits can bring gaps, screen wobble, or buggy UX. If sound quality ranks higher than screen size, you’re usually better off with an MMI box that supports MOST.

4. Audio quality can make or break your upgrade

Why AUX turns high-end sound into a hissy mess

AUX output is the weak link. It’s analog, which means your signal gets compressed by the phone, re-decoded by the MMI box, then digitized again by the head unit. Every step adds noise. Bass gets lost. Hiss creeps in. Even the best cable can’t fix a signal already chewed up by upstream conversions.

Cleaner audio paths that don’t butcher the sound

A Bluetooth reroute works better. It feeds CarPlay audio through the car’s built-in Bluetooth receiver, no analog cable, less distortion, and fewer volume spikes.

But for true fidelity, MOST fiber-optic is the one to beat. It feeds a raw digital signal directly to the amp, preserving OEM staging, balance, and tonal detail. If your car has a premium audio package (Hi-Fi, HK, B&O), use MOST. It’s worth every penny.

Set your levels like a pro, not a button masher

First step: confirm your sound tier, Base, Hi-Fi, HK, or B&O. Then match it with an MMI box that supports the right audio path. In the settings, flatten all EQ adjustments.

Next, balance your volume levels between CarPlay, iDrive, and phone at your usual listening volume. Never boost bass in both the phone and the car; that’s how you get clipping and muddy mids.

Audio path quality ranking

5. Install jobs aren’t plug-and-play; they’re full-on surgery

Coding your BMW without risking the head unit

Remote coding is the cleanest route, but it’s serious business, more like flashing firmware than tapping a phone app. A power drop, bad file, or wrong move can freeze iDrive on the spot. You need stable voltage, clear instructions, and a full backup. Skip any of that, and you’re rolling the dice.

Start by confirming you’ve got NBT Evo with ID5/ID6 and S6CPA. Connect a 12–20 A charger; flaky voltage ruins everything. Back up your CAFD files and screenshot the current config. Clear out Bluetooth pairings and Wi-Fi hotspots on your phone.

Stick with a vetted remote coder or a proven tool, not DIY guesswork with E-Sys. After activation, reboot iDrive and test for full-screen CarPlay. Always save activation files and restore instructions, both online and on USB. Once it’s stable, you’re good to go.

MMI retrofits demand planning, not just parts

This isn’t mounting a phone holder. You’re deep inside the dash, thin clips, sharp edges, and bulky harnesses that love to rattle. Audio glitches and voice command failures usually trace back to bad grounds or sloppy mic placement.

Disconnect the battery, tape off trim edges, and pull the screen and head unit. Photograph every plug before removing anything. Bench-test the MMI overlay first.

Switch it to match your chassis (CIC, NBT, Evo), then pick your audio path: MOST fiber if available, Bluetooth reroute next best, AUX last resort. Mic and USB cables need clean routing, no bends or pinch points. Mount the box tight behind the HU or glovebox and avoid loose bundles.

After reassembly, neutralize input gains and match them to your normal volume. Run checks on the backup cam, parking sensors, and system chimes. No hiss, no rattle, clean voice pickup? You’re golden. If not, fix it now or tear it back down later.

Android screen swaps need precision, not just boldness

Swapping to Android changes more than looks; it rewires the logic. The screen has to speak your BMW’s CAN system, manage clean audio output, and still trigger factory alerts. A good unit feels fast and seamless. A bad one glitches, reboots, or hums like it’s haunted.

Disconnect the battery and remove the factory screen and head unit with padded tools. Bench-test the new unit before reassembly, check touch, CarPlay, wheel controls.

Harnesses need to be labeled, and CAN profiles must match your chassis. Pair your phone to the new screen, not the car. Set your audio output path, sleep/wake timers, ignition sensing, and brightness.

Check that OEM mode still shows warnings and alerts. On the road, listen for buzz under throttle; bad power routing causes it. Save the vendor firmware and return details before closing up the trim.

6. Warranty, updates, and what the dealer actually sees

You’re protected by law, but prep is still your best defense

The Magnuson-Moss Act says your warranty can’t be voided just for adding mods. But if the mod causes the problem, that’s fair game. So if your head unit dies after coding, you’d better show receipts, backups, and stay calm. Don’t show up empty-handed, asking for a free fix.

Dealers spot coding faster than you think

They check firmware levels, build options, and I-Level history. If your Evo unit suddenly shows CarPlay without the factory code, they’ll notice.

That’s why you keep CAFD screenshots, revert files, and a note in your service booking: “No infotainment updates without owner approval.” Quiet prep beats a loud argument.

Updates can wipe your unlock, control the flashes

A dealer update often wipes CarPlay on ID5/ID6 systems. Even over-the-air updates can erase the activation. Always save your activation file and have a plan to reapply it before allowing any reprogramming. MMI retrofits usually survive updates, but still document your current settings just in case.

Resale value? Factory look wins, Android divides

OEM-style coding keeps things clean. It blends into the dash and doesn’t scare buyers. A well-installed MMI box with MOST audio comes close, especially for buyers who know what they’re getting.

Android screens? Some love them. Others see them as aftermarket clutter. If you’re selling, include receipts, install photos, and a one-page revert guide. Don’t rely on explaining it at the test drive; bring proof.

Risk and mitigation

7. Real-world costs, not brochure math

What owners actually spend, not the fantasy

CarPlay coding is by far the cheapest entry. Most pay $90 to $400 for activation, with no labor charge. Add $15–$30 for an ENET cable if needed, and $20–$60 for a Wi-Fi antenna if your ID5/ID6 Evo didn’t come with one. That puts the real-world total between $125 and $490, quick, clean, and fully reversible.

MMI retrofits fall in the middle. Hardware alone runs $200 to $700, depending on brand and features. Installation ranges from $0 to $300, based on how handy you are or how steep your shop’s labor rate is.

If you want premium sound on Hi-Fi or HK setups, a MOST-compatible unit adds another $100 to $250. It’s a smart upgrade if you care how the cabin sounds.

Android screen swaps are the high-dollar move. Units cost $600 to $1,200, with install adding $100 to $300. DIY jobs might need $10–$20 in trim clips or panel tools.

Final tally? Anywhere from $800 to $1,500. What you’re paying for: big screen, native apps, and full touch control. Just make sure the vendor sends working firmware and actual support, not just a box with a tracking number.

Real-world cost ranges

Where the money actually pays off

If your BMW shows NBT Evo with S6CPA, coding is the best value by a mile. It keeps the dash stock and skips tearing into trim. No coding option? Go for an MMI box that supports MOST audio. You’ll hear the difference instantly compared to AUX.

If it’s all about screen size and touch control, Android wins on visuals. But don’t cheap out, firmware quirks and glitchy UX from off-brand sellers will cost you more than the discount is worth. And if you plan to sell, coding or a clean MMI install is easier to explain and resell than a giant screen bolted into the dash.

Hidden costs that still catch owners

Dealer software updates can wipe CarPlay coding from ID5/ID6 units. Always keep your activation files and your coder’s restore instructions on hand.

Got a defective Android unit? Overseas returns are slow and expensive; buy from vendors with domestic support and clear return terms. And cheap harnesses? They lead to rattles, signal loss, and bad mic pickup. Spend upfront on clean connectors and solid wiring.

8. Pick your path in under 60 seconds, no guesswork

Check what your VIN and screen actually show

Don’t guess. Pull your build sheet and look for option S6CPA. Then open iDrive and confirm your system: NBT Evo ID5/ID6, MGU, or something older like NBT ID4. If it’s Evo with S6CPA, you’re eligible for coding. If it’s CIC or ID4, you’ll need hardware.

Have Evo with S6CPA? Don’t overthink, code it

This is the cleanest path. If CarPlay shows but it’s stuck in a small window, your firmware’s too old, update to NBTEvo N through Y to unlock full-screen.

Can’t connect wirelessly? You probably need the Wi-Fi antenna installed behind the dash. Save your activation files and write “no HU programming” on your next dealer service note. That alone can save you from a wiped activation.

No coding path? MMI keeps the OEM feel without the cost

When coding isn’t on the table, a MOST-equipped MMI keeps the factory look and nails the audio, especially on Hi-Fi or HK systems. Before you buy, check space behind the head unit to avoid rattles or loose fit. If you’re picky about sound, skip AUX-only kits. Bluetooth reroute is better, MOST is best.

All-in on modern visuals? Android leads that lane

Touch control, native apps, sharp visuals, Android delivers the full facelift. But the downside is variance. Fit, trim, and firmware can vary wildly between vendors.

Prioritize sellers with clear firmware support and return policies. If your car relies on factory chimes, seatbelt dings, reverse alerts, turn signals, make sure OEM mode is preserved. And if you hear buzz under throttle, fix your power routing before you button up the dash.

Edge cases to watch for

Late-build NBT ID4 units can look like Evo at first glance, but still need hardware swaps. Firmware versions H–M may allow CarPlay, but won’t do full-screen without updates.

And if your car has Base audio, you’ll get by with Bluetooth reroute, but don’t expect silence. For resale? Skip the giant screen. Factory-style coding or a clean MMI install plays better with cautious buyers.

Checklist before you hit “buy”

First, confirm your head unit, software version, and S6CPA status via VIN or iDrive settings. Choose your audio path in order: MOST first, Bluetooth second, AUX last.

Before placing your order, get written confirmation of firmware version, tech support contact, and return policy. And for coded setups, make sure the service desk knows: no infotainment updates without owner signoff.

9. Set it up clean, and it just works

Prep your phone to avoid pairing chaos

Start by updating iOS and making sure Siri, Wi-Fi, and Bluetooth are turned on. Then clear the slate. Forget every saved BMW or CarPlay connection from your iPhone’s Bluetooth list. In the car, or your MMI/Android box, do the same.

Delete all old phones, then reboot both the phone and the car. One more tip: disable any battery optimization features that might sleep Bluetooth in the background. And forget the myth about plugging in to “force” CarPlay, BMW doesn’t support wired CarPlay.

Get the pairing right the first time

For factory setups, ID7 uses COM > Mobile Devices > New Device, while ID8 starts under TEL > Connect New Telephone. Once your iPhone shows up, confirm the PIN and accept CarPlay.

Keep the phone unlocked until the tiles load; locking too early stalls the handshake. If it loops or fails, toggle Bluetooth and Wi-Fi off and back on, then start fresh.

MMI pairing needs the right signal path

With MMI boxes, pairing success hinges on the audio route. MOST fiber gives the cleanest sound, followed by Bluetooth reroute. AUX is your last resort.

If you’re stuck with AUX, choose a fixed level on the box and adjust volume from iDrive. Always pair the phone to the MMI, not the car, or you’ll end up with clashing Bluetooth streams.

Keep the antenna away from metal and test with trim off before final placement. For voice commands, make sure mic pass-through is active. If navigation prompts overpower audio, adjust guidance volume inside CarPlay, not on iDrive.

Dial in Android screens before locking it down

Android units take more setup, so finish everything before reinstalling trim. Pair your phone directly to the new screen, not the car. Set the correct CAN profile to keep steering buttons and iDrive inputs functional.

Tweak sleep and ignition delay settings to avoid sluggish boots or battery drain. Choose your audio path and match volumes before tuning anything. Then test OEM mode, make sure alerts, chimes, and prompts still come through clean. If Siri sounds muffled, check the mic input source in system settings.

Tune audio once, and save your ears

Start with flat settings. Turn off EQ on your phone, set iDrive tone to neutral, and keep gains at default in the MMI or Android settings. Play a familiar track at your usual volume.

Drop the MMI gain until background hiss disappears. If the bass gets fuzzy at low volume, it’s clipping; lower the gain one more notch. Don’t chase EQ perfection until the signal path is clean.

Stability isn’t just day one, it’s month two

For coded setups, back up your activation file and restore instructions. At the dealer, leave clear instructions: no infotainment programming without approval.

For MMIs, avoid firmware updates unless they fix something specific. On Android units, always export settings before flashing anything new, and test while parked, not mid-drive.

10. Troubleshooting that solves the issue, not your sanity

CarPlay doesn’t show up at all? Fix the handshake

When the CarPlay tiles never appear, the Bluetooth-to-Wi-Fi handoff is likely failing. Clear all BMW pairings from your phone and all phones from your car. Reboot both ends, then pair again with the phone unlocked. Still stuck? Move the MMI antenna forward and away from metal.

Paired but blank screen? Clear the conflict

Two Bluetooth connections can clash. On MMI or Android setups, your phone must pair with the box, not the car. Delete any leftover devices and power cycle. For factory setups, re-pair from scratch and don’t rush the CarPlay prompt. Let it load fully before touching the screen.

Audio stutters or lags? You’re feeding the wrong input

Lag usually means the wrong audio source is active. In MMI, prioritize MOST, then Bluetooth, with AUX as a fallback. Android units shouldn’t push audio over both BT and AUX; choose one. Once it’s set, play a nav prompt or make a call to test for sync.

Volume swings or hiss? Reset your gains

If it hisses, the gain’s too high. Turn off EQ on your phone, flatten the iDrive tone settings, and set the MMI gain to neutral. Raise the car’s volume to your normal level, then trim the MMI gain until the hiss drops out. If the bass still sounds muddy, you’re clipping; dial it back another notch.

Calls sound distant? Fix your mic routing

On MMI, verify mic pass-through is enabled, and check placement; it shouldn’t sit behind trim or near a vent. Android setups have selectable mic inputs; make sure the right one is active. If voice commands only work with windows up, move the mic away from airflow and pillars.

Random dropouts? It’s probably Wi-Fi, not ghosts

Signal drops usually trace back to poor antenna placement. Move the MMI antenna higher, farther forward, and away from harness bundles. On your phone, disable Low Power Mode or any app that might sleep Bluetooth. If your dashcam shares power, isolate the MMI on a clean circuit.

Steering buttons not working? That’s CAN confusion

Dead buttons often mean the wrong CAN profile. Android screens must match the exact chassis, or controls won’t respond. On MMIs, some systems need iDrive set as command priority to route inputs cleanly between menus. If only one direction works, it’s the wrong protocol.

Lost camera feed or chimes? Check signal pass-through

If your backup cam or parking alerts vanish, the signal path is off. In OEM mode, these should still work. On MMI, double-check that the reverse trigger is connected and mapped right. If you’re running AUX and forgot to set it as the active source, switch to MOST or Bluetooth, or fix AUX level first.

Dealer update nuked your activation? You’re not screwed

BMW updates can wipe CarPlay on ID5/ID6 units, but it’s recoverable. Reapply using your coder’s tool and backup file. Keep the key saved in two places, cloud and USB. Always tell the dealer: no head unit programming unless requested. If an OTA prompt shows up, delay it until you’re ready to restore.

Android screen glitching? Fix it before reassembly

Slow boots? Recheck sleep and ACC delay settings. Buzz under throttle? That’s a ground loop; move grounds to a single point and run clean power. CarPlay lagging behind startup? Set it as the default app and test it twice before sealing the dash.

Which upgrade path actually fits your car and your priorities

If your BMW runs NBT Evo with ID5 or ID6 and the build sheet shows S6CPA, stop overthinking. Pay for the coding, install a Wi-Fi antenna if needed, and unlock full-screen CarPlay.

It’s the cleanest, most cost-effective, and most OEM-feeling upgrade available. Just back up the activation file and keep your coder’s info close; dealer updates can still wipe it.

Driving something older, or missing S6CPA? An MMI retrofit hits the sweet spot. You keep the factory look and controls while adding wireless CarPlay or Android Auto.

Skip AUX-only boxes unless you’re okay with background hiss. Got Hi-Fi or Harman Kardon? Spring for a MOST-capable unit. The difference in sound is night and day. Installed right, it blends in and protects resale better than you’d think.

Chasing a full dash makeover? The Android screen swap gives you that in one move: large touch display, native apps, and a modern feel. But it permanently changes the cabin and brings its own quirks. For some, that’s a fair trade. For others, it never quite feels at home.

In the end, it’s about priorities. Factory feel, sound quality, or screen-driven tech. Pick one, and the upgrade path answers itself.

Sources & References

1. https://www.autonation.com/vehicle-research/bmw-apple-carplay
2. https://www.caranddriver.com/news/a30139034/bmw-apple-carplay-free/
3. https://www.bimmer-tech.net/blog/item/49-how-to-retrofit-carplay
4. https://bmwtweaks.com/personalisation/apple-carplay-activation/
5. https://g30.bimmerpost.com/forums/showthread.php?t=2101820
6. https://www.m3post.com/forums/showthread.php?t=1546382&page=55
7. https://www.mr12volt.com/products/p2000-cicmm
8. https://www.pempcar.com/blogs/knowledge/mmi-box-vs-screen-replacement
9. https://www.reddit.com/r/F30/comments/196v1o2/f32_carplayandroid_installer_perspec
10. https://faq.bmwusa.com/s/article/FAQ-Apple-CarPlay-What-are-the-requirements-touse-Apple-CarPlay-in-my-BMW-KQivT
11. https://www.bmwbuenapark.com/ownership/bmw-apple-carplay-setup.htm
12. https://www.bimmer-tech.net/blog/item/104-coding-software-bmw
13. https://bmwcodem.com/products/bmw-carplay-activation-for-idrive-5-idrive-6
14. https://bimmer-remote.com/products/bmw-carplay-fullscreen-activation
15. https://easybimmercoding.com/products/bmw-carplay-fullscreen
16. https://www.bimmer-tech.net/bmw-idrive-coding/
17. https://www.youtube.com/watch?v=NS_mXNRPNWY
18. https://codebmw.co.uk/bmw-coding/
19. https://oemnavigations.com/blogs/news/potential-of-bmw-e-sys-coding-personalising-your-bmw
20. https://www.mycarly.com/blog/car-coding/will-i-lose-my-warranty-if-i-code-my-car/
21. https://www.bimmer-tech.net/symfonySite/bmw-idrive-coding/?vin=WBAUF92020PS88898
22. https://www.bimmer-tech.net/category-bmw-apple-carplay-activation
23. https://www.reddit.com/r/CarPlay/comments/mi608p/bimmertech_mmi_prime_vs_alternatives/
24. https://www.bimmer-tech.net/category-bmw-carplay-mmi-retrofit
25. https://icodebmw.co.uk/shop/carplay/mmi-box/carplay-android-auto-mmi-box/
26. https://www.reddit.com/r/BMW/comments/12o9atv/idrive_vs_apple_carplay/
27. https://f20.1addicts.com/forums/showthread.php?t=1820109
28. https://f30.bimmerpost.com/forums/showthread.php?t=1681589&page=583
29. https://www.mr12volt.com/collections/bmw
30. https://www.scribd.com/document/426349347/BimmerTech-F32-F82-MMI-Installation-Instructions-and-User-Guide
31. https://f30.bimmerpost.com/forums/showthread.php?t=1528963
32. https://cartechstudio.com/blogs/apple-carplay/carplay-installation-cost
33. https://e84.xbimmers.com/forums/showthread.php?t=1675641
34. https://mergescreens.com/
35. https://cartechstudio.com/blogs/news/how-to-install-a-tesla-style-screen
36. https://www.carluex.store/collections/bmw-carplay-retrofit
37. https://nationalautosound.com/magnuson-moss-warranty-protection-act/
38. https://www.1addicts.com/forums/showthread.php?t=215590
39. https://www.reddit.com/r/BMWi3/comments/f1s6u0/does_coding_void_warranty/