ELM327 connected via Bluetooth but the car does not respond: 10 causes and fixes on Android

Two connections, not one

An OBD2 reading goes through two successive links:

1. Phone → adapter: classic Bluetooth, Bluetooth Low Energy (BLE) or Wi‑Fi.
2. Adapter → engine control unit: through the OBD2 port, using one of the standard protocols (CAN on most recent cars, K-Line ISO 9141 or KWP2000 on many older cars, J1850 on some American models).

When DiagAuto AI connects, it first resets the adapter and checks that it answers like an ELM327. It then queries the car, letting the adapter search for the protocol, then tries several others if nothing comes back. The message displayed therefore tells you at which step the problem lies:

• “does not answer like an OBD2 adapter”: the first link is wrong (often, the wrong device);
• “The car is not responding”: the adapter answers, but no protocol got a reply from the car.

The 10 causes, from most to least common

1. The ignition is not on

This is by far the most common cause. The engine control unit only answers with the ignition on (engine off or running). On a car with a “Start” button, press the button without your foot on the brake to switch the ignition on without starting the engine. With the key simply inserted, or after a few minutes of inactivity on some cars, the control unit stays asleep.

2. The adapter is not pushed in properly or the port has no power

Push the adapter all the way in: the port is stiff, and an adapter sitting “halfway” in sometimes lights up without communicating. If its light stays off, the port is getting no power: on many cars, it shares a fuse with the cigarette lighter. To find the port: where is the OBD2 port.

3. The wrong device was chosen in the list

Your car radio, a watch or a speaker also appear in the list of paired devices. An adapter's name is often “OBDII”, “OBD2”, “V-LINK” or “ELM327”. If the app says the device “accepted the connection but does not answer like an OBD2 adapter”, choose another name in the list.

4. Mixing up classic Bluetooth and BLE

The two technologies do not connect in the same way:

• a classic Bluetooth adapter must be paired once in Android's Bluetooth settings (the code is often 0000 or 1234), like a headset;
• a BLE adapter is not paired: pairing it in the settings fails or does nothing. In the app, run “Search for BLE adapters” with the ignition on.

A BLE adapter searched for in the list of paired devices will never appear, and vice versa. The manual or the product page states the type (“BLE” or “Bluetooth Low Energy”).

5. The “Nearby devices” permission was denied

Since Android 12, an app must be granted the “Nearby devices” permission to connect to a Bluetooth device. If you denied it on first launch, the connection fails with no further explanation in some apps. Open Android Settings → Apps → DiagAuto AI → Permissions, and grant it. On Android 11 and earlier, searching for BLE adapters requires the location permission: this is an Android requirement, DiagAuto AI never reads your location.

6. Another app is already using the adapter

A classic Bluetooth adapter accepts only one connection at a time. If another OBD2 app is still open in the background, or if a passenger's phone connected first, your app is refused. Fully close the other OBD2 apps (not just “go back to the home screen”), or turn the phone's Bluetooth off and on again.

7. Wi‑Fi adapter: the phone has left its network

With a Wi‑Fi adapter, the phone must be connected to the adapter's Wi‑Fi network, then the app connects to it by its IP address (often 192.168.0.10). This network has no Internet access: some phones leave it on their own to go back to a home router or a known network. Check the active Wi‑Fi network just before connecting. For the AI, the app then uses mobile data: keep it turned on.

8. A clone that does not handle all protocols

Adapters costing a few euros often display “v2.1” but contain a copied chip that only handles some of the protocols, or accepts commands without applying them. The typical symptom: everything works on a recent car using CAN, nothing gets through on a pre-2008 car using K-Line. Trying a better-quality adapter is then the quickest test. Our tested adapters page details what worked, and what did not, on our own cars.

9. A J1850 protocol (older Ford and GM)

The J1850 protocol was mainly used on cars designed for the American market until the mid-2000s (Ford with J1850 PWM, General Motors with J1850 VPW), and on a few Fords sold in Europe in the early 2000s, depending on the version. Many clones do not handle it at all. If your car is in this case, choose an adapter that explicitly states J1850 PWM and VPW support.

10. The car is not OBD2 compatible

In Europe, OBD (EOBD) has been mandatory on new petrol cars since 2001 and on diesels since 2004. Some slightly older cars already have the port, but not necessarily the standard protocol: the port is there, the car does not respond. See the question “Is my vehicle compatible?” on our help page.

The 5-minute method

1. Ignition on, adapter pushed all the way in, adapter light on.
2. All other OBD2 apps closed.
3. The right connection type chosen: paired device (classic Bluetooth), “Search for BLE adapters” (BLE) or the adapter's Wi‑Fi network (Wi‑Fi). The full procedure is on connect your adapter.
4. “Nearby devices” permission granted.
5. If the car still does not respond: try the adapter on another recent car. If it works there, the problem comes from your car's protocol; if it does not work there either, the adapter is to blame.

If nothing helps, the “Report a problem” button below the error message prepares a report with the technical log of the connection. You are the one who sends it, and it helps understand at which step communication failed. To choose a more reliable adapter: which ELM327 adapter to buy.