diff options
| author | Marie Janssen <jamuraa@google.com> | 2016-12-15 13:51:30 -0800 |
|---|---|---|
| committer | Andre Eisenbach <eisenbach@google.com> | 2016-12-16 22:50:13 +0000 |
| commit | ed50bbcffd3a18560fc3a7d7896aab051cb9b08e (patch) | |
| tree | 8e9f40ea1923c12191d278f4d19b6746e80f452c /rs/java/android/renderscript/Script.java | |
| parent | 08bff42ef4c403a591a68e9cc039fb6d4e8f359a (diff) | |
Bluetooth: fix issues re-enabling after crash
When Bluetooth crashes, sometimes an LE app restarts it before
ActivityManager gets a chance. In this case, the Bluetooth manager
would assume the state should be LE only and did not continue to fully
enabled.
Luckily in this case the persisted system state is also ON. Use the
persisted state as information about whether we should be fully enabled.
Test: basic sanity check, forced crash of BT
Bug: 33632976
Change-Id: I546d7abccb82a26fcca2eb70d6d7c76e9510404e
Diffstat (limited to 'rs/java/android/renderscript/Script.java')
0 files changed, 0 insertions, 0 deletions