The only permissions a user can control for a legacy app in
runtime style without crashing the app are the ones defined
by the platform because we have app ops only for these and
also we contorl the access to data guarded by them.
bug:27102458
Change-Id: Ifd1350d056b4fe29739ab8fdc5cbea89fa2e4037
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
Always save tile specs after move and don't trigger an entire data
set changed because we are aware of all changes.
Change-Id: Ic75b9ea8ed9b7d1a11d02f9af7858f3d040ec074
Fixes: 28334197
The HUN logic delays removing notifications for a second or
two, but this makes Direct Reply stick around too long after
sending. To prevent this, cancel notifications in the sending
state immediately.
Change-Id: I9e655bb17674265761e1f6cc25acb2fb9f0c72a6
Fixes: 28421972
If the insets change, "mWidth/mHeight" won't change
as it's based on the window frame (not the surface size),
we need to track when the insets change and call
HardwareRenderer.setup with the new values.
Bug: 28257246
Bug: 28368990
Change-Id: Ida304b57c4671d010d1cf7b370674c9453841c97
I think we were getting accounts uninstalled on android devices when
SyncManagers called validateAccounts() while GmsCore was updating.
I try to prevent this by not removing accounts unless the data directory
has actually been removed (which shouldn't happen during updates).
Bug: 25611016
Change-Id: Ib526b3000ad741815d48fd020af2cc19d6205166
Note - this should only ever be called from LockScreen after getting
the password to avoid the double prompt
Bug: 28376346
Change-Id: Ic44df4fdcc23408c56b1b9375deed1c6ad2af544
