| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Interop database entries are stored in the system settings entry
"BluetoothInteropDatabase". The format is a list of entries separated by
";". An entry consists of a BDA fragment, followed by a comma and an
integer representing a feature from interop.h.
Example:
To disable LE secure connections for devices starting with BDA 11:22:33,
use "11:22:33,0".
Bug: 26548845
Change-Id: I5903930178b70d1eb52d64b1c6051ce8ee346da4
|
|
|
|
|
| |
Bug: 26437927
Change-Id: I673de7f7c68b9a02b234bb99c6f89c7fc36f90c9
|
|
|
|
|
|
|
|
|
|
| |
Receive and handle ACTION_MESSAGE_SENT intent for SMS type
message to move it to SENT folder when pushMessage request
from MCE is processed and SMS delivered successfully.
Bug: 22343270
CRs-Fixed: 903561
Change-Id: I9dafffc737a34233ede2d10e22cd969f520a12cf
|
|
|
|
|
|
|
|
| |
Timestamps were being incorrectly filtered out of Vcards when sending
call-logs.
Bug: 25084927
Change-Id: Ied8912e7d2fdbcc6e6980c3773c4ec5a449842ec
|
|
|
|
|
|
|
|
|
| |
Used a file provider to serve up URIs to allow
applications to access files in the external
Bluetooth directory.
Bug: 23367919
Change-Id: Iadcdcafb235f3eeb50a0e147f3ef982fc9ee38b3
|
|
|
|
|
|
|
|
| |
Foreground scans were still broken even for L-or-earlier apps when the
location was disabled.
Bug: 24203266
Change-Id: Iaad8d7828a4b383b6cc0a033e94c7d2cd8c9328b
|
|
|
|
|
|
|
|
|
| |
The CALL_ONGOING_STATE was set twice, causing the connect
response not to be sent to the peer device when there was an
ongoing call on DUT. This was violating the SAP Spec.
Bug: 24520367
Change-Id: I290d924870381a82a4abd8b6c42a6d0ebf55652f
|
|
|
|
|
|
|
|
|
|
| |
Adjusted the PARAMETER_MASK_DEFAULT constant for when a
message listing request is recieved and a message filter isnt
provided. This new filter value causes the sender_address field
to be sent along with all the other default information.
Bug: 22163529
Change-Id: I49444cfb341d2e6cc72bdab55aa441d712b03f14
|
|
|
|
|
|
|
|
|
|
| |
Move a SMS message to the correct folder upon receiving an intent
detailing if the message was succesfully sent or not. If sent
successfully, move to the SENT folder, otherwise move it to
the FAILED folder.
Bug: 22992865
Change-Id: Ifdcfb7bb613844f507ef27460ead520c6573b89d
|
|
|
|
|
|
|
| |
Bug: 23471393
Change-Id: I46264238e4810a7f280e656220bc68e76eb0cb37
Signed-off-by: koh.changseok <koh.changseok@lge.com>
Signed-off-by: Sungmin Choi <sungmin.choi@lge.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The internal TEST flag was removing too much code.
To make it easier to run test, and avoid future issues
with removing needed code, the TEST flag is no longer used
to remove code.
This bug was noticed when running the PTS testcases without the
PTS_TEST flag set. It is assumed that this fix will make
TC_SERVER_DCN_BV_02_I work without the PTS flag, but unless PTS
have updated their test case to accept both a gracefull disconnect
and a forced disconnect, TC_SERVER_DCN_BV_03_I will still fail in
a production build. The SAP spec suggest to use a gracefull disconnect
when initiating a disconnect from a server, hence it is not a good
idea to expose a force disconnect option to the used without first
having tried a gracefull disconnect. Hence the PTS test case
implementation is in conflict with the intented use specified in
the SAP specification.
Without this fix a build with PTS_TEST=false will not work as
intented.
PTS_TEST replaced with system property bt.sap.pts. Set it to true
to enable the force disconnect button.
Bug: 23614694
Signed-off-by: Casper Bonde <c.bonde@samsung.com>
Change-Id: I776a53d6e786c21000ef62094f9a9948ee5880b8
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As per SAP spec, padding bytes can be 0-3 bytes, but the current code
has incorrect logic, that would lead to calculation of padding bytes
as 4 in case the APDU length was multiple of 4, which would lead to
incorrect parsing logic in SAP Server and can lead to issues of no
response for APDU request from SAP Server as it keeps waiting for
reading more bytes from rfcomm which are not present.
Also check added in code not to send msg to RIL if socket is null to
prevent crash in BT Sap module.
Bug: 23024598
Signed-off-by: Casper Bonde <c.bonde@samsung.com>
Change-Id: I24e4a6b850709c9c32b7e0992626a0219dacef03
|
|\
| |
| |
| |
| | |
* commit 'bf37a0295d110b77b635ca2986172bbdd59331bb':
Fix column ID for PBAP name lookup
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When a phonebook lookup is performed to resolve a phone number into a
name, the wrong column ID is used to retrieve the value from the cursor,
causing an un-caught exception and a failed lookup.
Bug: 22953958
Change-Id: I1f826412916012382903fdf30d43d5cb3516432c
|
|\|
| |
| |
| |
| | |
* commit '9135d866b12ff019a4eae37e7a8c0df56a4383f2':
HFP/A2DP: Remove pending auto-connect messages when connected
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes a bug in which being paired with multiple headsets causes
previously connected headsets to disconnect. This fix removes
pending connect attemps once one device is successfully connected.
Bug: 23111466
Change-Id: Id471189d92643b9626e63197c00e76defd0a72bf
|
|\|
| |
| |
| |
| |
| |
| | |
results.
* commit '72ecb4caa630b63f66505ccb202a807b1af4e294':
Make location enabled check configurable when returning scan results.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Some device classes (e.g. Wear) don't allow location to be enabled but
would still like to allow LE scanning to take place. This patch allows
the location enabled check to be bypassed if the platform is so configured.
Even if the location check is disabled, the calling app must still have
one of the location permissions.
Bug: 21852542
Change-Id: I206366ce262776d4668c0c42e066f0e20f5fdfeb
|
|\ \
| |/
|/|
| | |
mnc-dr-dev
|
| |
| |
| |
| |
| | |
Bug: 22943799
Change-Id: I48d411f4e3a79a891360a9a855c4680bea19d748
|
| |
| |
| |
| |
| |
| |
| | |
Apps holding PEERS_MAC_ADDRESS permission can still access scan results.
Bug: 21852542
Change-Id: I75fc289e8965df64efb7ff84fe5a4204904724ab
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit 86449ac4bc7a8f4b2afeab4da420ae4f980c850a.
The revert is needed to address an issue that crashes Bluetooth.
Bug: 22836458
Change-Id: I8c8b51544637dd1c2250eb91e86cb2ca1bbc9fe7
|
|/
|
|
|
|
|
| |
Implemented the factory reset function to be used to reset all bluetooth
settings on device to factory default
Bug: 16161518
|
|\ |
|
| |
| |
| |
| | |
Change-Id: I1e5989dbc73f89bd292465142560952bc8e44f59
|
|/
|
|
|
|
|
|
| |
Pre-M apps running in the foreground now get scan results. For legacy apps
running in the background, no results are returned and the error is logged.
Bug: 21852542
Change-Id: Ic7a91f34c6718c26f0dae30dade6a436fe1061af
|
|
|
|
|
|
|
|
|
| |
This CL adds permission and PID checks to avoid unauthorized deletion of any
MMS/SMS messages in BluetoothMapContentObserver.actionMessageSentDisconnected
function.
Bug: 22343270
Change-Id: I30254036309733be4d54db17a8ef17a571cd1c5a
|
|
|
|
|
|
|
|
|
|
|
| |
Fix to satisfy AVRCP 1.4 spec.
In EVENT_TRACK_CHANGED response request,
if a track is selected , then return 0x0 in the response.
if no track currently selected,then return 0xFFFFFFFFFFFFFFFF in the INTERIN response.
Bug: 22519285
Change-Id: Iaaae1d4acf918049d99c27d9ad98bde15242ade1
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Enforce location permission for apps targeting M, for legacy apps, log an
error.
Bug: 21852542
Change-Id: Ic406df1727eb0939531a22b76c2df9b13f03ec81
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The change consists of fixes required for the filter to work properly.
Without this change the API isFilteredOut() was basically removing those
attributes which are set in the filter while the expected behaviour is other
way round, so renamed the API to isFilteredIn().
This patch also adds provision for filtering call log date and time when
it is not been asked as per the filter since it is not a mandatory attribute
as per the PBAP specification.
This patch also renames "NOTES" to "NOTE" which was incorrect property for
vcards.
Bug: 20077258
Change-Id: Ifbe57706b86031cbb9656556843da1bab700ef5d
|
|\ |
|
| |
| |
| |
| |
| | |
Bug: 22075764
Change-Id: Id2f1c0d1660abd0c18de46c64596fc1a17b974ce
|
|/
|
|
|
|
|
|
| |
Receivers of ACTION_FOUND intent are now required to have
ACCESS_COARSE_LOCATION permission.
Bug: 21852542
Change-Id: Ia3bca7e9cd117536a3eb4f4d1fe405604b2ff40f
|
|
|
|
|
|
|
|
|
|
|
| |
When a PCE pull the missed-calls-phonebook (mch.vcf) from the PSE, a parameter
stating the number of _new_ missed calls must be included in the reply.
Currently the parameter is included but it is always set to zero, which is
incorrect.
This fix corrects the variable used for new missed calls
Bug: 13022843
Change-Id: I6094c50a76711cfff9347596d70ac2300cfbb543
|
|\
| |
| |
| | |
mnc-dev
|
| |
| |
| |
| |
| |
| |
| |
| | |
In onScanResult, skip a device if calling process has no location
permission/appop
Bug: 21852542
Change-Id: I4e3511b33d69d94c1df6e1bf2f9a351303a90685
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
Bug: 22215773
Change-Id: I21d06ec7839fdb4e1ba9b5a70c6ac7791788eb4f
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously, if there was "disable timeout" error during Bluetooth
shutdown, the Bluetooth state was set back to ON. However, the
internal Bluetooth stack runtime state was cleaned-up and
practically unusable.
The solution is not to re-enable Bluetooth if there is a
"disable timeout" error.
Bug: 21873347
Change-Id: I561683fa391f7bacbb1aa8f80d8f6583c7d3099c
|
|/
|
|
|
|
|
|
|
|
|
| |
Broadcast connection state of incoming device in pending
state and update UI for disconnection of outgoing connection.
This change in conjunction with bluedroid change handles
race condition scenarios when incoming and outgoing A2dp
connections collides.
Bug: 22028876
Change-Id: Ibd80fc7010613887df74fb1903b16de73c77939a
|
|
|
|
|
| |
Bug: 20341903
Change-Id: I6e9dbeb1d05bdcce56fab63ccdd701138c99f5a0
|
|
|
|
|
|
|
|
| |
When remove bond API is called from the stack layer,
the bond state change intent is not sent in the
upper layers to unbond a device.
Change-Id: I515bfaf3f1a575106b10e2f688b1e9de58770b87
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds support for erratas to make the specification version
compatible to PBAP 1.1.1 specification.
Following errata needs to be supported to make the specification version
compatible to PBAP 1.1.1
https://www.bluetooth.org/errata/errata_view.cfm?errata_id=1824
Proposed modification to the text of the spec:
5.3.3 Name
This is the name of the folder to be retrieved. The value shall not include
any path information, since the PullvCardListing function uses relative paths.
An empty name header may be sent to retrieve the vCard Listing object of the
current folder. However, it is illegal to issue a PullvCardListing request with
an emtpy name header from the telecom/ folder.
Any such request shall be responded to with a "Not Found" error message.
Bug: 21896912
Change-Id: I0fb2c7d96b6e34d0bf83bb62901a8fd47c470fe6
|
|
|
|
| |
Change-Id: Ia07d99d58785c7e974b1fb32afaeb157ad337932
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use Case:
1) Send files in batch from remote to DUT
2) Cancel the transfer in between from either side.
3) Check name of the files in failed tranfer message.
Failure:
Name shown in the failure message is different than actual file
name in batch
Fix:
Save names of all the selected files to be transferred even
before starting of client thread so that names remain intact
in the outbound information even when the batch is cancelled
from initiator.
Bug: 21896912
Change-Id: I42c98721365c4c8acb746d49ba9ceff5b0737b71
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use Case:
1. Create obex connection from remote to DUT.
2. Dont transfer any file and wait for the screentimeout.
3. Check if device goes to suspend.
Failure:
Device does not go to suspend mode if OPP connection is present.
Root Cause:
Acquire the full wakelock when user confirmation is required and
not during opp connection request.
Fix:
Obex server session will acquire the full wakelock only when user
confirmation is required. Otherwise, if session acquires the full
wakelock during connect request and did not receives the PUT
request from remote full wakelock will not be released. In this
scenario DUT will not go to suspend and cause battery drain.
Bug: 21896912
Change-Id: I17b90b206016c2a34d724393ac3b17a41983722c
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use Case:
1. Pair and connect to Dongle
2. Send a 2GB file from Dongle to DUT.
Failure:
File transfer failed in between.
Fix:
This patch fixes issue of problems in sending/receiving files
which cannot be accomodated in int type of Java. Instead of using
int, long data type is used, which can hold 64 bits data size in JAVA
which is suitable for storing file sizes in GB. Changes are done
in how updates are sent to progress bar which supports only int
by using the percentage of data transferred to update the progress.
Bug: 21896912
Change-Id: I49f9bf8a4a0e3668e32058d582a2700b0e6057e8
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use Case:
1) Pair with remote dongle and send a file over OPP.
2) Reset dongle such that there is obex response timeout.
Failure:
File transfer status is not marked a failed and hence cannot be retried
Fix:
This patch will handle the scenario of obex timeout which occurs due
to cancelling the transfer in between and trying sending again.
Bug: 21896912
Change-Id: Ide1a64e5874bda2c5cf71531f5971bc8bebf5e9f
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use Case:
1. Share a picture through Bluetooth, select partner devices.
2. The partner devices do not confirm to receive the file.
3. Check the transfer status on the DUT.
Failure:
Failure Notification pops up twice when the shared files not
received by the partner phone
Fix:
This change ensure that TRANSFER_COMPLETED_ACTION intent will not
sent to receiver if there is any exception occurred during OPP
operation because this intent is already sent to receiver from message
handler.
Bug: 22028876
Change-Id: I3ad2f24be185c37355dff43009a5236bede0106a
|