Skip to content
ev.care
EV Software
1 June 2026

EV ADAS & Driver-Assist Glitches in India: Fix Guide

Frozen touchscreen, false ADAS braking, app won't connect or a failed OTA? Here's how Indian EV owners diagnose software vs hardware and fix it.

By ev.care Service Team

EV ADAS & Driver-Assist Glitches in India: Fix Guide

Your EV beeped, slammed on phantom brakes for a biker who was never going to hit you, and the lane-keep warning chimed at a road with no visible lane markings. Or maybe your touchscreen is frozen on the boot logo, the connected-car app says "Disconnected" no matter how many times you re-open it, and last night's over-the-air update got stuck at 47%. If any of this sounds familiar, you are not alone, and you are not imagining it.

Indian EVs have quietly become some of the most software-heavy cars on our roads. A modern Tata Nexon.ev, Harrier.ev, Punch.ev, MG ZS EV, MG Windsor, or Mahindra BE 6 and XEV 9e is essentially a computer on wheels with a big screen, a digital cluster, a 4G connection, cameras, radar, and a driver-assist (ADAS) brain making split-second decisions. When that software stack hiccups, the car still drives, but the experience degrades fast: false alerts, dead screens, apps that refuse to pair, connectivity that drops in your own basement parking.

This guide is written for exactly that owner. We will cover the real, genuinely reported problems on Indian EVs, what actually causes them, the resets and steps you can safely try yourself, and the honest split between what needs the brand's dealer, what an independent specialist like ev.care can repair, and what is simply a software bug you have to wait out. We will be straight with you throughout: a large share of these issues are fixed by an OTA update, a screen reset, or a dealer software re-flash, not by a workshop. Knowing which bucket your problem falls into saves you time, money, and a wasted service-centre trip.

Common software, infotainment & connected-car problems Indian EV owners report

These are the symptoms owners are actually posting about on forums, owner clubs, and social media, grouped by what you experience.

Touchscreen and infotainment

  • The central touchscreen freezes, goes black, or stays stuck on the brand boot logo and won't respond to taps.
  • Random reboots while driving, sometimes taking the reversing camera feed down with them.
  • Severe lag, ghost touches (the screen registering taps you never made), and the audio muting itself for no reason.
  • Apple CarPlay or Android Auto failing to connect, dropping mid-drive, or refusing to launch. On the Mahindra BE 6 and XEV 9e, wired CarPlay was not even functional at launch and had to be added later through software.
  • On Mahindra's twin EVs, early units shipped with a passenger-screen GPU that would reset itself every few hours, a defect later patched in a firmware update.

Instrument cluster

  • The digital driver's cluster goes blank at startup, or shows warning lamps that don't match how the car is actually behaving.
  • Speed, range, or charge readouts that lag, freeze, or briefly disappear.
  • On Tata's newer IRA-platform cars (Punch.ev, Curvv.ev, Nexon.ev), the cluster and infotainment are linked tightly enough that one freezing can take the other with it.

Connected-car apps and remote features

  • Tata's connected-car app (branded ZConnect, and the newer Tata.ev app) showing the car as "Disconnected" even with an active subscription, or throwing an "UNKNOWN ERROR" on launch.
  • MG's iSMART app refusing to bind to the car, stuck on "activate car first" or "connection is abnormal," and remote climate/lock commands silently failing.
  • Mahindra's AdrenoX-linked features and digital key handed over at the showroom simply not working on day one for some buyers.
  • Remote commands (pre-cool the cabin, lock/unlock, locate the car) that work one day and time out the next, sometimes for 24 to 48 hours before mysteriously coming back.

OTA updates

  • An over-the-air update that downloads but won't install, fails partway, or gets stuck on a progress bar.
  • The car asking for an update repeatedly even after you thought it installed.
  • Worry (justified) about starting an OTA with a weak 12V battery or poor signal and ending up with a half-flashed, unhappy car.

