Also make sure not to do the restorecon() before the file is
created.
(Also fix binder identity bug in the 'bmgr fullbackup' flow.)
Bug 26834865
Change-Id: Ia8a59eeb55762264163c8b310caae5e303413571
- When opening recents while there is a task docked, initialize the
stack scroll to the front of the stack
- When undocking a task while recents is open, scroll to the front of
the stack
- Fixing offset when adjusting the task stack size due to top inset
being double applied in some dock states
- Fixing issue with task view not scaling when picking up from the
freeform workspace
Change-Id: I15436ac21f05ff521492d8ae1c682a414503101a
When "handling" an uncaught exception, make an attempt to stop
profiling. In case profiling was active, this will avoid losing
the profiling buffer.
Bug: 26291225
Change-Id: Ie5f5517b46ed89d0456a4aac9d4ff3b713d1d8aa
The issue was traced to go/aog/854901. This revert was only temporary.
Bug: 26863668
This reverts commit d9c31db2e9e4da08ed43c88135fa7e220bc26ebf.
Change-Id: I6724059db18263936cc392651c621d27836f1c33
When the roaming status of the cell network changes, it is handled as
follows:
-DcActiveState gets an event (either EVENT_DATA_CONNECTION_ROAM_ON or
EVENT_DATA_CONNECTION_ROAM_OFF) and calls
NetworkAgent#sendNetworkInfo with updated NetworkInfo.
-ConnectivityService then gets an EVENT_NETWORK_INFO_CHANGED and calls
updateNetworkInfo with the new info.
With the previous code, the NetworkAgent's NetworkInfo object would be
updated internally, but because the state of the connection had not
changed from CONNECTED, the change would be considered a duplicate and
otherwise ignored.
With the new code, we call notifyIfacesChanged() when the state is the
same but the roaming status has changed. That should be all that is
necessary, as roaming is not exposed as a link property or network
capability today.
Bug: 26545456
Change-Id: I33d32d1fa84ce41dbe01542e5b498eda4b744b74
This feature is very old and hasn't been used in many releases. In
addition, it was never taught about multi-user layouts, and it would
be incredibly hard to maintain in the new FBE world where CE keys
may not appear until several reboots after an OTA.
Bug: 26854442
Change-Id: I3e88d38fde671e41ea9bdd790173d8b93c8a5c12
If we try scheduling a pass before the system is ready, record a
pending event and dispatch once we're actually ready.
Bug: 26863668
Change-Id: I028285383c8bbe8b653aeaa7544eefe3d41277bc
Log to two new histograms - one for operations originating from system
providers, the other for operations originating from external providers.
Events in these histograms are bucketed by
- type (copy, move, delete, etc)
- destination (system vs external provider, with a special bucket for
intra-provider operations)
- result (success vs failure)
BUG=26737132
Change-Id: Ic24c7a22fa3c1227e23cfbd42ae80ca1f70a19ba
