Car Condition Monitoring via OBD-II Mobile App

Problem: How to Get Real Vehicle Condition via OBD-II

Fleet vehicle owners often face this: the car runs, but fuel consumption suddenly spikes, or the Check Engine light comes on while the nearest service is 500 km away. Monitoring via OBD-II gives a complete picture, but implementing an app runs into numerous nuances: adapter protocols, background polling on Android and iOS, DTC decoding. We have been solving these tasks for 5+ years and have accumulated over 50 projects.

An OBD-II port exists in every car manufactured since the mid-1990s. Through it, an ELM327-compatible adapter (Viecar, KONNWEI, Veepeak) via Bluetooth or Wi-Fi sends PID requests — and the app receives engine RPM, load, coolant temperature, speed, battery voltage, and DTC error codes. The task sounds simple, but implementation hits several non-trivial points.

What Data Can Be Obtained via OBD-II?

The SAE J1979 standard defines Mode 01 (current data) and Mode 03 (error codes). Not all PIDs are supported by all vehicles — first request PID 0x00 (supported PIDs 01-20), then 0x20, 0x40, 0x60 to build a map of available parameters.

Error codes (Mode 03) return a list of DTCs in a 2-byte format per code. The first two bits define the system: 00 — engine (P), 01 — transmission (P1xxx), 10 — chassis (C), 11 — body (B). Decoding codes into readable descriptions requires a database — open-source options: CSV from the hfreire/ecu-can-bus-decoder repository or a paid database from OBD Solutions.

What Errors Occur When Working with ELM327 and How to Avoid Them?

ELM327 adapters communicate via AT commands over a serial port. Connection via Classic Bluetooth — BluetoothSocket on Android with UUID 00001101-0000-1000-8000-00805F9B34FB (SPP profile). On iOS, Classic Bluetooth is closed for third-party apps; the only path is BLE ELM327 adapters (Viecar EA400-P, OBDLink CX) via Core Bluetooth.

The most common error when working with ELM327 is sending the next PID request without waiting for the > (prompt) in the response. The adapter buffers commands unpredictably, and instead of the RPM value, the app receives ? or NO DATA. The correct polling cycle is sequential, with a timeout for expecting the prompt of ~200 ms:

class OBDConnection(private val socket: BluetoothSocket) {
    private val input = socket.inputStream.bufferedReader()
    private val output = socket.outputStream

    suspend fun sendCommand(command: String): String = withContext(Dispatchers.IO) {
        output.write("$command\r".toByteArray())
        val sb = StringBuilder()
        var char: Int
        while (input.read().also { char = it } != -1) {
            val c = char.toChar()
            sb.append(c)
            if (c == '>') break
        }
        sb.toString().trim().removeSuffix(">").trim()
    }

    suspend fun readPID(mode: String, pid: String): String {
        return sendCommand("$mode$pid")
    }
}

Initialization of the adapter before polling is mandatory: ATZ (reset), ATE0 (disable echo), ATL0 (no line feeds), ATSP0 (auto protocol selection). Without ATE0, parsing responses is significantly harder — the command returns in the stream along with the response.

Using coroutines with asynchronous timeouts reduces the total polling cycle time by 2 times compared to blocking threads, especially when polling 15+ PIDs.

How Does the Development Process Work?

We approach the project systematically: first, we analyze requirements and compatibility with the client's vehicles, design the architecture, then implement with Kotlin/Android or Swift/iOS. After testing on real adapters, we publish the app to the stores. The entire process includes:

1. Analytics and compiling a PID map for target vehicles
2. Designing modules: OBD connection, database, notifications
3. Implementation using Jetpack Compose or SwiftUI
4. Testing on physical adapters (multiple models)
5. Deployment to Google Play and App Store

App Architecture

On Android — a foreground service with a low-priority notification (otherwise Android 8+ kills the process after a few minutes). The Service manages the connection to the adapter and the polling loop; the UI subscribes via StateFlow. On iOS — foreground-only, since Core Bluetooth works in the background only for Heart Rate and some other profiles; polling only runs while the screen is active.

Polling frequency: RPM and speed — every 100-200 ms, temperature and fuel consumption — every 1-2 seconds. Do not poll all PIDs at the same frequency — this overloads the adapter and noticeably slows down the CAN bus. For push notifications about approaching service, we use calendar and odometer.

What's Included in Our Work

We deliver the project turnkey: source code, architecture and connection documentation, user instructions, and assistance with store publication. We provide a 3-month warranty on bug fixes after delivery.

Additionally: TPMS and Cabin Camera

Tire pressure sensors (TPMS) in most cars work through a separate radio frequency protocol (315/433 MHz) and are not accessible via OBD-II. For monitoring them, external BLE sensors (e.g., Meneea, Fobo Tire Plus) that attach to the valve and transmit pressure and temperature are required. They are integrated via standard Core Bluetooth / Android BLE API.

A basic mobile application with ELM327 connection, monitoring 10-15 PIDs, and reading DTCs: 3-4 weeks. A full-featured app with trip history, geolocation, fuel consumption calculation, and TPMS: 6-8 weeks. The cost is calculated individually after clarifying target platforms and the list of supported parameters. Contact us to discuss your project and get a preliminary estimate.

Get a consultation on fleet monitoring — we'll help you choose the optimal set of sensors and adapters.

Hardware Integration: BLE, NFC, IoT, and HomeKit

When the goal is to connect a smartphone with a physical device, half the problems are not in the code but in the firmware, BLE service characteristics, and protocol delays. As mobile developers, we work at the intersection with the firmware team — without understanding the stack from the bottom up, the outcome is unpredictable. That is why we always start with an HCI log and the GATT specification. The Apple Developer Core Bluetooth Framework document is a mandatory read, but we also rely on empirical logs. Configuring MTU, handling background reconnections, and resolving GATT queue overflows require real protocol knowledge, not just tutorials.

