Moving STATE_DISCONNECTED broadcast.
In Telecom we were seeing a bug where we received an ACTION_CONNECTION_STATE_CHANGEDSTATE intent indicating the disconnection of a bluetooth headset. The BluetoothManager in Telecom would then query the Bluetooth service to see if there are any devices. Despite being informed that the device in use was disconnected, it still showed up as connected. To fix this, I moved the state broadcast AFTER the disconnected device is removed from the headset state machine. Looking through all other disconnect broadcasts in that file, the disconnection happens AFTER in all other cases as well. Bug: 17899941 Change-Id: Ice4b2a5b1093e04ffe4c3241a3379aba56898792
Loading
Please register or sign in to comment