bug: 28763785
related-to: 27989717
related-to: 28887408
Revert "Fix wallpaper crop during unlock animation"
This reverts commit 616c7c10b9.
Revert "Fix wallpaper cropped too soon when unminimizing dock"
This reverts commit f0b76b071c.
Revert "Set final crop on wallpaper instead of intersect clip with stack bounds"
This reverts commit dcf0183cea.
Revert "Crop wallpaper windows to their current target stack bounds"
This reverts commit e6cb450b0d.
If a touch outside the status bar window is detected
we schedule autohiding the status bar - which is wrong
when that touch is due to touching the IME for DirectReply.
Bug: 28914905
Change-Id: Ic86612192368181f195fa54ac4f20edaf02af685
am: 4f401f24c7
* commit '4f401f24c79c26a0554331bf13948e402c611015':
Fixed a few memory leaks in SystemUI
Change-Id: Iba8725618829c316bbf99dd47b0e73526a9ab044
In phone landscape, when the navigation bar is on the right,
and when the status bar is forcing the IME and NavBar, make
sure that the nav bar and IME don't overlap, even if the
NavBar is only transient.
Bug: 28914905
Change-Id: I22921f1aca7970c2d02dfd88408eb15c5b17151f
am: 92d0316d28
* commit '92d0316d2837baceffb22e1a7eb0e5da50f0a025':
Set StaticLayout.maxLines only when ellipsize is set
Change-Id: I17934afae1d5e8b7fe3b3ad8b4286dd43f68393e
This scenario typically happens when the device is on Doze Mode and a
notification action is triggered from a Wear device.
In a nutshell, the workflow is:
- ProcessRecord has a flag telling whether a process has "whitelist
management" privileges.
- When NotificationManager binds a new NotificationListenerService, it
sets the BIND_ALLOW_WHITELIST_MANAGEMENT flag.
- On bind(), ActiveService asserts that only system apps can set that
flag.
- On computeOomAdjLocked(), ActivityManagerService sets the
ProcessRecord flag if necessary.
- Upon creating a notification, NotificationManager calls AM to mark its
PendingIntents as coming from a notification.
- When PendingIntentRecord sends it to the target, it checks if it's
from a notification and if so calls AM to do the temp whitelist.
- On unbind(), ActiveService removes the ProcessRecord flag if necessary.
Fixes: 28818704
Change-Id: I00d46036a2cbb73f7f733fd35bf0b743a02807a1
When mutating vector drawables, we need to not only copy over
the VD tree structure, but also the properties of the VD tree,
such as alpha.
Bug: 28974071
Change-Id: I265e7e3cb92455b876cae248bcb9811230cb34f9
If you're on the lock screen and a child background needs
to be shown (e.g. custom background and user expanding) the
background should fade in from 0 alpha otherwise looks odd
visually.
Bug: 27591195
Change-Id: I1f46831fd8b46eca5b54e7bd964af35752c4fa2f
Force stopping the bound scoring service would not automatically
reestablished the binding.
Replaced the custom BroadcastReceiver with a more standard
PackageMonitor implementation that handles the same actions in
addition to force stop.
Also added a few more debug log statements as they were helpful
during my development.
BUG: 28930592
Change-Id: Ic36ea77deb5e2117edc201e97d71be63bdd4230d
am: 83e50327fc
* commit '83e50327fcf24e4d17a341cc2efaafc95046a8f9':
Don't drop IPv4 broadcast packets when WiFi multicast lock is held
Change-Id: Ib76e96a84820fa36357d820ef6845f6155ec902c
IPv4 broadcast packets can be very common (e.g. every 2s) so they
need to be dropped in the general case. They also may be critical
for certain discovery protocols, so allow them through with APF
when the WiFi multicast lock is held.
Bug: 26238573
Change-Id: I03e09a2b9c779da5da775e78b95e9e0339720eaf
Always use the packages' derived instruction sets.
This fixes a bug where otas and background dexopt would only
look at one instruction set.
bug:28994818
Change-Id: I730b59d24943c71de30adb485a823fd79c6806a6