am: 3f076da22b -s ours
am skip reason: change_id I12cd9f2c87a2e3c00d64b683edf3631e29a51551 with SHA1 aa1c962ded is in history
Change-Id: Id3408faeecfc203d89b6225790eceda530362fb3
am: 7a77e78ade -s ours
am skip reason: change_id I1ff4bea0a2ea163bf9c1ccc0d80ffd5d04c49191 with SHA1 032293a197 is in history
Change-Id: I60250c407a2b493cab59d97d632e11c0784147fc
This adds a new transition classification for apps which are
switching between 2 visible states. The primary example of this
is windowing-mode change.
This new classification is mChangingApps in DisplayContent and
there is a transition type for TASK_CHANGE_WINDOWING_MODE.
The mode-change transition is scheduled when AppWindowToken
detects a windowing-mode change. It immediately creates
a snapshot and temporary leash to "freeze" the visuals of
the app until the animation starts (all transitioning apps
are ready).
The transition itself is a blend of fading, scaling, and
cropping based on whether the end-state is bigger than the
start state.
The RemoteAnimationTarget now includes a startBounds and an
extra "snapshot" leash for controlling the snapshot overlay
relative to the AppWindowToken. If either of those is
populated, the client of the RemoteAnimation can assume it
is animating a change and is responsible for transforming
the leash from the startBounds to its final state.
Bug: 113253723
Bug: 111762928
Test: go/wm-smoke + RemoteAnimationControllerTests
Change-Id: I8654656124b888950e55e31d88ce7a4101e935f8
am: b8fb174ffa -s ours
am skip reason: change_id Id38a6ccabdcd0da02a53e76c47850e197016e781 with SHA1 eac7f4e15a is in history
Change-Id: I4542b392afd0b04e0923cf81c870419d549c810d
am: b8f046ea4e -s ours
am skip reason: change_id I25022d976e7444489aad1aeb1ce6b05736233476 with SHA1 c7a9dcf351 is in history
Change-Id: I0af7ada9c0b75d9a72b42a3ebc7f43ac57a632db
Bug: 122719904
Test: manual stats_client test and check the statsd logs
Change-Id: I3dac9f31f59e6f10393c97c6bd9ca0d0ccb11e23
Signed-off-by: Carter Hsu <carterhsu@google.com>
Instead of keeping reading the whitelist everytime, we want to store it in
Settings.Global variable and reuse it later.
BUG: 120869311
Test: Build, flash and boot.
Change-Id: I5e39757383c5ba7d31af7efb3e6e8a2996e669f4
InputMethodManager#setCurrentInputMethodSubtype(), which was
introduced in Android 4.0 ICS [1], was probably mistakenly exposed as
a public API, because it has required WRITE_SECURE_SETTINGS that
typical applications cannot have.
This CL marks InputMethodManager#setCurrentInputMethodSubtype()
deprecated. There is no actual implementation change at this moment,
but developers should avoid relying on this API in general not only on
futuer versions of Android but also on existing devices.
[1]: I55daa19ba924999def544bf841f00bf54852f3e1
b66d287e3003a0934d5714fbf15e554b3c814906
Fix: 123249820
Test: make -j checkbuild
Change-Id: Ia31df87ad2182484d7335503c5d87cb93540fd17
