Bluetooth: Changing vendor ID as Qualcomm for Device ID Profile

As per Specification, Device providers should configure the
vendor ID as the Company Identifier provided by the Bluetooth
SIG. Hence Changing vendor ID as Qualcomm for Device ID Profile.

Change-Id: I852113d2849ea4fd0725396fc92f320101aab0d0
CRs-Fixed: 547495
Bluetooth: Avoid overlapping Disconn commands from Host

In case the host doesnt reply to the pairing request,
and waits for the timeout, the timout causes a "disconnection"
and is folllowed by another one by SMP state machine,
at the pairing complete event. This changed adds a check,
to ignore the disconnect command, in case another one is in progress
to the same link

Change-Id: Ib71740bed80375fb44487e89600f05519cd58b10
CRs-Fixed: 546854
Bluetooth: Reject unspported AVRCP commands

DUT sends accepted response to some of unsupported
AVRCP Pass through commands like F1, left , Right,
left up. Changes are made to ensure DUT sends response
as not implemented for unsupported AVRCP commands.

Change-Id: I5ed4844d05abedd927081f4890df20769a775930
CRs-Fixed: 551638
Bluetooth: Filter out random type LE address from storing in cache

Random type MAC addresses are not required to store in database
as they changes their address very frequently. Removes scan device
entries from database which are not bonded and have rolling
Bluetooth mac address.

This avoid bluedroid crash when LE Scan runs continuously.

Change-Id: Ib6214c5b92ba34d595378d6d0d1457e7860b9e1a
CRs-Fixed: 551716
Bluetooth: Passing the correct parameter as hci_handle on modeChange.

if sco disconnect  is waiting for the mode change on particular ACL.
then need to pass the hci_handle instead of hci_status.

CRs-Fixed: 554757
Change-Id: Icf20ff00012a616b7b8aaef7d35124c9afff35b1
Bluetooth: Interleave scan intervals change for optimum results

In case of interleave scan, the scan intervals need to be short
at the start and increase for the last two portions.
This will help discovery of more number of devices.

Change-Id: I026207a3ae700583dd0c68e273cb1ba61ee5bee3
CRs-Fixed: 557624
Bluetooth: Cleaning up pan_conn DB, if connection is not successful.

A case where DUT is paired with remoteDeviceA &  remoteDeviceB.
remoteDeviceA is not pagable(turned off or some other reason).
DUT(PANU) try to connect remoteDeviceA(NAP). But connection is
unsuccessful, Because remoteDeviceA is not pagable, In this scenario
btpan_conn Database is not cleaning up at btif layer. Later
remoteDeviceB(PANU) connect to DUT(NAP) & connection is succesful,
When remoteDeviceB disconnect existing connection. As database
still has remoteDeviceA BD address at Btif layer. remoteDeviceA
BD address is passed instead of remoteDeviceB BD address from Btif
to UI. So remoteDeviceB still shows connected on UI. Cleaning up
pan_conn database for particular pan connection at BTIF layer,
whichever connection is not successful will solve this issue.

Change-Id: I31dfe3ef46295e74bbfb57563e4fd4fc7155f006
CRs-Fixed: 555310
Bluetooth: Saving remote trust value in config file.

Add change to set the trust value for remote device and saving it
to config file after updating the trust property value.

Change-Id: I7d20318a3ab398576da185ba3426b843cb359a1c
Merge "Bluetooth: Passing the correct parameter as hci_handle on modeChange."
Merge "Bluetooth: Avoid overlapping Disconn commands from Host"
Merge "Bluetooth: Filter out random type LE address from storing in cache"
Merge "Bluetooth: Interleave scan intervals change for optimum results"
Merge "Bluetooth: Saving remote trust value in config file."
Bluetooth: Handle getCapability failure for Incoming Connection

This change takes care of handling GetCapability failure event for
Incoming Connection. DUT will initiate disconnect if GetCapability
response is failed.

Change-Id: Icc121739cc3da6f999a09f2e576cbfaec3007155
CRs-fixed: 506864
Bluetooth: Reset data profile registration during socket cleanup

This patch fixes the regression caused by commit
30b0a2d049e17d1c47050798080a3cfdff15614c where data profile registration
was being reset during cleanup_rfc_slot() API which is called after
each successful data profile transfer which prevented changing viibility
mode after data transfer was complete. With this patch now data profile
registration is being moved to btsock_rfc_cleanup() API which is called
when BT is being turned off.

Change-Id: Ife13779b586f3bf42dc8760120832233117f35bc
CRs-Fixed: 567903
Bluetooth: Check A2dp device priority.

Check for device priority in stack before sending connect
request on time-out for remote open event.

Change-Id: I191f5f3089d7945cbd6facc223a341452462421c
CRs-Fixed: 510957
Bluetooth: Retain the old COD if already present

Retain the old COD as the initial value if the device
entry already present in the list and entry is not in use.

CRs-Fixed: 546135
Change-Id: I99b7269b1976ef7458c6568441e6e3c1e015a75f
Merge "Bluetooth: Reset data profile registration during socket cleanup"
Merge "Bluetooth: Changing vendor ID as Qualcomm for Device ID Profile"
Merge "Bluetooth: Retain the old COD if already present"