Add system trace events for several interesting points during the
loading of the WebView APK so we can measure how much each part
contributes to startup time.
Bug: 16870075
Change-Id: Iadfd1881faea0377fa01313dddabb1d030962c5f
- Fixed issue with focus going to send front most task when coming from Home
- Adding shortcut to dismiss a task
- Refactoring code to get secondary overlay and affiliation color
- Throttling alt-tab key presses
- Fixing issue with slivers of the task thumbnail being visible for affiliated tasks
Change-Id: Iaafe408318646a423fd58b51bbe93dbe0f2eed99
Changed it from /data/system/tv/{userId} to the directory obtained from
Environment.getUserSystemDirectory(userId).
Bug: 17018435
Change-Id: Ib9704a974c4397149ca4b50670cf11346b818de3
When accessibility is on, still use just recents.
While here fix strings to be less wrong. Still need finalization.
Bug: 16649417
Change-Id: I94debe9471d5132f1f662543cc98cbde638c758d
This addresses b/16486549.
This change updates public documentation to specify the behavior of
LeadingMarginSpan2s. This change specifies what happens when a
LeadingMarginSpan2 is combined with other LeadingMarginSpans. This
behavior was not previously documented.
LeadingMarginSpan2s specify the number of lines used for the leading
margin. When laying out and rendering, for all LeadingMarginSpans, the
first line margin is applied for the number of lines specified by the
LeadingMarginSpan2.
Previously, this behavior was slightly buggy -- the LeadingMarginSpan2
affected all LeadingMarginSpans when laying out text, but not when
rendering.
This change is designed to cause the least amount of breakage in
existing code while achieving consistency with the way
LeadingMarginSpan2 is handled in layout and drawing.
For the most common use of LeadingMarginSpan2 -- getting a multi-line
first margin in the first paragraph of text in a layout -- this should
cause no change in behavior. For any other uses, the old (buggy)
implementation most likely did not exhibit correct behavior to begin
with, so developers were most likely not relying on that functionality.
Change-Id: I6f69df09c0130e703458e65bf3eaac4a905df56e
To be able to pass information from dialer to incallui,
telecomm.Call needs to hold extra information. Add this extra bundle to
the intent.
Bug: 15284651
Change-Id: Ie462c35ece41647c7104c657cc1de947ff284729
This removes the fake stream from AudioService and cleans up
references to it. Also removes isLocalOrRemoteMusicActive.
bug:15884752
Change-Id: I1c2b57a2f8ba80061313737f254463f4c80ce8c3
OverlayViewGroup clipChildren=true, so that RenderNode
of GhostView will be forced clip its content to its bounds.
Because GhostView is transformed to a different location
other than (0,0), the content left/up to the bounds
is clipped out.
Introduce another clipChildren=false view between
OverlayViewGroup and GhostView.
b/16982904
Change-Id: Ia11926c78e19bffe80c3d4584a59b83b2fbee6df
