This reverts commit 821f43aa64.
Reason for revert: better fit:
- restrict the Package Manager feature flags to features for which the app developer would need to "target"
- typically hardware types should be mutually exclusive to each other
Bug: 124406307
Test: make checkbuild
Change-Id: Ie247a21eb8bbc83efad833ca8db675fd11e7ea4e
Clarify the docs around Resources.getSystem: the object returned is not
affected by Runtime Resource Overlay.
Test: builds, boots
Change-Id: I1011f37c98d81b8b1977f4dbc579bc2a536208cd
* changes:
Adds class and method documentation in all app prediction classes
Link Intent.EXTRA_SHORTCUT_ID to ACTION_SEND Intent
Change ShortcutInfo.Builder.setLongLived to take a boolean
Per API council feedback, we are making changes to include only the
namespace in the system API defined in DeviceConfig.java. Strings which
define property names should be defined in code local to the feature
instead.
Bug: 126411407
Test: atest FrameworksCoreTests:DeviceConfigTest
atest FrameworksServicesTests:PackageManagerServiceTest
Change-Id: Ie3b0539f51a582fb7583ece88e5d3bde0cc1efd7
This CL introduces a new @hide bind flag BIND_SCHEDULE_LIKE_TOP_APP so
that visible IMEs can have the same thread scheduling policy as the
actual top app, like SCHED_FIFO for UI and RenderThread when it's
available [1] and TOP_APP_PRIORITY_BOOST otherwise [2].
Hopefully this would provide more consistent UI performance and
responsiveness between the actual top app and IME.
[1]: I7b8a31830ad80f7efa00236928d5476998ed4e00
33eb07f575
[2]: Iced88269f7e2d378d5870ded1a5ccf9f259fda57
b783e7b44bf174075f6860d295808ee462b38451
Fix: 117274342
Test: Manually verified as follows.
1. Build aosp_blueline-userdebug and flash it.
2. make -j EditTextVariations
3. adb install -r \
$ANDROID_TARGET_OUT_TESTCASES/EditTextVariations/EditTextVariations.apk
4. adb shell am start \
-n com.android.inputmethod.tools.edittextvariations/.EditTextVariations
5. Tap the first edit text field to bring up the AOSP Keyboard.
6. Make sure that top app (EditTextVariations) and the IME (AOSP
Keyboard) have the same thread priority / scheduler policy for
their main UI threads and RenderThreads.
adb shell ps -p \
`adb shell pidof com.android.inputmethod.tools.edittextvariations` \
-T -o PID,TID,PRI,SCH,CMD
adb shell ps -p `adb shell pidof com.android.inputmethod.latin` \
-T -o PID,TID,PRI,SCH,CMD
For both UI threads and RenderThreads, Thread Priority should be 29 and
Scheduler Policy should be 0.
7. Tap the back button to dismiss AOSP Keyboard.
8. Make sure that Thread Priority of AOSP Keyboard is no longer boosted.
adb shell ps -p `adb shell pidof com.android.inputmethod.latin` \
-T -o PID,TID,PRI,SCH,CMD
For both UI threads and RenderThreads, Thread Priority should be 19 and
Scheduler Policy should be 0.
Change-Id: I143fb39cec55351b097e835cf8bbf9668e02d86d
Only allow rollback to be enabled on the modules included in a mainline
update. We don't want to support rollbacks for all apks in general yet.
Enforce that only installers granted the MANAGE_ROLLBACKS permission can
enable rollback for a package.
Introduce a new TEST_MANAGE_ROLLBACKS permission that can be used to
enable rollback on packages that are not modules. This allows us to
continue testing rollbacks, given we can't do a mainline update as part
of the rollback tests.
Test: atest RollbackTest, with new tests for permissions added.
Bug: 128277794
Change-Id: I29ab9a750a1283592b8a855322ece516e42260ca
Now that we have a definition for a SystemCaptionsService we should move to use it instead
of piggybacking on ContentCaptureService.
This is also required to ensure that T2C will be granted audio recording permission in case it will
be shipped in a different APK for OEMs.
Test: Manual and DefaultPermissionGrantPolicyTest.
Bug: 128622041.
Change-Id: Ic0b5b21b05ff1ad200472bfc1c4eaa3c588324df
Since uninstalling apexes is development/testing operation, only root
and shell are allowed to perform it.
Test: adb uninstall + adb reboot
Bug: 123667725
Change-Id: Ifd7b743b2581dbdeebd63c33fd343a830dfc377a
and the mechanism to use it
Since both starts and bindings might be contributing to the service
being whitelisted, track the state in ServiceRecord and update
the parent process accordingly when changes happen.
While we're at it, add that flag for bindings to accessibility
services, voice interaction services and QSTiles.
Also, make the timeout constant configurable for start-based
whitelisting.
Bug: 124298522
Bug: 123495976 (accessibility services)
Bug: 123337181 (paying via NFC, like Google Pay)
Bug: 122887611 (binding to InCallService)
Bug: 127774234 (binding to QSTile)
Bug: 124288681 (binding to voice interaction services)
Test: atest WmTests:ActivityStarterTests
Test: atest AccessibilityServiceConnectionTest
Test: manual with:
1) notifications from calendar and dynamite to test service starts
whitelisting
2) enabling talkback and livetranscribe to test service bindings
whitelisting
3) adding the LastPass QSTile and clicking on it
Change-Id: I8b6f23f999683920411ca40ab5b25c688a4f7055
This change adds TestAPIs for tests to retrive an instance of
ConnectivityManager, allowing it to build test TUN interfaces, as well
as test networks.
This also integrates the TestNetwork types with ConnectivityManager,
creating virtual networks if the network agent is a test agent.
Bug: 72950854
Test: Compiles, CTS tests using this passing correctly
Change-Id: Ic1a04aa66014d1c66a74e65dbace3218437403ae
Merged-In: I741ef9cdf4bd4125d9129af3a030edf32f438e4f
This change adds TestAPIs for tests to retrive an instance of
ConnectivityManager, allowing it to build test TUN interfaces, as well
as test networks.
This also integrates the TestNetwork types with ConnectivityManager,
creating virtual networks if the network agent is a test agent.
Bug: 72950854
Test: Compiles, CTS tests using this passing correctly
Change-Id: I741ef9cdf4bd4125d9129af3a030edf32f438e4f
Backwards compatibility takes a slight performance hit. Only apply this
rule to outdated system apps as they are the only ones that use these
libraries.
Bug: 86259915
Test: boot Pixel 2
Test: boot Pixel 3 and systrace app startup
Test: atest android.content.pm.AndroidHidlUpdaterTest
Change-Id: I2d2e2ca79266a92ba0e4efcf25e31d15daee87a1
This moves PackageBackwardCompatibility from parsePackage to
applyPolicy.
The motivation of this is to expose partition information to these
files. Specifically, to expose whether the app is a pre-installed
(or updated pre-installed app) for certain backwards compatibility
rules that should only apply to these cases.
Bug: 86259915
Test: boot Pixel 2
Test: Pixel 3: atest -p cts/tests/signature
- all passed except for CtsSystemApiAnnotationTestCases test which
failed (known issue b/124210145)
Change-Id: Ic824f06489781233dc98bf3dc0182681d32f7142
This ensures that there might be at most one committed non-finalized
(i.e. either applied or failed) session.
Note that from StagingManager POV atomic staged install is considered to
be a single session that is represented by the parent session of an
install.
Test: run adb install --staged foo.apk twice.
Test: StagedRollbackTest
Bug: 127296534
Change-Id: I497723173745d4f6eb64b7d22fa3adb0f9e8f6c0
... in order to remove unnecessary code.
9e4da717 Revert "Flip default of extractNativeLibs if targets Q+"
fe693a07 Revert "Fix default of extractNativeLibs in parseBaseApplication"
86e2783d Revert "Partial revert to not flip the default of extractNativeLibs"
Test: atest CtsDynamicLinkerTestCases
Bug: 128335904
Change-Id: I0e43608a76b3891e84c1622c7a98e2a1dab91985
