BT ConnectTrack records when your already-paired Bluetooth devices connect or disconnect, with timestamps and optional location. It listens to the system’s own connect and disconnect broadcasts and logs them without any app-side filtering.
This app is intended for devices that emit system connect or disconnect events, such as headphones and headsets using A2DP or HFP, car audio systems, classic speakers, and other devices that broadcast these events. It can work with Bluetooth Classic and with some BLE devices only if the device and operating system actually broadcast those events.
This is not a scanner or a “find my device” tool. It does not initiate connections, pair devices, or keep a live BLE session solely to detect state changes.
New in this version: CSV export lets you save your history to the Downloads folder for backup or analysis. The app now records all system-broadcast connect and disconnect events with no app-side filtering. The actual logs you see depend on whether the device broadcasts these events.
Important notes: Many BLE-only accessories, including smart tags, AirTag-type accessories, and some fitness bands or sensors, may not broadcast connect or disconnect events to third-party apps unless the app initiated the BLE connection. These devices may not appear in the log. Some manufacturers’ battery optimizations can restrict background receivers; for best reliability, allow the app to run in the background by whitelisting it from battery optimization.
How to use: First pair your devices in Android Bluetooth settings. Grant Bluetooth permissions. Allow Location only if you want location tags in entries. For consistent background logging, exempt the app from battery optimization. When system broadcasts are available, the app will automatically log connect and disconnect events.
Privacy: The app has no internet access and all data stays on your device. You can view, export to CSV, or delete your history at any time.
Compatibility: Android 8.0 or later is required. Behavior may vary by device, operating system, and manufacturer. Logging depends on device behavior and system broadcasts.