2d789e58a8d2665b980fa952ba233cdde40f0157 |
|
12-Dec-2011 |
Matthew Xie <mattx@google.com> |
Move broadcastState STATE_TURNING_ON before persistSwitchSetting CTS test revealed that persistSwitchSetting could take more than 1 second. STATE_TURNING_ON intent missed the test timing. We move the broadcast before persistSwitchSetting bug 5740715 Change-Id: I54a0a0afc8d1c4fc28f84e6122809af2f1456ca7
/frameworks/base/core/java/android/server/BluetoothAdapterStateMachine.java
|
a6ba6fd4bb931ba7c1cbda6adc8452609ea80dac |
|
06-Dec-2011 |
Matthew Xie <mattx@google.com> |
Broadcast turning on/off intent as early as possible when switch on/off BT Move broadcastState(BluetoothAdapter.STATE_TURNING_ON/OFF) before any other method calls when turn on/off Bluetooth. Bug 5703346 Change-Id: Iddbdab58367a7d648708aa23671eb09701d66793
/frameworks/base/core/java/android/server/BluetoothAdapterStateMachine.java
|
9de1feb673499519cb380a142ba1e453109480bd |
|
03-Oct-2011 |
Matthew Xie <mattx@google.com> |
Send TURN_HOT message to the state machine from BluetoothService after it starts All the messages sent to the StateMachine were ignored before the StateMachine starts. To avoid TURN_HOT message from being ignored, move it out to BluetoothService to send to the BluetoothAdapterStateMachine after the state machine starts bug 5333923 Change-Id: I14ccd6dd7e6430aad2bca9230d01578b5327cc3f
/frameworks/base/core/java/android/server/BluetoothAdapterStateMachine.java
|
dcbc97fc28f4eb5910acc11dfac5efcd597c737d |
|
17-Sep-2011 |
Matthew Xie <mattx@google.com> |
Check null of pidPair to skip the case the service record has been removed Check null of pidPair instead of pidPair.first which caused a nullpointer exception. clean local variables after sending out STATE_OFF intent. Check bluetooth state in removeServiceRecord. bug 5330367 Change-Id: Ib0af8143223bea48d3f587cca18544c4aef29980
/frameworks/base/core/java/android/server/BluetoothAdapterStateMachine.java
|
694c0b833b4235b396ec1b798610d617d0ec7b5c |
|
08-Sep-2011 |
Matthew Xie <mattx@google.com> |
Apply timeout for powerdown event and reset state machine when bluez crashes The powerdown event was missed some time for unknown reasons and bluez could crash for unknown reasons. We will debug on the issue. But for the time being, we add a powerdown timer and process power up event to recover from bluez crash bug 5239719 Change-Id: Ie7315fb01e029747951e1a97a2d2f1dce53a997b
/frameworks/base/core/java/android/server/BluetoothAdapterStateMachine.java
|
25c4e2a8032c38f6336f7f49e464c95c7b8798f2 |
|
16-Aug-2011 |
Matthew Xie <mattx@google.com> |
Change prepare bluetooth timeout from 7 seconds to 10 seconds It was observed that the preparing bluetooth could take up to 8 seconds before the SD loaded event came in. Change-Id: I722f94ed9cbd12bdd033ca405838366139c61383
/frameworks/base/core/java/android/server/BluetoothAdapterStateMachine.java
|
14e48e91f6def5448db9994cb13ddcdc676cba53 |
|
15-Aug-2011 |
Matthew Xie <mattx@google.com> |
Implement switchConnectable with Powered property setting instead of scan modes Bluez powered property setting is more apropriate for what this method intend to achieve and it fixes a bug that incoming connection request wake up the stack in The pairable events are replaced by power and discoverable events HotOff state bug 5080232 Change-Id: I43b44cb2f5203bd99bf764d5a1696e8ff52a31db
/frameworks/base/core/java/android/server/BluetoothAdapterStateMachine.java
|
9a943a64202aba8f885b2c736183bf53276a23df |
|
03-Aug-2011 |
Matthew Xie <mattx@google.com> |
Add a timeout for disconnecting devices to recover from error situation Start the timer (3 second) just after calling disconnect devices. If the timer expires, it indicates an error condition. we don't wait on the ALL_DEVICES_DISCONNECTED event upon the error. Instead, get out of switching state and turn off BT to reset out of the error condition. Change-Id: I27aa8cd7b6fe50d9191e2d32fc2d6eac50424403
/frameworks/base/core/java/android/server/BluetoothAdapterStateMachine.java
|
8594394aadeaaa3f834d33d7b198fb071e0f31fe |
|
30-Jul-2011 |
Matthew Xie <mattx@google.com> |
Move mBluetoothService.runBluetooth after broadcasting the STATE_ON intent. This is because broadcastState method move the Bluetooth adapter state to ON. The mBluetoothService.runBluetooth should be called only in the ON state. Remove mIsDiscovering variable in BluetoothService. Fix a bug in BluetoothA2dpService that caused 2 times of state change from DISCONNECTED to CONNECTING that messed up BluetoothService's connection state count. Change-Id: Ifb782a845ae70f007d2e036d930bb55f445d68b5
/frameworks/base/core/java/android/server/BluetoothAdapterStateMachine.java
|
ef2cb7c93a99096799d415e721dda46d1bf7a005 |
|
22-Jul-2011 |
Jaikumar Ganesh <jaikumar@google.com> |
Add ability to turn BT on / off on a per application basis. This changes adds an API for system applications to enable bluetooth without all the side effects like auto connection to headsets etc. Also some tweaks to the adapter state machine Change-Id: Ib9f22d548a26d72334b300101c8eb0d80f08a4bb
/frameworks/base/core/java/android/server/BluetoothAdapterStateMachine.java
|
7f9ecca8f2dc288f785b37d2478e89b80fc3cefc |
|
15-Jul-2011 |
Matthew Xie <mattx@google.com> |
Keep Bluetooth module hot to quickly swith it on/off Add BluetoothAdapterStateMachine to maintain a inter state machine other than the public BluetoothAdapter states. This is a improvement to BluetoothService code. 2 internal state are added, LoadingFirmware and FirmwareLoaded to place the Bluetooth module in a ready-to-switch-on state so that it can be quickly switched on to have a better user experience bug 5021787 Change-Id: Ia352e88cba509d9e98c900f85e7479f8cee1de5e
/frameworks/base/core/java/android/server/BluetoothAdapterStateMachine.java
|