ADAS and driver-assist

  • Phantom or false emergency braking: the car reading a biker cutting in, an overtaking truck, or a pedestrian near the bumper as an imminent crash and braking hard. On the Mahindra XEV 9e and BE 6, sudden ADAS braking at speed from false alerts has been reported.
  • Lane-departure and lane-keep warnings firing constantly on roads with faded or missing markings, or disengaging without warning.
  • Forward-collision and blind-spot alerts that cry wolf, plus driver-monitoring cameras (Mahindra calls its system Eyedentity) that nag you or, conversely, stop working entirely as a software glitch even though the camera hardware is fine.
  • Frozen rearview or 360-degree camera feeds; Tata specifically shipped an OTA for the Harrier.ev to fix frozen rear cameras and blind-spot monitoring.

If your problem is on this list, take a breath. Most of these have known causes and known fixes.

What actually causes these glitches

Understanding the root cause tells you whether to reach for a reset, wait for an update, or book a repair.

Software and firmware bugs

This is the single biggest cause. These cars run enormous, fast-evolving software stacks, and code is often shared across models before it is fully adapted to each one. The result is bugs that ship to customers: the Mahindra driver-monitor glitch (hardware fine, software broken), CarPlay missing at launch, and clusters that blank on startup are all software, not hardware, faults. The good news is that software faults are exactly what OTA updates and dealer re-flashes exist to fix.

Failed or interrupted OTA updates

An OTA is essentially open-heart surgery on the car's brain. If the download is corrupted by a network timeout, if you switch the car off mid-update, or if the 12V battery is too weak to hold the systems up through the flash, the update can fail and leave a module in a confused state. Most failures are recoverable by retrying on a strong connection with the car healthy and parked, but a genuinely bricked module needs the dealer.

Connectivity: SIM, network, and antenna

Every connected EV has an embedded SIM (usually a built-in eSIM) inside its telematics control unit, talking to a 4G network. Three things break this in India:

  • Weak or absent signal where you park. Basement and stilt parking, dense urban canyons, and rural dead zones all starve the car's connection, which is why so many app problems vanish the moment the car drives out into open sky.
  • Wi-Fi versus cellular confusion. Counter-intuitively, MG owners have found the iSMART app gets worse when the car latches onto a weak home Wi-Fi (reporting one bar right next to the router) and works fine once it is pushed back onto 4G.
  • Telematics-unit, eSIM, or antenna faults. If the embedded SIM deactivates, the telematics module hangs, or the antenna/connector is loose or damaged, remote features die even when your phone has full signal. This is a genuine hardware problem, distinct from a thin network.

Infotainment and cluster hardware

Sometimes the screen itself, the head unit behind it, the cluster, or a ribbon connector is physically failing: dead pixels, touch layer not registering, a unit that won't power up at all, water ingress, or a loose harness after a bump. Hardware faults don't get fixed by resets and don't get fixed by OTAs. They need repair or replacement.

Sensors, cameras, and calibration (ADAS)

ADAS leans on a forward camera (usually behind the windscreen) and often a front radar. Two very different things go wrong:

  • Calibration and environment. India is genuinely hard for ADAS. Faded, inconsistent, or missing lane markings, heavy monsoon rain, fog, dust on the sensor, and chaotic mixed traffic with two-wheelers and autos cutting in all push camera-based systems to their limit. Camera systems can disengage when rain is heavy enough that they simply cannot read the road. A lot of "false alerts" are the system honestly struggling with conditions it was never going to handle perfectly, and the fix is calibrating expectations, not the car.
  • Physical sensor faults or misalignment. If the windscreen has been replaced, the bumper knocked, or the camera/radar mounting disturbed, the sensor needs recalibration. A cracked or fogged sensor, or a damaged camera, is a hardware replacement plus recalibration job.

Fixes you can try yourself (step by step)

Try these in order. They are safe, they cost nothing, and they resolve a surprising number of issues. Always do them with the car parked, in P, handbrake on.

Soft reset (the screen restart combo)

This restarts the infotainment and, on many cars, the cluster, without touching your settings.

  1. Park the car, put it in P, apply the handbrake, and keep the car switched on.
  2. On most Tata IRA-platform EVs, press and hold the steering-wheel mute button for about 10 seconds, then hold the media/Bluetooth button for about 10 seconds. On Mahindra BE 6 and XEV 9e, owners use a hold of the volume and home buttons together for around 10 seconds for the audio-mute and freeze bugs. On MG, press and hold the physical home button on the screen for around 30 seconds.
  3. The screen will go dark and reboot. On Tata cars, opening and closing the driver's door can help the cluster and screen complete the reboot.
  4. Wait for the system to fully come back before you start driving.

