Android BLE偶发无法读写，第三方APP可恢复的技术原因问询

Great question—this is a super frustrating but common pain point with Android’s BLE stack, and that third-party app is addressing critical gaps in how your app handles connection cleanup. Here’s exactly what it’s likely doing to get your BLE functionality back on track:

• Enforcing a strict, full disconnection sequence
  Android’s BLE stack often leaves stale connections or half-open GATT instances hanging around when apps cut corners on shutdown. BLE Scanner is almost certainly following this exact flow:

  1. Calling gatt.disconnect() to properly initiate the disconnection process
  2. Waiting for the onConnectionStateChange callback to confirm the device is in STATE_DISCONNECTED
  3. Immediately calling gatt.close() to fully release the GATT instance and tie up all system resources

  Most custom apps skip waiting for the disconnect callback or forget to call close(), leaving the stack in a broken state where all subsequent operations return status 1 (GATT_FAILURE).

• Forcing a fresh cache of GATT attributes
  Android caches BLE device characteristics, descriptors, and service data to speed up reconnections. When a connection fails mid-operation, this cache can get corrupted or out of sync with the device. BLE Scanner likely uses the CONNECT_FLAG_NO_CACHE flag when calling connectGatt() (available on API 21+):

  bluetoothDevice.connectGatt(context, false, gattCallback, BluetoothGatt.CONNECT_FLAG_NO_CACHE);
  

  This forces the stack to re-discover all services and attributes from scratch instead of relying on stale cache data, which fixes those invalid status responses.

• Cleaning up orphaned GATT instances
  It’s easy to accidentally create multiple BluetoothGatt instances for the same device (e.g., if you retry connections without closing old ones). These orphaned instances clog up the BLE stack’s limited resources. BLE Scanner probably tracks and closes all active GATT instances for a device before attempting a new connection, ensuring no leftover resources are blocking operations.

• Resetting the BLE adapter’s internal state (gently)
  While you said restarting Bluetooth didn’t help, BLE Scanner might be triggering a soft reset of the adapter’s internal state through the proper disconnection flow. Unlike a full Bluetooth toggle, this targets only the problematic device’s connection context, clearing any stuck state that a full restart might not address.

Fixing Your App #

To replicate this behavior in your own app, make sure you:

1. Always follow the disconnect → wait for callback → close sequence for GATT instances
2. Use CONNECT_FLAG_NO_CACHE when reconnecting after a failure
3. Track active GATT instances and close them before creating new ones
4. Avoid calling close() before the disconnect callback completes

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