We only want to handle non-staged rollbacks here. Staged rollbacks are
handled elsewhere. Checks for new rollbacks can be replaced by
|!rollback.isStaged() && rollback.isEnabling()|.
Bug: 149069841
Test: atest RollbackTest StagedRollbackTest
Change-Id: I9488f94a76fdd4cedbfc494f9378d0baa054e057
Let apps that haven't been used in 4 days time out into the RESTRICTED
bucket (after being in the RARE bucket). Apps that timed out into the
RESTRICTED bucket can be pulled out of the bucket via prediction.
Bug: 145551233
Test: atest FrameworksServicesTests:AppStandbyControllerTests
Change-Id: I646b5c4e3d3b45bd0ba8404b5a0c3d26186737c0
The detector class to be used by the CountryDetectorService can be set
by overlaying config_customCountryDetector in the device config.
Test: atest CountryDetectorServiceTest
Bug: 141626568
Merged-In: I158abd6397e3102d13e431ba043e8ce45061b64a
Change-Id: I158abd6397e3102d13e431ba043e8ce45061b64a
(cherry picked from commit 34147601d8)
Undo forced usage for NO BT config set by wired device
connection or any other usage for media when hearing aid
device is connected.
Bug: 148883172
Test: plug USB headset, play music, connect hearing aid, verify music plays on hearing aid
Change-Id: I1db1d40eaf351fc6189ee8f8bb75003be374768a
am skip reason: Change-Id Ib18cefda42fd778f5868ba63007b0b18e83e2c4d with SHA-1 5bc3c58134 is in history
Change-Id: I2d16259fa0c240463ce052ebe652a4a3c430c4d6
Change the framework to handle brightness as a float rather than an int.
Test: AutomaticBrightnessControllerTest
BrightnessConfigurationTest
BrightnessMappingStrategyTest
BrightnessUtilsTest
DevicePolicyManagerTest
DisplayManagerServiceTest
DisplayTest
DozeScreenBrightnessTest
PowerManagerTest
PowerManagerVrTest
SettingsProviderTest
Exempt-From-Owner-Approval: Changing param from int to float
Change-Id: I413641cd987c5ec8f82753c0388a33f85a9682de
am skip reason: Change-Id Ib18cefda42fd778f5868ba63007b0b18e83e2c4d with SHA-1 5bc3c58134 is in history
Change-Id: Ibe601a5fd474fcdb858fe5ee60bc8996e627e0c1
am skip reason: Change-Id Ib18cefda42fd778f5868ba63007b0b18e83e2c4d with SHA-1 5e931c7e2e is in history
Change-Id: I8c6f3be311600528de50b842e91437bc30b8318d
am skip reason: Change-Id I572736ff773e71e420a732aa4c56d5dceee1a454 with SHA-1 b30b3ba232 is in history
Change-Id: I6e9e7ad37b35b0be2d62b3603dc5e060541e305c
This is a feature of two components:
1) Input code that takes user input around the PIP window border and
starts resizing
2) The actual resizing of the PIP task/stack that currently lives in WM,
but will live in SystemUI once migration is done to using Task Organizer
The CL only takes care of #1, the input side living in SystemUI.
Bug: 111426176
Test: Manually drag the corner of PIP window
Change-Id: If4b5e6ea5c482f4fa6eb571b441cf9e6966fbf4b
Classes that hooked on to NotificationEntryManager to add more state
would leak the entries because NotificationEntryManager wouldn't inform
them to clean up their state if NEM ends up removing a notification
that's pending inflation. This is because the notification isn't
technically "active" yet based off NEM's pipeline. We add this hook to
correct this.
This is not an issue in NotifCollection as it is unrelated to the
inflation pipeline and instantly considers an added notification
"active" when it's posted, so the removal/clean up callbacks are
actually called when it's removed shortly after posting.
Bug: 149212504
Bug: 149205483
Test: add + cancel notifications in Notify.apk
adb shell dumpheap com.android.systemui
Observe in heap dump that NotificationEntry's match up
Change-Id: I9e41399dd9ee0de853f39a47876d8c176a8d8b21
