summaryrefslogtreecommitdiffstats
path: root/stack/rfcomm
Commit message (Collapse)AuthorAgeFilesLines
* Fix a wrong check in rfc_parse_dataHansong Zhang2018-11-181-1/+1
| | | | | | | | Bug: 78288018 Bug: 111436796 Test: manual Change-Id: I16e6026acbaac230fe1453bbac040d1b75bcea2a (cherry picked from commit d1ced302cd1066087588c891027b1756be31db46)
* Add bound check for rfc_parse_dataHansong Zhang2018-11-181-1/+13
| | | | | | | Bug: 78288018 Test: manual Change-Id: I44349cd22c141483d01bce0f5a2131b727d0feb0 (cherry picked from commit 6039cb7225733195192b396ad19c528800feb735)
* Check remaining frame length in rfc_process_mx_messageHansong Zhang2018-11-181-0/+27
| | | | | | | | Bug: 111936792 Bug: 80432928 Test: manual Change-Id: Ie2c09f3d598fb230ce060c9043f5a88c241cdd79 (cherry picked from commit 0471355c8b035aaa2ce07a33eecad60ad49c5ad0)
* Merge tag 'android-6.0.1_r22' of ↵staging/cm-13.0+r22Steve Kondik2016-03-111-0/+1
|\ | | | | | | | | | | | | | | https://android.googlesource.com/platform/system/bt into cm-13.0 Android 6.0.1 release 22 Change-Id: I2e682780163afc7e9c88865192a6342027c80586
| * Fix BT connection failuresDevin Kim2015-12-141-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When HFP connection failed establishing between phone and watch, it can't recover RFCOMM status which causes that HFP connection will not be made unless BT radio goes off and comes back on. RFCOMM and HFP both trying to open RFCOMM control channel at nearly same time, at some point, there's a possibility that SABM packet didn't reach out to BT controller to connect to phone from watch with HFP while phone tries to connect to watch with AW RFCOMM. This will take care of pending SABM packet to reach out to controller properly so that RFCOMM status will not be messed. Bug: 24285000 Bug: 25579482 Bug: 25579423 Bug: 25578997 Change-Id: Icc26b86c644ebd8d1c12a2fb4e94d04ba16cc2dd
* | Bluetooth:CoreStack: DUT Stack LoggingMatadeen Mishra2015-10-061-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | DUT stack information logging: -L2CAP configuration parameter, -Device role information -L2CAP flow control and congestion information -L2CAP State machine and events -RFCOMM credits count change-id: I6e74bdb1cda4455c50314f67bbcd19accd3c31e4 CRs-Fixed:602294 Bluetooth:CoreStack: DUT Stack Logging set2 DUT stack information logging: -L2CAP CIDs, PSM and MTU -removed RFCOMM credits count from default logs change-id: I7a25d751b200e8ece87f9e5fd79ab48d736087cb CRs-Fixed: 602294 Bluetooth: Add debug logs for the remote device information change-id: I857016c056635907586d8a9d0d577edde4efc34a Add logs to provide the below remote device information - Remote device features - Service class - LMP version, subversion, manufacturer - Role changed event CRs-Fixed: 602291 Change-Id: I99f51841716e27ef7170b7566379b975c99a65e0
* | Bluetooth: Reconstruct new packet to accomadate extra header lengthSrinu Jella2015-10-061-2/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | - This issue was found while running rfcomm defensic test. - Rfcomm layer trying to reuse the same packet to send to the lower layer but it will fail due to strick buffer corruption checks. - To avoid that, created a new packet to accomadate new header and copied the same payload to the new packet. CRs-Fixed: 908390 Change-Id: I5d12b76229d11480f7f37bbcd3561de97c80a0c1
* | BT: Fixed Static Analysis IssuesMatadeen Mishra2015-10-061-1/+1
|/ | | | | | | | | | - This fix avoids NULL pointer dereferences, Array Index Out of Bounds Exceptions and Banned funciton in the bluedroid code space of Bluetooth. CRs-Fixed: 890309, 890321 Change-Id: I24ae794ee01b65b5ab15c73cd82677b0481910ad
* Reduce log spam on TX queue congestionAndre Eisenbach2015-04-221-1/+1
| | | | | Bug: 19544388 Change-Id: Ib16878c08345983b3f72b484f2d5e4eb4791f2f9
* Merge commit '4bf68bf020c7fd1aabcdc4b5d8f5fbb8bacdec9d' into merge_workPrerepa Viswanadham2015-04-102-2/+0
|\ | | | | | | Change-Id: Ibc6d6e691b7f97611d16f96220346dfd6ffbbf52
| * Fix missing #includes needed for glibcScott James Remnant2015-04-022-0/+2
| | | | | | | | | | | | | | | | 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
* | Merge commit 'f7f839985b3931682363d2ef3b7c5cae55a842ee' into mergeEtan Cohen2015-03-318-36/+129
|\| | | | | | | Change-Id: Iaaec1ea0bf3009b7e32a9a60f697631a3f56e889
| * Use fully qualified path for btcore includes.Sharvil Nanavati2015-03-163-3/+3
| |
| * Remove GKI timersSharvil Nanavati2015-03-161-1/+1
| |
| * Add platform-independent logging macros to OSI.Sharvil Nanavati2015-03-161-5/+5
| | | | | | | | | | | | 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.
| * Add RFCOMM result code string for an unspecified error.Sharvil Nanavati2015-03-161-0/+1
| | | | | | | | | | | | | | | | The code enumerating the list of possible error codes is not a C enum and the original authors skipped a value. As a result, the table mapping error codes to strings is off by one after that skipped value. I'm inserting a string for that error code even though it's not defined so the strings line up with the actual error.
| * Adding some logging for the close states for RFCOMM connections.June R. Tate-Gans2015-03-162-3/+50
| |
| * Instrument data flow a bitChris Manton2015-03-163-1/+12
| | | | | | | | Use counters to grab some select data metrics.
| * Removing unnecessary BTAPI #defines.June R. Tate-Gans2015-03-161-3/+2
| |
| * Enforce GKI API buffer usageChris Manton2015-03-164-13/+13
| | | | | | | | Also add another API GKI_queue_length(BUFFER_Q *)
| * rfcomm: Check for null pointers on DLC requestChris Manton2015-03-161-10/+45
| | | | | | | | | | | | The function to get the port control block from the DLCI explicitly mentions it will return NULL if there is no active rfcomm connection for the given DLCI.
* | Fix some more missing libc includes.Ian Coolidge2015-02-062-0/+5
| | | | | | | | | | | | stddef and signal are not pulled in transitively in glibc. Change-Id: I7a834bbdc31ae2aee4cb700a223c1636fda42afa
* | Cleanups needed to make clang happyBernhard Rosenkränzer2014-12-051-1/+0
|/ | | | | | | | | 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>
* Enable flow control when tx buffer is full andZhenye Zhu2014-09-181-0/+6
| | | | | | | peer stuck in receiving bug 17525124 Change-Id:Ic67e9c0aab7e64afc9679733e6c3de10a28078d7
* Logging cleanup: RFCOMM and GAP.Sharvil Nanavati2014-06-198-180/+180
| | | | Change-Id: I83fda4f0805aaeb2ca060870449868879edcff78
* Merge BT 4.1 featuresGanesh Ganapathi Batta2014-04-302-2/+3
| | | | | | | | | | | | | | | | 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
* Major warnings cleanupMike J. Chen2014-02-116-1/+21
| | | | | | | | | | | | 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>
* RFCOMM: fix connection timeout during security setupkschulz2013-12-161-2/+6
| | | | | | | | 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
* Fixed issue that failed to update rfc credit to peer when host can not ↵zzy2013-08-131-0/+79
| | | | | | handle the incoming packets fast enough Bug 10233699: Bluetooth sockets block indefinitely on read(...)
* Added available size check to fix zero byte data available issuezzy2013-05-131-0/+3
| | | | | Bug 8950703 rfcomm connection failed in case zero byte data available
* fixed rfc resouce leaking and multi-session issueMatthew Xie2013-01-154-8/+64
| | | | | | | also added more debug messages bug 7486080 Change-Id: Ic21e9d2df5f651b51ea2126a3cac25811808dcfb
* Snapshot 9fd57cbacd95e89602f430244c35bbc67f08b6d2The Android Open Source Project2012-12-121-9/+2
| | | | Change-Id: Ibc3a4bf4161d286c7cfab89a19c676eb5cc9224f
* Snapshot cdeccf6fdd8c2d494ea2867cb37a025bf8879bafThe Android Open Source Project2012-12-1211-0/+7798
Change-Id: Ia2de32ccb97a9641462c72363b0a8c4288f4f36d
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-18 02:30:26 +0000