Factor out the "should we be hiding sensitive data"
predicate so we get it right everywhere.
Show visibility stuff in Notification.toString().
Bug: 16307122
Change-Id: Ifd16d073c4595add2ac3582ffc0d0179e55246e5
This makes it easier to identify them later (e.g., for filtering).
The developer can always specify a different category if preferred.
Also fixed some javadoc related to setMediaSession()
Change-Id: I5f28514758218ff66fdbaa9fd37ccb19f12d4852
This change adds a way to get a dummy channel for starting pass-through
TV inputs which don't have real channels in TvProvider.
Bug: 15496325
Change-Id: I7a6b99964319f12a0f8692b4e307e03480119a69
Labels and icons will be extracted from URI in the future.
To acheive it, we need Context rather than PackageManager.
Bug: 16166859
Change-Id: I20f0506fba5876a6cf21b70e44bb3a2265f723d7
The WebView has zoomIn/zoomOut APIs which zoom in/out by a fixed
amount. This adds a more flexible API.
BUG: 13399510
Change-Id: Ia505048d5b1c48f9a3ff1c4ce7129ed2f55804f8
The scope of this change is to provide a skeleton code for supporting
multiple TV input per service.
Bug: 16138420
Change-Id: Ic51355902d5e0424b8fc8a75c495d4781a7ed744
Leanback theme uses a legacy layout with a done button, but
apps won't necessarily have target apilevel L.
Change-Id: Ib38b08df1fe07bd8fb4e64e93633ce0b7eb12567
Restore visibility logic (for mirrored view) and remove a bad
optimization from the clipping calculation.
Bug:16337935
Change-Id: I7eb82ef6c87f30da9d8b70136e05dab3abdbdead
This is going to be needed by applications to get information about the
inputs that are just added thus not included in the previously retrieved
input list.
Bug: 16166859, Bug: 15838097
Change-Id: Icecd03fcea208a0c4d41caab1eec64e574f40877
A recent change mandated that we should provide "input ID" instead of
ComponentName when building URIs for channels/programs while there is no
direct way to get one to use with. This CL added a method to build an ID
from a ComponentName.
Change-Id: Ia7f868cf241bb44ca0d4f689dc15326ce6944468
- Add more spacing at the top
- Update window animations to fades
- Improve style for alarm warnings
Bug:16200897
Change-Id: I7a64e235eff1f9a77fc697a98a4440bc69043386
Symptom: If app applies animation to enlarge a bitmap, there will be an residual
line on the screen
Root Cause: On platform which has Tile Rendering implementation (ex. Qualcomm
CPU), startTiling() call will restrict the framebuffer region which
GPU can affect. So the expansion of clear region by 1 will not take
effect if startTiling region is not expanded.
Solution: Expand the startTiling region by 1, too.
Reproduce steps: Apply animation to enlarge (and then shrink) a bitmap icon.
Cherry-pick of 20adb6ce4d52b15472e7e5ee953e06cc349a827c from AOSP
Change-Id: I163b898b87b74d221dc4210b7fa657aa93c82c19
