Compatibility

Know what connects before you buy.

OBD-II adapters may look similar while using different wireless transports, chipsets and command behavior. Skorost keeps adapter transport, standard OBD-II support and manufacturer-aware coverage separate so compatibility is easier to understand.

ANDROIDBluetooth Classic

Pair through Android first, then select the paired adapter in Skorost.

ANDROIDBluetooth LE

Discover and connect to compatible nearby BLE adapters directly from the Scanner workflow.

ANDROIDWi-Fi

Join the adapter network and connect to the adapter host and TCP port configured in Skorost.

Before buying

Choose the adapter for the transport you actually want to use.

"ELM327" describes a command interface, not one guaranteed piece of hardware. Quality and behavior vary widely between adapters sold under that label.

01Choose the connection type firstBluetooth Classic, Bluetooth LE and Wi-Fi use different connection flows.
02Prefer a reputable adapterLow-cost clones can misreport versions, omit commands or behave inconsistently even when the casing looks identical.
03Expect vehicle-dependent dataA successful adapter connection does not mean every standard PID, monitor or sensor is exposed by every vehicle.
04Separate generic from enhanced diagnosticsStandard OBD-II and manufacturer-specific ECU access are different layers with different coverage.
Connection matrix

Three supported Android adapter workflows.

These are the three adapter connection types supported by Skorost on Android.

Adapter typeSetupSkorost connectionNotes
Bluetooth ClassicPair in AndroidSupportedCommon with traditional ELM327-style adapters. Another diagnostic app may block the connection if it already owns the adapter.
Bluetooth LEScan nearby in SkorostSupportedNo traditional Android pairing is normally required for compatible BLE adapters.
Wi-FiJoin adapter networkSupportedThe correct local host and TCP port depend on the adapter.
Vehicle coverage

Connection success and data support are two different things.

Once the adapter responds, Skorost still has to ask the vehicle for data. Standard OBD-II availability depends on what the vehicle and responding ECU expose.

Standard OBD-II

Generic emissions diagnostics

Stored, pending and permanent trouble codes, readiness, freeze frame, supported PIDs and vehicle information are available only when the connected ECU exposes those standard services and values.

Live data

Only supported channels appear

RPM, speed, coolant temperature, boost and other values depend on the supported PID set reported by the vehicle. Skorost does not invent unavailable channels.

Vehicle age / market

OBD requirements vary

OBD-II or EOBD availability depends on vehicle model, market and production year. A physical diagnostic connector alone does not guarantee the same standardized data on every car.

Enhanced diagnostics

Verified manufacturer profiles, not guessed coverage.

Manufacturer-specific diagnostics can access more data than standard emissions OBD-II. Skorost adds verified support gradually and keeps these profiles read-only while coverage expands.

SUPPORTED PROFILE

BMW / MINI

Read-only ECU discovery and enhanced fault-memory reading are available for supported BMW / MINI CAN profiles, with standard OBD-II used as the safe fallback where appropriate.

SUPPORTED PROFILE

Volkswagen Group

Read-only module discovery covers a curated set of common Volkswagen, Audi, Škoda and SEAT/Cupra modules. Enhanced fault-memory reads are limited to confirmed responders.

EXPANDING

More manufacturers

Other manufacturer families may be recognized by the app, but recognition is not presented as enhanced diagnostic support until the request flow has been verified.

Good to know

What compatibility does not mean.

It does not guarantee every ECU in the vehicle will answer.It does not guarantee every live sensor is standardized or available.It does not turn a generic ELM327 adapter into a manufacturer dealer tool.It does not imply coding, programming or state-changing manufacturer functions.
iOS later

A native iOS version of Skorost is planned. Its final adapter compatibility will be documented separately when the iOS Scanner implementation is ready, so this page currently describes Android support.

Already have an adapter?

Connect it and let Scanner show what responds.

Explore Scanner