Check your owner's manual for the exact button combination for your model, as it varies.

Hard reset (12V power cycle)

If the soft reset doesn't take, a full power-down often clears a hung module.

  1. Switch the car fully off, lock it, walk away with the key, and wait 15 to 30 minutes so all the modules go to sleep.
  2. Return, unlock, and start up. Many "stuck" clusters and frozen screens clear after a proper sleep cycle.
  3. If you are comfortable and out of warranty considerations, briefly disconnecting the 12V auxiliary battery is the nuclear version of this, but do not attempt it if you are unsure; a wrong move can throw more faults than it clears. When in doubt, let the dealer or ev.care do it.

Re-pair phone, CarPlay, and Bluetooth

  1. On the car, delete (forget) your phone from the Bluetooth/CarPlay device list.
  2. On your phone, forget the car under Bluetooth settings.
  3. Restart your phone.
  4. Re-pair from scratch, granting all requested permissions. For wired CarPlay/Android Auto, try a different known-good cable and a different USB port.

Reinstall and re-link the connected-car app

  1. Confirm your phone has Bluetooth, Wi-Fi, and mobile data on, and that the app has all permissions.
  2. Update the app to the latest version, or uninstall and reinstall it.
  3. Log in and re-link the car. If it says "activate car first" (common on MG iSMART), the telematics activation has to be completed by the dealer; the app cannot fix that.
  4. The classic Tata ZConnect trick: drive the car for 10 to 15 minutes, park, lock it, walk away with the key for 5 to 10 minutes, then send a command from the app. This forces the telematics unit to re-handshake with the network.
  5. If the car is on weak home Wi-Fi, try turning the car's Wi-Fi off so it falls back to 4G, then test the app again.

Retry a failed OTA the right way

  1. Park where the car has strong mobile signal, ideally outdoors, not in a basement.
  2. Make sure the 12V system is healthy. If your car has been sitting unused for a long time, drive it first to top up the 12V.
  3. Keep the car switched on and do not interrupt the update once it starts. Leave it parked for the full duration.
  4. If it still fails, do not keep hammering retry. Note the version and error and contact the brand; some OTAs are pushed in waves and your car may simply not be eligible yet.

If two or three of these have not fixed it, the problem is likely either a known bug awaiting an official update, or genuine hardware, and it is time to escalate.

When it needs the brand/dealer vs an independent specialist

Here is the honest split. Neither side can do everything, and good advice tells you which door to knock on.

Go to the brand's dealer when:

  • The fix is an official OTA update or a software re-flash. Only the manufacturer can push firmware and re-flash control modules. The Harrier.ev camera/blind-spot/braking fixes, the Mahindra firmware patches, and any ADAS logic improvement all come this way. No independent can flash brand firmware.
  • ADAS calibration after a windscreen or sensor job needs the OEM's proprietary targets and software, which many dealers and authorised glass partners have.
  • The fault is under warranty, especially anything touching ADAS, braking, or the telematics module. Let the dealer own it so you don't risk your warranty.
  • The telematics SIM/subscription needs reactivation, or the car needs "binding" to your account.

An independent specialist like ev.care is the right call when:

  • You need an honest, brand-neutral diagnosis of whether your problem is software or hardware before you spend money. Dealers are sometimes quick to swap an expensive part; an independent diagnosis can save you a screen replacement you never needed.
  • The infotainment screen, head unit, or cluster has a confirmed hardware fault and needs repair (often far cheaper than a full OEM replacement) or out-of-warranty replacement.
  • The fault is connectivity hardware: antenna, wiring/connector to the telematics unit, or an eSIM/module issue that survives every reset.
  • You are out of warranty and want a cost-effective fix rather than dealer-list pricing.
  • Your dealer keeps saying "it's a known issue, wait for the update" but you need a second opinion on whether something physical is actually wrong.

A simple rule: software push and warranty work, go to the brand. Hardware repair, neutral diagnosis, and out-of-warranty value, talk to an independent.

Hardware faults & repair, with indicative INR costs

