Add explicit reasons for when a job is stopped because the real-time
clock was updated and for when a job called jobFinished() on its own
(...why did we not have this to begin with???).
Bug: 141645789
Test: atest frameworks/base/services/tests/servicestests/src/com/android/server/job
Test: atest frameworks/base/services/tests/mockingservicestests/src/com/android/server/job
Test: atest ContentResolverTest (all)
Test: atest CtsJobSchedulerTestCases
Test: atest CtsSyncManagerTest
Test: atest SyncManagerTest
Test: atest SyncOperationTest
Test: atest SyncRequestTest
Change-Id: I61392c55355d2526a32ea9597a0010b04f3875ac
There are some uses for the "legacy" stop reasons that the public API
stop reasons can't cover well. Since we'll be keeping the "legacy"
reasons around, renaming them to "internal" to help explain the
differentiation.
Bug: 141645789
Test: atest frameworks/base/services/tests/servicestests/src/com/android/server/job
Test: atest frameworks/base/services/tests/mockingservicestests/src/com/android/server/job
Test: atest ContentResolverTest (all)
Test: atest CtsJobSchedulerTestCases
Test: atest CtsSyncManagerTest
Test: atest SyncManagerTest
Test: atest SyncOperationTest
Test: atest SyncRequestTest
Change-Id: I97e40d35b79dbd012216bc22e90d649639614854
AndroidKeyStoreCipherSpiBase.engineDoFinal may get called with a null
input argument. In the case where we forward the operation to the
default provider doFinal() needs to be called instead of
doFinal(byte[], int, int).
Bug: 183913233
Test: atest android.keystore.cts.CipherTest#testEncryptsAndDecryptsUsingCipherStreams
Change-Id: Ia3afaf281be7c8e5493ac8e4155a7aa02d1d37f0
This moves tests that cover SDK methods to CTS. Some methods on
TimeZoneConfiguration are not SDK APIs, so those tests remain in
coretests.
Bug: 184947690
Bug: 183239145
Test: atest CtsTimeTestCases
Change-Id: Ic0840cddb907171294f439f19fa09021b3c8807f
Address API review feedback, add getters to UnderlyingNetworkInfo
instead of exposing fields.
Instead of wasting memory by converting this into an array, have
migrateTun take a List<String>. In turn, tunAdjustmentInit should
also take a List<String>.
(cherry picked from ag/14211075)
Bug: 183972554
Test: atest android.net.UnderlyingNetworkInfoTest
Merged-In: Id59744097208d91298a25ef110ade91a9cf291a1
Change-Id: Id59744097208d91298a25ef110ade91a9cf291a1
Changing the per-app default request flows to fallback to a request of
type TRACK_DEFAULT as opposed to type REQUEST. The main benefit of this
change is that these requests will no longer be sent to the factories
which is desired.
Bug: 180452284
Bug: 176494815
Test: atest FrameworksNetTests
atest FrameworksNetIntegrationTests
atest CtsNetTestCasesLatestSdk
Change-Id: I312e55a54f70aa82953a32ab9369d5afc02b75e5
Playing status of audio source is checked using the native handler
not 0.
However, if AudioSystem#startAudioSource fails, the native handler
returned is not 0, but an error code.
In fact AudioPolicyManager sets the PORT to NONE (0) and sets an error
status.
JNI layer transforms the failure status into a native handler returned
to the caller.
Signed-off-by: Francois Gaffie <francois.gaffie@renault.com>
Change-Id: Iaa920c073885c2556a93a1b5ae23467fa6ffad4f
Merged-In: Iaa920c073885c2556a93a1b5ae23467fa6ffad4f
In case of failure, port handle reported is not initialized
by JNI layer. Any failing call to native AudioSystem::startAudioSource
will not set the port handle, but returning an error status.
JNI checks for port handle validity rather than error status.
This CL ensures JNI checks first status to report an error, otherwise
asserts on handle validity.
Signed-off-by: Francois Gaffie <francois.gaffie@renault.com>
Change-Id: I4eb8046a1263aeb7d464d35a360a8adb77c4b1a5
Merged-In: I4eb8046a1263aeb7d464d35a360a8adb77c4b1a5
Revert "API changes as requested by API council."
Revert submission 1662226-compatibility-rename
Reason for revert: Broke aosp-stage-master.
Reverted Changes:
Ie465c49ff:API changes as requested by API council.
I3c5a5734b:API changes as requested by API council.
I16bf86a9c:API changes as requested by API council.
Change-Id: I3af51d240cec9dac013d81dc448b44ef2ca60f9c
Original design uses the pattern digits + . + digits
to recognize a number. However, some locales (e.g., Dutch)
uses comma (,) as floating point.
This change uses the pattern digits + . or , + digits
to recognize a number.
Bug: 185666660
Test: atest UsageProgressBarPreferenceTest
Change-Id: Ie72b3e8a5ddc4eb3621bdd72976836b9285e96d0
The permission is necessary for ConnectivityService to obtain its
resource package. As the integration tests run ConnectivityService
in-process, they need the permission.
Bug: 186091860
Test: atest FrameworksNetIntegrationTests
Change-Id: I60cf9b54faddf0ea4cb02146c83c9bba58370749
As the framework bug is fixed, re-enable the transition by correcting
the conditions.
Bug: 177480673
Test: rebuild and test on the NotificaitonHistory page
Change-Id: Icb62dad12ba5889f750d0ea2765ae76186fc79e7
The window type Floating Accessibility Button is
TYPE_NAVIGATION_BAR_PANEL which is unmagnifed, it leads to
the cut out while drawing the magnification bounds.
To fix it we did a compromise. We omit the window bounds of
TYPE_NAVIGATION_BAR_PANEL windows while computing the
magnification bounds. The cons is that magnification region
is really changed. That means the interaction with such
windows might have latency depending on if they are
inside the magnification bounds. However, it is acceptable because
users don't have complex interaction witch such windows and
see them rarely.
bug: 185401123
Test: manually test
Change-Id: Ia0088a0140fb8d5516e703ebfa5e203f857636d9
The new configuration did not reported to the NexusLauncher activity
when the device rotated to landscape. It seems that the configuration
object of the ActivityClientRecord was unexpectedly updated somewhere,
so the configuration handling was skipped and not reporting to the
activity.
Copy the configuration from mPendingMergedConfiguration vs. directly
assigning the given configuration object reference.
Bug: 185820525
Test: atest NexusLauncherTests:TaplTestsQuickstep
Change-Id: I6768fe86e5c977c32a975562ec058c82d4f9c2fc
Address API council feedback, add getters to NetworkStateSnapshot
instead of exposing the bare fields directly.
(cherry picked from ag/14233655)
Bug: 183972826
Test: FrameworksNetTests
Merged-In: Id1707753b42ae88d2b95e4bd00a792609434e4f5
Change-Id: Id1707753b42ae88d2b95e4bd00a792609434e4f5
