Android与自研设备蓝牙连接数分钟后停止接收字节的原因探究

Hey there, let’s dig into why your Android device stops receiving Bluetooth data from your custom hardware after 1-7 minutes—this is a super common pain point with Android’s Bluetooth stack, and it sounds exactly like the issue bboydflo described. Here are the most likely culprits and fixes:

1. Android的省电机制在“搞事情” #

Android is obsessed with saving battery, especially on newer versions (8.0+ with Doze Mode and App Standby). If your connection is only one-way (device sending data to Android with no response), the system might misjudge it as an idle connection and kill it to save power. Different devices and Android versions have varying timeout thresholds, which explains the 1-7 minute range you’re seeing.

Fixes:

• For BLE connections: Use BluetoothGatt.setCharacteristicNotification() to keep the connection active, and make sure you’re acknowledging notifications with BluetoothGatt.writeDescriptor() (the CCCD descriptor).
• For classic Bluetooth: Send a small "heartbeat" packet from Android to the device every 30-60 seconds—even a tiny empty payload will tell the system this connection is in use.
• Ask users to add your app to the battery optimization whitelist (use ACTION_REQUEST_IGNORE_BATTERY_OPTIMIZATIONS to prompt them).

2. 输入流读取逻辑有漏洞 #

If your code for reading the Bluetooth InputStream is flawed, it might get stuck or terminate silently, making it look like Android stopped receiving data. Common issues include:

• Blocking reads without handling exceptions (e.g., if the connection drops mid-read, the thread might hang).
• Buffer sizes that are too small for the data your device is sending, causing the buffer to overflow and stop accepting new data.
• Running read operations on the main thread (which will get blocked and eventually cause ANRs, leading to system intervention).

Fixes:

• Always run Bluetooth read operations in a dedicated background thread (use Coroutines, avoid deprecated AsyncTask, or a plain Thread).
• Implement a loop that continuously reads from the stream, and handle IOException gracefully (restart the connection if needed).
• Use a buffer size that matches your device’s data chunk size—try 1024 or 2048 bytes as a starting point, and adjust based on your hardware’s output.

3. 蓝牙资源未正确释放或栈存在厂商bug #

Android’s Bluetooth stack can be finicky, especially with custom devices. If you’re not cleaning up resources properly, the system might run out of handles and force the connection closed. Also, different manufacturers (Samsung, Xiaomi, etc.) have their own custom Bluetooth implementations that might have bugs.

Fixes:

• In your app’s lifecycle callbacks (like onDestroy()), make sure to close BluetoothSocket, InputStream, OutputStream, and BluetoothGatt instances properly. Never leave these hanging.
• For BLE connections: When reconnecting, always create a new BluetoothGatt instance—reusing old ones can cause unexpected behavior.
• Test on multiple devices and Android versions to narrow down if the issue is specific to a manufacturer or OS release.

4. 应用进程被系统杀死 #

This is probably the issue bboydflo was referencing. If your app is running in the background without a foreground service, Android’s memory management will kill it when system resources are low. Once the process dies, your Bluetooth receiving thread stops with it.

Fixes:

• Implement a foreground service to keep your app alive while the Bluetooth connection is active. You’ll need to show a persistent notification (required by Android’s rules) to let users know the app is running in the background.
• Minimize memory usage in your app—avoid memory leaks, use efficient data structures, and don’t run unnecessary background tasks.

调试小技巧 #

• Check Logcat for clues: Filter logs with tags like Bluetooth, BluetoothGatt, or ActivityManager. Look for messages like "Disconnecting due to inactivity" or "Process com.your.package killed".
• Add logs on your custom device to confirm it’s still sending data—rule out the possibility that the device is stopping transmission.
• Use Android Studio’s Profiler to monitor your app’s memory usage and thread activity while the connection is active.

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