When resets and updates are exhausted, these are the physical repairs in play. Treat every figure below as indicative only; actual cost depends on your exact model, variant, parts availability, whether you go OEM or independent, and your city. Always get a written quote first.

  • Infotainment touchscreen / head-unit repair (touch layer, display panel, connectors, or board-level repair at an independent): roughly 8,000 to 30,000 INR depending on the fault and model. Repair is usually far cheaper than replacement.
  • Full OEM infotainment head-unit replacement (genuine part, big-screen premium EVs): commonly 40,000 to 1,20,000 INR or more, which is exactly why a proper software-versus-hardware diagnosis first is worth it.
  • Digital instrument cluster repair or replacement: roughly 12,000 to 60,000 INR depending on whether it is a repair or a full genuine unit.
  • Telematics control unit / connectivity module repair or replacement, including antenna or harness/connector fixes: roughly 6,000 to 35,000 INR. A loose connector or antenna can be a small fix; a dead TCU is a bigger one.
  • eSIM reactivation / connected-car subscription renewal: typically a small fee through the brand, sometimes bundled free for the first few years; the app and remote features simply will not work if the subscription has lapsed.
  • ADAS forward-camera or front-radar replacement plus mandatory recalibration: the calibration alone is a meaningful chunk of cost globally, and in India a camera/radar replacement with recalibration commonly runs into the tens of thousands of rupees. Recalibration after a windscreen replacement is a must on most ADAS-equipped cars, so always confirm it is included when you replace the glass.

For context, plain aftermarket Android head units sell from around 7,000 INR upward, but those are not a like-for-like replacement for an integrated OEM system tied to your cluster, steering controls, cameras, and connected features. Fitting a random aftermarket unit to a modern EV usually breaks more than it fixes.

Warranty: software and infotainment coverage, and how to claim

Most Indian EVs carry a vehicle warranty (commonly three years/unlimited km or similar, model-dependent) plus a separate, much longer battery warranty. Where do glitches sit?

  • Software bugs are not a warranty "claim" in the parts sense; they are fixed for free via OTA updates or dealer re-flashes regardless of warranty, because they are defects the manufacturer is correcting. If your fault is a known software issue, you should not be paying anyone.
  • Infotainment, cluster, telematics, camera, and radar hardware are covered under the standard vehicle warranty if they fail within the period and you have not caused the damage. A genuinely faulty screen or dead TCU inside warranty should be repaired or replaced at no cost by the dealer.
  • The connected-car subscription (the data plan behind the app) is usually time-limited and separate from warranty. When it lapses, remote features stop, and that is a renewal, not a fault.

How to claim cleanly:

  1. Keep service records and note the date, symptom, and any error messages or dashboard photos.
  2. Report the issue to your authorised dealer in writing (email or the service app) so there is a timestamped record, and ask them to log it against your VIN.
  3. Ask explicitly whether the fix is an OTA/re-flash (should be free) or a hardware replacement (warranty-covered if in period).
  4. If a dealer tries to charge you for what is clearly a known software bug, escalate to the brand's customer care with your written record. For Tata ZConnect-type issues, there is dedicated connected-car support; use it.
  5. Avoid unauthorised hardware modifications while in warranty, as they can give the brand grounds to decline a claim.

How ev.care helps

ev.care exists for the messy middle, the part where you are not sure if it is software or hardware, your dealer is slow, or you are out of warranty and dreading the bill. Across any brand, we focus on what independents do best:

  • Software-versus-hardware diagnosis. Before anyone replaces a costly screen, cluster, or module, we determine whether your fault is a known software bug (wait for the OTA, or push it at the dealer), a connectivity problem, or a genuine hardware failure. This single step prevents the most expensive mistake in EV ownership, paying to swap parts that were never broken.
  • Infotainment and cluster hardware repair and replacement. Frozen screens, dead displays, ghost-touch panels, blank clusters, and failed head units, repaired where economical and replaced when not, typically at better value than dealer-list pricing once you are out of warranty.
  • Connectivity and antenna fixes. eSIM/telematics-module issues, loose or damaged antenna connectors, and wiring faults that survive every reset, the things that make remote app features fail even when your phone has full bars.
  • Honest escalation guidance. When the right answer genuinely is "this is an OEM OTA, go to your dealer and don't pay," we tell you that plainly and help you frame the warranty conversation.

