am: bca6ffddd8
* commit 'bca6ffddd8e9db7f89565a13cc3322e8dbbfdc2a':
Make sure all Notification actions are shown
Change-Id: I221b6755607d55b8e8f2d14ae75017adc08c97cc
am: 798a860efb
* commit '798a860efb0c599448483d5a8e6a9429777c5bc5':
Make sure all Notification actions are shown
Change-Id: I094ba82280047da811da0e65e1a2e6d38f88497f
am: c09542b84e
* commit 'c09542b84ed974b5f74bdc67937cefe3cf527e19':
Add api to WearableExtender for setting and getting the dismissal id. Bug:27696581
Change-Id: Id1d0131b1e2ef55863d917d7b647694e57a17419
am: f4810f5506
* commit 'f4810f5506203ac03439d1ed6e33e021540568f8':
Add api to WearableExtender for setting and getting the dismissal id. Bug:27696581
Change-Id: I3a16e15adaf26be3528224c265be9a0e82957a38
When entering split-screen mode by long pressing the recents button, the
top task in the fullscreen stack is moved to the docked stack and the new
top task is the fullscreen stack is considered visible for a short amount
of time until sys-ui launches the recents activity. This causes the new
top activity in the fullscreen stack to be relaunched due to configuration
change.
To fix this sys-ui now sends an hint to activity manager to move the home
stack forward so that it can be on-top of the fullscreen stack and makes
it invisible before recent is launched and animated in.
Bug: 28470261
Change-Id: Icfd85e932fe913dfb498752b5878cc7c690fd559
am: 027612d71f
* commit '027612d71f9e50b900cba8b53320a8fe87e6f7f1':
Set ActivityInfo.resizeMode to RESIZE_MODE_RESIZEABLE by default
Change-Id: I7039b26a64e8a63515de5b42907135e53b2ea97b
am: e7fefcb565
* commit 'e7fefcb5650afddff544c008bc06ce748f635727':
Set ActivityInfo.resizeMode to RESIZE_MODE_RESIZEABLE by default
Change-Id: I7187746826a5ae3f82f95ac203d6ae063b56275e
Previous assumption was ActivityInfo was completely initialized in
PackageParser, but that isn't the case with the ResolverActivity
whose ActivityInfo in populated in PackageManagerService.
This was causing the device to exist multi-window mode since
the default ActivityInfo.resizeMode was 0 (RESIZE_MODE_UNRESIZEABLE).
Bug: 28378995
Change-Id: I46e58d434f2a0274c461a8ff00b59ed3d2a1dd52
GmsCore will use different filenames to distinguish a security update
from a normal update. (update.zip for normal update and update_s.zip for
security update.) So, if framework observes the filename as
"update_s.zip", write command "--security" to BCB. This cmd ask the
recovery image to choose the right background string for update.
Bug: 27837319
Change-Id: I2ef12267a6be57d8a81f7f9f34c09aea54530c1f
am: 98d57313f2
* commit '98d57313f247a80928b6358dda05a16c3b4000dc':
Flag to mark foreground jobs, fix data saver.
Change-Id: Id863d0ff4f8e7f13049231298feaab9839b4667c
am: 9a977b7d45
* commit '9a977b7d45df0d3d59c5eec7f9534c3bd5fcd91d':
Flag to mark foreground jobs, fix data saver.
Change-Id: I908d725a84e9590d0da38a586b066a63473d4f28
By declaring a <restrict-update> tag in its manifest, a system package
can restrict its update to be the singular package that has the same
given hash. An update's hash is the SHA-512 across all its APKs [i.e.
for splits, the SHA-512 is calculated over the concatenation of the
base plus all splits].
The restriction only applies to system packages.
Bug: 28398205
Change-Id: Iec493fc8ef27edee53f1d437cb0caaa78782f329
When a job will eventually run in the foreground, the internal
scheduling needs to ignore any background network restrictions when
satisfying constraints. This also means the job should ignore the
current device doze state, since the requesting app could get the
same behavior by starting their own foreground service.
Always dispatch network policy changes to ConnectivityService first
to ensure that it has up-to-date information. Fix bugs around data
saver that were causing networks to not be marked as BLOCKED for
background apps; before this fix apps would have been spinning in
internal connectivity loops, thinking that the network was actually
connected when the kernel was actually blocking their traffic.
Offer new ConnectivityService method overloads to ignore the blocked
state for a specific UID.
Print unsatisfied job constraints to aid debugging.
Bug: 26571724
Change-Id: Iaaa17933e6dc1bf6d3dff26d0bfc12222e51e241
am: c5e5cd5be7
* commit 'c5e5cd5be7f90474f753f8ea5069a72ba684eb8b':
Fixes on handling messages from apps to host.
Change-Id: I56964bc90ddd047d46e4cb277ede780410eff984
