| 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_sock_l2cap.c
|
| 56a3be0d6eaa1bc264736e399fb32d3094f0b513 |
|
02-Jun-2015 |
Pavlin Radoslavov <pavlin@google.com> |
Replace malloc/calloc/free with osi_malloc/osi_calloc/osi_free
There were several leftover places that were still using
malloc/calloc/free .
Those are replaced to use osi_malloc/osi_calloc/osi_free like
majority of the rest of the code.
Note: There are few remaining places that are still using
malloc/calloc/free:
* Some of the unit tests
* audio_a2dp_hw/audio_a2dp_hw.c
It is used as part of the audio.a2dp.default.so library,
and the bluetooth.default.so library
Its usage of malloc/calloc/free should be refactored
independently.
Change-Id: Iafbed996e5f1ae8eb1343fb2acfadf32e515e419
/system/bt/btif/src/btif_sock_l2cap.c
|
| 9f2120c15220a8bc865d3a065e6121a1b4d6cf57 |
|
24-Apr-2015 |
Etan Cohen <etancohen@google.com> |
Merge commit '00e8f5e' into merge2
Change-Id: Ifa83bd342458eba33fdd11a9db38d2f9e818b759
|
| 949baaef237d08f482b5132dc389ae84b05113f8 |
|
16-Apr-2015 |
Ian Coolidge <icoolidge@google.com> |
Fix missing includes under glibc on new code.
Change-Id: I2451f782ce3f51147ebaddc559c616eac0a2b7d9
/system/bt/btif/src/btif_sock_l2cap.c
|
| f54df6b47616eeae11001b1d2e977548fe316227 |
|
15-Apr-2015 |
Vinit Deshpande <vinitd@google.com> |
Fix build issues after the merge
Change-Id: Ia856311187a0b2168cb859bd8b2300ff59df6569
/system/bt/btif/src/btif_sock_l2cap.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_sock_l2cap.c
|