Skip to main content
Bring compatible hardware

Test the adapter you already own before buying another one.

A shell color, marketplace title, or ELM327 label does not prove the transport, firmware, electrical quality, or vehicle coverage. ScanWrench performs an exact preflight and reports what responded.

01

Android connection paths

Android can evaluate compatible BLE, Wi-Fi, and supported Bluetooth Classic adapter candidates.

  • BLE service discovery
  • Wi-Fi endpoint probing
  • Supported paired Bluetooth Classic serial paths
  • Protocol and ECU-response attribution
02

iPhone connection paths

iPhone apps ordinarily use compatible BLE or Wi-Fi hardware; generic Bluetooth Classic serial profiles are not generally exposed to ordinary iPhone apps.

  • BLE is usually the simplest direct path
  • Wi-Fi can temporarily change network routing
  • Exact firmware and electrical behavior still matter
03

The five-second preflight

ScanWrench separates phone-to-adapter contact from adapter-to-vehicle evidence and reports the exact observed boundary.

  • Phone and operating system
  • Adapter candidate and transport
  • Vehicle protocol and responder
  • Requested function and returned evidence
Compare the workflow

Choose the setup that fits your decision.

ScanWrench vs FIXD ScanWrench vs BlueDriver ScanWrench vs Carly
Direct answers

Before you connect.

Does ScanWrench require its own OBD2 adapter?

No. ScanWrench is designed for compatible customer-supplied adapters and checks the exact unit at connection.

Why can the same adapter work on Android but not iPhone?

Android can expose supported Bluetooth Classic serial profiles that ordinary iPhone apps generally cannot. BLE and Wi-Fi behavior can also differ by device and firmware.

Does connecting mean every feature works?

No. Connection, generic OBD2, enhanced data, full-system access, and state-changing functions are separate levels.