Requirement to use stable AIDL parcelables in priv-apps.
Bug: 254476191
Test: aidl_integration_test, build target added which uses this
Change-Id: Ib2434e5566bf8bd804f76cf1e63ec1df0e904d77
There is existing PKCS#7 signature used in the kernel for verifying
fs-verity digest. The purpose of this change is to pave the way to
migrate the existing signature check to userspace (and longer term,
migrate away from PKCS#7).
To mitigate the complexity of PKCS#7, only the configuration we're
currently using is supported.
Bug: 253668864
Test: atest FrameworksCoreTests:com.android.internal.security.VerityUtilsTest
Test: Manually added some code to use the API with correct and incorrect
signatures. Saw the API behave expectedly.
Change-Id: I80bbbd88881303c0b9a261b1fe59e9682e43bcad
Merged-In: I80bbbd88881303c0b9a261b1fe59e9682e43bcad
Root hash is only part of the fs-verity digest covers. Rename to avoid
confusion.
Bug: N/A
Test: m
Change-Id: I12c2a4ac57fb8772483473f951e97474ebd894c9
Merged-In: I12c2a4ac57fb8772483473f951e97474ebd894c9
These will be used by the ANGLE Developer Options GUI to process the
deferlist
Test: logcat + various flash/wipe + system-driver scenarios
Bug: 224558229
Change-Id: I47f940612f8be0c83f0be04c2cc1af7908e37382
Merged-In: I47f940612f8be0c83f0be04c2cc1af7908e37382
Change the sense of the run-time switches so that ANGLE can be an
optional GLES driver or the default system GLES driver. When ANGLE is
the system GLES driver, also handle the case of there being no legacy
GLES driver.
Test: logcat
Test: atest CtsAngleIntegrationHostTestCases
Test: atest CtsEffectTestCases:android.effect.cts.EffectTest#test5_effectCreate
Bug: 224558229
Change-Id: Ie53f5221d51b62db226c0c634537959612a06655
Merged-In: Ie53f5221d51b62db226c0c634537959612a06655
Any AIDL interface that has @VintfStabilty should be
able to be used everywhere.
Bug: 254476191
Test: aidl_integration_test
Change-Id: I3138a6e4dbfdfb972d87e7c4eb9b591be40b6d39
Make sure not to overwrite any current user selection for
Secure.STATUS_BAR_SHOW_VIBRATE_ICON that the user may have
made.
Issue: 253992986
Test: Manual - see issue
Change-Id: I33155a27707e6d30ff56fb090c71b9670a98fc31
Reset IKE session when data stall happens in VPN network.
When a data stall is suspected, MOBIKE will be triggered to try
to recover the network. If MOBIKE does not help, more aggressive
recover step is required. Thus, resetting the ike session
if the situation is not recovered for a while. Also rate-limit
the timer to prevent the session being reset for every fixed
time.
Bug: 238692379
Test: atest FrameworksNetTests
Change-Id: If72ee8a2ecdf4ec9038b78b98055ee21b7fa47da
All the code using getCallingUid here should be
ripped out anyway because it's Java-centric. Here
are some of the issues with the current stuff around
here:
- it's broken because it won't handle things happening in
native code
- it's slow (e.g. big transactions are already logged in
native code anyway)
Bug: 254835230
Test: boots, atest MicrodroidTestApp (with new tests)
Change-Id: I7315059bff138966e9509f1d529a6417466d2b7f
Platform API, in order to fix bugs like b/254835230 where
certain utilities call getCallingUid, which doesn't make
sense for RPC calls.
Bug: 254835230
Test: android.os.ParcelTest
Change-Id: If2dd13d8edd515c945ccde2a2554f6f2b7b87b26
Make sure the access is in the synchronized block.
Bug: 254320691
Test: Manual test
Signed-off-by: miaojian <miaojian1993@gmail.com>
Change-Id: Ia244b5ba2d3ba891319b32513841f397177cde0f
When volume level is restored after mode change from incoming call back
to normal mode (media playback) invalid contextual stream was used to
calculate volume level. Should use getBluetoothContextualVolumeStream()
instead.
Additonally, the workaround for some cases where we don't get the proper
LE Audio device was moved into the 'setLeAudioVolumeOnModeUpdate()'.
Bug: 241501978
Tag: #feature
Test: verified manually, missed and placed call scenario, check restored volume value
Change-Id: Ibc1b92c8ea053ccab3cf4c66afce6e6e9c5c9e53
This reduces the dex size by ~1.5MB (~85%). Note that we intentionally
use a very conservative Proguard config to minimize risk, as this target
isn't as widely used or tested as other system apps. In any case, most
of the reduction comes from trimming transitive deps, as the app layer
is relatively thin.
Test: m + toggle several easter eggs
Bug: 203241149
Change-Id: I5e13e2246053fde2c4ac71e38a28f8de5c6c51c7
