This is a follow up CL for 35d3f37bd51268cc99d81a3f537ac364d178e851 [1],
which changed some method signatures of IInputMethodManager.
[1]: Ia1fe120af7d71495c5f3a4fc0ec6390efb8240ca
We need to update BridgeIInputMethodManager.java every time when we
change IInputMethodManager.
Bug: 25373872
Change-Id: I126dc4234f921039a9d29010ea411a0a7d2ef6c6
Two changes:
1. Allow to specify which user the call is inserted to
2. Store addForAllUsers in call, so that we do not need to copy every call
Change-Id: I8fc9e8e4f2e0bdb0049ca2914fdf8908f62b3eb2
This defers looking up the meta-data from the install call to when the
rest of the config is lazily initialized.
Change-Id: I008a86f885e158ebe06a2bacdc358cd217635d05
- Now, all task views will be bounded by the stack rect, and the
thumbnail bitmaps will be scaled accordingly to fit either by width
(when stacked) or to the view rect (when freeform)
- Fixing issue where the history button was not offset in freeform
- Tweaking thumbnail sizes of fullscreen screenshots
- Still requires changes to fix clipping to the correct aspect ratio in
freeform.
Change-Id: I678b87c2f06947d32f3bb7c60a35f28eb36b5a68
- Adding a notion of session to the stack. If the history is enabled,
the stack will now be constrained to show either tasks that were last
active in a window of time, or a minimum number of tasks.
- Giving the history button the full space above the stack so that it
looks more balanced.
Change-Id: If7b647349e8bb164ae86fd6dba3f7e974257eb5b
- Initial changes to show a history view within Overview (behind tuner
flag)
- Restoring the task view dim in the stack
Change-Id: I0503d11768736c86f3145942404391dfacd0ddd6
am: dd52b3db36
* commit 'dd52b3db3678dc0840b82f5406d445cea59d2b59':
ssl: make DistinguishedNameParser a package-private class in org.apache.http.conn.ssl
- Also make sure DPMS.mOwners is always guarded with DPMS.this.
(and remove synchronization from Owners.)
Bug 25796840
Change-Id: I83f7b78e7b437d9c2a2b1d6e714346cd15f95330
As a preparation to fix Bug 25373872, this CL introduces an additional
int parameter into the following two methods
- IInputMethodManager.startInput()
- IInputMethodManager.windowGainedFocus()
so that IMMS can know why IMM needs to start input. Currently the
"startInputReason" parameter is used only for debug message only when
the OS is rebuilt with flipping IMMS#DEBUG to true. Basically this
should have no impact in production builds except for a tiny overhead
of having one int parameter in some internal IPC calls.
Note that since 7663d80f6b6fd6ca7a736c3802013a09c0abdeb9 [1] basically
IMMS#windowGainedFocus() has been a superset of IMMS#startInput().
Hence we should pass to "startInputReason" parameter to
IMMS#windowGainedFocus() as well as IMMS#startInput().
[1]: Icb58bef75ef4bf9979f3e2ba88cea20db2e2c3fb
Bug: 25373872
Change-Id: Ia1fe120af7d71495c5f3a4fc0ec6390efb8240ca
The visibility of a window might be toggled to true even when it doesn't
have a surface, which is a case for windows under the lock screen. We
can't blindly create surfaces in that case, but only do it for the
windows that destroy their surfaces when they are hidden.
Bug: 25879215
Change-Id: I6cf2c6810ce02fba0d2207a56de9924c0270dfeb
Make the following broadcasts protected:
android.intent.action.PRE_BOOT_COMPLETED
android.intent.action.USER_INITIALIZE
Bug: 25022002
Change-Id: Ic36e29c51b930e4d7367688ab837c6a40d74ec23
Needed by AbstractVerifier, needed by framework/base
DistinguishedNameParser taken from libcore, commit a5c16db453098d7ab945edd379a
This commit was adapted from commit 50dc0c27ff00bfd82fb9cce1c86312efa550170f
Not cherrypicking from dev branch as the original CL to do it went wrong
and would need to cherrypick more changes
Change-Id: I1c282b731c778a79775d9d54b7b7d7223d84397d
This allows us to build a special jar with methods exposed strictly
for CTS. An @TestApi should not be a public API or a system
API.
Bug: 25608286
Change-Id: Ifbc64bb6958d2deec5b9cf0b944acfd068f0f051
