This CL use CopyOnWriteArrayList to avoid
ConcurrentModificationException.
Bug: 148176840
Test: manually
Change-Id: If6107892bbdebf2bb10f8add63e96ccbae3b4cd5
There are some design limitations in PacService (one-way aidl calls
from ConnectivityService) that causes it to be racy when PAC proxy are
set and cleared in quick succession. Attempt to mitigate them with the
following changes:
1. Make PacNative a singleton instead of one instance per binder. The
underlying v8 engine is singleton so it makes little sense to have
multiple instances of the PacNative wrapper.
2. Remove the startPacSystem and stopPacSystem API and bind the
PacNative lifecycle to the PacService. Otherwise the one-way
stopPacSystem() binder call could have raced with a next
startPacSystem() call when PAC proxy is cleared and then set.
For this change, startPacSystem() and stopPacSystem() and made no-op
only. They will be fully removed in the next change.
Test: atest --iterations 200 com.android.cts.devicepolicy.DeviceOwnerTest#testProxyPacProxyTest
Bug: 147359729
Change-Id: Ie3ce098167694421f8bd2a6dec85d7c437cfb0be
EDIT
delete the apk file while the other verification is still accessing it.
Test: locally verified that the exception does not occur anymore.
Bug:145674131
Change-Id: I16c37a9acb9e02b4c454c1ad036167a42aed2c66
This CL introduces ENABLE_SCOPED_STORAGE and REQUIRE_SCOPED_STORAGE as
AppCompat changes that are enabled for apps with targetSDK > P and apps
with targetSDK > Q respectively.
This change removes the getMinimumTargetSDK method, as it
is no longer needed.
Change-Id: I6b05252d42d3b2f1030928ffd03c02523c5a01d2
Fix: 147034231
Bug: 144914977
Bug: 131432978
Test: atest RestrictedPermissionsTest
Test: atest RestrictedStoragePermissionSharedUidTest
The CL only allows a target to be the control target if the insets
source provider has a control. This prevents the arrays in
InsetsStateController.mControlTargetTypeMap contains a type which
doesn't have a control. If an insets source provider haven't had
a window yet while we are updating control for target, we let the
target be the pending control target, and then use it to update again
while the provider get the window.
Bug: 149121559
Test: Manual test
Change-Id: I3c63e892f870f4daca667106d935e05423dfece8
This is necessary to avoid subsequent conflicts.
Test: none needed
Change-Id: I6e2cd9188e0e4bd7c71c6c56635f192dce73f325
Merged-In: I621cfbe165996c67b201ca2dd2f95a5ab9af10ee
TetheringUtil JNI is too big that it statically linking hidl and its
dependency library. To remove these static libraries, calling hidl in java
directly instead of using JNI.
Bug: 148984662
Test: -build, flash, boot
-manually ON/OFF tethering
Change-Id: Id5a9759eb453fddaf0c3b7a31da17224e35e963e
-All types of MediaDevice use the same MediaRoute2Info API
-Update test cases
Bug: 148756190
Test: make -j42 RunSettingsLibRoboTests
Change-Id: I4a01aaa03c657b24e2c747f1202d968deb4d9932
Currently, even if a JPEG file has an XMP data stored separately
from the EXIF data, it saves it as an EXIF tag, and when
ExifInterface#saveAttributes is called, the XMP data is stored
inside the EXIF data. This can cause a problem since the maximum
bytes that an EXIF data can hold inside a JPEG file is 65536 bytes,
and having the XMP data inside the EXIF data can make the EXIF data
exceed this limit.
This CL solves this issue by separately saving the EXIF data if it
existed separately in the original file.
Bug: 147778520, Bug: 149010485
Test: manually with file attached in bug
Change-Id: I320942858beb14cc3b2e80330857089a0ad26533
Before Android Q, we will start PiP animation when activity requests to
enter pinned stack. Since we will move the pinned stack control to SystemUI,
the original transition sequence would break and cause flicker.
An easy way to prevent flicker is to check if the animation needs to
start early.
Fix: 146432422
Test: Manual enter PiP with gesture/3-button navigation several times.
Test: atest PinnedStackTests
Change-Id: I646efe7fbf0c58224d55112ab1bc8749c3dc41da
PendingIntent can be built with implicit intent (i.e. intent without
ComponentName), while using it cause exception.
However, apps can still create and set media button receiver with
implicit intent. Prevent crash when MediaSessionService is notify about
such app's media button receiver.
Bug: 147536687
Test: Build and run
Change-Id: Icfdd45edaa8e25dbdeca3c2180bd234718eef202
Bug:119800099
Test: boots, correct image is being picked up, correct files are being
pinned
(cherry picked from commit 9ac03a0504)
Change-Id: I0fd94e27ec2e8ecd814576efed8363b0e6b6d438
Merged-In: I7add3006b0d72b005daabb6609d954b466985304
Bug: 138116789
Test: manual - overflow & normal bubbles look the same size now.
Previously, overflow bubbles were smaller as a result of the padding.
Change-Id: I3660d0f347468b25a1501758e1a170c8269a9434
Partners have requested that we index XMP metadata so that gallery
apps can quickly determine XMP values (such as photosphere camera
parameters) without having to perform their own expensive indexing
of the underlying files on disk.
This change also redacts any location metadata contained in the
indexed metadata, since we can't safely perform dynamic redaction of
database values.
Bug: 148571206
Test: atest --test-mapping packages/providers/MediaProvider
Change-Id: I9be27cbfca037ccc59d3cc4bd4b004bbba51a5a8
