Get connected.
Get more from your vehicle.

ECUtilities is available for Android through Google Play. Use the official listing at Google Play.

Yes. ECUtilities uses a shared EC account for vehicle profiles, cloud-synchronized information, entitlements, settings, and ECUniverse. Sign in with your existing account or create one when prompted.

The main vehicle interface is designed primarily for landscape use so dashboards, diagnostics, gauges, navigation, and driving information can use the available screen width effectively.

An adapter is required for features that read live vehicle or diagnostic data. Account, vehicle-profile, ECUniverse, and some GPS-based functions can still be used without an active OBD connection.

Use a compatible ELM/STN-style OBD-II adapter supported by your Android device. Bluetooth and supported USB/OTG adapters are the primary connection options. Adapter quality matters: low-quality ELM327 clones can be slow, unstable, or falsely advertise capabilities.

With the vehicle safely parked, plug the adapter into the OBD-II port and switch the ignition to the required position. Open ECUtilities, choose your adapter/connection method, allow any requested Android permissions, and start the connection. ECUtilities will establish the adapter link and then communicate with the vehicle ECU.

The OBD and ECU indicators show the two-stage connection. Red means disconnected, flashing yellow means that stage is connecting, and green means connected. The adapter must connect first; ECU communication follows.

Check that the ignition is on, the adapter is fully seated, the correct connection method is selected, and another app is not already using the adapter. Some vehicles also require the engine to be running before certain data becomes available.

Open Live Data and use the PID selection controls for the gauge or data tile you want to change. The searchable/filterable PID picker lets you choose supported standard, custom, or enhanced parameters available for your setup.

Yes. Your selected Live Data layout is designed to persist so you do not need to rebuild it every time you reopen the app.

Yes, where supported. Custom/enhanced PID tools are intended for advanced users who know the request, header, equation, unit, range, and polling requirements for the vehicle data they want to read.

Yes. ECUtilities supports customizable dashboards, movable widgets, gauge options, vehicle profiles, and multiple interface skins. Some advanced customization features require Pro.

Connect to the vehicle, open Diagnostics, and start a fault-code scan. ECUtilities will request supported diagnostic trouble codes from the vehicle and present the results with the information available for each code.

Yes. Use the confirmed clear-codes workflow in Diagnostics. Clearing a code does not repair the underlying problem, and some monitors or learned values may reset, so use the function only when appropriate.

Freeze-frame data is a snapshot of selected vehicle conditions captured when a fault was recorded. When the vehicle exposes it, ECUtilities can show this information to help provide context for a diagnostic code.

Start a data-logging session from the appropriate Live Data/logging controls before or during your drive or diagnostic session. Stop the session when finished and save the log for later review or export.

Yes. Supported logs can be exported as CSV so they can be reviewed outside the app or shared for diagnostic analysis.

The debug export is intended for troubleshooting ECUtilities itself. It packages diagnostic information that can help DriftLine support investigate connection, device, or app issues. It is separate from your normal Live Data CSV logs.

Dyno provides an on-road performance estimation tool using available vehicle and motion data. Results are estimates and can be affected by vehicle information, road grade, traction, weather, GPS quality, sensor data, and configuration.

Yes. ECUtilities supports power-unit preferences so performance information can be viewed in the units you prefer.

Performance leaderboards are being developed for ECUniverse. The planned system will distinguish verified ECUtilities performance results from ordinary user-posted claims so rankings have a trustworthy data source.

Dashcam can record supported device cameras and combine video with selected vehicle-data overlays. Available cameras and recording capabilities depend on the Android device.

Android requires explicit permission for hardware and file access. Only grant the permissions needed for the recording features you intend to use.

Passenger Mode lets another supported device connect to the ECUtilities Host device and view permitted vehicle telemetry. It is useful for passenger devices, secondary displays, Android head units, co-driver monitoring, and track/performance use.

No. Passenger Mode is intentionally read-only. The Host device owns the physical OBD connection and controls the telemetry made available to connected Passenger devices.

Connected Services covers metered online functionality such as navigation and live posted-speed-limit services. It is separate from Pro because these services create ongoing mapping and data costs.

No. Connected Services and Pro are separate entitlements. You can subscribe to Connected Services without purchasing the Pro lifetime upgrade.

Yes. ECUtilities navigation supports saved destinations such as Home and Work along with route planning and guidance.

ECUniverse is the community side of the EC ecosystem. It includes profiles, vehicle pages/builds, posts, media, follows, notifications, safety controls, and automotive Crews, using the same account as ECUtilities.

Yes. Visit social.driftlinemedia.ca to access the web version of ECUniverse.

No. ECUniverse includes visibility and privacy controls. Only share information you are comfortable publishing, and review your profile/post visibility before posting.

Crews are automotive communities inside ECUniverse. Public crews can be joined directly, while private crews use join requests. Crew owners and admins can manage membership. Crew activity and crew-vs-crew performance rankings are planned as the next expansion.

Confirm the adapter has power, the ignition state is correct, Android has granted the required Bluetooth/USB permissions, the correct adapter is selected, and no other OBD app is using it. Disconnect/reconnect the adapter and retry before changing advanced settings.

Not necessarily. Vehicles vary widely in what they report. A PID may be unsupported, require a manufacturer-specific request, be exposed by a different ECU/module, or only become valid under certain operating conditions.

OBD-II data is polled over a limited connection. Update speed depends on the adapter, protocol, number of selected PIDs, ECU response time, and whether enhanced requests are being used. Reducing the number of simultaneously polled values can improve responsiveness on slower setups.

Use the DriftLine contact page for product and support inquiries. If the issue is technical, include your Android device, vehicle year/make/model, adapter model, ECUtilities version, what you expected to happen, and what actually happened. A debug export is especially helpful when available.