Age | Commit message (Collapse) | Author |
|
Extend the timeout delay in out_write() when waiting for
available space in output buffer to accomodate A2DP sink with a long
startup time.
Issue 5781477.
Change-Id: I4e31b5116ddbea8774a15b2016d088ea7039ec93
|
|
|
|
* commit '5611c7de4927835d73f132e65dd3b72f28affb8b':
Add missing LOCAL_MODULE_TAGS
|
|
* commit '176eb17c88caf1bb3f2641dfd0bd6cf68eaf53d3':
|
|
into ics-mr1
* commit '52c8f9ae61aa01d7c3ebac19d8cbd9e61578bc73':
Fix channel connected signal emission.
|
|
* commit '1e5617c1aa3b6e2d8dd7721851ec2b1304e2b2cc':
Add missing LOCAL_MODULE_TAGS
|
|
* commit '6ad49c1894f6b50078f69efee2dad8acccb6e164':
Add missing LOCAL_MODULE_TAGS
|
|
|
|
Change-Id: I30d0a8dd58ee6ca4cd3d74a4370933deb8198abf
|
|
|
|
* commit 'a345fd4f5204db63b590c5e993052952379426a8':
Fix channel connected signal emission.
|
|
* commit 'a345fd4f5204db63b590c5e993052952379426a8':
Fix channel connected signal emission.
|
|
|
|
* commit '3904034df7159db16017b6a40f46a878a73fc097':
|
|
Channel Connected signal was being emitted too early
leading to failure in acquisition of the fd. Delay channel
connection signal it is ready to be used by users.
Patch in consulation with Jose Antonio Santos Cadenas <santoscadenas@gmail.com>
Bug: 5732670
Change-Id: I7855bd9d372ec9d548240c9086a66e9a340ce1ce
|
|
Change-Id: Ie82bdb1fa8cfb9deccdb979ee84ff59fc7a6c2cd
|
|
Change-Id: I55bd573a2b8dabff0c06bb67ffd3472db900d429
|
|
|
|
|
|
Change-Id: I0657769de025844efb7a36e5ab868a9505c5faf7
|
|
* commit '355afe9a49d429650c955894220caebc1db3b1cf':
a2dp HAL: add write thread to avoid audio skips
|
|
The a2dp stack is throttling the audio throughtput
to accommodate headsets that can accept audio too fast.
This makes that very limited audio buffering exists in the
A2DP output path. We are therefore vulnerable to irregular scheduling of
audioflinger mixer thread when CPU clock speed or system activity changes.
The fix consists in adding an intermediate audio buffer between audioflinger
mixer thread and the A2DP socket.
Issue 5682206.
Change-Id: I6f2387fb694a75e62c0805b7f134f7cb88eaedd6
|
|
Change-Id: Ic5c91490dcdfb5b09650505413d9d2782c909d36
|
|
|
|
|
|
|
|
|
|
* commit '999d00b91f78f2fe1aa0648aab49bc857bdec8f6':
Rename LOGV(_IF) to ALOGV(_IF) DO NOT MERGE
|
|
See https://android-git.corp.google.com/g/#/c/143865
Bug: 5449033
Change-Id: I68754993ff27a3048758905b8928f9791e9a7fbc
|
|
|
|
|
|
|
|
memset the addr variable.
Change-Id: I3a3567145985ba425ebf8e4b21d426dcb490dbf5
|
|
|
|
The AVDTP spec allows for a race condition between remote and local
device when issuing an AVDTP_START cmd on a stream in the OPEN state.
However, the internal state must continue to be consistent. For example,
suppose that avdtp_start() has been called while in the OPEN state and
a AVDTP_START cmd is sent. Now before we have received a response (and
thus entered the STREAMING state), we *receive* a START cmd. Prior to
this fix, since the sep is still in the OPEN state, we would accept
the new START cmd. This will leads us to send both a Start_Ind and
Start_Cfm - not good.
Now, we track this transitional state (starting == TRUE).
NB - 'starting' is only in a valid state while the sep is in the
OPEN state. 'starting' is reset when we return to the OPEN state.
|
|
When we disconnect an A2DP device by immediate power off and quickly
also initiate a disconnection from our side, a crash is occurring. This
is happening because of the disconnect_timeout coming after freeing the
session.
|
|
Before we power down HCI dev, we should disable Bluetooth chip scan mode so that
the chip set would not repond to device outside inquiry and page.
bug 5080232
Change-Id: I357a300ad61332c6f95376c0690602cf396e5973
|
|
Before we power down HCI dev, we should disable Bluetooth chip scan mode so that
the chip set would not repond to device outside inquiry and page.
bug 5080232
Change-Id: I357a300ad61332c6f95376c0690602cf396e5973
|
|
This reverts commit 6b08f121c817cda19431fa472c9640733df05d6f
|
|
|
|
This reverts commit 6b08f121c817cda19431fa472c9640733df05d6f
|
|
|
|
Before we power down HCI dev, we should disable Bluetooth chip scan mode so that
it saves power.
bug 5080232
Change-Id: I28a761ebcb14c0a4215c53ed82e4ff9430a32250
|
|
If cancel is pressed on the pin request dialog (for non SSP case),
auth request continues in a loop. Add additional checks for
the auth agent.
This is a gross temporary hack till we move to the mgmt interface.
Change-Id: I565a75698cb4fa1c2ed8c93ed6198b05a1a7b8af
|
|
|
|
Fix Paired device property if 'No Bonding' authentication is used. It is
set to be false when device is disconnected and no link key is stored.
Otherwise, there can be cases when device is still valid and being
claimed as paired without available bonding information.
For instanse, use of CreateDevice method call and obex client file
transfer is such use case.
|
|
SDP_ATTR_EXTERNAL_NETWORK is not part of the HS specification.
Original Author: Jh Kim
Change-Id: Ic649e7532acabfbbb9adeaa1db3e7c8e51d3fd19
|
|
When Bonding was failing due to authentication
failure, this error report was not being sent to the caller,
because cancel_bonding was being called from btd_event_conn_failed,
which was sending the wrong error code back.
Change-Id: I2816d714fc85c499d0d4850733e33807f3073217
|
|
utility for CSR bluetooth modules"
* commit 'cfd4fe3f0bf605978fc72efada90060efbeb16c3':
Add make file to build bccmd utility for CSR bluetooth modules
|
|
modules"
* commit 'f3d1a2c3f2005451f40cfa48782ee5aebebe784e':
Add make file to build bccmd utility for CSR bluetooth modules
|