test.
So the instrumentation can have the same permssion as app and it can
skip the FGS background start while-in-use restriction.
Also reuse the ProcessRecord.mAllowBackgroundActivityStartsTokens flag.
Bug: 136219221
Test: atest cts/tests/app/src/android/app/cts/ActivityManagerFgsBgStartTest.java
Change-Id: I7d8708945ffe79b83825f8edb688078706c46770
(cherry picked from commit 5a5daafbca)
- Buttons and whatnot should match the theme accent color
- Background should be white to maintain a11y contrast
Test: manual
Fixes: 149569128
Change-Id: I0d38484bb91aa1cdd4ae2f7de6dc2c72d15cd0ef
The build system collects transtive deps from jni_libs for APKs.
No need to list them explicitly in android_app definition.
Bug: 146992436
Test: m com.android.tethering
deapexer extract com.android.tethering.apex apex
unzip apex/priv-app/Tethering/Tethering.apk -u apk
ls apk/lib/arm64-v8a
Merged-In: Icba6ea3611c443cbf22ad6363d0239377d16ac9e
Change-Id: Icba6ea3611c443cbf22ad6363d0239377d16ac9e
(cherry picked from commit 9618b66f28)
Some OEMs may not want the PIP window to resize on touch; this is true
for those that ship only large-screen form factor devices, so the PIP
window is already big enough for the controls (e.g. ChromeOS).
Bug: 148083488
Test: Build, touch - PIP does not resize.
Change-Id: I997c3f428981aafda4b6cffece355ba0cfdac4e6
The permission is being lost somewhere, so remove it from the manifest
and instead explicitly invoke the permission in the individual test
itself.
Test: atest SystemUITests
Fixes: 149740458
Change-Id: I1268ddd37d243735ff21e6761dbd59f43b3be0e2
4579c0aea2 changed the method signature
of the constructor of ResourcesKey, which is marked
UnsupportedappUsage. Restore the previous signature and provide a new
constructor that is hidden.
Bug: 147359613
Test: none
Change-Id: I391167e9064b1d88f4ad75200a190e5e3b0968cf
Settings.Global.ENHANCED_CONNECTIVITY_ENABLED was not added to the
SettingsBackupTest. Adding to test to fix android.provider.SettingsBackupTest#globalSettingsBackedUpOrBlacklisted
Bug: 150207643
Test: atest SettingsProviderTest
Test Result:
[1/107] android.provider.SettingsBackupTest#systemSettingsBackedUpOrBlacklisted: PASSED (26ms)
[2/107] android.provider.SettingsBackupTest#globalSettingsBackedUpOrBlacklisted: PASSED (0ms)
Change-Id: Ia5c225919c54594d17cbdfa4d8268be0aeb995b9
For some reason, ITestDevice property getting and setting is flaky on
GCE. This causes frequent test failures.
(cherry-picked from commit 94d9a21ccb)
Test: tested on cuddlefish device
Bug: 149802360
Merged-In: Iba48c173bdea2d55d8f2aa7f0fa382628582fe1c
Change-Id: Iba48c173bdea2d55d8f2aa7f0fa382628582fe1c
Use the system properties instead of phenotype since GMS can change the
values more arbitrarily for PH properties.
Test: manual
Bug: 149645847
(cherry-picked from commit 599079b381)
Merged-In: If0a716075597f45e95b8357480e4b4a7c52fbb2a
Change-Id: If0a716075597f45e95b8357480e4b4a7c52fbb2a
Created a SurfaceFreezer class which lives in WindowContainer
and manages/will-manage per-container freezing (snapshots).
This replaces the one-off change transition code.
Change Transitions used to create its own temporary leash
on initialization and that leash would be replaced/cleaned-up
as soon as the animation leash was created.
Now, the SurfaceFreezer creates the animation leash immediately
and SurfaceAnimator can take a SurfaceFreezer instance when it
starts an animation. At this point it will take the leash that
was already created by the freezer and use that. This removes
the messy reparenting/cleanup.
To deal with this, though, leash callbacks into Animatable
needed an extra stage: onLeashAnimationStarting. This is called
when SurfaceAnimatior is actually starting to animate the leash.
Next, DC.mChangingApps was converted to list of WindowContainers
rather than ActivityRecords. Some of the existing change code was
cleaned up (ie. there was some visibility stuff that doesn't make
sense because changing apps are visible->visible) and some of the
Activity-specific functions were generalized. For now, there are
a couple things that use the top-activity for changing Tasks.
The result of this means that windowing-mode change transition can
now fully live at the Task level. This also should allow freezing
at any hierarchy level which enables app-freezes that don't freeze
the whole screen and potentially mixed seamless/snapshot-based
rotations.
Bug: 149490428
Test: existing tests pass. Manually open app in freeform and
maximize/restore it.
Change-Id: Ib32524ebbbb084a98442d3d035897306a11ee6c2
(cherry picked from commit e55b9e0f9d)
Any exception here (e.g., NPE) will crash the entire system process.
Bug: 150217444
Test: atest AppIntegrityManagerServiceImplTest
Change-Id: I86eaa0bf7cb9d39fb23ee6aa71e80547bb95cc7e
(cherry picked from commit 1787f31065)
Fix a crash with NotifBindPipeline where we try to inflate a group child
after it's removed. This is due to some edge case logic where we delay
view hierarchy updates til later (i.e. after the notification is
removed) and inflation logic and group change logic being precedented on
view hierarchy changes.
This fixes that by checking if the row is already removed in order to
stop inflation. We add a similar check for redaction since that is
similarly triggered at the view hierarchy stage.
Bug: 149989491
Test: Repro from bug
Change-Id: I42114bcdaf0d135bcbb68f0b634b77252ea7b8b0
