| 76f0078459f751ddb4a85adf89b86a801c05f328 |
|
10-Nov-2016 |
Jakub Pawlowski <jpawlowski@google.com> |
BLE OOB Pairing - parse address type (1/5)
When address type is not parsed, creating bond to devices not using
random address is impossible.
Bug: 32780409
Test: try pairing with nRF52DK using random address
Change-Id: Idc0315e9e3f9e17c3cf56fa483c8e21eb3590f01
(cherry picked from commit 7921e8f594079e00e90173a8fe7483ad72443b34)
/system/bt/stack/include/btm_ble_api.h
|
| 59e0b06149584a9ded4efe4de5c24d0e84535fd0 |
|
28-Jul-2016 |
Jakub Pawlowski <jpawlowski@google.com> |
Add LE Secure Connection data parsing (3/4)
Bug: 30460956
Change-Id: I216142090fe99b25ef7697fceceb278b761a182b
/system/bt/stack/include/btm_ble_api.h
|
| bfc90ee868b042aa245eed8305047b35bddfdc5c |
|
27-May-2016 |
Jakub Pawlowski <jpawlowski@google.com> |
Add minimum LE connection timeout that can be used for HID devices
Fixes: 28979841
Change-Id: I520608a13224601fb9101d00c08b34cdb0f8d374
/system/bt/stack/include/btm_ble_api.h
|
| 78bcff79e1b1f0efce436b33bdd6da88745bfc8a |
|
05-Dec-2015 |
Pavlin Radoslavov <pavlin@google.com> |
Refactor the Bluetooth timers
* Updated the alarm API:
- Existing API alarm_new() is modified to take an alarm name
as an argument.
- New API alarm_new_periodic() is used to create a periodic
alarm.
- Added new API alarm_is_scheduled() to test whether an alarm is
scheduled.
- Existing API alarm_set_periodic() is removed: a periodic
alarm is created by alarm_new_periodic().
- Added new API alarm_set_on_queue() to set an alarm whose
callback is executed on a specific queue.
- Added new API alarm_register_processing_queue() and
alarm_unregister_processing_queue() to register/unregister
a queue and the corresponding thread for alarm processing.
- Added corresponding unit tests.
* Updated the alarm internals:
- Added alarm_info_t for collecting alarm-related information
and statistics.
- Collect and store alarm-related statistics into alarm_info_t
per alarm.
- Include the alarm-related statistics and info into the native
dumpsys output for Bluetooth.
- Once an alarm expires, the alarm execution is scheduled for
processing on another internal alarm-specific thread, not
on the thread that is maintaining the alarms.
- Implemented callback execution ordering guarantee among
timers on the same thread with exactly same timeout values.
* Refactor some of the usage of alarm_set() and simplify the
code by using alarm_set_on_queue() instead.
* Removed the non_repeating timers wrapper, and use directly
the alarm mechanism / API.
* Refactored all timer_entry_t timers and replaced them with alarm_t
timers:
- Replaced the btu_start_timer() / btu_stop_timer() /
btu_start_quick_timer() / btu_stop_quick_timer() /
btu_oneshot_alarm() mechanism with alarm_set_on_queue() and
alarm_cancel()
- Removed the whole mechanism around the BTU_TTYPE_* timers.
* Fixed a bug when processing the GATT indication confirmation timer
expiration (timer tGATT_TCB.conf_timer: b/26610829).
* Renamed and/or split misc. timeout functions, fields, and timers
* Renamed time-related constants and changed the values from seconds
to milliseconds
* Replaced timer tAVDT_CCB.timer_entry with three mutually exclusive timers:
idle_ccb_timer, ret_ccb_timer, rsp_ccb_timer
The reason we are using three timers, is because in the original code
function avdt_ccb_chk_timer() used the timer type in its logic: it
would stop the timer only if the type is "idle".
* Removed btm_ble_timeout() and replaced it with multiple timeout
callback functions (per timer)
* Fix the actual value of the global constant BT_1SEC_TIMEOUT and
rename it to BT_1SEC_TIMEOUT_MS
* Removed btu_cb and associated timers and events, because they are
never used.
* Removed unused timers, functions, struct and declarations that are
not used / needed.
Bug: 26611369
Bug: 26610829
Change-Id: I812c8c31710a5daefc58b01fcf35c353768f390f
/system/bt/stack/include/btm_ble_api.h
|
| 258c2538e3b62a8cdb403f2730c45d721e5292b4 |
|
28-Sep-2015 |
Pavlin Radoslavov <pavlin@google.com> |
GKI cleanup - moved GKI buffer allocation wrappers to OSI
* Moved the following GKI buffer allocation functions to OSI:
- GKI_getbuf() -> osi_getbuf()
- GKI_freebuf() -> osi_freebuf()
- GKI_get_buf_size() -> osi_get_buf_size()
For now we need the osi_getbuf() / osi_freebuf() allocation wrapper,
because we need to be able to call osi_get_buf_size() on the allocated
buffer.
In the future those should be replaced with osi_malloc() / osi_free().
Currently, the osi_malloc() buffer size internal allocation tracker
does not always track the size, hence we need the osi_getbuf() wrapper.
* Replaced GKI_MAX_BUF_SIZE with BT_DEFAULT_BUFFER_SIZE
* Added new file include/bt_common.h that can be usee to include
few files that should be included alost everywhere (e.g. bt_target.h"
NOTE: This file might be removed in the future and we should include
everywhere the right set of header files.
* Removed some of the GKI-related references
* Removed file include/gki_target.h
Change-Id: Ie87830e73143de200746d54235aa99f228a95024
/system/bt/stack/include/btm_ble_api.h
|
| 9f1c9ad85759c7663e3bbc494f8e75b2f107da67 |
|
28-Sep-2015 |
Pavlin Radoslavov <pavlin@google.com> |
GKI cleanup - Moved struct TIMER_LIST_ENT to OSI
* Moved struct TIMER_LIST_ENT to file osi/include/non_repeating_timer.h
and renamed it to timer_entry_t
NOTE: This is a short-term solution. timer_entry_t should be
removed, and its usage everywhere should be replaced by
struct non_repeating_timer_t .
* Renamed TIMER_CBACK to timer_callback_t
* Renamed TIMER_PARAM_TYPE to timer_param_t
Change-Id: I9ca830718bf900195f9c0a513a97f6995322693b
/system/bt/stack/include/btm_ble_api.h
|
| 1a1b3ebb41aa89f0ab38ea6ef41444f7f9b010f5 |
|
24-Aug-2015 |
Ian Coolidge <icoolidge@google.com> |
am bc6ad53e: Merge "Improve adv_data transfer between contexts."
* commit 'bc6ad53e310c2b6b1734883e8d92f5c147279d23':
Improve adv_data transfer between contexts.
|
| d4c103624b3d7672110abeb753ed79113ee48989 |
|
08-Aug-2015 |
Ian Coolidge <icoolidge@google.com> |
Improve adv_data transfer between contexts.
- Drops some unused members from btgatt_multi_adv_inst_cb.
- Flatten tBTA_BLE_ADV_DATA to only require one allocation.
- Copy all of tBTA_BLE_ADV_DATA contents to bt_workqueue_thread.
Bug: 23042223
Change-Id: I5f4d25d5cdd39731a2dfe64394928b7fb77c7c7c
/system/bt/stack/include/btm_ble_api.h
|
| 76356aee883af67898ddc1aa3b628195f396d42a |
|
21-Apr-2015 |
VenkatRaghavan VijayaRaghavan <venkatrv@broadcom.com> |
Bug fix PM changes and LE connectivity mode fixes
Allow PM to support multiple delay timer for different profiles and
power mode requests. And set correct connectivity mode.
Bug: 22040710
Change-Id: Idabd9ea944f0c5a89ce542d85db9f103fa7d1816
/system/bt/stack/include/btm_ble_api.h
|
| 71334dcd2c58564a195dade1f862f052ecd07b50 |
|
10-Jul-2015 |
Andre Eisenbach <eisenbach@google.com> |
Do not reject valid connection parameter updates
As a side-effect to increasing BTM_BLE_CONN_INT_MIN, valid connection
parameter updates can be rejected if the requested minimum is < 11.25ms,
but the requested maximum is >= 11.25ms.
This patch introduces a new parameter "BTM_BLE_CONN_INT_LIMIT" and
resets BTM_BLE_CONN_INT_MIN to the HCI spec defined minimum.
Bug: 22245224
Change-Id: I6a2e4d18488b63570f7d0070413d00f16a7fdba1
/system/bt/stack/include/btm_ble_api.h
|
| 579fa2a950f21f3e5808a2d060afebbf5e8f0732 |
|
27-May-2015 |
Prerepa Viswanadham <dham@google.com> |
Increase the min LE connection interval to 11.25ms
To reduce audio choppiness, increase the min LE connection interval
to 11.25ms from 7.5ms
Bug: 18776956
Change-Id: I8404ebe2f9562d555a2131ae30dd63b74bb362a4
/system/bt/stack/include/btm_ble_api.h
|
| 1f38e92c7045e92b6b9d7f31bf85ceb585733885 |
|
22-Apr-2015 |
Satya Calloji <satyac@broadcom.com> |
Unpair the other transport on a device paired
When unpair is initiated for LE or BR-EDR transport for a device,
close the link for other transport and unpair the device on
both transports, since both transports on a device are paired
due to cross key.
Original author: Priti Aghera <paghera@broadcom.com>
Change-Id: I13d4757eb056c4bd4c7cc0699ec61a28852702c5
/system/bt/stack/include/btm_ble_api.h
|
| 70b9598970e5b18ba53c282319e68faea6eb5681 |
|
24-Apr-2015 |
Satya Calloji <satyac@broadcom.com> |
Static address is seen on scanner after unpairing
Fix for bonded devices that cannot be removed from resolving list when
scanning, advertising or when a connection is being initiated.
Suspend all active adv, scanning or connection initiation upon
completion of any resolving list operation.
Original author: Chaojing Sun <cjsun@broadcom.com>
Change-Id: Id104dace2944b1878eaf65b93aba3d01e477191d
/system/bt/stack/include/btm_ble_api.h
|
| 935324abbe8706307297f09cf79bbcd4efb73367 |
|
31-Mar-2015 |
Satya Calloji <satyac@broadcom.com> |
LE low power scan feature
LE low power extended scan feature stack changes
based on Google BLE spec v0.95
Bug: 20029342
Change-Id: I1db2d9bb648295340d0e93ca89d27e1b938d33d3
/system/bt/stack/include/btm_ble_api.h
|
| 82f066faddcf45c9bd12e018c682dca616aaa079 |
|
27-May-2015 |
Prerepa Viswanadham <dham@google.com> |
Merge "Increase the min LE connection interval to 11.25ms" into mnc-dev
|
| 3b0fbc4ea1dfca19917ea6bdfa535a891e03ef35 |
|
27-May-2015 |
Prerepa Viswanadham <dham@google.com> |
Increase the min LE connection interval to 11.25ms
To reduce audio choppiness, increase the min LE connection interval
to 11.25ms from 7.5ms
Bug: 18776956
Change-Id: I8404ebe2f9562d555a2131ae30dd63b74bb362a4
/system/bt/stack/include/btm_ble_api.h
|
| 6fc9526bba383fdb33c0536ed050489aa2215554 |
|
22-Apr-2015 |
Satya Calloji <satyac@broadcom.com> |
Unpair the other transport on a device paired
When unpair is initiated for LE or BR-EDR transport for a device,
close the link for other transport and unpair the device on
both transports, since both transports on a device are paired
due to cross key.
Original author: Priti Aghera <paghera@broadcom.com>
Change-Id: I13d4757eb056c4bd4c7cc0699ec61a28852702c5
/system/bt/stack/include/btm_ble_api.h
|
| 877123f5b9df90e7a71ea7b15997c521229decc1 |
|
24-Apr-2015 |
Satya Calloji <satyac@broadcom.com> |
Static address is seen on scanner after unpairing
Fix for bonded devices that cannot be removed from resolving list when
scanning, advertising or when a connection is being initiated.
Suspend all active adv, scanning or connection initiation upon
completion of any resolving list operation.
Original author: Chaojing Sun <cjsun@broadcom.com>
Change-Id: Id104dace2944b1878eaf65b93aba3d01e477191d
/system/bt/stack/include/btm_ble_api.h
|
| f6c48a09e398de804f7d563a44904e917afd2c32 |
|
08-May-2015 |
Brian Carlstrom <bdc@google.com> |
Resetting system/bt
git reset --hard fa5fec7c98ff3c56bd825bc51a1d28bdc3bad0bb^^
git reset --soft aosp/master
git commit -a
Change-Id: I2939d9bbd825110a42a71008e5255945e38a77e1
/system/bt/stack/include/btm_ble_api.h
|
| 5725fc6d2c639a8c22a08b9b6629309eeda3715e |
|
31-Mar-2015 |
Satya Calloji <satyac@broadcom.com> |
LE low power scan feature
LE low power extended scan feature stack changes
based on Google BLE spec v0.95
Bug: 20029342
Change-Id: I1db2d9bb648295340d0e93ca89d27e1b938d33d3
/system/bt/stack/include/btm_ble_api.h
|
| 7613dc004f6901f535d484ecabbd8f608717ee6f |
|
30-Apr-2015 |
Nitin Arora <niarora@codeaurora.org> |
Increases number of LE multi-advertiser instances supported
Change-Id: I0d43b3922b2b5dc8c57511d908f45dfe8d8f1b9c
/system/bt/stack/include/btm_ble_api.h
|
| 636d6714a4c08dd99d2147dcce05dc3892e804b4 |
|
18-Dec-2014 |
Priti Aghera <paghera@broadcom.com> |
LE Data Packet Extension support
Included support for LE data packet extension feature according
to BT 4.2 spec. This patch checks if the controller supports LE
packet extension and provides functions to set the PDU length.
Bug: 20013956
Change-Id: I6a92970fede2f793ad48c9fa2e0247ad00297533
/system/bt/stack/include/btm_ble_api.h
|
| 444a8da807abaf5f9e813ce70c56a79160495fb3 |
|
06-Mar-2015 |
Satya Calloji <satyac@broadcom.com> |
LE Privacy 1.2 and LE secure connections
Bug: 19816438
Original author: Chaojing Sun <cjsun@broadcom.com>
Change-Id: I5951f4d4e038f8348a62aa6d19b2111bae0b3ecc
/system/bt/stack/include/btm_ble_api.h
|
| f538707fe64c62b1dbb8e4210e4a1bfa0bab2b56 |
|
10-Feb-2015 |
Satya Calloji <satyac@broadcom.com> |
OnFound/OnLost feature changes based on Google spec v0.90
Bug: 19609671
Change-Id: If9e61b405a141cb77fb65741d08227284cb22ccd
/system/bt/stack/include/btm_ble_api.h
|
| f9fdf890ffe79c934958b56ab9120deb684481ad |
|
03-Feb-2015 |
Satya Calloji <satyac@broadcom.com> |
Random address does not get written properly
The random address not getting written with correct
instance ID, as per Google spec.
Bug: 19370739
Change-Id: I7e5fc8d274bad5f127bd791469a46e2f257eaddd
/system/bt/stack/include/btm_ble_api.h
|
| 24933b5b1a06274c47133debac5251a97128a267 |
|
25-Sep-2014 |
June R. Tate-Gans <jtgans@google.com> |
Removing unnecessary BTAPI #defines.
/system/bt/stack/include/btm_ble_api.h
|
| 3f24f460ec3efedde25723e6a4297efc10873cd2 |
|
17-Sep-2014 |
Satya Calloji <satyac@broadcom.com> |
All 00 mac address with advt
Read the controller features before local name read
Bug 17505545
Change-Id: I7995a8c714ebec6e1751af5371edfd29c74b12ea
/system/bt/stack/include/btm_ble_api.h
|
| 9e3ce4ba4952c5405ee20b89c2916dbe2c06599d |
|
21-Aug-2014 |
Satya Calloji <satyac@broadcom.com> |
onBatchScanStorageConfigured returns status 12
Stack changes for handling the API call sequence changes. Please refer buganizer for more details on the API sequence changes
Bug:16850169
Change-Id: Iabef8247a290d163c1fe03cb853d12678b559664
/system/bt/stack/include/btm_ble_api.h
|
| d77eec93e5299f5bff987fceceba612b33251a14 |
|
07-Aug-2014 |
git-zhenye.broadcom.com <zhenye@broadcom.com> |
Moved per device tx power configuration capability in bdroid_buildcfg.h
Bug 16711526
Change-Id: Ia8099765113068fd3b211acb882702d3581bd4b1
/system/bt/stack/include/btm_ble_api.h
|
| 16fe0822ccd3eb6f66d3afd9965d25a0a0cb4c30 |
|
07-Aug-2014 |
Prerepa Viswanadham <dham@google.com> |
Use run time parameters to control LE features
Use values read from controller to enable and control LE features such as
multi advertising, RPA offload, maximum irk size etc
bug 15393216
Change-Id: I193e2b9a0dc61b86f667e986803571440e390160
/system/bt/stack/include/btm_ble_api.h
|
| f1dba910daa5f0ce9ca89f840bb7e6269f07af1d |
|
16-Jul-2014 |
Satya Calloji <satyac@broadcom.com> |
LE batchscan consolidated reports
Provide consolidated batchscan reports
Change-Id: Ie3da240c38b014fe29d4394438f3858fd4e731fa
/system/bt/stack/include/btm_ble_api.h
|
| 6e2d9db5148176d88d7f48c3b2ad5b27c57ca14d |
|
09-Jul-2014 |
Satya Calloji <satyac@broadcom.com> |
Settings app does not show BLE devices
Settings does not show all BLE devices when scan filter is set
Change-Id: I669ef3b87a9a21dfce26c1e22b5d984a5ea6f75c
/system/bt/stack/include/btm_ble_api.h
|
| f2c9280a1c7647c06278f31738575caf1b85027e |
|
24-Jul-2014 |
Matthew Xie <mattx@google.com> |
Merge "Increase BLE background scan window for faster re-connection" into lmp-dev
|
| 24364958c9d1367634d20542182df30eeb1ae491 |
|
24-Jul-2014 |
Matthew Xie <mattx@google.com> |
Increase BLE background scan window for faster re-connection
The scan window is increased from 11.25ms to 30ms.
The scan duty cycle is still very low at 2.34% while user experience
is greatly improved.
bug 16521059
Change-Id: Ice37c54fdc7d852fd19709112075e7492b6a1480
/system/bt/stack/include/btm_ble_api.h
|
| e5ba8841cd39e17c05aeb4ab65b5b761d41577da |
|
04-Jul-2014 |
Satya Calloji <satyac@broadcom.com> |
LE energy info feature
Stack and BT-IF changes for LE energy feature
Change-Id: I671e63aaead210c6352b45a5e20ad5e4bbbb77b7
/system/bt/stack/include/btm_ble_api.h
|
| 4c94c5f9fc2c3102c52706fd5bb4cd8d065e5716 |
|
19-Jul-2014 |
Prerepa Viswanadham <dham@google.com> |
Fix build: Revert the reversion done due to build failure.
original commit id: 347a1d64c7a9c345793c61b03bdcaa31ad8e5678
revert commit id: 571c81ed119833b5e5cbd6bedffd7409a10be21d
Fix builds: Revert "Added code to publish ble adv tx power in dBm""
This reverts commit 571c81ed119833b5e5cbd6bedffd7409a10be21d.
Change-Id: I2afeeaa4b52aa449e54115fd5f816a7a949d2ea8
/system/bt/stack/include/btm_ble_api.h
|
| 571c81ed119833b5e5cbd6bedffd7409a10be21d |
|
18-Jul-2014 |
Ed Heyl <edheyl@google.com> |
Fix builds: Revert "Added code to publish ble adv tx power in dBm"
This reverts commit 347a1d64c7a9c345793c61b03bdcaa31ad8e5678.
Change-Id: If62571a3f5bd87d04e5643855c9fea1b8048aa5a
/system/bt/stack/include/btm_ble_api.h
|
| 347a1d64c7a9c345793c61b03bdcaa31ad8e5678 |
|
16-Jul-2014 |
git-zhenye.broadcom.com <zhenye@broadcom.com> |
Added code to publish ble adv tx power in dBm
Bug 15412969
/system/bt/stack/include/btm_ble_api.h
|
| 1acb61ce065053f91a0f8d43e8328c9eeec4b5ed |
|
15-Jun-2014 |
Satya Calloji <satyac@broadcom.com> |
LE Onfound and Onlost feature
BTIF and stack layer changes for onfound/onlost feature
Change-Id: Id52cdd5855ca8c0ff276b42613b51c4cd3882bfc
/system/bt/stack/include/btm_ble_api.h
|
| 1a9247a1229aa65b3d1dce16426177bc5828e54d |
|
05-Jun-2014 |
Satya Calloji <satyac@broadcom.com> |
LE ADV Filter changes
BTIF and stack layer changes for ADV filter feature
Change-Id: I865e57c41802751e172248547b8510598261ec94
/system/bt/stack/include/btm_ble_api.h
|
| c4e2596a112a0dd63ac681b1226548c0f95e828c |
|
11-May-2014 |
Satya Calloji <satyac@broadcom.com> |
LE batch scan feature
BTIF and stack changes for batch scan feature
Change-Id: I4dd2d551435e9f1f0e43906bd695294e97ed4bba
/system/bt/stack/include/btm_ble_api.h
|
| 21cf5dbe659716e5ac6cae107b7734b97c16fd94 |
|
30-Jun-2014 |
Nitin Arora <niarora@codeaurora.org> |
am 021e17a6: Clear background conn list entries during BT power off
* commit '021e17a641e61e3f139717cd755bf6f9b9b9eb12':
Clear background conn list entries during BT power off
|
| 021e17a641e61e3f139717cd755bf6f9b9b9eb12 |
|
30-Jan-2014 |
Nitin Arora <niarora@codeaurora.org> |
Clear background conn list entries during BT power off
This clears whitelist entries and resets bgconn device lists
Change-Id: I551791d63fa826071c113abd383540838f6c59b2
/system/bt/stack/include/btm_ble_api.h
|
| 9c07b33b335dfa3b4357f9ee293e1c1c03a7389a |
|
20-Jun-2014 |
Steve Paik <spaik@google.com> |
[bluedroid] Fix slave latency and conn timeout defaults in BLE
The default connection parameters were not being applied properly in BLE.
Also fixed a typo in btm_ble.c.
Change-Id: I6cfb0f2a400740578910dcf4c7192ea16406aa1b
Signed-off-by: Steve Paik <spaik@google.com>
/system/bt/stack/include/btm_ble_api.h
|
| 8d41691e6b16ba945711e8c3846df1ec70fdb724 |
|
31-May-2014 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Support for reading LE specific controller features
Support for reading LE specific controller features via get adapter properties
API
Change-Id: Ia0b813be45fb826ce27d1d7a31ca41650d7286dd
/system/bt/stack/include/btm_ble_api.h
|
| 9546abf9fc4400853803ee220482ae63e63f0d9d |
|
31-May-2014 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Support for reading LE specific controller features
Support for reading LE specific controller features via get adapter properties
API
Change-Id: Ia0b813be45fb826ce27d1d7a31ca41650d7286dd
/system/bt/stack/include/btm_ble_api.h
|
| bf6119caaa0edf418e014c1a724d9dac144dec7a |
|
02-Jun-2014 |
Adam Hampson <ahampson@google.com> |
Merge "ble: use appearance uuid to determine class of device"
|
| e6c7450a2addbb856e68b66a726b71286f809b19 |
|
31-May-2014 |
Adam Hampson <ahampson@google.com> |
ble: use appearance uuid to determine class of device
The current code is inferring the cod of a ble hid device based on
the service type. This change uses the appearance uuid to map to
to an equivalent cod.
Bug: 15346094
Change-Id: I6ab2c49bc5e7e956a285c9684ddefb339944a3dc
Signed-off-by: Adam Hampson <ahampson@google.com>
/system/bt/stack/include/btm_ble_api.h
|
| 66988a022d219f5385b3f76e3ae26566ad80fb86 |
|
29-May-2014 |
Nitin Arora <niarora@codeaurora.org> |
This patch contains bug fixes for solving race conditions for multiple
advertisers and incorrect VS command length which makes uuid filters not
working.
b/15094154, b/15174583
Change-Id: I78746b923301fa47afb21f8bedb0d79b42f492b9
/system/bt/stack/include/btm_ble_api.h
|
| fa994c9b7d63d381e33a5d63a7c97ae3edf4dc0f |
|
29-May-2014 |
Nitin Arora <niarora@codeaurora.org> |
Bluetooth: Changes to enable features on KWD
This patch contains changes needed to enable features,
multiple advertisment, packet content filtering and
privacy mode on kwd branch
Change-Id: If95bfb38eafe26f16db20e7650865c2f19553548
/system/bt/stack/include/btm_ble_api.h
|
| a6ce7751d84218c193eb90d390aef23217b1737e |
|
20-May-2014 |
Wei Wang <weiwa@google.com> |
Revert "Revert "LE Multi ADV feature""
This reverts commit ea85048a8e86b1e1b6b725649f6bb0834ba17301.
Change-Id: I9a9305db4fabff07b4309a38f65361dca3f5f37c
/system/bt/stack/include/btm_ble_api.h
|
| ea85048a8e86b1e1b6b725649f6bb0834ba17301 |
|
20-May-2014 |
Wei Wang <weiwa@google.com> |
Revert "LE Multi ADV feature"
This reverts commit 87776cf5e201b18646cbc16f11a7110d5ffe510c.
Change-Id: I5b544a5c965999096b665b1bd2edb021e3054be8
/system/bt/stack/include/btm_ble_api.h
|
| 87776cf5e201b18646cbc16f11a7110d5ffe510c |
|
01-May-2014 |
Satya Calloji <satyac@broadcom.com> |
LE Multi ADV feature
BTIF and stack changes for LE multi ADV feature
Change-Id: I5e009ff8cbac5fc6f92ca943c61c4faf98e4e2ce
/system/bt/stack/include/btm_ble_api.h
|
| ffb3960bb05f9acb0717d213612403487e9ad433 |
|
01-May-2014 |
Satya Calloji <satyac@broadcom.com> |
LE Multi ADV feature
BTIF and stack changes for LE multi ADV feature
Change-Id: I5e009ff8cbac5fc6f92ca943c61c4faf98e4e2ce
/system/bt/stack/include/btm_ble_api.h
|
| 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
/system/bt/stack/include/btm_ble_api.h
|
| 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
/system/bt/stack/include/btm_ble_api.h
|
| 5f72121ddc2f0249e896e19b186a05888bce2331 |
|
10-Feb-2014 |
Zhihai Xu <zhihaixu@google.com> |
support peripheral mode feature to connect iphone to android device.
enable BLE_PERIPHERAL_MODE_SUPPORT flag and fix the bug
the discoverability flag is not set in advertisement packet,
which cause the central device(iphone) can not find android device
during scan.
use displayOnly IO cap for dory, so dory can display the pin,
and the iphone(central device) will input the pin.
bug:12797572
Change-Id: Ie15ea9e340e3692df846399b9a85aa6d2a97eba7
/system/bt/stack/include/btm_ble_api.h
|
| 602162a13c6ed8abae53aee6deeda48b79f30911 |
|
10-Feb-2014 |
Zhihai Xu <zhihaixu@google.com> |
support peripheral mode feature to connect iphone to android device.
enable BLE_PERIPHERAL_MODE_SUPPORT flag and fix the bug
the discoverability flag is not set in advertisement packet,
which cause the central device(iphone) can not find android device
during scan.
use displayOnly IO cap for dory, so dory can display the pin,
and the iphone(central device) will input the pin.
bug:12797572
Change-Id: Ie15ea9e340e3692df846399b9a85aa6d2a97eba7
/system/bt/stack/include/btm_ble_api.h
|
| 6975b4d711142b885af479721cada448952c6b41 |
|
06-Aug-2013 |
Andre Eisenbach <andre@broadcom.com> |
LE: UPF 45 bug fixes
This change fixes the following issues:
- Second GATT-over-BR/EDR channel cannot be established when there
already is an existing GATT-over-BR/EDR channel
- If encryption fails for an LE connection due to a missing key,
the security state is not being cleared and blocks all further
security processing
- When DM discovery of an LE Peripheral device fails with a
connection timeout, no further discovery requests can be made
- GATT service discovery can get into endless loop when duplicate descriptor
definitions are found on the remote device
- When GATT over BR/EDR fails, BTA does not give a connection
callback to the application initiating the connection
- BR/EDR connection to remote platform does not generate API callbacks
- Stack crash discovered during UPF after remote disconnects
- The host is sending HCI disconnect to invalid HCI handle when
SMP fails because of a connection timeout
- Possible race condition:
If a disconnect is immediately followed by a connection complete,
the connection complete cannot be processed in the BTA GATT state
machine
- Write Complete event is not triggered for Prepare Write requests
Change-Id: I539cdedd68007818ff4f0d0213cee1c913f72d0f
Conflicts:
bta/gatt/bta_gatts_act.c
/system/bt/stack/include/btm_ble_api.h
|
| 781b5adee20e222ef87b56b72bfcd3f64013e4a0 |
|
28-May-2013 |
Andre Eisenbach <andre@broadcom.com> |
LE: Integrate power table for GATT
No power table exists for GATT, causing the device to never enter sniff
mode while using GATT over BR/EDR.
Change-Id: I0db539c1814a61af620f3dba560da64481291beb
/system/bt/stack/include/btm_ble_api.h
|
| ead3cde4bac0c3e32cd31f149093f004eef8ceeb |
|
06-Feb-2013 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Initial version of BLE support for Bluedroid
Change-Id: I9825a5cef9be2559c34c2a529b211b7d471147cf
/system/bt/stack/include/btm_ble_api.h
|
| 5738f83aeb59361a0a2eda2460113f6dc9194271 |
|
13-Dec-2012 |
The Android Open Source Project <initial-contribution@android.com> |
Snapshot cdeccf6fdd8c2d494ea2867cb37a025bf8879baf
Change-Id: Ia2de32ccb97a9641462c72363b0a8c4288f4f36d
/system/bt/stack/include/btm_ble_api.h
|