17a1dfbadd39101faf713b2cd03a3428bda5e8da |
|
06-Apr-2016 |
Sharvil Nanavati <sharvil@google.com> |
Delete unused JV code Bug: 28068134 Change-Id: I16d017ef90269a435b8f66a58ed06d2fc89d407f
/system/bt/bta/jv/bta_jv_act.c
|
ab99638f9a05ae7ed04ab0a75d48cbd1d78b36e8 |
|
09-Mar-2016 |
Navin Kochar <navin.kochar@intel.com> |
Add LE L2CAP Connection Oriented Channel This implementation for LE L2CAP Connection Oriented Channel (a Bluetooth Core Spec 4.1 feature) has been tested on the following formal and informal IOP events conducted by BT SIG Sport and Fitness Working Group. * Informal IOP – Tokyo 2014 * UPF 49 – Berlin 2014 * Formal IOP – Tokyo 2014 * Formal IOP – Santa Clara 2015 Bug: 27852645 Change-Id: Ia6de62f9321a78b98930629f65078884157a9c0d Signed-off-by: Navin Kochar <navin.kochar@intel.com>
/system/bt/bta/jv/bta_jv_act.c
|
9b4de840e65ce051f9585c12071f4bcf5fa26ea3 |
|
20-Sep-2015 |
Srinu Jella <sjella@codeaurora.org> |
Cleanup L2CAP socket properly on close Use case: 1. Sometimes pairing pop up occurs during Android beam transfer though it is not required. 2. No OPP Tx request over OBEX if we cancel during file transfer. Precondition 1. WIFI ON and conneted with AP. Steps: 1. Pair and connect from DUT to remote. 2. Go to gallery and send a file. 3. Accept same file and stop it from remote during transfer. 4. Repeat step 2-4 10 times. Failure: OPP Tx should not fail. Root cause: Close request was not properly handled from BT-IF layer. Fix: 1. Handled the close request properly from BT-IF layer to close the socket variables and instruct the BTA layer close from there as well. 2. Clean up L2CAP socket properly on closure to free the entry registered with security manager to avoid leak in security manager records. Bug: 27852645 Change-Id: I4f5d6ac92317bcaee5f9285ba71d13eea84c737c
/system/bt/bta/jv/bta_jv_act.c
|
2bbedbf283f30378aaf347f9f0dd7986ed408f64 |
|
16-Feb-2016 |
Srinu Jella <sjella@codeaurora.org> |
Track TX empty event to manage sniff timer Use case: OPP TX while inquiry is in progress. Steps: 1. Send any file from DUT to remote using BT. 2. Accept file on remote. 3. During file transfer, start inquiry on DUT and observe behaviour. Failure: DUT sends sniff command in the middle of the transfer though it is not required. eventually OPP Tx over L2CAP file transfer fail. Root Cause: As per the current implementation, for tx it will immediately starts idle timer without checking for the completion status of tx. Fix: Handled the tx complete event from L2CAP properly to start the idle timer to manage the sniff properly. Bug: 27852645 Change-Id: I298075590042e82a2f33837f6df6af0b2fd8179a
/system/bt/bta/jv/bta_jv_act.c
|
12265e39b511f28425236b0dc97c78e7d837304b |
|
13-Feb-2016 |
Pavlin Radoslavov <pavlin@google.com> |
Fix C/C++ compiler generated warnings * Remove unused functions: -Wno-unused-function * Fix logical operations that are missing parentheses: -Wno-logical-not-parentheses, -Wno-parentheses * Add missing braces in initializers: -Wno-missing-braces * Remove unused variables: -Wno-unused-variable * Fix printf()-like formatting issues: -Wno-format * Avoid using unitialized variables: -Wno-maybe-uninitialized, -Wno-uninitialized * Fix a bug inside bta_gattc_get_gatt_db_impl() when the processed GATT DB attribute type is unknown. * Fix warnings about missing field initializers: -Wno-missing-field-initializers * Re-implement macro COMPILE_ASSERT(COND) to fix a compilation warning: -Wno-non-literal-null-conversion * Fix sign mismatch comparison warnings: -Wno-sign-compare * Fix warnings related to enum conversion: -Wno-enum-conversion * Fix warnings related to incompatible pointer types: -Wno-incompatible-pointer-types * Fix warnings related to enum conversion: -Wno-enum-conversion Bug: 26879229 Change-Id: I522931fe156aeab23ae841051a9e25ceab00b1c2
/system/bt/bta/jv/bta_jv_act.c
|
5fe6f0cf6b223e3ed6be4912d55b3ed5b41ce0cd |
|
06-Feb-2016 |
Pavlin Radoslavov <pavlin@google.com> |
Removed checks for NULL returns after osi_calloc() / osi_malloc() Removed explicit checks for NULL pointer returns after calls to osi_calloc() and osi_malloc(), because those are not needed. If the memory allocation fails, osi_calloc() and osi_malloc() will trigger an assert. Bug: 27048759 Change-Id: I2791eb2f69c08f991f8fcdef10e101a41568cd95
/system/bt/bta/jv/bta_jv_act.c
|
abd70abb5e42c9431df94fe9d2c4a78a0d8d9af9 |
|
05-Feb-2016 |
Pavlin Radoslavov <pavlin@google.com> |
Replaced osi_getbuf()/osi_freebuf() with osi_malloc()/osi_free() Removed the alternative buffer allocation osi_getbuf() / osi_freebuf() and use instead osi_malloc() / osi_free(). Correspondingly, replaced usage of osi_freebuf_and_reset() with osi_free_and_reset(). Bug: 24914560 Change-Id: I7a9599ba7fa900321f087da684428133eb0ddd6b
/system/bt/bta/jv/bta_jv_act.c
|
b2c46a45410d6ecfa2b6df57fb81ee4b192e5455 |
|
27-Aug-2015 |
Hemant Gupta <hemantg@codeaurora.org> |
Fix RFCOMM Rx speed of transfer Use Case: 1. OPP Rx use case on the DUT Side 2. Transfer 10Mb+ of file from remote to DUT 3. Observe speeds over RFCOMM (expected 1.5Mbps+) Failure: Actual speeds lesser than 1.5Mbps Root Cause: Rx bottlenecks seen due to frequent timer operation during incoming data on RFCOMM Fix: BUSY and IDLE states of BT Power manager are already handled inside the stack and no need to explicitly set IDLE and BUSY states from JV layer anymore. Bug: 22487461 Change-Id: Icdc25c52103d6a849cc6e12656d9c69f5e152b05
/system/bt/bta/jv/bta_jv_act.c
|
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/bta/jv/bta_jv_act.c
|
e084febf18d903518dc44bd878c5ea4e4110e7ff |
|
01-Aug-2015 |
Sharvil Nanavati <sharvil@google.com> |
am 9de273d9: Fix CTS Verifier test for insecure RFCOMM connection. * commit '9de273d9fb99b9f612b8acd50e09225f60444363': Fix CTS Verifier test for insecure RFCOMM connection.
|
9de273d9fb99b9f612b8acd50e09225f60444363 |
|
31-Jul-2015 |
Sharvil Nanavati <sharvil@google.com> |
Fix CTS Verifier test for insecure RFCOMM connection. Closing an RFCOMM server socket does not remove the corresponding service record from the security database. However, the RFCOMM channel becomes free for reuse. The next RFCOMM server socket will therefore "inherit" the service record for the closed one if it happens to reuse the same channel. Bug: 22880207 Change-Id: Ida3fee49e5f40667d9992dc4c4442f9289adae9e
/system/bt/bta/jv/bta_jv_act.c
|
bb95452741bfd65723ea417c25dbd326c7568ab7 |
|
03-Jun-2015 |
Arman Uguray <armansito@google.com> |
build: Fix ptr <-> integer cast warnings This CL removes the -Wno-pointer-to-integer-cast and -Wno-integer-to-pointer-cast flags from GN build files. The resulting errors were fixed using the following: 1. All ptr <-> integer casts are now done by using the new PTR_TO_INT/INT_TO_PTR macros defined in osi.h 2. The TIMER_PARAM_TYPE macro, defined in gki/common/gki.h and include/bt_target.h have been redefined as void* rather than UINT32. This is better, since "void*" can act as a simple container without any precision loss that would be caused by a type such as UINT32 on 64-bit systems. void* inherently is a safer container for all pointer types but UINT32 isn't. BUG=21570302 Change-Id: I4a82c4a40c91caa31e372382c40d424be220cbe3
/system/bt/bta/jv/bta_jv_act.c
|
cab5fc179730ce6910989307680b275195876c4d |
|
02-Jun-2015 |
Arman Uguray <armansito@google.com> |
gn-build: Remove all -Wno-unused-* flags from build files This CL removes the -Wno-unused-variable, -Wno-unused-value, and -Wno-unused-function flags from all GN build and Android.mk files (except in test/ & tools/, which are not built using GN yet). Compile warnings, caused by the newly enabled flags, have been fixed throughout the code base. Bug: 21570302 Change-Id: I1c128b62256faa17668124798341005bcd0f7315
/system/bt/bta/jv/bta_jv_act.c
|
eae61663a5c44f2a5757ae3df80cbc3b97fa6d60 |
|
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/bta/jv/bta_jv_act.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/bta/jv/bta_jv_act.c
|
b8b3e8070ad027e7a45ca5048ae807c4ec099b15 |
|
18-Apr-2015 |
Priti Aghera <paghera@broadcom.com> |
Initialize white list size after stack reset The white list size is not currently set correctly, preventing devices from being added to the LE whitelist, thus completely breaking re-connects. This fixes the white list management and propagates the correct reason code for HID close events to make sure a device is re-added to the white list if necessary. Bug: 20290744 Change-Id: I46d7254ff3568c9964688cb192b9deb6b7d3062d
/system/bt/bta/jv/bta_jv_act.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
|
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/bta/jv/bta_jv_act.c
|
e1a9e52ff59d36bd1bb5b7b3a02fafba6394edfe |
|
31-Mar-2015 |
Etan Cohen <etancohen@google.com> |
Merge commit 'f7f839985b3931682363d2ef3b7c5cae55a842ee' into merge Change-Id: Iaaec1ea0bf3009b7e32a9a60f697631a3f56e889
|
8ff3fea05b0d01f7a011326542161f892e2b31d6 |
|
07-Jan-2015 |
Chris Manton <cmanton@google.com> |
Rename legacy uuid_copy to not conflict
/system/bt/bta/jv/bta_jv_act.c
|
794f3b5f126fffc3dd1129a710187591348bbf23 |
|
01-Oct-2014 |
Chris Manton <cmanton@google.com> |
Removal of bd.[c|h] Consolidate legacy types into bt_types.h
/system/bt/bta/jv/bta_jv_act.c
|
14c80d98b0b6ea5e6f7a2302626cb61a38d17101 |
|
08-Oct-2014 |
Zach Johnson <zachoverflow@google.com> |
Refactor bta_jv functions Remove unused L2CAP and SDP code to reduce distraction from unused code path. In general, if we need any of this behavior in the future, it's best to talk directly to the apis instead of through another layer.
/system/bt/bta/jv/bta_jv_act.c
|
39110ec88460421618330863807804e03594ef67 |
|
06-Oct-2014 |
Zach Johnson <zachoverflow@google.com> |
Remove duplicate local bdaddr management functions
/system/bt/bta/jv/bta_jv_act.c
|
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/bta/jv/bta_jv_act.c
|
d3460f3b6b2d5a5504371df1d3bf594cfd9ecacb |
|
29-Jun-2014 |
Hemant Gupta <hemantg@codeaurora.org> |
am d9e2d0f1: Bluetooth: Restarting PM timer during incoming rfcomm data. * commit 'd9e2d0f1fa19f737632e82c24ba278990b8a7548': Bluetooth: Restarting PM timer during incoming rfcomm data.
|
d9e2d0f1fa19f737632e82c24ba278990b8a7548 |
|
30-Sep-2013 |
Hemant Gupta <hemantg@codeaurora.org> |
Bluetooth: Restarting PM timer during incoming rfcomm data. During incoming rfcomm data, we were setting the pm mode to active, thereby stopping timer and never restarting it again. So Dut was never going to sniff , if the last packet is incoming packet. Therefore add change to restart the PM timer during incoming data. Change-Id: I4396bb2f267b12cb92a944c15609ddeaa13288ad
/system/bt/bta/jv/bta_jv_act.c
|
afa6e1abbedaad8fe854b0f43999b8aeb801af91 |
|
28-Jun-2014 |
Matthew Xie <mattx@google.com> |
resolved conflicts for merge of e8c3d75b to master Change-Id: I78ef69c4d54a36243620ae14296d3507e3339567
|
e8c3d75b75493911ebf0f99c83676359657178f7 |
|
04-May-2014 |
Sharvil Nanavati <sharvil@google.com> |
Logging cleanup: BTIF and APPL. Change-Id: I5b1214642bbb4b9aecc0fd2c899a6ec2c9793286
/system/bt/bta/jv/bta_jv_act.c
|
1a3006f317b1b493dde1b80c4debbcf1bf5f6727 |
|
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/bta/jv/bta_jv_act.c
|
60a0084d55c2473a3b3fd311ee071c92e186fe43 |
|
28-May-2014 |
Matthew Xie <mattx@google.com> |
Change error message to debug to avoid spamming bug 15116703 Change-Id: I7b218418b1a57c3d68d6b239f961a930f0c98371
/system/bt/bta/jv/bta_jv_act.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/bta/jv/bta_jv_act.c
|
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/bta/jv/bta_jv_act.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/bta/jv/bta_jv_act.c
|
5303f9d369946f43167b5e2423799d30c4455df1 |
|
27-Feb-2014 |
Narayan Kamath <narayan@google.com> |
resolved conflicts for merge of 277ba466 to klp-modular-dev-plus-aosp Change-Id: Idc42f72a94c205cfe94feb220651a483cf418e84
|
22c6e505dc65ab3d624e4ccd7c48c95fe2128703 |
|
12-Feb-2014 |
Kévin PETIT <kevin.petit@arm.com> |
Various fixes for LP64 Changes include - Cast numbers to their proper length before casting to a pointer. - Use intptr_t when pointers are stored as integers. - Eliminate 'implicit declaration' warnings Signed-off-by: Matthew Leach <matthew.leach@arm.com> Signed-off-by: Ashok Bhat <ashok.bhat@arm.com> Signed-off-by: Marcus Oakland <marcus.oakland@arm.com> Signed-off-by: Kévin PETIT <kevin.petit@arm.com> Change-Id: I5664a087c5fbc322baa9178552404dbe9a992359
/system/bt/bta/jv/bta_jv_act.c
|
a69e0ae1107e3148542a76ac840f3bcaa8ee2661 |
|
24-Feb-2014 |
Matthew Xie <mattx@google.com> |
am 47128cf9: Merge "Bluetooth: fix sniff issue with multiple rfcomm connection in same ACL" * commit '47128cf95b72eedb7a6da29687b1ff6b668b59d6': Bluetooth: fix sniff issue with multiple rfcomm connection in same ACL
|
b26a902ec2458256150dc85a694efe8f3b15dcf7 |
|
17-Sep-2013 |
Pradeep Panigrahi <pradeepp@codeaurora.org> |
Bluetooth: fix sniff issue with multiple rfcomm connection in same ACL When there are multiple rfcomm connection with same appid and peer bd address, we were clearing jv pm control block in addition to closing connection to service with registered app id. Since appid is common across all the client and server app registed to jv. we were clearing entire connection to service for this appid and peer bdadres which was corrupting sniff logic, when another rfcomm connection exists with same peer bdaddress. So avoiding closing of connection to the service when multiple rfcomm connection exists in same ACL. Change-Id: Id71ef5f7f0e00f1bda3b70a4826c31bef46caafc
/system/bt/bta/jv/bta_jv_act.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/bta/jv/bta_jv_act.c
|
016e25eae39ff5249d076e973005a2d21fdb6813 |
|
01-Feb-2014 |
Mike J. Chen <mjchen@google.com> |
Fix bug with wrong parameter passed to logu Caught by compiler warning "passing argument 2 of 'logu' from incompatible pointer type". Change-Id: If6047654c9862209d3426f832a366ac884b2c9e9 Signed-off-by: Mike J. Chen <mjchen@google.com>
/system/bt/bta/jv/bta_jv_act.c
|
511b814ae29e33f7dc9089186f1cbe914767c5b9 |
|
20-Oct-2013 |
Matthew Xie <mattx@google.com> |
Handle CL opening state in bta_jv_free_rfc_cb When the local device is openning an rfc channel and is being closed before it's opened, we should close the channel instead of ignoring. bug 11299049 Change-Id: I702500d489c8b3d3764e36340106433232a127c0
/system/bt/bta/jv/bta_jv_act.c
|
2f338f25530d2aaab7acf45701c271d10b81d96d |
|
24-Mar-2013 |
Ganesh Ganapathi Batta <ganeshg@broadcom.com> |
BT: JV rfcomm socket sniff support Bug:8322094 Change-Id: Ib472f39488b685ac396289e65c1da21fdfd93c4c
/system/bt/bta/jv/bta_jv_act.c
|
9ac641d0a674333af57b85b367e64cf94dfae291 |
|
16-Jan-2013 |
Matthew Xie <mattx@google.com> |
fixed rfc resouce leaking and multi-session issue also added more debug messages bug 7486080 Change-Id: Ic21e9d2df5f651b51ea2126a3cac25811808dcfb
/system/bt/bta/jv/bta_jv_act.c
|
689d66b6559dcb3a0ad7f6cc33b6129e50910253 |
|
13-Dec-2012 |
The Android Open Source Project <initial-contribution@android.com> |
Snapshot 9fd57cbacd95e89602f430244c35bbc67f08b6d2 Change-Id: Ibc3a4bf4161d286c7cfab89a19c676eb5cc9224f
/system/bt/bta/jv/bta_jv_act.c
|
5738f83aeb59361a0a2eda2460113f6dc9194271 |
|
13-Dec-2012 |
The Android Open Source Project <initial-contribution@android.com> |
Snapshot cdeccf6fdd8c2d494ea2867cb37a025bf8879baf Change-Id: Ia2de32ccb97a9641462c72363b0a8c4288f4f36d
/system/bt/bta/jv/bta_jv_act.c
|