7fa4fba6f59f97df00aff07dbe8fb21b114b3c2c |
|
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 Conflicts: stack/btu/btu_hcif.c
/external/bluetooth/bluedroid/btif/include/btif_storage.h
|
0977fc84e0314b7b71668885a433f5ad4b6ec49c |
|
26-Feb-2014 |
Matthew Xie <mattx@google.com> |
am e736740d: am 5834e63b: am 759280ee: Merge "bluetooth: hid: store ssr_max_latency and ssr_min_tout in bonding db" into klp-modular-dev * commit 'e736740ded718c76c0007baa97b7f55e69ceb1b1': bluetooth: hid: store ssr_max_latency and ssr_min_tout in bonding db
|
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/include/btif_storage.h
|
8a82348c04109cb85e3c0b676dd1c7c5cb461c24 |
|
27-Jan-2014 |
Adam Hampson <ahampson@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/include/btif_storage.h
|
ead3cde4bac0c3e32cd31f149093f004eef8ceeb |
|
06-Feb-2013 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Initial version of BLE support for Bluedroid Change-Id: I9825a5cef9be2559c34c2a529b211b7d471147cf
/external/bluetooth/bluedroid/btif/include/btif_storage.h
|
5738f83aeb59361a0a2eda2460113f6dc9194271 |
|
13-Dec-2012 |
The Android Open Source Project <initial-contribution@android.com> |
Snapshot cdeccf6fdd8c2d494ea2867cb37a025bf8879baf Change-Id: Ia2de32ccb97a9641462c72363b0a8c4288f4f36d
/external/bluetooth/bluedroid/btif/include/btif_storage.h
|