Connection Troubleshooting
Most connection issues are solved in 5-10 minutes. Work through the steps in order — each one checks a deeper layer of the problem.
Adapter doesn’t appear in the Bluetooth list
1. Make sure the adapter has power. Plug the adapter into the OBD-II port with the ignition on. Most adapters have a power LED (blue or green). If nothing lights up — try a different ignition key position or check the OBD fuse (usually 10-15A in the fuse box).
2. Check the Bluetooth version. Our app supports only Bluetooth Classic (SPP). Adapters labelled “BLE”, “Bluetooth 4.0 Low Energy”, or “BLE 5.x” are not compatible with the ELM327 standard for automotive diagnostics.
3. Pair the adapter first. Before the adapter appears in the app — pair it in Android’s system Bluetooth settings. Common device names: OBDII, ELM327, V-LINK, VGATE, OBD2. Default PIN is 1234 or 0000.
4. Adapter was paired but disappeared from the list. Remove the device from Bluetooth settings and pair again. Some adapters need re-pairing after a phone reboot.
App connects but doesn’t read data
5. Protocol auto-detection in progress. After connecting, the app tries to auto-detect the ECU protocol (ISO 9141, KWP2000, CAN 11-bit, CAN 29-bit). On some cars this takes up to 30 seconds. Wait for initialization to finish — don’t interrupt.
6. Ignition is off. Some commands (especially live PID data) need the engine running or at least ACC mode. Try again with the engine running.
7. Adapter has frozen. If connected but no PIDs update — exit the app, unplug the adapter for 10 seconds, plug it back in, and reconnect. Cheap ELM327 clones sometimes freeze after long idle periods.
App shows “Protocol Not Found” or “No Response”
8. Car older than 1996 (US) or 2001 (EU). OBD-II is mandatory from these years. Older cars may have OBD-I or a proprietary protocol — our app doesn’t support those.
9. Some cars require the engine running. If the protocol isn’t detected with just ignition on (Acc/On) — start the engine and try again.
10. Incompatible adapter chip. The 25K80 chip and some Chinese clones have an incomplete AT-command implementation. If nothing else helps — try a name-brand adapter (VGATE, OBDLink).
No fault codes shown after connecting
11. No active codes — that’s normal. If the engine is running fine, there may be no stored DTCs at all. Try reading Pending codes (Mode 07) — these appear before the CEL turns on.
12. ABS/SRS module not responding. Some safety modules (ABS, SRS, airbags) use OEM-enhanced protocols not accessible via standard Mode 01/03. Visit a dealer for those codes.
Connection keeps dropping
13. Weak Bluetooth signal. Keep the phone within 6-10 feet of the adapter. The car’s metal body attenuates signal — avoid leaving the phone on the rear seat.
14. Android battery saver is killing the connection. Some Android skins cut Bluetooth in the background. Add our app to battery optimization exceptions: Settings → Battery → Optimization → Car Diagnostics → Don’t restrict.
15. Cheap clone overheating. Some ELM327 clones overheat after 20-30 minutes and drop the connection. Check if the OBD port is enclosed by a cover — remove it to allow airflow.
Contact support
If none of the above helped — reach out via the Contacts page and include:
- Car make, model, and year
- Adapter name and part number
- Android version and phone model
- Screenshot or text of the error from the app