New Title: Classic Bluetooth Setup for Android
Old Slug: /how-to-pair-a-bluetooth-3-0-elm327-device-on-windows-and-android/
Categories: Getting Started, Connection & Hardware
Last Updated: December 2025
Overview
OBDAI handles Classic Bluetooth (BT 3.0) scanning and pairing entirely within the app. You don’t need to visit Android Settings first — everything happens in OBDAI.
Looking for Windows setup? See our Complete Windows Setup Guide.
Requirements
Before connecting:
- Android 8.0 or higher (Oreo+)
- Classic Bluetooth OBD2 adapter (ELM327-based, BT 3.0/2.0)
- Adapter plugged in to your vehicle’s OBD2 port
- Ignition ON (engine running or ACC position)
Required Permissions
OBDAI will request these permissions on first launch:
| Permission | Why It’s Needed |
|---|---|
| Bluetooth | Communicate with your OBD2 adapter |
| Location | Required by Google’s Android API for Bluetooth scanning (Google requirement, not OBDAI) |
| Network | AI features, vehicle lookup, cloud sync |
⚠️ Location Permission Note: Google requires Location access for ANY app that scans for Bluetooth devices. OBDAI doesn’t track your location — this is purely a platform requirement.
Step-by-Step Setup
1. Open OBDAI and Grant Permissions
Launch OBDAI. If prompted, allow:
- Bluetooth access
- Location access (required for BT scanning)
- Network access
2. Select Classic Bluetooth Mode
- Tap the gear icon (⚙️) to open Settings
- Under Connection Type, select Classic Bluetooth
- The scan button will change to “Scan for Classic BT”
3. Scan for Your Adapter
- Make sure your adapter is plugged into the vehicle
- Turn ignition ON
- Tap “Scan for Classic BT”
- Wait for the scan to complete (up to 20 seconds)
Your adapter should appear with a name like:
- OBDII
- OBD2
- VGATE
- Veepeak
- ELM327
4. Pair Your Adapter (First Time Only)
- Tap your adapter in the device list
- If not already paired, OBDAI will prompt: “Pairing Required”
- Tap “Pair”
- Android will show a PIN dialog
- Enter the PIN code: 1234, 0000, 7890, or 1111
- (Check your adapter’s documentation if these don’t work)
- Tap OK or Pair
Once paired, the adapter will show as “Paired Device” in future scans.
5. Connect to Your Vehicle
- Tap “Connect”
- OBDAI will:
- Connect to your adapter
- Initialize communication with your vehicle’s ECU
- Discover supported sensors and data
Connection typically takes 5-15 seconds.
Common Adapter Names
| Adapter Name | Type | Notes |
|---|---|---|
| OBDAI | OBDAI Gen 1 | Our recommended adapter (BLE + Classic support) |
| OBDII BLE | OBDAI Gen 2 | Premium adapter with expanded protocol support |
| OBDII | Generic | Common ELM327 clone |
| VGATE | VGate iCar | Popular aftermarket brand |
| Veepeak | Veepeak | Popular aftermarket brand |
| ELM327 | Generic | May or may not work depending on chip quality |
Troubleshooting
Adapter Not Found in Scan
- Check adapter is powered: LED should be lit when plugged in with ignition ON
- Move closer: Classic Bluetooth range is ~30 feet, but obstacles reduce it
- Restart adapter: Unplug for 10 seconds, plug back in
- Scan again: Tap “Scan for Classic BT” to refresh
Pairing Fails or PIN Rejected
- Try all common PINs: 1234, 0000, 7890, 1111, 6789
- Check adapter documentation: Some adapters use unique PINs
- Forget and re-pair: Go to Android Settings > Bluetooth, tap your adapter, select “Forget,” then try pairing again in OBDAI
Connection Times Out
- Verify ignition is ON: Some vehicles require engine running
- Check adapter compatibility: Very cheap ELM327 clones may have unreliable chips
- Try BLE mode: If your adapter supports BLE, try that instead (more reliable on modern phones)
“Location Permission Required” Error
Google’s Android API requires Location permission for Bluetooth scanning. This is a platform requirement — OBDAI doesn’t track or store your location.
- Go to Android Settings > Apps > OBDAI > Permissions
- Enable Location (set to “Allow” or “While using the app”)
- Return to OBDAI and try scanning again
Why OBDAI Handles Pairing In-App
Previous versions required manual pairing through Android Settings. The current version scans and pairs directly within OBDAI, which:
- Eliminates confusion about where to pair
- Auto-detects adapter type (BLE vs Classic)
- Prioritizes known OBD adapters in scan results
- Handles PIN entry through native Android dialogs
Recommended Adapters
For the best experience with OBDAI, we recommend our purpose-built adapters:
OBDAI Gen 1 Bundle — $59.99
- Supports both BLE and Classic Bluetooth
- No aggressive power management (stays connected reliably)
- 1 year Premium subscription included
OBDAI Gen 2 Bundle — $119.99
- Supports both BLE and Classic Bluetooth
- Expanded protocol support (ISO + SAE J1850)
- Custom OBDAI branding
- 1 year Premium subscription included
Both adapters are tested and optimized for OBDAI.
BLE vs Classic Bluetooth: Which Mode Should I Use?
Many OBD2 adapters support both Classic Bluetooth (BT 3.0) and BLE (Bluetooth Low Energy 4.0+). The problem? Packaging rarely makes this clear, and identical-looking adapters may support different protocols.
If you’re not sure which mode your adapter supports:
- Try BLE mode first (more reliable on modern phones)
- If your adapter doesn’t appear, switch to Classic Bluetooth mode and scan again
- If neither works, your adapter may be defective or incompatible
OBDAI Gen 1 and Gen 2 adapters support both modes — use whichever you prefer. We recommend BLE for most users (lower power consumption, faster pairing).
Still Having Issues?
- Check our Connection Troubleshooting Guide
- Contact support via the in-app chat widget
- Email: support@obdai.app