Sync Preference in UI for new cached device

Use Case: Inquiry results not updated to UI when A2DP
streaming is initiated.

Failure: Inquiry results updated to settings APP but
it's not reflecting in UI.

Steps:
1. A2DP streaming from DUT.
2. OPP Rx initiated from remote.
3. Initiating inquiry from DUT.

Root Cause: No callback to UI to sync the preference
parameter of new cached device in DeviceFoundHandler class.

Fix: Create preference in UI whenever new cached device is added.

change-Id: Ib02f953f4dc6e3a74fac70442dc7959504ca9374

Bluetooth: Handle user switch with new states

When user switch occurs, BT is toggled. However since the state
change callbacks are disabled, state never moves forward from
STATE_BLE_ON. This causes toggle timeout, causing recovery.
This change handles the case by manually causing the state
change handling during the wait period.

Change-Id: I635421440d262a7d51d5955c15343d65dc1ae32c

BT: Update wait function in ManagerService to handle  BLE states

-> The wairforOnOff method while waiting for on/off event to
   occur doesn't takes BLE states into account. Since Bluetooth
   Manager Service needs to takes action to completely turn On
   or completely turn off Bluetooth when BLE turns ON, this
   intermediate state to handle BLE On State need to be handled
   at Manager Service to avoid waitforOnOff timeout.

-> Replaced the waitforOnOff method with waitForMonitoredOnOff
   which handles state changes while waiting.

-> In an another change, after receiving Enable Message, added
   condition to wait for off event only when Bluetooth is being
   disabled, no need to wait for Off while enabling Bluetooth
   because this serialization is handled at Adapter State.

change-Id: I83dd6c8b28b819b1f305ba45853d56a685eccc4e

BT: Set persiste Bluetooth State during enable timeout case

Use case: When enable timeout occurs during S&S testing and
Bluetooth state is moved from Turning On to Off.

Steps: Changes related to enable timeout case, to test the
changes, S&S testing can be done.

Failure: Changes done to handle Bluetooth enable timeout
case when Bluetooth state changes from Turning On to Off.

Root cause: Setting Bluetooth Persist state to handle the
enable timeout case so that Bluetooth doesnot self enable
after enable timeout case is handled.

Fix: Setting the Bluetooth Persist State to Off when enable
timeout occurs.

change-Id: I17b3b05020eb7469666e6d8c88c86df7764b4024

BT: Rectifying recovery functionality in case of timeout scenarios

-> When timeout occurs, Bluetooth Manager Service tries to
   recover by restarting the Bluetooth process.
-> Since stopping of Bluetooth process is already handled
   at Adapter State level, here we only need to send the
   message to start the service is not already started.
-> Trying to stop the service may result in dead object
   leading to failure in Bluetooth enable process.

change-Id: If8c72763451d42ade6618bff823f1a832325913e

BT: Fix for BT enable after User Switch

Bluetooth state is not moved past BLE On state if
BLE app count more than zero.
Added additional condition to check Bluetooth
Persist case in such scenarios.

change-Id: I91ba0e7630a5f1f705d821e2cd0d4ad2088efc3e

Bluetooth: Handling BLE disable during device power off.

Problem: When device is turned off, Shutdown thread initiates
Bluetooth disable. However, in case of BLE on, Bluetooth does
not turn off and ultimately process is killed by the framework
Once Bluetooth process is killed, BluetoothManagerService take
it as a abnormal termination and initiates  Bluetooth enable again.

Fix: To fix the issue, the disable method, when called as part
of shutdown sequence, need to reset ble app count. Further, it
need to send appropriate signal to AdapterService to completely
turn ooff Bluetooth based on current state.

change-Id: I4a3bc6b4f584373d1afd5f61e6acdbc31d6e2ef9

BT: Always update service object in BluetoothDevice Class

Problem: In case service down callback is missed, the service
object is not reset. This causes the object to miss the update
when Bluetooth Service again comes up causing Dead Object
Exception when used.

Cause: When the apps using BluetoothDevice Class are inactive
or killed, they can miss the ServiceDown callback. Because of
NULL check, the object is not updated on receiving the service
up callback.

Fix: Removed the condition to always update the Service object
on receiving the Bluetooth Service Up callback.

change-Id: I8cf0f316fb4f8a1df17b7e5476b0cb3bd580fff1

BT: Limiting the thread lock to critical part of state update

Issue: ANR occurs due to UI wait for long time waiting to
acquire thread lock.

