| d5bba906b0704cd60e824613bd2e438935ba5d89 |
|
04-May-2014 |
Sharvil Nanavati <sharvil@google.com> |
Logging cleanup: RFCOMM and GAP.
Change-Id: I83fda4f0805aaeb2ca060870449868879edcff78
/external/bluetooth/bluedroid/stack/rfcomm/rfc_mx_fsm.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/stack/rfcomm/rfc_mx_fsm.c
|
| 5acd502368d1eb3fc445d6787a1d7d64d45d0a5c |
|
05-Nov-2013 |
kschulz <k.schulz@samsung.com> |
RFCOMM: fix connection timeout during security setup
The RFC_T2_TIMEOUT used in rfc_mx_conf_cnf is replaced with RFCOMM_CONN_TIMEOUT,
increasing the timeout value from 20 sec to 120 sec.
Bug: 11523955
Change-Id: I992f3d20e9e4c6465850dcf1f52af0b7d39dd893
/external/bluetooth/bluedroid/stack/rfcomm/rfc_mx_fsm.c
|
| 5738f83aeb59361a0a2eda2460113f6dc9194271 |
|
13-Dec-2012 |
The Android Open Source Project <initial-contribution@android.com> |
Snapshot cdeccf6fdd8c2d494ea2867cb37a025bf8879baf
Change-Id: Ia2de32ccb97a9641462c72363b0a8c4288f4f36d
/external/bluetooth/bluedroid/stack/rfcomm/rfc_mx_fsm.c
|