| 5e808468e0667a6a2a8a1e6de80efbc4f42fa0f0 |
|
21-Oct-2014 |
Andre Eisenbach <eisenbach@google.com> |
LE: Do not remove bond on encryption failure
If the encryption fails during the re-connection process with a
previously paired LE device, the pairing is removed. Thus, a single
connection failure could lead to the device be unpaired.
This patch prevents unpairing when encryption fails.
Additionally, the IRK is restored from NV ram to fix reconnection to
dual-mode devices.
Bug: 18072300
Change-Id: I077a16d0715fdaa07b95b1c664c18bd839754896
/external/bluetooth/bluedroid/btif/src/btif_storage.c
|
| afa6e1abbedaad8fe854b0f43999b8aeb801af91 |
|
28-Jun-2014 |
Matthew Xie <mattx@google.com> |
resolved conflicts for merge of e8c3d75b to master
Change-Id: I78ef69c4d54a36243620ae14296d3507e3339567
|
| d5ebf6b695a5b40563b5fddca97c0591e39557f1 |
|
28-Jun-2014 |
Matthew Xie <mattx@google.com> |
handle link key check in non_ble case
Change-Id: Ibbdf3c4fbff9e53f8e2a85db9d6de62cd2925c60
/external/bluetooth/bluedroid/btif/src/btif_storage.c
|
| e8c3d75b75493911ebf0f99c83676359657178f7 |
|
04-May-2014 |
Sharvil Nanavati <sharvil@google.com> |
Logging cleanup: BTIF and APPL.
Change-Id: I5b1214642bbb4b9aecc0fd2c899a6ec2c9793286
/external/bluetooth/bluedroid/btif/src/btif_storage.c
|
| f281b43fbf6832b80651e0dbf300294ba9808f20 |
|
15-May-2014 |
Priti Aghera <paghera@broadcom.com> |
Reload Hid info only for bonded device
Check if the device is bonded before loadind HID device information
after BT reset. If the HID info exists in NVRAM for unbonded device,
the device will not be able to repair.
bug 14837902
Change-Id: I5e6d5e8c5344ca8ae18f102e40867745d3f460ab
/external/bluetooth/bluedroid/btif/src/btif_storage.c
|
| 479a9a3750e243b40663ddbd1ac44d4fc1c3ec4e |
|
04-Jun-2014 |
Sharvil Nanavati <sharvil@google.com> |
Parse auto_pair_devlist.conf file with the generic config parser.
Change-Id: Idfd1aca2417d74725a8f9ac67b1ca946a33bf14d
/external/bluetooth/bluedroid/btif/src/btif_storage.c
|
| ed999f5e92ef9e718f4e6a5d6e68caf1001961c8 |
|
05-Jun-2014 |
Matthew Xie <mattx@google.com> |
Save remote device name immediately
bug 7381249
Change-Id: Ief1910c608116ebc28f5dc3e5804be65797ec53c
/external/bluetooth/bluedroid/btif/src/btif_storage.c
|
| 1025687c6679608fe9df918f37011414ffc72b62 |
|
19-Aug-2013 |
Hemant Gupta <hemantg@codeaurora.org> |
[2/4] Bluetooth: Add support for HFP Client role.
Implementation changes in BTA and BTIF layer to support
HFP Client role.
Change-Id: I9f939c18e8f989a50f298d0b313c5a0959c030a7
/external/bluetooth/bluedroid/btif/src/btif_storage.c
|
| 740def526e757f5ea8f30d9d28d1e7a668dadc42 |
|
04-May-2014 |
Sharvil Nanavati <sharvil@google.com> |
Eliminate dead code (helped by compiler warnings).
I've removed all functions that the compiler decided were unused.
Change-Id: I0cbddf874ebd1586abe29b80e8d6390680679542
/external/bluetooth/bluedroid/btif/src/btif_storage.c
|
| fbf76881316471faf631dc543089efaeaf72df8d |
|
06-Jan-2014 |
Hemant Gupta <hemantg@codeaurora.org> |
GAP: Update local device name immediately
Though the function btif_config_set_str requests to
save device name immediately, sometimes it doesn't
call save device name if the cached changes are more.
So calling the "btif_config_save" explicitly to avoid
failure cases.
Change-Id: I9fb05caf284d6a6feb906f87a4db19896182d2c9
/external/bluetooth/bluedroid/btif/src/btif_storage.c
|
| 8fe58875ce67c6e1099e7ba2339dcd2b979491b0 |
|
17-Apr-2014 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Merge BT 4.1 features
The features include:
- LE Peripheral Mode
- Link Layer topology (LE Central & Peripheral Concurrency)
- Dual Mode Topology (Ability to choose LE transport when connecting with
other Dual Mode devices)
- Fast advertising Interval
- Limited Discovery Time Changes
- GAP Authentication and Lost Bond
- Dual Mode Addressing
- Common Profile and Service Error Code
- 32 bit UUIDs
Change-Id: Ic6701da4cf6aaa390ff2c8816b43157f36b7fb42
/external/bluetooth/bluedroid/btif/src/btif_storage.c
|
| a7ea809912e5a945d657957491753260826422f4 |
|
27-Nov-2013 |
Zhihai Xu <zhihaixu@google.com> |
Bluetooth: GAP: Remove bonded device info on Authentication fail
Remove bonded device information from the BT-IF layer storage
on authentication failure if already bonded with just works
model.
from QCOM
Change-Id: Ia3c1635c446f39b1dbd4cdd0122c2f70cbbc8dd7
/external/bluetooth/bluedroid/btif/src/btif_storage.c
|
| 6efaf223753108aa84f55332898340db0c9d5ebf |
|
27-Jan-2014 |
Zhihai Xu <zhihaixu@google.com> |
bluetooth: hid: store ssr_max_latency and ssr_min_tout in bonding db
Store the ssr_max_latency and ssr_min_tout parameters in the
bonding database. Previously these parameters were not stored for HID
devices. This caused an inconsistency in sniff behavior between
when the HID device was paired and following a reboot of the host.
When the HID device is paired the SSR parameters are retrieved
from the HID device and are stored in the HID Host's device list.
If the host is rebooted then the HID Host's device list is
constructed from the bonding database.
If the SSR max latency is non-zero then the SSR parameters are
sent to the firmware and SSR is used. In the event that the SSR
max latency is 0, as it is if the parameters are not found, then
SSR is disabled.
Bug: 12764547
Change-Id: I63637575fdfcf4cb4ca0ce8dc2e4ccda9cccaf66
Signed-off-by: Adam Hampson <ahampson@google.com>
/external/bluetooth/bluedroid/btif/src/btif_storage.c
|
| 7e6b379268f973752863e333b55e6068373e1664 |
|
24-Feb-2014 |
Matthew Xie <mattx@google.com> |
am 9d368b68: am 1292dd82: am 6bc62a36: Merge "Bluetooth: GAP: Update bonded device info immediately on NVRAM"
* commit '9d368b68841dee6e6f581a3890433dcdc022fbb8':
Bluetooth: GAP: Update bonded device info immediately on NVRAM
|
| 1292dd82812d76c54568796fbdafd1fdadc816eb |
|
24-Feb-2014 |
Matthew Xie <mattx@google.com> |
am 6bc62a36: Merge "Bluetooth: GAP: Update bonded device info immediately on NVRAM"
* commit '6bc62a368da0a434a4e01f7bcb3273bd52a07568':
Bluetooth: GAP: Update bonded device info immediately on NVRAM
|
| 377cb1407ee6ee1ff91b15bfa7052abed1023d18 |
|
20-Nov-2013 |
Sunny Kapdi <sunnyk@codeaurora.org> |
Bluetooth: Cleanup bt_config.xml during BLE Scan
BLE Scan needs to clean up the bt_config.xml periodically so that
new entries could be added to bt_config.xml. Also, there is no
need to add BLE Random bd_addr to the bt_config.xml
Change-Id: I00ba2e50dd39a021099052cb569786f6cb2cc8b9
b/12912008
/external/bluetooth/bluedroid/btif/src/btif_storage.c
|
| 5e08d1ec92555e2cb3d80f1a9a3c746c76ed3e5d |
|
21-Nov-2013 |
Srinu Jella <sjella@codeaurora.org> |
Bluetooth: GAP: Update bonded device info immediately on NVRAM
As the new bt-if config updation have delay in writing items
to the NVRAM, some times there is a chance of not updating
incase of battery removal happens before the actual write onto
NVRAM.
As the bonded device info is important data to store, it will
update bonded info immediately onto NVRAM.
Change-Id: I9699c8225a77d9272420334b4c76b3c1df87e459
/external/bluetooth/bluedroid/btif/src/btif_storage.c
|
| 2a2701cdddac0859a95e58aec542742c450145b9 |
|
16-Sep-2013 |
Kim Schulz <k.schulz@samsung.com> |
Fixes for problems found with coverity analyzer
- fixed UNINITIALIZED variable (hdl) in bta_hh_act.c :220
- fixed possible RESOURCE LEAK in btif_config_util.cpp in relation to open_file_map() if file is fd size=0
- fixed possible RESOURCE LEAK in create_socket_server() in uipc:196 (s not closed)
- fixed possible OVERRUN in l2c_csm.c, (l2c_csm_config), array "l2cb.fixed_reg" of 4 20-byte elements at element index 60 (byte offset 1200) using index "p_ccb->local_cid - 3" (which evaluates to 60)
- fixed possible OVERRUN in btm_pm.c, (btm_pm_reset) array "btm_cb.acl_db" of 7 288-byte elements at element index 7 (byte offset 2016) using index "btm_cb.pm_pend_link" (which evaluates to 7).
- fixed possible OVERRUN in btif_storage.c, (btif_storage_add_device_to_autopair_blacklist) array "input_value" of 20 bytes by passing it to a function which accesses it at byte offset 20 using argument "20U".
patch set 2:
- fixed {}
Patch set 3:
- fixed review commment in stack/btm/btm_pm.c:379
bug: 10777562
Change-Id: I2a6d57f93acaaf9b25c49a6a29cb60d0e1e3c5d8
/external/bluetooth/bluedroid/btif/src/btif_storage.c
|
| b0a43da3b412f53557125bf352dd9dddfd1a9991 |
|
24-Sep-2013 |
Kim Schulz <k.schulz@samsung.com> |
memset arguments wrongfully swapped
the arguments for one of the memset calls was wrong.
Bug: 10907215
Change-Id: Ie00a3a6b829b99fd94659a764b6f0309684d9303
/external/bluetooth/bluedroid/btif/src/btif_storage.c
|
| 7939ed0c9a50c769e9e648a2d7751e0894b485ed |
|
28-Sep-2013 |
zzy <zhenye@broadcom.com> |
added filter remove api to control the # of child node for bt_config.xml
Bug 10949832
Change-Id: I10589b9d0a0b4b8d7cbf66122c66bb2e99be04a1
/external/bluetooth/bluedroid/btif/src/btif_storage.c
|
| 76d041f915e4c14b3fb11bae3c12fcb59f77bef5 |
|
10-May-2013 |
Matthew Xie <mattx@google.com> |
am e1405531: am e915116a: Merge "Solve compilation problem when BLE/GATT/SMP features are false" into jb-mr2-dev
* commit 'e1405531f637a3851371a2a2c624ff3db5e074fa':
Solve compilation problem when BLE/GATT/SMP features are false
|
| fc4b2f1953dbe60464d0f5ef7daaa10001fbc62f |
|
07-May-2013 |
Matthew Xie <mattx@google.com> |
Solve compilation problem when BLE/GATT/SMP features are false
bug 8664724
Change-Id: I582846ccf4b8995f298d8db533488fceb7993ae3
/external/bluetooth/bluedroid/btif/src/btif_storage.c
|
| 6ded3e4bc35c9878771a59cb8cc75b702c2097fd |
|
24-Apr-2013 |
Priti Aghera <paghera@broadcom.com> |
am f9020d0d: am f8f30c2c: HDP fix for Single SDP record
* commit 'f9020d0de5c8ade5fab86b26979620aac4f67dc9':
HDP fix for Single SDP record
|
| f8f30c2cecf221b2c3983b72d5a849d799c39dd7 |
|
03-Apr-2013 |
Priti Aghera <paghera@broadcom.com> |
HDP fix for Single SDP record
Modified stack code to support single SDP record
for each register app call.
bug 8656462
Change-Id: I92570243306d5c1ca8339042eba5733e43fdb72c
/external/bluetooth/bluedroid/btif/src/btif_storage.c
|
| 7fe56f58c2a3cf0ac80177aaa890c143cd5fd950 |
|
29-Mar-2013 |
Priti Aghera <paghera@broadcom.com> |
Save the HID info into storage while adding device
Previously HID device info was not saved immediately to NVRAM, thus
when device was rebooted sometimes the hid information was missing
from NVRAM, thus host does not identify the HID Device
bug 8192743
Change-Id: I7ca8b607399e141fa851242e83c1c6d3854384f8
/external/bluetooth/bluedroid/btif/src/btif_storage.c
|
| ead3cde4bac0c3e32cd31f149093f004eef8ceeb |
|
06-Feb-2013 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Initial version of BLE support for Bluedroid
Change-Id: I9825a5cef9be2559c34c2a529b211b7d471147cf
/external/bluetooth/bluedroid/btif/src/btif_storage.c
|
| 689d66b6559dcb3a0ad7f6cc33b6129e50910253 |
|
13-Dec-2012 |
The Android Open Source Project <initial-contribution@android.com> |
Snapshot 9fd57cbacd95e89602f430244c35bbc67f08b6d2
Change-Id: Ibc3a4bf4161d286c7cfab89a19c676eb5cc9224f
/external/bluetooth/bluedroid/btif/src/btif_storage.c
|
| 5738f83aeb59361a0a2eda2460113f6dc9194271 |
|
13-Dec-2012 |
The Android Open Source Project <initial-contribution@android.com> |
Snapshot cdeccf6fdd8c2d494ea2867cb37a025bf8879baf
Change-Id: Ia2de32ccb97a9641462c72363b0a8c4288f4f36d
/external/bluetooth/bluedroid/btif/src/btif_storage.c
|