Reduce log level for BluetoothSocket errors

This exception is also logged when the other side disconnects gracefully
(because there is no way to distinguish this case using the Bluetooth
APIs). This change reduces the log level to a warning because it is
almost always a red herring.

Test: TH
Flag: NONE yes
Change-Id: I94f20be91ff8481fdd1a50fbbc27200c57885426
This commit is contained in:
Patrick Rohr 2025-09-11 11:47:56 -07:00
commit 81a472014a

View file

@ -227,7 +227,10 @@ public class L2capPacketForwarder {
mWriteFd.write(mBuffer, 0 /*off*/, readBytes);
} catch (IOException|BufferUnderflowException e) {
Log.e(mLogTag, "L2capThread exception", e);
// This exception almost always indicates that the other side disconnected.
// Unfortunately, there is no way to distinguish between an EOF triggered by
// some disconnect or some actual error.
Log.w(mLogTag, "L2capThread exception", e);
// Tear down the network on any error.
mIsRunning = false;
// Notify provider that forwarding has stopped.