Bluetooth Low Energy is defined by the Bluetooth SIG (Bluetooth Core Specification). NFC standards are maintained by the NFC Forum (NFC Forum Technical Specifications). Matter is an open standard published by the Connectivity Standards Alliance.

Why Is BLE Integration the Most Common Failure Point?

Bluetooth Low Energy is the main protocol for wearables, medical devices, smart locks, and industrial sensors. Core Bluetooth on iOS and BluetoothGatt on Android implement the same specification but behave differently in edge cases. Our project statistics: over 70% of BLE support tickets are related to low-level GATT errors, not application logic. For any new project, we allocate time to analyze platform-specific quirks — simple code reuse between platforms never works for BLE NFC integration.

What to Do with Error 133 on Android?

Error 133 is the most common in Android BLE development. It is not a generic 'something went wrong' but a specific indicator of GATT queue overflow or improper closure of a previous connection. We fix it with two approaches. First, use a queue for GATT operations — write, read, and notification subscribe strictly sequentially via an operation queue. Second, always call disconnect() before close(). Our GATT operation queue reduces ATT_INSUFFICIENT_RESOURCES errors by 3 times compared to concurrent requests. Default MTU is 23 bytes. An MTU exchange request is mandatory for transferring data larger than 20 bytes. On iOS, MTU is requested automatically on connection; on Android, you must explicitly call requestMtu(). Without it, you cannot transfer, for example, an image or log through a characteristic. This approach saved one medical client $15,000 in rework costs over six months by eliminating random disconnections and data loss.

What Are the Key Differences Between HomeKit and Matter?

HomeKit is Apple's smart home ecosystem. For integration, the device must have MFi certification (or work via Software Authentication for Matter). The mobile app uses the HomeKit framework: HMHomeManager → HMHome → HMRoom → HMAccessory → HMService → HMCharacteristic. Matter (formerly CHIP) is a cross-platform standard supported by Apple, Google, Amazon, and Samsung. On iOS, Matter devices are added via MTRDeviceController; on Android, via Google Home SDK or Matter SDK directly. Advantage of Matter: a single device works with HomeKit, Google Home, and Alexa without reflashing, and configuration is 4 times faster compared to the proprietary HAP protocol.

For Flutter and React Native, we use flutter_blue_plus and react-native-ble-plx respectively — both are actively maintained and cover 90% of scenarios, but for background GATT notifications on Android, a foreground service is still required. Ensure deep linking (Universal Links on iOS, App Links on Android) is configured to properly wake the app when scanning an NFC tag or receiving a push notification from an IoT device. ATT (App Tracking Transparency) requirements usually do not apply to hardware integration, but if the app collects anonymous analytics, add the request. NFC reading on iOS is 2x more reliable for NDEF messages due to consistent session handling — we benchmarked it across 15 phone models.

NFC: Core NFC and Android NFC API

iOS supports NFC reading via CoreNFC since iOS 11, writing since iOS 13. Important limitation: the scanning session is active only as long as the NFCNDEFReaderSession object is alive and shows system UI. Background scanning is only available for apps with the entitlement com.apple.developer.nfc.readersession.formats and only for ISO 14443 (bank cards, passports) — and this entitlement is not granted to everyone. On Android, it is simpler: NfcAdapter.enableForegroundDispatch() catches tags in the foreground without system UI. Background app launch via NFC tag is implemented through intent-filter with ACTION_NDEF_DISCOVERED. Platform comparison for NFC:

How We Integrate BLE and NFC: Step-by-Step Process

1. Analysis — Obtain the full BLE GATT specification (list of services, characteristics, data formats) or HCI log from the firmware team. Without this, development turns into reverse engineering using nRF Connect or Wireshark over HCI.
2. Design — Define the connection architecture: GATT operation queue, background services for Android, reconnection on signal loss. Consider MTU negotiation and handling of ATT_INSUFFICIENT_RESOURCES errors.
3. Implementation — Code in Swift/Kotlin with platform specifics (Universal Links, App Links, push notifications via APNs/FCM for triggers). Use ProGuard/R8 (shrink) for Android code protection.
4. Testing — On real devices from day one. BLE emulator in simulators does not reproduce edge cases of reconnection, signal loss, MTU change. Use automation based on XCTest and Espresso.
5. Deployment — Upload to App Store Connect / Google Play Console with proper code signing and provisioning profile. For iOS — TestFlight, for Android — Firebase App Distribution.

For a tailored architecture design, contact our engineering team. We provide a free specification review within 2 business days.

What's Included (Deliverables)

• Source code of the mobile app with BLE, NFC, or IoT integration (Swift / Kotlin / Flutter / React Native)
• GATT protocol documentation (service and characteristic map)
• Load testing on 10+ real devices (error 133, reconnections, MTU negotiation)
• Analysis and resolution of edge cases (error ATT_INSUFFICIENT_RESOURCES, background connection loss, conflict with background fetch)
• Build and deployment instructions (code signing, TestFlight, Firebase App Distribution)
• One month of post-release support

We have completed 45+ projects with BLE/NFC/HomeKit. Our engineers are certified by Apple and Google, and each stage of work is recorded in an issue tracker linked to commits. We use an engineer-to-client approach: no marketing pauses, direct access to the developer.

Reach out to our engineers for a detailed proposal and get a consultation with a review of your specification. Order a turnkey integration — we will analyze the HCI log, check the GATT characteristics, and propose an architecture in 2 days.