Android 8.1调用connectGatt连接BLE外设失败，回调始终显示断开

Hey there! Since you’ve got a working iOS app for the same peripheral, we can be pretty sure the issue isn’t with the BLE device itself—let’s focus on Android-specific pitfalls that might be causing your connectGatt calls to always disconnect.

Here are the most common fixes to try:

• Use a stable Context for connectGatt
  A lot of new Android devs use the Activity context when calling connectGatt, but if your "device details" Activity undergoes a configuration change (like screen rotation) or gets destroyed mid-connection, the GATT client can get into a broken state. Instead, use your app’s Application context, which stays alive for the entire app lifecycle:

  // Bad: Using Activity context (this)
  // bluetoothDevice.connectGatt(this, false, gattCallback);
  
  // Good: Using Application context
  bluetoothDevice.connectGatt(getApplicationContext(), false, gattCallback);
  

• Double-check runtime permissions (critical for Android 12+)
  Android’s BLE permissions got stricter starting with API 31. Make sure you’ve requested both BLUETOOTH_SCAN and BLUETOOTH_CONNECT at runtime, not just declared them in your AndroidManifest.xml. For older Android versions (pre-12), you’ll also need ACCESS_FINE_LOCATION (since BLE scanning relies on location services).

  Don’t forget to handle the permission request result—if the user denies BLUETOOTH_CONNECT, your app won’t be able to establish a connection.

• Verify the autoConnect parameter
  The third argument in connectGatt is autoConnect, and it’s easy to mix up its purpose:

  • Set it to false when you’re actively connecting to a device you just discovered (this is what you want for your "select device then connect" flow).
  • Set it to true only if you want the system to automatically reconnect to the device later (even if your app isn’t in the foreground).

  Using true for an immediate active connection can cause unexpected timeouts or failures.

• Inspect your BluetoothGattCallback implementation
  Make sure you’re properly handling the onConnectionStateChange callback and logging the status and newState values. The status code will tell you exactly why the connection failed—for example:

  • BluetoothGatt.GATT_SUCCESS (0) means the state change was successful.
  • Code 133 is a common "connection timeout" error, which might mean you need to adjust how you handle service discovery after connecting, or check if the peripheral has strict connection timing requirements.

  Here’s a minimal callback to start with:

  private final BluetoothGattCallback gattCallback = new BluetoothGattCallback() {
      @Override
      public void onConnectionStateChange(BluetoothGatt gatt, int status, int newState) {
          super.onConnectionStateChange(gatt, status, newState);
          Log.d("BLE_DEBUG", "Connection state changed: status=" + status + ", newState=" + newState);
          
          if (newState == BluetoothProfile.STATE_CONNECTED) {
              Log.d("BLE_DEBUG", "Connected! Starting service discovery...");
              gatt.discoverServices(); // Don't forget this step to interact with peripheral services
          } else if (newState == BluetoothProfile.STATE_DISCONNECTED) {
              Log.e("BLE_DEBUG", "Disconnected. Status code: " + status);
              // Handle disconnection here
          }
      }
  
      @Override
      public void onServicesDiscovered(BluetoothGatt gatt, int status) {
          super.onServicesDiscovered(gatt, status);
          if (status == BluetoothGatt.GATT_SUCCESS) {
              Log.d("BLE_DEBUG", "Services discovered! Now you can interact with characteristics.");
              // Get services/characteristics here
          }
      }
  };
  

• Ensure the BluetoothDevice object is valid
  If you’re passing the BluetoothDevice between Activities, make sure it’s still a valid, reachable device. Sometimes scanned devices can become unreachable if too much time passes between discovery and connection. Try re-scanning the device right before connecting, or ensure the connection is initiated immediately after selecting the device.

• Clean up old GATT connections
  If you’ve previously connected to the device, make sure you closed the old BluetoothGatt instance before creating a new one. Leftover open connections can block new ones:

  if (mBluetoothGatt != null) {
      mBluetoothGatt.close();
      mBluetoothGatt = null;
  }
  // Now create a new connection
  mBluetoothGatt = bluetoothDevice.connectGatt(getApplicationContext(), false, gattCallback);
  

Start by checking the Context and permission setup first—those are the most common culprits for new Android BLE devs. Then use the Log statements in the callback to get specific error codes, which will help narrow down the issue even more.

内容的提问来源于stack exchange，提问作者brant