| 2a1b8ac5b15f3026fac1c697fc3b9c04228051f0 |
|
08-Sep-2015 |
tturney <tturney@google.com> |
Allow BT inquiry while discovery is in progress.
BT Inquiry is disallowed when service discovery
is in progress. Innitially when GATT discovery
is in progress (crosskey pairing), it resulted
in inquiry requests being rejected. During an
insecure connection like OPP, bonding link key
is not stored. In an earlier patch (b820aec7),
BR/EDR discovery was bypassed if the bonding was
temporary. However, this was not done for LE.
Applying the same logic to LE, resolved the
inquiry issue reported in this bug.
Bug: 23468169
Change-Id: I6111c80a420aeb0bc36a0393eb215c112512d251
/system/bt/btif/src/btif_dm.c
|
| ac72840a3d7409adbb3ee4904ab1ed5de2d66586 |
|
27-Jun-2015 |
Nitin Arora <niarora@codeaurora.org> |
Update device type correctly in the NVRAM at inquiry result
This patch checks for the NVRAM data when inquiry result
is received from the remote device. In case the device is
marked as LE only or BR/EDR only, and inquiry result is
received from the alternate transport, the device type is
marked as Dual mode in the NVRAM
Bug: 22604450
Change-Id: Id925e8bad152a33c2bd3c371ca42a6f9c694e3b0
/system/bt/btif/src/btif_dm.c
|
| b4365c55ccb2e985d00619c30dc14d5c156771b7 |
|
26-Jun-2015 |
Nitin Arora <niarora@codeaurora.org> |
Adding transport type while initiating remote discovery
This change ensures that the completion of SMP pairing for LE
devices specifically requests remote device discovery based on
transport type set to LE to prevent initiation of BR/EDR
connection due to incorrect transport type info
Bug: 22515456
Change-Id: Id1e5603d3cc53ca3dff427b93059a00f8d9150a7
/system/bt/btif/src/btif_dm.c
|
| 65f9c04aa36af5379ba3a28dba36a5de16686024 |
|
17-Jul-2015 |
Pavlin Radoslavov <pavlin@google.com> |
Fix the logic for removing bonded devices
* Removed btif_storage_is_device_bonded(), because it is not needed,
and it was giving the wrong answer in use cases like Smart Setup
with BR/EDR connections.
* Added a call to btif_storage_remove_ble_bonding_keys()
within btif_storage_remove_bonded_device() so the bonded device
state is properly removed.
* Don't save the BLE bonding keys if it is temporary bonding
Bug: 22233299
Change-Id: I33d9f76a124acc60173f0acaa517bc29ee6603e8
/system/bt/btif/src/btif_dm.c
|
| 21331c62310dda2f523712c536da3e65afce0f38 |
|
16-Jun-2015 |
Srinu Jella <sjella@codeaurora.org> |
Store the link key derived from cross tranport link key
Use case: PTS test case for cross transport link key
derivation
Steps to reproduce:
1. Start Test case GAP TP/LEP/DM/BV-15 in PTSv6.0
Failure: PTS test case TP/LEP/DM/BV-15 fails as the link
key is not stored when the key is derived from other
transport key. So it will again go for pairing even though
it has link key but not stored.
Root cause: Link key is stored only when bond type is
presistent, but it sets the bond type to persistent only
when it receives SSP request but not link key is derived.
Fix: So making the solution generic to store always when the
link key type is authenticated combination key with P-256.
Bug: 22486860
Change-Id: I3eb201262f72c86a9438351cad14a6698065fa90
/system/bt/btif/src/btif_dm.c
|
| 27c4e634cb0d6e618bc3e53da7c0f9a305d1593b |
|
07-Jul-2015 |
Andre Eisenbach <eisenbach@google.com> |
Move pairing auto-retry workaround to new interop db
Change-Id: I7177aaa0e2d0c3b0fa79ae655c0171f0703c54f3
/system/bt/btif/src/btif_dm.c
|
| f1029c7afb9b4c9fcf95b3f98ce9c68b10d5a02c |
|
02-Sep-2014 |
Srinu Jella <sjella@codeaurora.org> |
Remove stored link key for temporarily paired devices
Problem: Device shows up in paired list during just work pairing
1. Create a connection from DUT to remote.
2. Remove the link key in remote.
3. Send a file from remote to DUT.
4. Turn OFF BT. Turn ON.
Failure: Device should not move to paired list after BT on/off
as device removed from UI during just work pairing
Root cause: remote device is not removed from btif but
its removed from UI during justworks pairing
Fix: remote device is removed from btif during justworks
pairing to sync up UI and btif paired list
Bug: 19417758
Change-Id: I73de0a94c4f7ada644d258790a9e3e4bf11fc4e5
/system/bt/btif/src/btif_dm.c
|
| af753a253bb3e40f11be33d2c70368adc205cca6 |
|
09-Jun-2015 |
Andre Eisenbach <eisenbach@google.com> |
Do not ask for confirmation for temporary pairing
Bug: 20187234
Change-Id: I4213a3c2cafecdb39fcf3f19464c91776180267a
/system/bt/btif/src/btif_dm.c
|
| 818d0f2afb10c75125b0df9ea2bce6108268a269 |
|
21-May-2015 |
Casper Bonde <c.bonde@samsung.com> |
SAP: Make it possible to enforce a 16-digit pin code (1/5)
This change enable the posibility to enforce using a
16-digit pin or MITM for a RFCOMM or L2CAP connection.
This is needed for the SIM access profile.
Change-Id: I02886ce284f27295205def3c66fb76372f5dab4f
Signed-off-by: Casper Bonde <c.bonde@samsung.com>
/system/bt/btif/src/btif_dm.c
|
| 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/btif/src/btif_dm.c
|
| 7cb76b4277d603e5abfe7f9222a45ebdf7a715e2 |
|
07-May-2015 |
Satya Calloji <satyac@broadcom.com> |
Fix GATT connection failure after BT reset
Handles the address type incorrect value storage issue
and removes usage of DMT supported flag which was based
on legacy code
Bug: 20912064
Change-Id: I5bd20dc9cd0997ac3dbd4b346cc0513f1809f241
/system/bt/btif/src/btif_dm.c
|
| 7bd4038ea9a2f1953dc98fa67aec413b6247c584 |
|
19-May-2015 |
Satya Calloji <satyac@broadcom.com> |
Fix for IRK and IR key write issue
Fixes the incorrect flipping of values
for IRK and IR keys in bt_config.conf file
Change-Id: Ia4f9c274b6a3f7594ec31d8bd89b27d1ae54ac78
/system/bt/btif/src/btif_dm.c
|
| 1287166da9c34f041d54a78800b79cb2738675a9 |
|
09-May-2015 |
Andre Eisenbach <eisenbach@google.com> |
DO NOT MERGE Fix compilation on platforms with BLE_INCLUDED == FALSE
This is not a comprehensive fix. More work is necessary to ensure the
correct separation of BLE_INCLUDED TRUE/FALSE as well as removing many
of the hacked-up if() statements resulting from this patch.
Change-Id: I1812594feba0bf43369096e472a8b18cde305255
/system/bt/btif/src/btif_dm.c
|
| 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/btif/src/btif_dm.c
|
| e87ef6dba42ebaa94c7f0200d9e5223d1259b9d9 |
|
01-May-2015 |
Andre Eisenbach <eisenbach@google.com> |
Use BTM structures for LE pairink keys and store LTK
The long term key (LTK) was not assigned to the correct struct element
before saving the key to NVRAM.
Change-Id: Icfce82f5b70518e725875771756edde0b9caeb88
/system/bt/btif/src/btif_dm.c
|
| 8a05724400085c56bdb2c4d7293226a7aa1ace37 |
|
30-Apr-2015 |
Andre Eisenbach <eisenbach@google.com> |
Fix LE pairing LTK storage issue
Two separate issues prevented the correct LTK from being storred in
non-volatile storage and thus prevented an LE device from working after
Bluetooth was restarted:
1. tBTM_SEC_BLE_KEYS contained a field "pltk" which stored the LTK, but
downstream the field "ltk" in the same structure was used to access
the key.
2. The structure element p_key_value was not deep-copied for
BTA_DM_BLE_KEY_EVT events, causing data corruption and instabilities.
This patch addresses both issues.
Bug: 20091926
Change-Id: I9f9481a44bfe83cacd351f9e578451e77b573564
/system/bt/btif/src/btif_dm.c
|
| e28055315f96c0d06e73a66a9bb06df85247b5a7 |
|
22-Apr-2015 |
Chaojing Sun <cjsun@broadcom.com> |
Cross transport key mapping fixes
Change-Id: I22d97303054eccc876c4a9c7c0a50e369ff4fa62
/system/bt/btif/src/btif_dm.c
|
| 2cd086a11a972f2e437dd521a121ed76ea79a15a |
|
15-Apr-2015 |
Vinit Deshpande <vinitd@google.com> |
am f29a2fb..e07ad10 from mirror-m-wireless-internal-release
e07ad10 merge in m-wireless-internal-release history after reset to d232721ae5e5b6949a5249f0d116408b8a3c5f1d
d232721 L2CAP socket - fix merge errors
899b771 BR/EDR secure connections support
7fb0da6 Support numeric comparison in SMP
aa351f2 merge in m-wireless-internal-release history after reset to 399e89150b3df87172bdf92d54712b379324b149
399e891 Fix for AVRCP CTRL stops sending pass through command
daddea9 Free Avrcp Controller callbacks on Cleanup
764babe Protect reset of out stream with mutex
444a8da LE Privacy 1.2 and LE secure connections
8372aa5 L2CAP and SDP Search API for BT profiles (2/2)
fd422a7 Update Service Availability.
2a0652a merge in m-wireless-internal-release history after reset to 0b47e0a35c16f5b7d77c30ec1c095ed92ff4fd74
78d0f4c merge in m-wireless-internal-release history after reset to m-wireless-internal-dev
0b47e0a Avoid duplicate disconnection callbacks for fixed channel connections
5646973 Add a section on assertions to the style guide.
d768767 Merge "Avoid null-pointer dereference in l2c_release_lcb()" into m-wireless-dev
ef92b53 Avoid null-pointer dereference in l2c_release_lcb()
4bf68bf merge in m-wireless-internal-release history after reset to f538707fe64c62b1dbb8e4210e4a1bfa0bab2b56
de6ac86 Add a 'Bluedroid conventions' section to the style guide.
1b80439 Add a section to the style guide on variable declarations.
485f19e merge in m-wireless-internal-release history after reset to 4540f59bc447dc2b7b31a3e974b74a60b2417e7d
bef8940 merge in m-wireless-internal-release history after reset to 841c9103cad1898ceca87b734acd4d4537f9f452
ab4c38c merge in m-wireless-internal-release history after reset to a7e698f5a9e062f62e21bc435643975c30bab846
2807a74 merge in m-wireless-internal-release history after reset to a7e698f5a9e062f62e21bc435643975c30bab846
99dbe9a merge in m-wireless-internal-release history after reset to 78c0b060f29b7b7014adddb2f98bf6ae9755c488
f7f8399 merge in m-wireless-internal-release history after reset to a5371c238b4e874d8313ac56a23451e7345ff541
3aa60d7 Make A2DP audio HAL a shared library again
3256a31 Move unused include file out of hci_audio.h
b866b69 Add option for schedule_next_instance to force rescheduling
4ae5e3e Ensure alarms are called back when they expire in the past
a7bd03e Rewrite alarms to use a single posix timer instance
88e7b15 Resolved hardware error observed during SCO Connection setup
Change-Id: Ib9a0a2ffca1d4811a9a9e56674bf43275d8b2205
|
| 7fb0da6c0df9491f06c61ab0ba4183129502a065 |
|
30-Jan-2015 |
Satya Calloji <satyac@broadcom.com> |
Support numeric comparison in SMP
Enable support for numeric comparison in SMP when LE Secure connection
is supported. The change will distinguish between passkey confirmation
in case of Security grant and Passkey confirm.
Original author: Priti Aghera <paghera@broadcom.com>
Bug: 19816438
Change-Id: Id1fd072d1e567a80b020b4ba217486c3308ad39d
/system/bt/btif/src/btif_dm.c
|
| 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/btif/src/btif_dm.c
|
| 8372aa5fa535ee4f09c09981b6125b54ace31fe2 |
|
25-Mar-2015 |
Kim Schulz <k.schulz@samsung.com> |
L2CAP and SDP Search API for BT profiles (2/2)
Added support for exposing L2CAP to Java such that OBEX over L2CAP
is made possible.
Added support to create SDP records as a seperate step.(as opposed to
creating a SDP record when a BluetoothSocket is created).
This allows both a RFCOMM channel and a L2CAP PSM to be included in a
SDP record. (Additionally the content of the SDP record is set by the
profile in Java, in stead of beeing hardcoded in the socket layer.)
This completes the L2CAP channel exposure to Java.
Change-Id: Iaf68a07d910145cdd33e940d73cd680f79164100
/system/bt/btif/src/btif_dm.c
|
| b246a1a750c5a337faaa6033b39e78c8bdd4c2fb |
|
10-Apr-2015 |
Prerepa Viswanadham <dham@google.com> |
Merge commit '4bf68bf020c7fd1aabcdc4b5d8f5fbb8bacdec9d' into merge_work
Change-Id: Ibc6d6e691b7f97611d16f96220346dfd6ffbbf52
|
| 9c8dface40b8427b3dc03ddd13ca7532f7d855d5 |
|
08-Apr-2015 |
Rakesh Iyer <rni@google.com> |
Fix init sequence for BT AV sink.
BTA_AvEnable_Sink() was being called to early causing
a crash loop when the BT AV_SINK was included. This patch
changes up the init sequence to match that of the av
source. Also, rename a few constants for clarity.
Change-Id: I3e6a7e22a2643eeceb4afc082979d1d9967b0b99
/system/bt/btif/src/btif_dm.c
|
| 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/btif/src/btif_dm.c
|
| 4540f59bc447dc2b7b31a3e974b74a60b2417e7d |
|
05-Feb-2015 |
VenkatRaghavan VijayaRaghavan <venkatrv@broadcom.com> |
Static code analysis cleanups and minor bug fixes
- Fix for initializing all the un-initialized variables
- Handling system call failure like socket,fcntl etc...
- In btpan_tap_close validate tap_if_down and close the socket.
- Invalid memset size, which could have potential memory issue
- Change -1 to INVALID_FD where appropriate
Bug: 19417758
Change-Id: Id31832f8678b2d72c80740c29b946a94e7ae0197
/system/bt/btif/src/btif_dm.c
|
| 933926c92e1378cc76bc9c149107e670c4872d4e |
|
03-Apr-2015 |
Scott James Remnant <keybuk@google.com> |
Fix missing #includes needed for glibc
Some standard library functions are used while relying on bionic headers
including the headers the functions were actually declared on. Add those
missing #includes so that bluetooth.default.so will compile on glibc.
Change-Id: Ied9f89ce5a05911fca63f6bfe1b8cc8196ab3b1c
/system/bt/btif/src/btif_dm.c
|
| e1a9e52ff59d36bd1bb5b7b3a02fafba6394edfe |
|
31-Mar-2015 |
Etan Cohen <etancohen@google.com> |
Merge commit 'f7f839985b3931682363d2ef3b7c5cae55a842ee' into merge
Change-Id: Iaaec1ea0bf3009b7e32a9a60f697631a3f56e889
|
| 7b85efab9d5921642e841f0145047093571cce20 |
|
26-Sep-2014 |
Nitin Arora <niarora@codeaurora.org> |
Delete 0 index LE scan filter at inquiry cancel
This patch ensures that the 0 index filter is deleted when the
inquiry is cancelled due to initiation of a direct connection
from inquiry or due to return from the Settings menu screen
Change-Id: I281c6ace15b17fb7e413c42d36e016b8f82d2ace
/system/bt/btif/src/btif_dm.c
|
| f8027005333c88a2f097cfd70d15c3d54c7764ae |
|
12-Mar-2015 |
Chris Manton <cmanton@google.com> |
Demote, cleanup and extend observed logging
/system/bt/btif/src/btif_dm.c
|
| 95b74f252f534ec757aab1fc08e086e02b2cfe8d |
|
12-Mar-2015 |
Sharvil Nanavati <sharvil@google.com> |
Use fully qualified path for btcore includes.
/system/bt/btif/src/btif_dm.c
|
| 1d8e6b8e7fcf6bc691be94a362030915ac15b23b |
|
06-Feb-2015 |
VenkatRaghavan VijayaRaghavan <venkatrv@broadcom.com> |
Prevent Memory overbound and initialize variables
1. Fix for initializing all the un-initialized variables
2. Potential strncpy overbound
Bug: 19417758
/system/bt/btif/src/btif_dm.c
|
| 8ff3fea05b0d01f7a011326542161f892e2b31d6 |
|
07-Jan-2015 |
Chris Manton <cmanton@google.com> |
Rename legacy uuid_copy to not conflict
/system/bt/btif/src/btif_dm.c
|
| 44802768c447ab480d4227b3a852a97d923b816d |
|
24-Dec-2014 |
Sharvil Nanavati <sharvil@google.com> |
Add platform-independent logging macros to OSI.
These macros should replace ALOG* and the various trace macros
used throughout bluedroid. This change eliminates all uses of the
ALOG* macros in favor of the new ones.
/system/bt/btif/src/btif_dm.c
|
| a50fc88c9f784a2422ceac014fea47ac1717647b |
|
31-Oct-2014 |
Zach Johnson <zachoverflow@google.com> |
Remove BTA_CheckEirData, a direct redefinition of BTM_CheckEirData
Gentle move towards using more of BTM directly.
/system/bt/btif/src/btif_dm.c
|
| 9609cee33087141eeb7b5adede488d7e13bfcebd |
|
16-Oct-2014 |
Sharvil Nanavati <sharvil@google.com> |
Use correct service ID for A2DP source to make way for A2DP sink.
/system/bt/btif/src/btif_dm.c
|
| 794f3b5f126fffc3dd1129a710187591348bbf23 |
|
01-Oct-2014 |
Chris Manton <cmanton@google.com> |
Removal of bd.[c|h]
Consolidate legacy types into bt_types.h
/system/bt/btif/src/btif_dm.c
|
| f1c764fab01c929f71e185b97433bf40938026d3 |
|
24-Feb-2015 |
Sharvil Nanavati <sharvil@google.com> |
Make build more strict by adding more warning flags.
This change introduces -Wunused-but-set-variable to help catch
programming errors. It also undefines NDEBUG so assertions are
fatal and defines LOG_NDEBUG=1 to suppress LOGV.
/system/bt/btif/src/btif_dm.c
|
| 39110ec88460421618330863807804e03594ef67 |
|
06-Oct-2014 |
Zach Johnson <zachoverflow@google.com> |
Remove duplicate local bdaddr management functions
/system/bt/btif/src/btif_dm.c
|
| 8a6a89faa942aed4f176b0c98402d01c8bdd6aa6 |
|
20-Aug-2014 |
Sharvil Nanavati <sharvil@google.com> |
Introduce btcore, a low-level library to manipulate Bluetooth data types.
This change adds a single module to btcore: bdaddr. The bdaddr module
is reponsible for manipulating and working with Bluetooth addresses.
/system/bt/btif/src/btif_dm.c
|
| 9d52f88bfc07556cb01ab3055f5b1242c9b467aa |
|
19-Aug-2014 |
Sharvil Nanavati <sharvil@google.com> |
Eliminate unused arguments to btif_config and clarify variable names
/system/bt/btif/src/btif_dm.c
|
| 1b8b1397dad3ba82ec2b7d10233922e13cf510cf |
|
10-Feb-2015 |
Andre Eisenbach <eisenbach@google.com> |
am dfb3b2f2: Add flag indicating encrypted connections to btif_dm_get_connection_state()
* commit 'dfb3b2f2595dc16fe7f576a4b0c2f5e73db0327f':
Add flag indicating encrypted connections to btif_dm_get_connection_state()
|
| 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
/system/bt/btif/src/btif_dm.c
|
| 7c5823798cccb6731a164edff7127ebfce074558 |
|
28-Jan-2015 |
Andre Eisenbach <eisenbach@google.com> |
am 89363761: Change pairing_cb to assume temporary pairing by default
* commit '893637614568b8ac7dc996c2e9bdbde481fbdc08':
Change pairing_cb to assume temporary pairing by default
|
| 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
/system/bt/btif/src/btif_dm.c
|
| 7fbc6954fac90dd7148ac73aa478fcc5e2d75be8 |
|
25-Jan-2015 |
Elliott Hughes <enh@google.com> |
am f976082e: Merge "Fix omitted libc includes."
* commit 'f976082eead2b7c19bf8c00d79e4723e6c4eb8e9':
Fix omitted libc includes.
|
| c7503db23f91676b2df732becb9579d5ccdcc7a7 |
|
24-Jan-2015 |
Ian Coolidge <icoolidge@google.com> |
Fix omitted libc includes.
Change-Id: I72c08984aeef60e4833e600b4351759b9687a014
/system/bt/btif/src/btif_dm.c
|
| 11cf5ccd5cd6dd1568bf69e4b6cbc27c95f5026d |
|
11-Dec-2014 |
Chih-Hung Hsieh <chh@google.com> |
resolved conflicts for merge of ed0bdd42 to lmp-mr1-dev-plus-aosp
Change-Id: Ife8b72d3688ed78a95ccb8d5e0b60f40e7fec9e9
|
| 104e3f238f500cacdb8afaccdc672dfc34eae7ee |
|
12-Nov-2014 |
Bernhard Rosenkränzer <Bernhard.Rosenkranzer@linaro.org> |
Cleanups needed to make clang happy
This patch removes a slew of unused variables and some unused functions,
fixes some incomplete initializations of structs and an sprintf
parameter mismatching the format string.
Change-Id: I35f22fdccc8350f885cd357d3685b869224fa433
Signed-off-by: Bernhard Rosenkränzer <Bernhard.Rosenkranzer@linaro.org>
/system/bt/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
/system/bt/btif/src/btif_dm.c
|
| 3e0dc7324e7b0127f9d15609bab395100a22098d |
|
24-Oct-2014 |
Andre Eisenbach <eisenbach@google.com> |
LE: Make local privacy configurable
Bug: 17753401
Change-Id: I288ea8b6194d91d18485d0f3f1bbf997f97a26dd
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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>
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/btif/src/btif_dm.c
|
| 249f600c1518c015f5cb45720cb022a203ba744e |
|
18-Jun-2014 |
Andre Eisenbach <eisenbach@google.com> |
LE: Add is_connected() function (2/3)
Change-Id: I73c4ea7f13982bf9c208996f9c749d2dfbe698be
/system/bt/btif/src/btif_dm.c
|
| e8c3d75b75493911ebf0f99c83676359657178f7 |
|
04-May-2014 |
Sharvil Nanavati <sharvil@google.com> |
Logging cleanup: BTIF and APPL.
Change-Id: I5b1214642bbb4b9aecc0fd2c899a6ec2c9793286
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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>
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/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
/system/bt/btif/src/btif_dm.c
|
| 5738f83aeb59361a0a2eda2460113f6dc9194271 |
|
13-Dec-2012 |
The Android Open Source Project <initial-contribution@android.com> |
Snapshot cdeccf6fdd8c2d494ea2867cb37a025bf8879baf
Change-Id: Ia2de32ccb97a9641462c72363b0a8c4288f4f36d
/system/bt/btif/src/btif_dm.c
|