We'll keep them around in the pending queue until the user is
unlocked, at which point we'll consider running them.
Bug: 27358148
Change-Id: I2eb538a89206d4caac620b3b4e989b011b309201
Encapsulating the logic to toggle multiwindow mode from recents,
and plumbing it through to accessibility global actions. Sending
accessibility events when windows bounds change. Exposing the
dock divider window type to accessibility services.
Bug: 27250995
Change-Id: Ib7491f1f853dc7f01bf5c5a4ac1f914f55d0608a
With this change ApplicationLoaders.getClassLoader()
creates linker-namespace for the classloader at the
construction time. Before this change the namespace
was created on first load of a jni library.
With this change we ensure that every classloader
has initialized namespace associated with it.
As an additional advantage we now can avoid storing
namespace-specific fields in the classloaders.
Bug: http://b/27189432
Bug: http://b/22548808
Change-Id: I3b160bd478a55171008682c40b2ebc13bdbd9882
* changes:
Removing boot completed check before hiding Recents.
Track double taps to launch the previous task.
Dev preview changes for incompatible apps.
- This was legacy from old code that was calling sendBroadcast(), and
with the event bus, we no longer need to wait until boot is completed
before launching home.
Bug: 26616934
Change-Id: I4d542a096174ac8b69035836e9311cbf8340b15b
- Disable drop targets when picking up a task that can’t be docked, and
show toast notifying user (for now)
- When a task is docked, update the task headers for non-dockable tasks
to indicate that they don’t support multi window. Update these
headers every time the multi window state changes.
Bug: 26774190
Change-Id: I020dcbac9b1230dba166eecaa12366986e684f9e
This reverts most of commit 21d361806c9e2dce5bae5b30f44be5ad87f32c22, which
broke too many expectations in both apps and framework widgets. We need to
find a safer way to handle the exit transition callback.
Bug: 27359366
Bug: 27353218
Change-Id: I769ac7a25cb900c50e857839ca0563fbc5a3cb16
That toast was kind of reduntant (since the phone already vibrates
before taking a screenshot) and often useless (because it was displayed
seconds after requested).
BUG: 26577203
Change-Id: I0ba6f974eefd473d158f7fefb12f6a5d2a50b772
We now have a fixed array of job service contexts, which doesn't
vary by build configuration. Instead, we keep track of the maximum
number of concurrent jobs we want to allow to run, and don't
make use of a context if it would put us over that limit.
The available contexts is now 8 (the largest used to be 6), although
the maximum we will normally schedule is still 6. We have the other
two around only for use by the current foreground app, to allow it
to schedule work while the user is in it, even if we have reached
our normal limit on the number of concurrent jobs.
The maximum number of concurrent jobs varies based on the memory
state of the device, from 6 (if memory is normal) down to 1
(if memory is critical). We aren't yet trying to stop all jobs
if memory gets lower than critical.
Instead of just keeping track of whether a uid is in the foreground,
we now track whether it is the top as well. Only the top uid
can schedule additional jobs above the current limit.
Also improved some of the dumpsys output.
Change-Id: Icc95e42231a806f0bfa3e2f99ccc2b85cefac320
It was appearing from the night tile being unavailable and causing
extra nulls in the list. Fix the night mode tile so the nulls don't
happen. Also fix the null handling to avoid this happening with other
bad specs.
Bug: 27061683
Change-Id: I48f769c06ed17c2ff1f166434857ec1faff14d02