Cause: The synchronized function that updates state also
read paired devices as an additional operation. When the
number of devices is cached list is large, the block time
for other threads waiting for same lock tends to increase
causing ANR in case of UI thread.

Measure: Limited the synchronized block to the part where
actual update of local state takes place.

change-Id: I69ff9f8a032b3772bf3d048d8db70181319ad31d

change-Id: I6b15f7cac51799188f5e9e31d908406e502741c0

Bluetooth: Prioritize Bluetooth state change intent to start Service

Set FLAG_RECEIVER_FOREGROUND flag, then recipient will be allowed to
run at foreground priority hence Bluetooth state change intents are
usually prioritized. So service will be loaded and started earlier.

change-Id: I0ae5e2a60a5655cce04c78c397444a469885dad4

Bluetooth: Persist BT On with BLE app concurrency

If user turn on BT from settings menu When BT state is BLE On
(BLE app running in backgroud),it never persists BT on state.

This fix make sure to persist bt on state with BLE app concurrency.

change-Id: I1eb9e8e1267879ae2c4c120e47f8b0485af576c9
CRs-Fixed: 2016553

Bluetooth: Avoiding NULL pointer dereferences

getDeviceClass method accessed from bluetooth class
without any null check and leading to exception
in sns test.

Hence added null check while accessing getDeviceClass

change-Id: Ie1a541a13b7a78a068ff4d4c98cd277949863ad2
CRs-Fixed: 2058747

SettingsLib: Added a new function to clear all devices from cache

  - Added a function to remove all bluetooth devices form cache

change-Id: Icf7b56f7978e9f629456d276116709d565184f8c
CRs-fixed: 2084834

BT: Add new intent to broadcast IOT device details

This intent will be used to broadcast IOT device details
when IOT related issue is encountered.

CRs-Fixed: 2109009
change-Id: I5eb97e3e2835a5acf3b2edb6c3d29e9da81bdc75

BT:killed due to null pointer exception..

Reason: Trying to access remote device
object (mobjectdevice)which have been set to NULL before.

Fix:Avoid handling state changes for invalid devices(NULL)

change-Id: If21cf7a3059a7942dcfa5b2cbe568810fa4676a9
CRs-Fixed: 2121814

Move BT state to OFF when BLE app count is zero

During processing of disableBLE, move BT state to
OFF when BLE is enabled(state is BLE ON) and the
BLE app count is zero.

change-Id: I427aa54330bb00e9b4cf06c50428a17fbaae1fda

Bluetooth: catch exception when unlinkToDeath

In rare cases, linkToDeath failed. Then when calling
unlinkToDeath, NoSuchElementException will be thrown, which
leads to system server termination.

change-Id: I2dbf794d1a5c65dd1a55a9d038f688f4e833dc82
CRs-Fixed: 2129413

Bluetooth: Fix for Global reference table overflow issue[1/2]

 -  To avoid RemoteCallbackList object leaks in Bluetooth Manager
    Service, Added unregister API in BluetoothAdapter.java which
    internally calls unregisterAdapter of Manager Service

CRs-Fixed: 2138560
change-Id: I58ce5f5e1b86d87e0ff602b453abb74d0b5e1982

BT: Resetting mEnableExternal to false when BLE app count is zero

- Added a logic to reset the value of mEnableExternal
  varible to false, When no BLE app is present
  and BT status is BLE ON state.

change-Id: I5645799c13f42b1e23270cdb10894b3307668f5e

Bluetooth: Don't remove UUIDs if profile in connected state

If any external triggers sdp service search after profile
connections, Some remotes don.t give UUIDs of already connected
profiles.

If settings removes connected profiles from UI, user can't
disconnect remote from UI.

Hence don't remove already connected  profiles from UI.

change-Id: I7d65cf1b37c7caa7583ee03bf2befaee5b22cf6c
CRs-Fixed: 2174306

Bluetooth: Fix to handle FATAL Exception when A2DP SINK is enabled

Usecase:
Turn on Bluetooth. (On service discovery)

Issue:
Systemui process killed.

Root Cause:
NULL pointer exception on mA2dpProfile.getConnectionStatus as
A2DP Sink is enabled.

Fix:
This change will ensure that when UI is updated on UUID change
and A2DP Sink is enabled, condition to check A2DP Source connection
state and UUID check wont be invoked.

Change-Id: I521063d6e4fd0a9ad94f5e4924f64368905f0b1b
CRs-Fixed: 2203965

0 files changed, 0 insertions, 0 deletions