From 0901e601b53b79e5ff37d9aed7acd4291a6ce9dc Mon Sep 17 00:00:00 2001 From: Matthew Xie Date: Wed, 16 Nov 2011 17:14:36 -0800 Subject: Call notifyIncomingA2dpConnection with correct rejected status notifyIncomingA2dpConnection was called with wrong rejected status. Fix this. bug 5626476 Change-Id: Ie8e4a8bdc6f6357a62172c86c21ee547376952a4 --- core/java/android/server/BluetoothEventLoop.java | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'core/java/android/server/BluetoothEventLoop.java') diff --git a/core/java/android/server/BluetoothEventLoop.java b/core/java/android/server/BluetoothEventLoop.java index aa62cd7..a2038c9 100644 --- a/core/java/android/server/BluetoothEventLoop.java +++ b/core/java/android/server/BluetoothEventLoop.java @@ -784,12 +784,12 @@ class BluetoothEventLoop { // machine. We don't handle AVCTP signals currently. We only send // intents for AVDTP state changes. We need to handle both of them in // some cases. For now, just don't move to incoming state in this case. - mBluetoothService.notifyIncomingA2dpConnection(address, true); + mBluetoothService.notifyIncomingA2dpConnection(address, false); } else { Log.i(TAG, "" + authorized + "Incoming A2DP / AVRCP connection from " + address); mA2dp.allowIncomingConnect(device, authorized); - mBluetoothService.notifyIncomingA2dpConnection(address, false); + mBluetoothService.notifyIncomingA2dpConnection(address, true); } } else if (BluetoothUuid.isInputDevice(uuid)) { // We can have more than 1 input device connected. -- cgit v1.1