* changes:
Changed the documentation of the colorization
Fixed the appearance of colorized fullscreenintent notifications
Adapted the interpolator when using fingerprint
The row is now labeling the expand button
There was still a reference to ongoing, which wasn't needed
Test: non, documentation change
Fixes: 34469375
Change-Id: Ic76d996f92f339db869f25d7696313eefc0c07bb
* changes:
Rely on view animations for ResolverActivity
Create a valid ActivityOptions Bundle even for default animations
Remove scale up animation for startActivity from RemoteViews
ANDROID_ID for Instant Apps now has the following properties:
1) per-app scoped
2) reset if the user clears the Instant App
3) remains the same if the Instant App gets upgraded to an installed
app.
Note that if the user goes instant -> installed_1 -> uninstall ->
installed_2 the ANDROID_ID at installed_1 will not be the same as
installed_2. This was deemed better than the id changing on the upgrade
step.
Test: manual
Change-Id: I532975c50049c94ff80902a897e001dd35a69f9f
Bug 37413327
When there was an animation and the fragment transaction wasn't
optimized, the fragment visiiblity wasn't being set during show().
Test: I0fd4029a02d6c9f082011bf56f0d3c8245803f68
Change-Id: Idc2c74ae2fc4759a755a5988ce6ca1b39ef8d554
The ActivityOptions bundle can hold additional information beyond the
animation details (such as the usage time report, launch, display id, etc). We
need to return a non-null Bundle even if we're using the default animations to
retain that information.
Test: Added in 8209c4bf
BUG: 34235073
Change-Id: If69edadb3f7ff937f07fc618bddbd10cf46666e6
Bug 37156970
Many applications need to get the LayoutInflater used for
fragment View inflation. onGetLayoutInflater() can be heavy
weight, so a version that caches that last value is added.
Support Lib: I11d719d7416a5bb3b65f37a78e6ed96a69c32332
Test: I6aa0ecfe7136d133d15a597857f6cf6f3cf68fca
Change-Id: I686d5b39f7a046396fff124c33c22a73952ee5d7
The job queue now handles URI permissions associated with
the Intent of each job. Just (kind-of) like Service!
Also do the second pass of locking in job scheduler, getting
rid of all the async dispatching on a handler, and just executing
calls right in line with simple locking. This probably fixes
a few other race issues, and allows us to make sure that we
always finish a job correctly when dequeuing the last work (we
will always atomically dequeue and finish, so no new work can
slip in between).
And fix a little debug output in IntentFilter.
Test: ran CtsJobSchedulerTestCases, added new test for URI perms.
Change-Id: I52f700ef0cd5be3ff70050f9c0f5fe3e8a5ccac1
- As a part of transitioning into PiP, we remove the content insets, and
as a result, we also need to adjust the source hint rect for the change
in insets as well.
Bug: 37418994
Test: Enter PiP from YT, ensure no jump at the end
Change-Id: I74219b05c91d3c8b8466dd8fff4d6dd692f08725
This change deprecates the method akin to the previous deprecation of
ActivityManager#getRunningTasks. The documentation has been updated
to reflect the current limitations of the method.
Change-Id: I6f35309c1224fdf1f890bce3cc614be8aa343368
Fixes: 36937370
Test: documentation
- JobServiceEngine now takes a concrete Service instead of
generic Context in its constructor, since it really must be
associated with a real Service.
- Expand documentation of how dequeueWork() operates.
- Fix some job scheduler implementation to hopefully actually
match the docs: transfer remaining executing work to the new
job, and actually correctly transfer state from old and new
jobs if we are rescheduling due to a true return from onStopJob().
Test: bit CtsJobSchedulerTestCases:*
Change-Id: Ia66797049883eefb566264f930070afb69d469b1
