dfb3b2f2595dc16fe7f576a4b0c2f5e73db0327f |
|
06-Feb-2015 |
Andre Eisenbach <eisenbach@google.com> |
Add flag indicating encrypted connections to btif_dm_get_connection_state() Add a check to btif_dm_get_connection_state() to see if the currently active connection is encrypted. Bug: 19186961 Change-Id: I27bcc6e296d272ffd17c0bbe97631ffa4df57ccd
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
893637614568b8ac7dc996c2e9bdbde481fbdc08 |
|
26-Jan-2015 |
Andre Eisenbach <eisenbach@google.com> |
Change pairing_cb to assume temporary pairing by default When pairing takes place, the pairing_cb.is_temp flag indicates whether a pairing is temporary or permanent. Link keys are not stored for temporary pairings. Since this is a "positive" flag, resetting the pairing_cb control block (ex. memset to 0), it will assume persistent pairing by default. Under certain circumstances, this can lead to a link key being stored for temporarily secured connection. This patch reverses the flag to be a "negative" flag. Renamed to "persistent_bond", the default 0 meaning is now used to indicate a temporary bond. If the lag is not properly set now, it will default to a temporary bond and will not save the link key erronously. Bug: 18345373 Change-Id: I6e821595877ff30d64dc6e33602ac049cab3dd1e
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
86f97eda524568f2d264186844450db5e56dac36 |
|
10-Nov-2014 |
Matthew Xie <mattx@google.com> |
Use the device type from saved properties instead of assuming default DUMO device can do both BLE and BREDR operations. It was wrong to assign BLE or BREDR type to it. Bug: 18275230 Change-Id: I8d6c17e5157ba29a1af459629de9e2d6f6dc5e99
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
3e0dc7324e7b0127f9d15609bab395100a22098d |
|
24-Oct-2014 |
Andre Eisenbach <eisenbach@google.com> |
LE: Make local privacy configurable Bug: 17753401 Change-Id: I288ea8b6194d91d18485d0f3f1bbf997f97a26dd
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
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_dm.c
|
31a640079c9a7b9a2bf014f06f6c371afb66cc63 |
|
14-Oct-2014 |
Andre Eisenbach <eisenbach@google.com> |
Retry pairing if the device did not respond (page timeout) Implements a "blacklist" identifying troublesome remote devices which may require multiple pairing attempts to succeed. Change-Id: I11b6b7da7230e37fbd5ec4c07cd38b30dc12b40e
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
303d4ac5ff7758ab2cdde4040cb8db6cf37552f5 |
|
17-Sep-2014 |
Matthew Xie <mattx@google.com> |
Merge "For pairing over le transport, set default device type and address type" into lmp-dev
|
64c5479fc050c537ef6d39625de2032c77fc5676 |
|
16-Sep-2014 |
Matthew Xie <mattx@google.com> |
For pairing over le transport, set default device type and address type When the LE pairing is initiated over NFC, skipping device scan, there is no device type or address type info. We set the default as le and public. bug 17497942 Change-Id: I3dcbb9029ead6ea0f7c48e62f46c8a055f1bc293
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
a015a8348b9e09caf5261689f4c288a4d2ff6acd |
|
11-Sep-2014 |
Andre Eisenbach <eisenbach@google.com> |
LE: Use random address when initiating background connections When re-connecting to HID devices, the first reconnection immediately after a reboot incorrectly uses the static, public Bluetooth address of the phone/tablet as the own address. This patch fixes the Bluetooth initialization sequence to make sure privacy is enabled before any Bluetooth services are started. Bug: 16952502 Change-Id: I43e595ddc7e347fab972b059382b512fb03e9459
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
3baff79dcd63bc33b17f475939d0e282526d9995 |
|
29-Aug-2014 |
lungtsai_lin <lungtsai_lin@htc.com> |
Add LE device to inquiry DB before pairing There is no remote device type info wgeb OOB pairing LE devices. Add device type according to transport. Bug: 17156993 Change-Id: I29182ca13f801f8a7f2c3a95969d6ae23312dd7e
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
62a54c5b374c1eb9d3664da2717f82fdeea8bb7e |
|
05-Aug-2014 |
Andre Eisenbach <eisenbach@google.com> |
Merge "Add transport parameter to createBond() function (2/4)" into lmp-dev
|
b0daa5d79d4e2950701fb9a5f76a306e1da42de0 |
|
05-Aug-2014 |
Andre Eisenbach <eisenbach@google.com> |
Add transport parameter to createBond() function (2/4) Change-Id: I8176b932da705f8d0a230abd56bc5faa00005eb6
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
c0edf9f2038d23a3ba0cd424e187cb0d8fa201e8 |
|
26-Jun-2014 |
Priti Aghera <paghera@broadcom.com> |
Blacklist Apple HID devices to skip SDP Remote initiated HID connection fails as Apple devices goes out of resource. During incoming connection SDP is performed after authentication is successful. Apple device is out of resources and thus sends No resources available error for SDP request. In order to avoid this situation a apple HID devices are blacklisted to skip SDP after authentication in case of incoming connections. bug 15566403 Change-Id: Ic7fdfd2543c90e81341b4d5b7bef9c1d1c11b928
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
d773c2cfd3675aaec431a42b79b26b24e0555ed9 |
|
30-Jul-2014 |
Satya Calloji <satyac@broadcom.com> |
Incorrect data type in local LE features bt_local_le_features_t of wrong size b/16653133 Change-Id: I81da7f8c6b9151b8def8d4e3c655cf746d0e3db9
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
efaddcb2cec21bfcdcadfa86720d3ca720a4253d |
|
29-Jul-2014 |
Satya Calloji <satyac@broadcom.com> |
Bug 16498557 Inconsistent energy reporting Fix for inconsistent energy reporting Change-Id: Iddd77354624a631ca8db52f12086d3afa5751d36
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
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
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
81b03192d4284acc7c9903f5b183927797dceca4 |
|
24-Jul-2014 |
Prerepa Viswanadham <dham@google.com> |
Fix build for non BLE supported targets(nakasi and manta) Change-Id: I0de46e1dfce3a51367bc0e2640e91cdefc8a21c6
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
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
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
2772dac59971dd9c135cfac73a1ba77a912324f4 |
|
17-Jul-2014 |
Thomas.TT_Lin <Thomas.TT_Lin@htc.com> |
Bluetooth: fix the HOGP device(iBUFFALO BSMBB09DS) pair and reconnect problem. in bta_hh_le.c (fix reconnect issue) Since new LE security flags are import, (BTM_SEC_LE_AUTHENTICATED, BTM_SEC_LE_ENCRYPTED, BTM_SEC_LE_NAME_KNOWN, BTM_SEC_LE_LINK_KEY_KNOWN, BTM_SEC_LE_LINK_KEY_AUTHED), we have to use new BTM_GetSecurityFlagsByTransport() function with LE transport to get right sec_flag, or will cause cannot correctly add to white list and cause reconnect fail. in btif_dm.c (fix HOGP mouse pair issue) the HOGP mouse will become abnormal if we update connection parameter too many times. Therefore the is_hid case is not suitable for HOGP mouse, it will trigger call to L2CA_EnableUpdateBleConnParams() several times due to service discovery and bonded state. L2CA_EnableUpdateBleConnParams() update connection cause mouse abnormal. The change will make the flow: complete bonding procedure first, then do service discovery, connect to mouse. in gap_ble.c (fix HOGP device pair issue) After pairing status is bonded, host start to create ATT layer to get some information from HOGP device. If host send "disconnect" command during period. Device will stop to feedback anything. Suggest to delete it. in smp_act.c (fix HOGP device pair issue) update connection parameter too many times may cause mouse abnormal, so remove this code since this will be called again after service discovery. Suggest to delete it. Change-Id: I4b722343c2b08d33530bc6b928bc9ffe89fd09e9 Signed-off-by: Thomas.TT_Lin <Thomas.TT_Lin@htc.com>
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
a3c936eae6fd686658dd84d546326908904029c8 |
|
11-Jul-2014 |
Priti Aghera <paghera@broadcom.com> |
am 156c52bb: Send correct status for SMP AUTH failure * commit '156c52bb003a14147db99d8a151edc08f591bd34': Send correct status for SMP AUTH failure
|
156c52bb003a14147db99d8a151edc08f591bd34 |
|
09-Jul-2014 |
Priti Aghera <paghera@broadcom.com> |
Send correct status for SMP AUTH failure Send correct corresponding status for SMP AUTH failure to JAVA layer. This will enable BluetoothEventManager to display correct error message for bond state changed callback. Bug 15677623 Change-Id: I6a8742926bac862f960890417b5d68c23b33e010
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
2dc999935d4c69ae31ea93d9014165965dd373d6 |
|
17-Apr-2014 |
Hemant Gupta <hemantg@codeaurora.org> |
Bluetooth: Support MAP Client role on Bluedroid. Implementation changes from BTA and BTIF layer to support MCE role on Bluedroid stack. Change-Id: I8547b0f28338e83edabae969121872ca23fdcb36
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
e146869fec903400e601d2ac7b0a59bd05934f0e |
|
14-Nov-2013 |
Hemant Gupta <hemantg@codeaurora.org> |
GAP: Remove device info from storage on Pairing Cancel Remove paired device information for SSP devices from the BT-IF layer storage on pairing cancel. Change-Id: I4660e3659866bd66339350b5cdb92bf3ad3cc850
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
b4801441a5b7a093bc78f2143a8ed28605c51dc6 |
|
07-Jan-2014 |
Hemant Gupta <hemantg@codeaurora.org> |
GAP:Add authentication failed error code in auth_compl_evt. There is an unhandle failed HCI error code when pairing with symbian OS phone nokia n95 which will cause no prompt when auth failed. Change-Id: I3a37c7732d1bf71c090bb968380d8c5f0af2ff79
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
aef7a6716e72e9304af36469500ee53c97350c21 |
|
31-Jul-2013 |
Hemant Gupta <hemantg@codeaurora.org> |
[2/2] Bluetooth: Security: Handle authentication rejected error status Handle error codes in authentication complete event with failures like reject pairing , unspecified error. Change-Id: I392b7531a8625efbf91bf80f7f617a6954229892
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
59a88ec207ead601c7ba5e767fd1373c7f2df70b |
|
19-Mar-2014 |
Hemant Gupta <hemantg@codeaurora.org> |
Bluetooth: Handle missing key event This change handles HCI_ERR_KEY_MISSING event coming to the stack when user doesn't enter any key and timeout happens. Change-Id: If530e8acce3f105e4f1e2841bf350ee5330f389e
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
831423ea1879244e746f39d7696ad4a66681f306 |
|
07-Jan-2014 |
Hemant Gupta <hemantg@codeaurora.org> |
Bluetooth: Fix to avoid NULL pointer dereferences This fix for avoiding NULL pointer dereferences: - Added check for state checking in btm_remove_acl function to avoid sending disconnect command if already in Disconnecting state. - Added NULL check for 'pin_code' in btif_dm_pin_reply function - Null check before accessing in BD interface layer configuration node variables. - Add NULL check before accessing p_bd_addr variable to avoid null pointer exception while referring to invalid memory. Change-Id: Ib7ed45b6a1692785a45224d739a564f767e5b10f
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
249f600c1518c015f5cb45720cb022a203ba744e |
|
18-Jun-2014 |
Andre Eisenbach <eisenbach@google.com> |
LE: Add is_connected() function (2/3) Change-Id: I73c4ea7f13982bf9c208996f9c749d2dfbe698be
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
e8c3d75b75493911ebf0f99c83676359657178f7 |
|
04-May-2014 |
Sharvil Nanavati <sharvil@google.com> |
Logging cleanup: BTIF and APPL. Change-Id: I5b1214642bbb4b9aecc0fd2c899a6ec2c9793286
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
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
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
bf0e4b26d8f0748ff4f9522a2ac7001bfb9ca5cc |
|
20-May-2014 |
Wei Wang <weiwa@google.com> |
Fix build issue for devices without BLE features. Change-Id: I6499663d253c791cc739ed76b839eb3aefe6613a
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
0943c10ed5713a08659f08e39e13de4894aaba61 |
|
12-May-2014 |
Satya Calloji <satyac@broadcom.com> |
LE: Add RRA offloading and vendor specific PCF commands Change-Id: Iadca8e73ceaadcd0429421ea70f1b76644e88c42
/external/bluetooth/bluedroid/btif/src/btif_dm.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_dm.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_dm.c
|
a217ab9a0294a8285641b141efccf7d54b437a33 |
|
29-Apr-2014 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Resolve Pairing failure with IPhone When pairing is initiated from the iPhone side, it sets Bonding bit without MITM. We responded to this with No bonding, No MITM. This resulted in JustWorks & Unauthenticated link key. After pairing iPhone initiates a RFCOMM connection. This caused a link key upgrade to be done, which the iPhone rejected, resulting in pairing failure. To resolve this the following enhancements were made 1. If locally initiated pairing always set Bonding bit + MITM 2. If remote initiated a. copy over the bonding bit b. if peer has DisplayYesNo set MITM 3. As a fallback if remote had MITM, enable MITM in our response This forces pairing to use Bonding bit+MITM thus resulting in authenticated combination linkkey Change-Id: I08f16c80821bc822023180d01868614ba41e6d88
/external/bluetooth/bluedroid/btif/src/btif_dm.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_dm.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_dm.c
|
87b7cce18f64b1b5f1cdff81d883a5c8720ead77 |
|
28-Nov-2013 |
Hemant Gupta <hemantg@codeaurora.org> |
GAP: Try to retrieve CoD from NVRAM if 0 This patch tries to retreive CoD from NVRAM if CoD is 0. This is because in scenarios when airplane mode on/off, inquiry is not performed again on devices shown in Available devices List of UI, so CoD is 0 during SSP information as database of stack is not properly updated since inquiry is not performed again. Without this patch it was observed because of wrong CoD info device icon for HID mouse was changed to Joystick and device is not shown in Paired List. Also some extra debug logs are added in code for better debugging. Change-Id: I14858ccee04728cb4b9cd60d397b79fa6494b842
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
8d2128d5740c8a7282e2336cd9f5901e98d3eb63 |
|
13-Dec-2013 |
Zhihai Xu <zhihaixu@google.com> |
HID: Remove device from nvram on auth failure This patch removed hid pointing device from nvram on authentication failure due to pairing timeout or when wrong passkey is entered. Without this patch it was observed that hid pointing device was always shown in paired list when DUT was restarted after authentication failure. CL from qcom(Hemant Gupta) Change-Id: I69c43d2ed982d5d5abfd5707db90ef4b5c65b34f
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
b820aec7a022231fa30a3493af861db9d9aa625d |
|
24-Dec-2013 |
Hemant Gupta <hemantg@codeaurora.org> |
Bluetooth: GAP: Send bond none in case of temp pairing Send BOND_NONE in case of temporary device pairing on receiving the authentication complete, so that UI doesn't get stucked in pairing for that device. Change-Id: Ided412ef89d928f958a0052362be145232411c0a
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
5cd8bff2dd0337cb52bf48f312e3d2d55a8882fb |
|
01-Feb-2014 |
Mike J. Chen <mjchen@google.com> |
Major warnings cleanup Mostly fixing unused parameter warnings. A few other warnings also fixed like possible use of unitialized variables (no real issue found, just compiler couldn't follow the path), signed vs unsigned warning. Also fixed some typos, indent issues, removal of dead code, etc. Change-Id: I95eb887aefc4d559d7921f71a0af5f3bfb01ac01 Signed-off-by: Mike J. Chen <mjchen@google.com>
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
a9eb25c8c01e70613bace21b23a06bd9a10871b1 |
|
30-Sep-2013 |
Kim Schulz <k.schulz@samsung.com> |
Pairing with dissapeard HID decive never times out (in UI) - added function to notify the UI about failed HID pairing patch set2: - added function header patch set3: - break long line Bug: 10998578 Change-Id: I7314bf07da7ebac7252c6902d987fbca20da2abc
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
d7ee77bf8bb7f009b8088c15dcf5458b6f1fd05d |
|
06-Nov-2013 |
Zhihai Xu <zhihaixu@google.com> |
need to save the BLE HID UUID to NVRAM need to save the BLE HID UUID to NVRAM. otherwise we will miss the HID profile setting in device profile list of the BLE HID device after reboot. bug:11541617 Change-Id: I11e1c871768e999ec1f48396018c3be379cc1b7d
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
7f3e42943b834ff0f556cd5c063a896f54d53167 |
|
30-Sep-2013 |
Matthew Xie <mattx@google.com> |
Interleave br/edr device discovery with BLE device scan for some targets This change only applies to targets which do not support interleaved scan in controller. bug 8508849 Change-Id: Ia99faf92c942b4b33abfde2708eff25ec9cd5468
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
a30d95acf60f04531923e8ab06d976744697bf51 |
|
18-Sep-2013 |
Matthew Xie <mattx@google.com> |
Increase default bluetooth name from 15 to 31. bug 7441329 Change-Id: I79d64e77f206268ace06ce0f7b16119f63655bec
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
1e5109b5cbf49810abd0c94c413ce07db52caaca |
|
10-Nov-2012 |
Matthew Xie <mattx@google.com> |
Use product model as default bluetooth name if not defined bug 7441329 Change-Id: I6afe54a8a0c4d1120e96eb808cf9fc4bf5b37fdb
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
607e3b79f1731de0d08a2c03d38ae17874bc282d |
|
16-Aug-2013 |
Matthew Xie <mattx@google.com> |
Place handling of BTA_DM_DISC_BLE_RES_EVT in BLE feature ifdef Without this fix, bluetooth fail to compile for non-BLE platform Change-Id: Ida10c54ab841e0a2bcaeb389a9813dd846db8200
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
2e7fa68bfd9723b7ec7b6b0b128d89f31a2e06ee |
|
09-Aug-2013 |
Andre Eisenbach <andre@broadcom.com> |
LE: Add support for the HID-over-GATT profile (1/3) bug:8330048 Change-Id: I5727161b0a87700487bee96cdffa8fd169034204
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
5c44e45473e5fc2fa89411ab1add7dbfc979f1f8 |
|
07-Aug-2013 |
Andre Eisenbach <andre@broadcom.com> |
LE: Add peripheral role support (2/4) Initial stack support for the LE peripheral role. Change-Id: I261d751b43b7020760bff345b472b6f60caa60be
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
4c03040fa975cc23ea27b183908b1008bb3231f9 |
|
26-Jun-2013 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
am 29a69a11: am ec7e2c8e: Do not abort bonding if link disconnects during SDP after Auth cmplt * commit '29a69a1144fc42d3742bacb9acee89a612cbf8b3': Do not abort bonding if link disconnects during SDP after Auth cmplt
|
ec7e2c8e06396101c6b26187995db7c105ed3c3f |
|
20-Jun-2013 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Do not abort bonding if link disconnects during SDP after Auth cmplt If ACL link gets dropped during service search after bonding, re-attempt service search instead of setting bond state to BOND_NONE Bug 8611134 Change-Id: I77672d9f4feab634b3795a41e0d4e58903b5d275
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
390c94dc0f9deee917f52caaf3f8bb9f79aa98b4 |
|
16-May-2013 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Removed COD check for unbond and UNPAIRED_EVT PC supporting HID Device would not have Peripheral as its MAJOR COD. So COD check for major peripheral device was removed in case of UNBOND and while receiving UNPAIRED_EVT. Additonal checking is done when virtual unplug evt is received to remove bonding only for HID Devic with MAJOR COD as Peripheral or if its a locally initiated VUP. Change-Id: I5343919463e48babc9cd03e05ff92a3f93f6d26d
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
e915116a24142955edbc40a0e380b4828957c762 |
|
09-May-2013 |
Matthew Xie <mattx@google.com> |
Merge "Solve compilation problem when BLE/GATT/SMP features are false" into jb-mr2-dev
|
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_dm.c
|
95664a9acc57b5e51365454f26d2fac0f2e1ecd4 |
|
03-May-2013 |
Kausik Sinnaswamy <kausik@broadcom.com> |
Fix for SDP data structure leak during pairing During pairing, bluedroid initiates a SDP request to search services. Upon SDP completion, some data structure buffers were not returned to the pool resulting in leak. Bug : 8797456 Change-Id: Ic512fd22ca6b8b748c5b92c02e24016fe785c0b1
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
ca22ac493ab777199084d87b3c7627e7f27555af |
|
13-Feb-2013 |
Andre Eisenbach <andre@broadcom.com> |
LE fixes - Null pointer exception check added. An exception occurs at the memcpy in the bta_dm_gatt_disc_result. User removed the battery on Ble device(Smart Nudge) during bonding and connection. This exception occurs sometimes. I used Broadcom LE Explorer to reproduce it. - Fixed disconnect and encryption behaviour Disconnect will now disconnect the physical link immediately when no other application is interested in the device anymore. Also, the connection to a remote device is now dropped if encryption fails. - Deep copy buffers when transfering context Certain BTA server event types require a deep copy of the request data buffers when transfering context. Shallow copy of the pointers involved may cause a crash when overlapping read and write requests are received. - 2nd encryption has not started need to send encryption complete callback when the encryption fail due to link drop without a complete event. Otherwise BTA layer would not be able to clean up the status, and no further encryption can be started. Change-Id: If93e0a188e8779830c8991e4193b96dc95e23e5d
/external/bluetooth/bluedroid/btif/src/btif_dm.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_dm.c
|
e17bf003d4eefdc8525e55894210e9ee494972b8 |
|
16-Feb-2013 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
Cancel device search before starting SDP Also update bonding state when acl link goes down during bonding b/8120036 Change-Id: I28e4cb6f35e4c524b7a67281e78a196ba1fce0cb
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
ebb1d755818704a662f7ea8ae3cc1b5593d582d8 |
|
28-Nov-2012 |
Priti Aghera <paghera@broadcom.com> |
Fixed unpair and reconnect issue with certain non-pointing hid devices Hid info would not be removed from storage if COD is NON_KEYBOARD_NON_POINTING. Due to this the device will be added to stack even if it is unpaired and subsequent connections will fail. bug 8055549 Change-Id: Ib493fc165120de3c71398f5fe24b17f31fa5fc3e
/external/bluetooth/bluedroid/btif/src/btif_dm.c
|
d70b7a8ebce5a9646b8baf16a24a6eda88b1a4f6 |
|
31-Jan-2013 |
Nick Kralevich <nnk@google.com> |
fix too small buffer property_get must be called with a buffer of at least PROPERTY_VALUE_MAX len. The supplied buffer is too small. Fixed. Change-Id: I6c6b3050b30f6aa5ece69888263394e572551aff
/external/bluetooth/bluedroid/btif/src/btif_dm.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_dm.c
|