Skip to main content

Overview

The Mikey Android SDK enables mobile applications to communicate with compatible Cartrack in‑vehicle terminals over Bluetooth Low Energy (BLE) for short‑range vehicle access and status retrieval.

What you can do​

  • Connect to a nearby BLE terminal associated with a vehicle.
  • Perform supported actions (for example, lock and unlock).
  • Retrieve supported vehicle status and statistics.
  • Receive connection state, signal strength, and action callbacks.

Where to start​

  • The SDK package is provided on request: see Request SDK access.
  • Follow the Integration guide from top to bottom: prerequisites, installation, configuration, key, connection, actions, callbacks and errors, disconnection. The demo app in the SDK package follows the same steps.
  • If something does not behave as expected, check Troubleshooting.
  • Use the API Reference pages for details on the core classes and enumerations.

Privacy and data​

The SDK collects no data. It makes no network connections and sends nothing to Cartrack or to anyone else: it talks only to the terminal, over Bluetooth.

  • Stored on the phone: only the vehicle's authentication key saved with saveAuthKey(), encrypted with a key held in the Android Keystore, in your app's own storage. removeAuthKey() deletes it.
  • Location: the SDK checks that the location permission is granted and that location services are on, because it needs them for Bluetooth scanning. It never reads the phone's location.
  • Identifiers: the SDK reads no device, advertising or user identifier.
  • Logs: the SDK writes diagnostic lines, such as the terminal name and the commands sent, to the phone's system log (logcat). They stay on the phone.

The SDK itself therefore adds nothing to your app's Google Play Data safety form.

Important notes​

  • BLE capabilities, permissions, and behavior vary by Android version and device.
  • Command availability depends on vehicle hardware and provisioning.