This would only kill processes if there were activities associated
with the recent task; now it always kills processes.
Always fix some debug output.
Change-Id: Iccda19ba0a20823347b06c13b450587283d28284
* commit '40b4f04ac3f8dd11fc1313472aca3713b34d7f6a':
docs: update various SDK and AVD Manager screenshots and remove one from the licensing doc that's not necessary
Further work to isolate layout from animation and surface operations.
Remove cruft and minor refactoring.
Change-Id: I6f910ed72c7c614996641c353870c2b2ab5e8bb4
* commit '1fbc85d32ddd8a764d522ba56cae10ca0d6c5f93':
docs: update various SDK and AVD Manager screenshots and remove one from the licensing doc that's not necessary
* commit '150107763d1b5ced8e70992268d7d6fc1888f7dd':
docs: update various SDK and AVD Manager screenshots and remove one from the licensing doc that's not necessary
* commit 'f32ab914147ede0b02302a28cce6fd2f301b0b3e':
docs: update various SDK and AVD Manager screenshots and remove one from the licensing doc that's not necessary
* commit 'f32ab914147ede0b02302a28cce6fd2f301b0b3e':
docs: update various SDK and AVD Manager screenshots and remove one from the licensing doc that's not necessary
During normal operation, it's common on a multi-core device to get
EINTR. This is especially noticable during a bugreport where several
services get EINTR even though it's not fatal.
This change adds TEMP_FAILURE_RETRY around the system calls that can
receive EINTR where a retry should happen.
Change-Id: If13d24f57c587392f57961fe2caf46e2a6fa843e
A recent change to enable View properties at the native DisplayList level
mistakenly cuased Animation transforms get be ignored for any View with
a DisplayList. The correct code should have checked whether DL properties
were enabled for the view (disabled by default for now).
Issue #6173975 Animations are gone
Change-Id: I5d5f53f854fb1b533a3150158e84392d7283d2a8
If the remote end of a bulk cursor died, then it was possible
for getColumnNames() to return null, violating the invariant
that it never returns null. As a result, the application could
crash in strange ways due to an NPE.
Since we are often interested in the column names anyhow, prefetch
them when setting up the bulk cursor adaptor. This way, a
remote cursor will never return null even if the remote end died.
It is possible for an application to continue to use a remote cursor
even after the provider has died unless it needs to requery it
for some reason. Of course at that point, bad things will
happen... but usually the app is better prepared for it than
if it just randomly encounters a null array of column names.
This change also optimizes the bulk cursor adaptor to return the
initial cursor window back to the client, potentially saving
an extra RPC. Because the communication protocol between
the CursorToBulkCursorAdaptor and BulkCursorToCursorAdaptor was
getting a little hard to follow, introduced a new type called
BulkCursorDescriptor to hold all of the necessary parameters.
Deleted several unnecessary IBulkCursor methods that are never
actually called remotely.
Bug: 6168809
Change-Id: I9aaf6f067c6434a575e2fdbf678243d5ad10755f
