Compile ForwardingOs fdsan-using functions. Follow-up to commit
5625660c650a0923d4c7f020f2eb7eef7d5962d4.
The function is relatively hot now, and importantly part of the
'abort' stack for fdsan issues.
Test: m
Change-Id: Iad9883b8fd85fc362bb3252739e3e3acc45373af
Implement readback from Surface, TextureView and HW Bitmap
for Vulkan pipeline by wrapping the graphics buffer in an SkImage.
Refactor both Vulkan and GL readback to use common code.
TextureView readback is moved from IRenderPipeline interface to
Readback class. Refactor all 3 readback flows to use common
implementation.
Test: Passed all view, uirendering and graphics CTS tests with GL
Test: Passed many CTS test with Vulkan, that require readback
Bug: 113673613
Change-Id: Ifbfd8170a5401f87a709b4b1b9fa058e8e11768d
* changes:
Revert "Add null check for vrManager"
Revert "Add null check for vrManager"
Revert "Add null check for vrManager"
Revert "Do not start VrManagerService if VR is not supported"
QSSecurityFooter refreshes its state and listens regardless of the
expansion of QSPanel. It now knows its size before expansion animation
starts and is reported properly.
Change-Id: I66e29b4b14c2fbc663704255649515f68f41bd48
Fixes: 80219694
Test: Manual & runtest
Moved out of change I9cd4c819297ea34ab59c3cf9cfd11136987acc22 because
this part needs the SE Policy to be updated first.
Test: manual
Change-Id: Id6efed69394a34c41a7e6f9b73cb54dac8b5aeb5
There was a small mistake in my previous CL [1].
What updateStatusIcon() takes is a resource ID for Drawable, not ID
for an integer value.
These @*Res annotations are still just hints for IDE and lint tools.
They are actually all @Retention(SOURCE) hence this kind of mistake
has no impact at run time actually.
This CL also adds the right annotation for corresponding methods in
InputMethodManager and InputMethodManagerService.
[1]: I995c4b922f91b94438c1292392b2c3030598594f
c7ca36845edb9937f7f9d09d50505ade3c8abf9f
Bug: 114418674
Test: atest CtsInputMethodTestCases CtsInputMethodServiceHostTestCases
Change-Id: Id7fd610c07643c79b8ec03efbda24b3dc0686844
This is one further step towards deprecating 8 IME APIs that were
accidentally defined InputMethodManager (IMM) instead of
InputMethodService (IMS).
With this CL, API calls to those 8 deprecated ones in IMM will be
forwarded to IMS so that we can completely remove corresponding IPC
methods from IInputMethodManager.aidl. This guarantees that processes
that have no InputMethodService running there become unable to access
IPC methods behind such IME APIs that are intended to be used only
from IMEs.
One tricky thing is that the following 4 public APIs have been allowed
to processes that have WRITE_SECURE_SETTINGS permission, even if such
a process does not have active InputMethodService.
* InputMethodManager.setInputMethod
* InputMethodManager.setInputMethodAndSubtype
* InputMethodManager.switchToLastInputMethod
* InputMethodManager.switchToNextInputMethod
In general, user mode apps should not have WRITE_SECURE_SETTINGS
permission. Thus it might be not that difficult for us to simply
deprecate such a special rule. Bug 114488811 is tracking that effort.
For now, this CL preserves the existing behavior when a null IME token
is specified to those 4 APIs.
Bug: 114418674
Test: atest CtsInputMethodTestCases CtsInputMethodServiceHostTestCases
Change-Id: If762714b2003fa6477e1318110f63e13968c1d7e