We will never pretend a software bug is a workshop job. If a screen reset or an official update fixes it, we will say so. Where there is real hardware or connectivity work, that is exactly where we add value.

Start with a proper diagnosis: book an EV diagnosis. If charging is also misbehaving alongside your software gremlins, our EV charging repair & service and the free EV charging diagnostic tool will help you isolate that too. And if your Nexon.ev is throwing more than just software faults, our deep-dives on Tata Nexon EV charging problems, Tata Nexon EV motor problems, and EV motor controller and inverter faults are good companion reads.

FAQ

My EV's touchscreen is frozen. Will I damage the car if I keep driving?

No. The infotainment and cluster are separate from the systems that actually move and brake the car, so a frozen screen is an annoyance, not a driving hazard, in the short term. Park safely and try the soft-reset button combination for your model, then a full sleep cycle (lock it, walk away 20 to 30 minutes). If it keeps freezing, it is either a known software bug awaiting an update or a hardware fault worth getting diagnosed. One caution: if the reversing camera or critical warnings are affected, drive extra carefully until it is fixed.

Is the ADAS false braking a defect I can claim, or just how it is?

It depends. If your car is hard-braking for genuine non-threats (a biker merging normally, an overtaking truck) at speed, that points to ADAS logic that needs tuning, and several Indian brands have shipped OTA updates precisely to calm this down. Report it to your dealer in writing and ask if a software update addresses it. But some false alerts are the honest limit of camera-based systems on Indian roads with faded markings, rain, and chaotic traffic. ADAS is an assistant, not an autopilot. Keep your hands on the wheel and eyes on the road regardless, and use the system's sensitivity settings if your car offers them.

My connected-car app says the car is disconnected even though my subscription is active. What do I do?

This is usually a network/telematics handshake problem, not a dead car. Drive the car 10 to 15 minutes to refresh its connection, park where there is strong signal (not a basement), lock it, walk away with the key for 5 to 10 minutes, then send a command. Update or reinstall the app and confirm the subscription is genuinely current. If the car is on weak home Wi-Fi, turn the car's Wi-Fi off so it uses 4G. If it still shows disconnected for days, the telematics unit, eSIM, or antenna may have a hardware fault worth diagnosing.

A software update failed midway. Is my car bricked?

Almost certainly not. Most failed OTAs are recoverable. Park outdoors with strong signal, make sure the 12V is healthy (drive the car first if it has been idle), keep it switched on, and retry without interrupting it. If it still fails, stop retrying and contact the brand with the version and error, as the update may be rolling out in waves and your car may not be eligible yet. A truly half-flashed module that won't recover needs the dealer to re-flash it, which they can do.

Should I take a software or infotainment problem to the dealer or to an independent like ev.care?

Software re-flashes, OTA updates, ADAS calibration with OEM targets, and anything under warranty should go to the brand's dealer, because only they can push firmware and honour warranty. An independent like ev.care is ideal for a neutral software-versus-hardware diagnosis before you spend money, for out-of-warranty hardware repair of screens, clusters, and connectivity modules at better value, and for a second opinion when the dealer keeps saying "wait for the update." The smart move is often a quick independent diagnosis first, then the right door.

How much does it cost to fix a dead infotainment screen or cluster in India?

Indicatively, an infotainment touchscreen or head-unit repair runs roughly 8,000 to 30,000 INR, a full genuine head-unit replacement on premium EVs can be 40,000 to over 1,20,000 INR, and a digital cluster repair or replacement is roughly 12,000 to 60,000 INR. Connectivity-module and antenna work is often cheaper, around 6,000 to 35,000 INR. These are ballpark figures; the exact cost depends on your model, OEM versus independent parts, and your city. This is exactly why a proper diagnosis first matters, so you only pay to replace hardware that is genuinely faulty. If your car is in warranty, a confirmed hardware failure should cost you nothing.

ev software
infotainment
adas
tata nexon ev
ota update
connected car
driver assist
india

Need EV service?

Book a repair, health check, or annual care plan in 60 seconds.

WhatsApp