- The change to setTasks() was causing us to queue items to be loaded
before the activity had even started. This change ensures that we
don’t do this for the dummy-transition-only stack view, and only when
setting stack tasks for real.
Bug: 27538945
Change-Id: I4ff0413cb2fb961a4dedcad42471293bab4f955a
Also add proper names for the different dim layer surfaces, so we
better know where they are coming from when we see it in the
surface flinger dump.
Bug: 27270126
Bug: 27200491
Change-Id: Ic085e8505d20a941f4631ec914f00eefda74a766
The hiding of the thumbnails needs to be synchronized with the hiding
of the app window. Because destroying them immediately destroys them
without being part of the transaction, that can happen earlier than
hiding the surface.
Instead, hide the thumbnail in the transaction first and then put it
into a list to be cleared after the transaction is closed.
Bug: 27275815
Change-Id: I1530262c26c0751e53d218b686c46129f7c7df1d
To help investigate performance regressions, an option is added to
'adb shell cmd package compile' to compile all packages with the
given mode.
Bug: 27391290
Change-Id: I70a3a518e08b54535bb34f13f0cedda3a1f7085f
This happens because suggestions are gathered based on the
selection after setting the cursor position to the middle
of the user selected range, which means 0-width selection
at that position. As a result, SuggestionsPopup was not
shown when any suggestion spans don't overlap middle point
of the selection.
Bug: 20709442
Change-Id: I3e1cb570f451b4ab14cf36f7da23dc2bd22f4ac8
This ports my previous CL for InputMethodManagerService [1] to
TextServicesManagerService (TSMS).
In order to make TSMS encryption-aware, we are going to introduce a new
state where any read/write access to Secure Settings from TSMS is
virtualized so that we can temporarily enable only encryption-aware
spell checkers until the user unlocks the device then revert
any changes made before the device enters into an unlocked state.
See my previous commit message [1] for details.
This is still a preparation code. Behavior change is not intended yet
in this CL.
[1]: I0f79243e5cc1556764da37fa38078e075a27d42b
8752367042
Bug: 27456430
Change-Id: I97a1e2f75bdecb0aa88fb35dfe56732c08fcbbd5
setHasTransientState(true) and setHasTransientState(false) have to
be coupled, but they were not always coupled in TextView. e.g. when
we fire PROCESS_TEXT intent.
With this CL, TextView calls setHasTransientState() always when
selection is created or cleared to make sure 2 setHasTransientState
calls are always coupled.
Bug: 27409041
Change-Id: Ib454b0fbbc2c2f8d19818f154f415c4a5d7e2d7e
- Documented what TvInputInfo.getTunerCount returns if the input is not
of TYPE_TUNER.
- Documented what all getters/setters in TvTrackInfo throw if not called
on proper types.
Bug: 27531254
Change-Id: I32d83ce888507ec29cda8dce74871a3d55783766
