This change makes sure that we don't update the hardware for the
notification layer when we collapse or expand the panel. It does so
by starting the fading when the panel is more collapsed.
Bug: 17287256
Change-Id: I35dc35494d71d816b7e6c5821b769847aaa183b0
It turns out that the semantics of the return value are confusing
and so we decided to not return a result from this method at all.
The developer can call canZoomIn/canZoomOut to determine whether
the WebView is at the zoom limit, so there is no loss of
functionality.
BUG: 17374808
Change-Id: I4dfde71d5ac4a3f91c8755b257411aad06a1b1f6
Not really needed anymore and adds a lot of overdraw. Let's get rid
of it.
Bug: 17287256
Bug: 17346296
Change-Id: I319596f7059b6ed0d3d7a578d3c786921001f4b5
This is because we did not receive a layout request even though
the notification was updated.
Bug: 17357688
Change-Id: Ie6295d07f4c00ec014b17671ad646261c4bb7e0f
Problem:
1. ProviderTestCase2 passes a null as a ProviderInfo to the ContentProvider
2. mAuthority and mAuthorities will be null during the test
3. ContentProvider.matchesOurAuthorities will throw an NPE.
Fix:
Supply a ProviderInfo with authority.
Example bug:
b/17379295
Change-Id: Ia533313c0994727ef81f337a4e31a57ae7ec3c15
Bug: 16637957
- In Camera1 API, front facing camera preview is always mirrored across
the vertical axis. Undo this flip in the legacy mode Camera2 API
sampling operation when copying from the texture drawn to with the
Camera1 API preview buffers.
Change-Id: Ib8ae4fa97f4ad62a3e55ae7da7d474a8655e747d
We need to allow for event dispatching in non-interactive states so
that we can enable a richer set of interactions when a device is
dozing (i.e. is in a low power state with an Always-on-Display).
Bug: 17167296
Change-Id: I8ae0f544a8106cb91ff38c2309b8b57cbe2f2c72
Pass through the menu mode change events and make sure Activities get
prepare/open/close events properly.
Bug 17326424
Change-Id: I0ac2f56e4d0054ef01720b2ff1c41ded053750c7
The remote print spooler can only be accessed off the main thread
by design as calls into it may block for a short amoun of time since
the frist call into the spooler may have to wait for the system to
bind to the spooler service. A recent change introduced a regression
where the user state changes are now dispatched on the main thread.
This change schedules the user change handling to a background handler
thread.
bug:17396682
Change-Id: I059be8f31ba41122cb2967d8afadd19e6b5a08e5
