Instead of waiting 30 minutes to update the standby bucket for FGS, we
will now only wait for 1 minute due to the new restrictions.
Additionally, the continuity check for interaction is now reduced to
ten minutes from two hours. This is to ensure there are no irregular
bucket de-elevations from ACTIVE.
This change is gated by targetSdkVersion check and is only enabled if
apps target S or above.
Bug: 183972877
Test: atest OomAdjusterTests
Change-Id: Icb2638ba5a20ebb79d55b0575bf351eadc11f8f6
Put a bound on the recursion in Session#toString
to ensure we do not accidently cause a Stack overflow
Bug: 186694546
AOSP: aosp/1691210
Test: atest TeleServiceTests
Change-Id: I52f44dd02d0d860d0894e9b84fded8cf5ff5a18e
Put a bound on the recursion in Session#toString
to ensure we do not accidently cause a Stack overflow
Bug: 186694546
Test: atest TeleServiceTests
Merged-In: I52f44dd02d0d860d0894e9b84fded8cf5ff5a18e
Change-Id: I52f44dd02d0d860d0894e9b84fded8cf5ff5a18e
Only uninstall on UNRECOVERABLE on USB.
BUG: 186468840
Test: atest android.cts.statsdatom.incremental.AppErrorAtomTests
Change-Id: I4bdb9b05658fe60795d5eac4ba9e111e39dffa2c
mEvents to null to remove possible NPE.
* clearEvents() needs to be called by destroy() which could cause race
condition on whether mEvents is null for other func calls.
Fixes: 185162720
Test: atest CtsContentCaptureServiceTestCases
Change-Id: I7330e651bc890c8a86822158efcf17a61e927112
The first one is it erroneously accepts tasks with null realActivity. It
shouldn't save launch params for such tasks.
The second one is when it receives a package removed notification from
PackageManagerService, it touches mLaunchParamsMap without holding WM
global lock.
Bug: 186696426
Test: atest LaunchParamsPersister
Change-Id: Ib0159835f177b7a3e9208bf77b3b608920262588
The resource id/handle mapping is no longer needed in the TunerClient
once the TunerService migration is done.
The mapping should only be maintained in the TunerService
Test: make
Bug: 186785141
Change-Id: Idfb02fe5935d9b25aac749c0f77eda111e0959ea
note the RECORD_AUDIO_HOTWORD op, rather than the RECORD_AUDIO. In
addition, check the RECORD_AUDIO permission for preflight, not data
delivery
Bug: 186164881
Test: Manual
Change-Id: I3275647d0f9a6e3ce8b97a556f56723b49170c8e
Bug: 186430321
ScrollView and HorizontalScrollView was not allowing a fling
effect while overscrolling. This adds the ability to fling
while overscrolling.
Test: new test
Test: manual ApiDemos
Change-Id: Iebd402ff0f5b6f16518ecc5403e085cb58de5976
media filter
Previously we get the share memory handle on filter opening, which only
has the information on filter types.
Now we move the share memory handle to the filter config API call so
that only the non-passthrough filter will get the share memory handle.
Test: sample tis on cuttlefish
Bug: 185627837
Change-Id: I33fd4950ec12291f6ca31a36b081d66643d5c319
This fixes issue where calls are not included inside privacy items in AAOS.
Bug: 186518774
Test: Manual
Change-Id: Ie7b057c5af21b5fb1c51f6f9a4067c85b9ea373b
Test: manual - look at user education screens for the bubble stack and
manage button in light & dark theme and make sure the
text is as expected
Bug: 183238079
Change-Id: Ia83b2e849f46c3e3eb055ff263a0171f4ad62288
When users revoke a runtime permission, they expect all interactions
to be blocked, including those protected by the BLUETOOTH_PRIVILEGED
permission.
This change finishes applying that policy to any remaining Bluetooth
APIs which didn't already implement it. To keep the implementation
straightforward, this change does "data delivery" checks when
registering for callbacks; the ideal behavior would be to wait
until data is actually delivered through the callbacks, but
RemoteCallbackList doesn't have support for AttributionSource yet.
Bug: 186405452
Test: atest BluetoothInstrumentationTests
Change-Id: Idd7be143eb8baff020a0718065293baae708041b
Inject SystemClock so that we can mock it in tests and ensure the clock
will always advance. Also switched to using elapsedRealtime, which is
guaranteed to be monotonic
Fixes: 182813365
Test: atest MediaDataManagerTest
Change-Id: I133fb48e8242dc7f8e75bfa5c585c8b6142963aa
Three bugs were present here:
1) isLocationEnabled() will return incorrect results for USER_CURRENT
and USER_CURRENT_OR_SELF
2) Disabling the location enabled cache does not work properly in the
system process, we only disable the cache for a single instance of
LocationManager.
3) isLocationEnabled() was not respecting the user as defined by the
context used to create the LocationManager.
Bug: 185401689
Test: atest CtsLocationFineTestCases
Change-Id: I84bff02604a4b2d84494a0e099e172c4ffb400a2
