Which adapters are supported?
ECUtilities supports ELM/STN-compatible Bluetooth and Wi-Fi adapters. USB/OTG serial support is being added as a beta transport for compatible Android devices and adapters, including the OBDLink EX.
Compatibility answers for testers and vehicle enthusiasts. This page describes the current app and clearly separates active features from items still being evaluated or developed.

Adapter support depends on both the Android device and the hardware used by the OBD interface.
ECUtilities supports ELM/STN-compatible Bluetooth and Wi-Fi adapters. USB/OTG serial support is being added as a beta transport for compatible Android devices and adapters, including the OBDLink EX.
The next development build adds Android USB-host/OTG serial support. A compatible Android device with USB host capability and the correct OTG cable is required. Real hardware testing remains part of the beta rollout.
Some do, but clone quality varies widely. Connection stability, supported commands, buffer size, and actual protocol support can differ even when two adapters use the same ELM327 label.
Generic OBD-II is standardized; many manufacturer-specific values are not.
Yes. ECUtilities supports custom read-only PID definitions including request commands, headers, equations, units, ranges, and polling settings. Current custom live polling allows read services 01, 09, 21, and 22.
Usually the same underlying PID can be recreated when its service, request, header, and equation are supported. A Torque definition may need to be entered in ECUtilities rather than imported in Torque's exact file format.
Not in the current build. Mode 23 remains outside the allowed custom live-polling services while enhanced-diagnostics safety and vehicle compatibility are evaluated.
Adapters can operate through their normal ELM-compatible command set. Proprietary ST/VT performance optimizations are not currently enabled and are being evaluated for future adapter-specific improvements.
ECUtilities sends the OBD requests required to communicate with vehicle modules, but it does not expose an unrestricted raw CAN injection or ECU-write console. Potentially dangerous write/control services remain restricted.
Yes, through the app's normal confirmed DTC-clear workflow. That is intentionally different from exposing unrestricted write commands.
Many diesel values live behind manufacturer-specific enhanced diagnostics.
Standard emissions faults can be read when the vehicle exposes them through normal OBD-II. Detailed soot load, regeneration status, exhaust temperature, and related values often require manufacturer-specific PIDs. ECUtilities can use supported custom/enhanced PIDs when the correct definition is available.
Generic powertrain DTCs may identify some SCR/DEF problems. Deeper information such as dosing, tank, heater, pressure, NOx sensor, or SCR-efficiency data varies by manufacturer and may require enhanced module access.
Yes. Closed-test feedback is being used to identify the vehicles and enhanced PID families that provide the most value for future diagnostics packs.
These items are not promised as current production features.
Not currently supported. A driver-focused Android Auto interface for selected live gauges and important vehicle warnings is being evaluated, subject to Google's Android Auto category and driver-distraction requirements.
Not currently supported. Because pre-OBD-II diagnostics were not universal, legacy support would need to be added by manufacturer/protocol and may require dedicated cables or adapters.
English is the current primary interface language. Broader localization is planned after the app's user-facing text is fully centralized and each translated layout can be tested properly.
The community is part of the same EC account ecosystem, but users control what they publish.
No. ECUniverse is an integrated community feature, but using vehicle diagnostics and utility functions does not require publishing posts or sharing a public vehicle profile.
The hardened social build restricts external sharing and feed resharing to public posts. Followers/private content remains inside the visibility rules applied by ECUniverse.
Yes. Report and block controls are being placed directly on posts, comments, and member profiles, in addition to the Settings & Safety area.
Vehicle, adapter, and manufacturer-specific questions are especially useful during closed testing.