v2 (earlier attempt was reverted due to deadlock)
Don't come out of doze when screen is on, but
wait until the keyguard is dismissed as well.
Pass along the keyguard dismissed to DeviceIdle
Request exitIdle when notifications are clicked.
Bug: 63527576
Test: Manual:
Turn off screen
adb shell dumpsys battery unplug
adb shell dumpsys deviceidle step x4
Turn on screen, verify still in doze
Unlock, verify out of doze
Change-Id: Ic5129611d4f098723b31d62a27db8f50860697d4
Fixes an issue where the keyguard going away flag was not cleared
until the keyguard showed again, which prevented SystemUI from ever
controlling the orientation while it is not showing the keyguard,
such as during unlocked AOD.
Change-Id: I40d4052321fe76c988d673a5ecbc07b74192bec6
Fixes: 69368568
Test: Set up secure keyguard, Turn off "power button locks", open a landscape app, press power button, verify AOD shows in portrait.
This reverts commit 5564f880db.
Reason for revert: Resolve merge conflict for another revert (ag/3537193)
Bug: 72710855
Change-Id: Id7c3a3993a45c588ee4668d7486d67d764541b1e
Packages can now get to run alarms only if a certain amount of time has
elapsed since they last go to do so. The time interval is decided based
on the current app standby bucket the package is in. So, frequently used
apps get to run alarms more frequently than the rarely used ones
Test: atest CtsAlarmManagerTestCases
or
atest CtsAlarmManagerTestCases:AppStandbyTests
Bug: 72660630
Change-Id: Ib89c81e8166eab4c985152e01178da61f8a880f7
Change certificate checks to also consider the possibility of
signing certificate rotation by checking the
SigningDetails#pastSigningCertificates field. In particular, add a
SigningDetails#checkCapability method which reports whether or not
the older SigningDetails is an ancestor of the current one, and
queries whether or not the old one has been granted capabilities,
such as being a sharedUser.
Bug: 64686581
Test: Builds, boots, browser and camera work, all with v3 signing.
Change-Id: I4199ff3f2d9ae959325b117b28e666ae31889800
Unlike Parcelables, Byte array produced by the class can be safely stored in the database.
Bug: 71804644
Test: adb shell am instrument -w -e package
com.android.server.locksettings.recoverablekeystore
com.android.frameworks.servicestests/android.support.test.runner.AndroidJUnitRunner
Change-Id: I826a0cc4d7dc33ff1a062374a4fc8471db8e2f34
This change removes deprecated classes and constants that were not
renamed from ephemeral to instant prior to O. There were no
consumers of these APIs as correctly named alternatives existed and were
referenced in docs. No known consumers of these APIs exist on user
builds.
Fixes: 38137176
Fixes: 38121489
Test: manual; builds and instant apps launch
Change-Id: I982f8a6edc5668dd42cea65e52a1433ec8d6f8ef
When iterating through each child to set its updated position,
the transaction object was passed to the children. This could allow
multiple transactions to update the same property on the same child.
If that occurs, then the merge does not guarantee the same order.
This could cause earlier transactions to overwrite later ones. Instead,
have each WC update its own transaction object.
Change-Id: Ie1bb758e4efd74fa012c7ec945d9c1c586162df4
Fixes: 72198558
Fixes: 72463091
Test: Issues from bugs no longer occur.
Test: go/wm-smoke-auto
This is a regression caused by I33531a3f6148232b777ea8bfd02f13700649e317
Test: SystemServerTiming_StartPackageManagerService_avg: 789.5 -> 577.5
Bug: 30972906
Bug: 72572541
Change-Id: I6eafc317f3864bf15ac7653bc526e634148d8b00
There are two existing cases where apps that share a sharedUserId
potentially end up in separate SELinux domains.
1. An app installed in /system/priv-app runs in the priv_app domain.
An app installed on the /data partition which shares a
sharedUserId with that priv_app would run in the untrusted_app
domain (e.g. GTS b/72235911). This issue has existed since
Android N.
2. The untrusted_app domain may now deprecate permissions based on
targetSdkVersion, so apps with sharedUserId may have different
permissions based on which targetSdkVersion they use. This issue
has existed since Android O, but is particularly problematic for
feature "Deprecate world accessible app data" which puts every app
targeting P+ into its own selinux domain.
This change fixes#1 and adds a temporary workaround to prevent #2.
Test: cts-tradefed run cts -m CtsSelinuxTargetSdkCurrentTestCases
Test: cts-tradefed run cts -m CtsSelinuxTargetSdk27TestCases
Test: cts-tradefed run cts -m CtsSelinuxTargetSdk25TestCases
Bug: 72290969
Change-Id: I211de05ad6f10b69e3e082cfe977f2dd43d90549
The lib2 implementation of libtextclassifier is incompatible with models
for lib1. To avoid trying to load a lib1 model and failing (which happens
when devices are upgraded from O to P), we need a new update model path.
Using this opportunity to remove smartselection from the filename, which
isn't appropriate any more given what the model is used for.
Test: Ran core framework tests
Change-Id: I79a80d10d920019f5091fe9884f370149d39fe88
Also, remove all watchlist events before last midnight when we want to clear db
Bug: 63908748
Test: Visit watchlist site, then set date to tomorrow and reboot
will see records in db is removed and watchlist report has this record
Change-Id: I9543441a49c3ad3a0bf79ad9a9ec231ff10c0748
Since we split tasks into separate stacks, mNoAnimActivites from
other tasks/stacks were pretty much never cleared, leading to
skipped animations in the following cases:
- Enter/exit multi-window, relaunch anything, animation was
always skipped.
- Reopen PIP activity from notification shade
Now, we make this a global list which we immediately clear
after using it.
Test: go/wm-smoke
Test: Enter/exit multi-window, relaunch
Bug: 64674361
Change-Id: Ic36d278b263d6b3c6a7ec7416c8b94c4eed8e440
