- 29 Jun, 2016 1 commit
-
-
Andre Eisenbach authored
To add another datapoint and potentially narrow down *why* we had to flush the buffers, add RSSI logging to keep track of signal strength during audio drop-out events. Change-Id: Ie52f56290951130165a9f375a898a9bacf459d55
-
- 27 Jun, 2016 2 commits
-
-
Andre Eisenbach authored
am: d1387007 Change-Id: Iff3e3643f4cc36c093e5a7d0d47af8e3aa79fe9c
-
Andre Eisenbach authored
Bug: 29157087 Change-Id: If227963b939a9b0ed55e6d900364c71932d3cfe8
-
- 24 Jun, 2016 5 commits
-
-
Andre Eisenbach authored
am: d881c4b4 Change-Id: Ie00432fcec7e869c212a04374d6fcd58094eb643
-
Andre Eisenbach authored
Currently, our TX queue does not allow for quick recovery of minor congestion. As we only clear as much room in the queue as is needed to fix the news frames needed for a given timer tick, any minor congestion on the TX path can result in single frames to be dropped over an excessively long amount of time. From the "just rip the band-aid off" school of thought, drop the whole queue instead to cause a single drop-out on congestion and catch up to the live stream immediately, hoping that the stream recovers... Bug: 29601962 Change-Id: I482c3cfef6d8b51143e54733eb2da5f70663636f
-
Andre Eisenbach authored
am: 6b142ed4 Change-Id: I7dd99e2af5ec4b09a9cba9830df9cf0c677ca46b
-
Andre Eisenbach authored
am: ffdb33b5 Change-Id: I1df2268b7ddd28220f69d4eeeaee30097a976e7c
-
Andre Eisenbach authored
-
- 23 Jun, 2016 2 commits
-
-
Andre Eisenbach authored
Bug: 29601962 Change-Id: I30ce09f1c7550a1be9fd1c8ed70745f9aa0cdb44
-
Andre Eisenbach authored
Bug: 29601962 Change-Id: I4a86b786609b0203a72b750a1c4a38c82fcc5f97
-
- 22 Jun, 2016 4 commits
-
-
Sharvil Nanavati authored
am: edb7ce12 Change-Id: Ie7ea41474e11479b54ba526294977dfaa60c8cd7
-
Sharvil Nanavati authored
am: 8e80a260 Change-Id: I54a690024ccd316058d9d59ff7b16206f7fcd543
-
Sharvil Nanavati authored
am: f15ca6d2 -s ours Change-Id: Ic1a23e2c6d0284b9fdf346a681f59cdcbaa599e0
- 21 Jun, 2016 2 commits
-
-
Sharvil Nanavati authored
Change-Id: I7278875d21c59316217cb1b99d902f4fc248ca06
-
Sharvil Nanavati authored
Bug: 28885210 Change-Id: I63866d894bfca47464d6e42e3fb0357c4f94d360
-
- 20 Jun, 2016 2 commits
-
-
Matadeen Mishra authored
am: 92e0f19f Change-Id: I3df89a1a7933976c30ab3cdf4851149bc128d839
-
Matadeen Mishra authored
- Handled Buffer over flow for uint16_t - Discard invalid HCI packets from Codenomican test tool as data length and actual data not matching during reassembly Use case: Execute L2CAP test suit from Defensics Codenomican Steps: 1. Pair and connect DUT to Codenomican tool 2. Execute L2CAP test suit from Defensics Codenomican Failure: Crash observed on DUT and Codenomican tool stuck in execution. Root cause: Codenomican tool sending invalid HCI packets to DUT and there are no checks to handle buffer over flow and other invalid data from Codenomican tool. Bug: 29498064 Change-Id: I6f93c80244fc39d607ad285185136bbbca83d7ae
-
- 17 Jun, 2016 2 commits
-
-
Pavlin Radoslavov authored
am: ba64c39c Change-Id: I4c010baf150c5daf88de73efdc3041a30cf90ddd
-
Pavlin Radoslavov authored
Each pointer that was freed by one of the following functions should be reset to NULL: - config_free() - data_dispatcher_free() - fixed_queue_free() - list_free() Bug: 29421693 Change-Id: Ie55a04ed986393994564edcf872d7413b0767a85 (cherry picked from commit 8cbc2910)
-
- 15 Jun, 2016 4 commits
-
-
Andy Hung authored
By polling, we ensure the socket buffer is nearly always full, as blocking socket writes may not wake in time to avoid underflow. Bug: 28286313 Change-Id: I056768dbd860993c41d44c33a4846d62c50db933
-
Jakub Pawlowski authored
am: bfbda174 Change-Id: I1565542c0f9fd29b97d7235a799e3df27e8c8c41
-
TreeHugger Robot authored
- 14 Jun, 2016 8 commits
-
-
Jakub Pawlowski authored
am: 8577ffca Change-Id: I71cf1e5e38eed1a0136105d5cd4e1db2fff2ec54
-
TreeHugger Robot authored
-
Jakub Pawlowski authored
am: a1d67727 Change-Id: I26659d38b1241962bd286c0c806687b6f95a7637
-
Jakub Pawlowski authored
am: 552e6304 Change-Id: I7539fc75908cf70833f4380b5b7a805094b2a341
-
Jakub Pawlowski authored
-
Jakub Pawlowski authored
Some HID devices will accept both write request and write command. Prefer write commands when possible. This is due to bug in some hardware, that will not send write response when too many commands are queued. Bug: 29184976 Change-Id: I5bafc067f044a48f152c60b8e17722067bc1453e
-
Jakub Pawlowski authored
Id field is equal to attribute handle, so it must be 16bits. Otherwise only piece of GATT database can be used. Bug: 29253825 Change-Id: Ia88e3ad3eb96ca8e97349aa5e852e66c57072b49
-
Jakub Pawlowski authored
GATT Service is contained between start and end handle. If characteristic definition is at end handle, and it's value definition is after end handle, it will not be properly discovered. That's because we use value_handle instead of attribute_handle to identify characteristics. As a workaround, increase service boundary if value is defined after it's definition. Bug: 29253825 Change-Id: Ib145aea4f5cf38a1fbb977c301136e16f8f900f7
-
- 13 Jun, 2016 1 commit
-
-
Jakub Pawlowski authored
If there are any HID operations scheduled after disconnect, mark the device as no longer executing after establishing connection. Otherwise we'll be unable to send any HID commands to it. Change-Id: Ie1bb622388a3bcb574dec3dde76ef4518ee1102f
-
- 11 Jun, 2016 1 commit
-
-
Jakub Pawlowski authored
am: 22fc3825 Change-Id: I6f6707eb9c69b34b12243f72f2b893c68ba31a72
-
- 10 Jun, 2016 1 commit
-
-
Jakub Pawlowski authored
If there are any GATT operations interrupted by a disconnect, mark the device as no longer executing. Otherwise we'll stil receive data from the device, but we'll be unable to send any HID commands to it. Bug: 29184976 Change-Id: I489f41c970abad0ff1145005d3250beafa83d27e
-
- 09 Jun, 2016 3 commits
-
-
AnubhavGupta authored
am: 470466e6 Change-Id: Ibc2f939f4e07dcccac95c88b8ac163d9a22586ff
-
AnubhavGupta authored
Also fixed AVRC_PDU_GET_PLAY_STATUS timeout response. Bug: 28177785 Change-Id: Icde64a5c1806453850abe101f9707fff61566566 (cherry picked from commit 1c512b85)
-
Srinu Jella authored
am: 70035577 Change-Id: Ibd241e1dc6608a96576d9d4db4dcdd16f7c0d383
-
- 08 Jun, 2016 2 commits
-
-
Srinu Jella authored
Use Case: Disable time out when atleast one active ACL connections Steps: 1. Turn ON Bluetooth 2. Connect to any Headset 3. Turn OFF bluetooth. Failure: Turn OFF bluetooth is failed when atleast one active ACL connections Root Cause:i If we have one or more active ACL links, so it is not notitying BTA_DM_DISABLE_EVT to upper layer. Fix: Set disable timer in case of any active ACL connection Bug: 29217385 Change-Id: Ica47717119f1ab9fa9f4f5244e8483c408276a2a (cherry picked from commit 3e4f01ad)
-
Myles Watson authored
am: 59bc2de9 Change-Id: I9234f8a567883fdbccb20326328f9cdb444de479
-