| 4d08a485db5021638b0abcb8675ba00579bd7fcc |
|
07-Jul-2015 |
Sanket Padawe <sanketpadawe@google.com> |
Add Null checks while processing pairing cancel intent
Use case: Exception while handling pairing cancel
Intent received
1. Initiate pairing from DUT to remote
2. Power off DUT after getting pairing popup
Root Cause:Crash observed in settings application
Change-Id: Ia05fe196ecf6a1d4ec26f85b0cf984e23089c728
Fix: Fixed by adding Null check in PairingCancelHandler
/frameworks/base/packages/SettingsLib/src/com/android/settingslib/bluetooth/BluetoothEventManager.java
|
| 107cb81f9054a406b94e249c99fd7d64be71faec |
|
25-Jun-2015 |
Jason Monk <jmonk@google.com> |
Merge "Make BluetoothEventManager listen to ALIAS_CHANGED" into mnc-dev
|
| d2b033aeb4123ec92892495c262e0272ffb7ecdc |
|
04-Jun-2015 |
Pavlin Radoslavov <pavlin@google.com> |
Add a missing check for null pointer.
There is a race condition when processing intents inside
PairingCancelHandler.onReceive() that could trigger NPE.
A speculative list of events (untested) that could trigger it:
1. Trigger Pairing Cancel for a Bluetooth device.
2. Turn Off Bluetooth
This should call CachedBluetoothDeviceManager.onBluetoothStateChanged()
and should remove the device from (1) from the list of cached devices
3. BluetoothEventManager.PairincCancelHander.onReceive() receives
an intent about about Pairing Cancel event.
Within the processing of that intent, cachedDevice.getName()
is called without checking whether cachedDevice is null.
In this specific example, cachedDevice could be null because of (2)
Bug: 21368124
Change-Id: I86f5d5287b440d1d2e0fe147278b1c2257902e95
/frameworks/base/packages/SettingsLib/src/com/android/settingslib/bluetooth/BluetoothEventManager.java
|
| 8c495be48fc6973cc291fb4e6200154e2f28d571 |
|
03-Jun-2015 |
Jason Monk <jmonk@google.com> |
Make BluetoothEventManager listen to ALIAS_CHANGED
Bug: 20341903
Change-Id: Ibc0836bfd7f033f57ff6ae9c3ccce22fd92595f3
/frameworks/base/packages/SettingsLib/src/com/android/settingslib/bluetooth/BluetoothEventManager.java
|
| 744cf647f71b1e5a012a90ef195bf2c3c486f418 |
|
19-May-2015 |
Jason Monk <jmonk@google.com> |
SysUI: Move BT receivers to bg
Bug: 19520495
Change-Id: I58e7d023b9eaf67fccd1634e00803c8c8d871fff
/frameworks/base/packages/SettingsLib/src/com/android/settingslib/bluetooth/BluetoothEventManager.java
|
| be3c5dbee66758517a8198f98ed2e20c80af326b |
|
04-Feb-2015 |
Jason Monk <jmonk@google.com> |
Make QS use SettingsLib's BT code
A couple of changes needed to be made to SettingsLib to support this.
- SettingsLib needed to track ACTION_CONNECTION_STATE_CHANGED
- The summary code needed to move from Settings up into SettingsLib
- Added a getMaxConnectionState to CachedBluetoothDevice
- This simplifies the states of all of the profiles into
one.
Change-Id: I7f828f0038ad0cf39274986ece6d486d545f0286
/frameworks/base/packages/SettingsLib/src/com/android/settingslib/bluetooth/BluetoothEventManager.java
|
| 7ce96b9e610de2782ec5f2af806e7bc0f90c8578 |
|
02-Feb-2015 |
Jason Monk <jmonk@google.com> |
Move non-ui bt settings code to SettingsLib
Mostly this is moving classes from Settings to SettingsLib but there
were a few changes to support this separation.
- A bunch of things became public rather than package
- Moved some settings only code out of these classes
- Added error callback to handle errors
To see the changes from original classes view the diff against
patch-set 1.
Bug: 19180466
Change-Id: I69fd888362c6dbb325f6113b32c4b15cc6a23a41
/frameworks/base/packages/SettingsLib/src/com/android/settingslib/bluetooth/BluetoothEventManager.java
|