GitLab

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

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

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

Apps holding PEERS_MAC_ADDRESS permission can still access scan results.

Bug: 21852542
Change-Id: I75fc289e8965df64efb7ff84fe5a4204904724ab

This reverts commit 86449ac4.

The revert is needed to address an issue that crashes Bluetooth.

Bug: 22836458
Change-Id: I8c8b51544637dd1c2250eb91e86cb2ca1bbc9fe7

This CL adds permission check to avoid unauthorized deletion of any MMS/SMS
messages in BluetoothMapContentObserver.actionMessageSentDisconnected
function.

Bug: 22343270
Change-Id: I30254036309733be4d54db17a8ef17a571cd1c5a

This CL adds permission check to avoid unauthorized deletion of any MMS/SMS
messages in BluetoothMapContentObserver.actionMessageSentDisconnected
function.

Bug: 22343270
Change-Id: I30254036309733be4d54db17a8ef17a571cd1c5a

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

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

Enforce location permission for apps targeting M, for legacy apps, log an
error.

Bug: 21852542
Change-Id: Ic406df1727eb0939531a22b76c2df9b13f03ec81

Receivers of ACTION_FOUND intent are now required to have
ACCESS_COARSE_LOCATION permission.

Bug: 21852542
Change-Id: Ia3bca7e9cd117536a3eb4f4d1fe405604b2ff40f

Bug: 22075764
Change-Id: Id2f1c0d1660abd0c18de46c64596fc1a17b974ce

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

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

In onScanResult, skip a device if calling process has no location
permission/appop

Bug: 21852542
Change-Id: I4e3511b33d69d94c1df6e1bf2f9a351303a90685

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

In stress testing of BT on-off usecase, crash was observed
due to triggering double clean-up. This fix introduces
additional Check for handler validity while clean-up to
avoid the crash.

Bug: 21896912
Change-Id: I14b1c35d1fa0345c59d61682d92795aa617436b5

We tell the device idle controller to go out of idle before
starting the voice command activity.

Change-Id: I41900518af61f0cb477ec56eaebfe798c69512f9

The energy value can get quite high, so use longs.

Change-Id: Ib03c07160339c82a834ea94fe155a65f0efb03d2

b/20187218

Change-Id: I2349c9ca2cd1186ceff98f3eb42b6ecba9da002e

Bug:21494402
Change-Id: I3d5d6e87bb8aef8760aa4087559abfeebabb42b1

Currently DEBUG, VERBOSE and PTS_TEST_MODE is on as a default.
There is no reason for that in production code (except for during test
where the code needs to go through PTS test)

Bug: 21692162
Change-Id: Id092a79959fa38608d06755cc43148eee9ec3e00

This change enable the posibility to enforce using a
16-digit pin or MITM for a RFCOMM or L2CAP connection.

This is needed for the SIM access profile.

Change-Id: I42ada9b36d24d43697a2010eccbc0103f15af77d
Signed-off-by: Casper Bonde <c.bonde@samsung.com>

Use case:
Connect 2 headsets one after another in quick
succession.

Failure:
SLC for first headset is not happening.

Root cause:
SLC for first headset is not handled when second
headset is connecting.

Fix:
Add handling for SLC event for HS1 in MultiHFPending state.

Change-Id: If0c2553c28e233bea4622fca10c94fddd913afa7

Added null checks identified by static analysis tool.

Change-Id: I5ff04775313b06d549c5ae97e497dd44e9231b04

Use case:
1. Connect one headset.
2. Make MO/MT call.
3. While connecting second headset, change
   call volume on the phone.

Failure:
SCO volume changed is not updated to first headset.

Root cause:
Volume change is not handled in MultHFPending state.

Fix:
Added handling volume change in MultiHFPending state.

Change-Id: I6ac3cb2968b99de194fa7c0114d45f9d81dcb663