An OBD2 app that works with Android Auto

Date: 2026-08-21T00:00:00+00:00 - (Skid Vis)

If you want an OBD2 app that works with Android Auto, first check what “works with Android Auto” actually means. The app should run on your Android phone, communicate with an OBD-II adapter, and present a driver-appropriate view through a compatible car display. It should not require installation on the vehicle itself.

OBD Auto for Android is built for that phone-projected setup. It can show selected, vehicle-supported readings through Android Auto templates and provide access to fault information. On the phone, it can also scan stored and pending fault codes, record trip samples, and export those samples as CSV or JSON. The app is coming soon on Google Play.

Android Auto and Android Automotive OS are different

This distinction determines whether an app is compatible with your car.

Google describes Android Auto as a phone-based platform. A compatible app runs from the user’s phone and provides a driver-optimized experience on the vehicle’s display. That is the platform OBD Auto supports.

Android Automotive OS is an Android operating system built into the vehicle. Apps for it can be installed in the car rather than projected from a phone. OBD Auto does not support Android Automotive OS and does not install on a vehicle’s built-in system.

In practical terms, you need all of the following for the car-screen experience:

  • A compatible Android phone running OBD Auto
  • A vehicle or head unit that supports phone-projected Android Auto
  • An OBD-II vehicle
  • A compatible Bluetooth Classic OBD-II adapter

The phone remains the center of the setup. You choose readings and manage the adapter there, while the compatible car display presents selected information in Android Auto templates.

The adapter must use Bluetooth Classic

“Bluetooth OBD2 adapter” is not specific enough. Bluetooth Classic and Bluetooth Low Energy, commonly called BLE, are separate connection options in Android’s Bluetooth platform. Google’s Bluetooth overview documents both Classic Bluetooth and BLE as supported Android technologies with different APIs and use cases.

OBD Auto requires a compatible Bluetooth Classic adapter that has already been paired in Android settings. It does not support:

  • BLE-only adapters
  • Wi-Fi-only adapters
  • An adapter that has not been paired with the phone

That exclusion matters when shopping. An adapter described only as “Bluetooth” may still be BLE-only, so confirm Bluetooth Classic support rather than relying on the product name.

OBD Auto has been tested with the OBDLink MX+. This does not guarantee that every vehicle, adapter, or requested reading will work. OBD-II support varies by vehicle, and OBD Auto displays only the readings it implements and that the connected vehicle reports as supported.

What OBD Auto can show in Android Auto

The Android Auto experience is meant to keep selected information glanceable. It can show chosen telemetry and link to fault information through phone-projected templates. It is not a mirrored copy of every phone control.

Depending on what the vehicle reports, supported live readings can include:

  • Vehicle speed
  • Engine RPM
  • Coolant temperature
  • Intake air temperature
  • Throttle position
  • Fuel level
  • Mass airflow
  • Control module voltage

You can select from one to six dashboard items and choose US customary or metric units on the phone. A reading missing from the list does not necessarily indicate a connection failure. The vehicle may not report that parameter as supported, or OBD Auto may not implement it.

The app also scans stored and pending diagnostic trouble codes. Bundled offline descriptions are shown where available. Treat those codes as diagnostic context, not as a completed diagnosis. A code can identify the system reporting a problem, but a qualified automotive professional should determine the cause and repair.

What stays on the phone

The main phone app handles the controls that should not be managed from the car screen. That includes selecting the adapter, choosing dashboard items, scanning or clearing codes, controlling trip recording, and exporting files.

Trip samples remain in memory while recording. After stopping the recording, you can choose CSV or JSON and select a destination from the Android share sheet. The current app has no account, ads, analytics, Internet permission, or configured developer endpoint. Unshared trip samples, settings, selected adapter details, vehicle readings, fault codes, and app-private session logs stay on the device.

This local design also means the app can provide its bundled fault-code descriptions without an internet connection where a description is available. Export is explicit. A file goes to the destination you choose through Android’s share interface.

How to connect OBD Auto

Set up the connection while parked.

  1. Plug a compatible Bluetooth Classic OBD-II adapter into the vehicle’s diagnostic port.
  2. Turn the vehicle on as required by the vehicle and adapter instructions.
  3. Open Android Bluetooth settings and pair the adapter with the phone. Android’s Bluetooth setup guidance separates finding paired devices from discovering new ones, and OBD Auto connects only to an already-paired adapter.
  4. Open OBD Auto and select the paired adapter.
  5. Connect to the vehicle and choose the supported readings you want on the dashboard.
  6. Connect the phone to a compatible Android Auto host for the projected car-screen view.

Pairing and connecting are separate steps. Seeing an adapter in Android’s paired-device list confirms that Android knows the device. It does not confirm that the adapter is compatible, that the vehicle is responding, or that a particular reading is supported.

If the adapter is paired but OBD Auto will not connect

Work through the connection chain from the adapter to the app:

  1. Check the adapter type. Confirm that it supports Bluetooth Classic. A BLE-only or Wi-Fi-only adapter will not work with OBD Auto.
  2. Check the vehicle state. Make sure the adapter has power and the vehicle is in the state required for OBD communication.
  3. Check Android pairing. OBD Auto expects the adapter to be paired in Android settings before the app connects.
  4. Check the selected device. If several Bluetooth devices are paired, verify that OBD Auto is using the OBD-II adapter.
  5. Separate connection from reading support. If the app connects but a parameter is absent, that can be a support limitation rather than a Bluetooth problem.

Avoid changing several parts of the setup at once. Confirm adapter type, pairing, app connection, and vehicle-reported readings in that order. This makes it much easier to identify where the failure occurs.

Use fault clearing carefully

OBD Auto allows a clear request only while connected and stopped, after displaying a warning. Clearing codes erases stored fault information, and it does not repair the condition that caused the code. Before an emissions inspection, check local requirements rather than assuming the vehicle is ready. The California Bureau of Automotive Repair’s OBD test reference explains that readiness-monitor status is part of the inspection and limits how many incomplete monitors may pass.

Read the codes first and preserve any information you may need. If a warning light, vehicle message, or drivability problem indicates a safety issue, follow the vehicle manufacturer’s guidance and have the vehicle inspected. OBD readings can be late, incomplete, unsupported, or wrong, so they should not be the sole basis for a safety decision or proof of vehicle condition.

The same caution applies while driving. Start trip recording before moving. Do not use phone controls to configure the app, scan or clear codes, start or stop recording, export files, or manage the adapter while the vehicle is moving. Glance at Android Auto only when it is safe and legal.

Is OBD Auto the right fit?

OBD Auto fits a specific setup: an Android phone, an OBD-II vehicle, a compatible Bluetooth Classic adapter, and, for the car-screen view, a compatible phone-projected Android Auto host. It is designed for drivers who want selected live readings on Android Auto while keeping detailed setup, scanning, recording, and export controls on the phone.

It is not the right fit for an Android Automotive OS installation, a BLE-only adapter, or a Wi-Fi-only adapter. If your hardware matches the supported path, see the current feature list, requirements, safety guidance, and launch status on the OBD Auto product page.