Notification messages are posted through a handler with a main thread.
When a caller of TIS.notifyXXX runs also in a main thread, the notification
is delivered after the method including the caller is finished.
So we added runOnMainThread and made notification messages sent through
runOnMainThread.
Change-Id: Ieb2c5c04ff031e42a532acfc45e0174563265c6b
This will listen properly for the connection of the VPNs. It will
also listen for disconnects, but may catch them slightly delayed
as the connection may be held on to.
Bug: 16153201
Bug: 17164598
Change-Id: I0c522f7fb4007c3376153c4b2a0345391e0b724f
Also fixed multiple bugs regarding focusability, where
some elements were focusable even though invisible.
The buttons, QS-tiles, QS-detail buttons, QS Header
icons and other elements now have the correct focusability
state.
The rect indicating accessibility focus is now also
correct for dual label tiles, instead of just the whole
button.
Also fixes an ordering issue where notifications were above
the camera circle when launching.
In addition the focus order of the notifications now work
correctly.
Bug: 15569922
Bug: 15682123
Bug: 17159249
Bug: 15690386
Change-Id: Ie9f7ae73397b41ce2e9a4060699301fdef3a0d01
Ongoing notifications from chrome and drive
don't have content in line 3 so profile badge
wasn't shown.
Add profile badge to large notifications which
hide line 3.
Bug: 16366324
Change-Id: Ib4f1e888674743aa8ef93b7eaceae72602d8df4d
This CL removes CursorAnchorInfoRequest and related stuff
in favor of InputConnection.requestUpdateCursorAnchorInfo,
which is more easy to understand. This CL also deprecates
InputMethodManager#updateCursor and related stuff.
Rationale:
1. The spec of #updateCursor says that it provides the cursor
position in local coordinates, while the input method
requires it in the screen coordinates.
2. #updateCursor has never been enabled in AOSP, because
InputMethodManager#isWatchingCursor always returned false.
3. There has been no way to let
InputMethodManager#isWatchingCursor return true.
4. In L, InputMethodManager#updateCursorAnchorInfo is
introduced to address all the issues above.
Given that we no longer need to support #updateCursor,
CursorAnchorInfoRequest is overkill when we need to convey
just a couple of parameters.
BUG: 17185263
BUG: 17182367
Change-Id: I4a577bfd02b37b9e56c80b8b41bb25afa95dd8ef
This change introduces a new helper class, HdmiLogger,
which prevents spammy log for same error message.
Bug: 17179667
Change-Id: Ia55808408e0a92b0370cd627361f80754b2f1018
1. Add sendScratchpadCommand to IHdmiControlService interface,
which is used to send scratchpad command.
2. Add IHdmiMhlScratchpadCommandListener to handle incoming
MHL scratchpad command.
Bug: 17146522
Change-Id: I8e8e743dc08a18c80867be470997ce79d3292c15
The action taken is dependent on whether the device is in an
interactive state, allowing for interactions to work even when the
device isn't actively being used
Bug: 16292420
Change-Id: I897f4383e7e4766c0bcb6246b41514b46e03a9ac
Window decor action bars already inherit window title changes if no
explicit action bar title has been set but from an Activity's
perspective setting the activity title is a stronger signal. This is
especially relevant when the activity's action bar has been provided
by the application in the form of a Toolbar.
Bug 17138048
Change-Id: Ibf042cab6bbda3dc29590c09d1a0910b6ba78870
