Bug 5731093
Replace TextView by EditText to make it cleaner.
Had to force the text color, although the TextAppearance should
handle it. Maybe something is wrong with the theme.
Also added a hint for consistency.
Change-Id: Icd7170a0ef3757d0313e0799873f2dd375b02f2f
This fixes several layout issues on phones and tablets with MultiWaveView.
It adds a new background scrim to be shown behind the MultiWaveView
on the navigation bar.
MultiWaveView is updated to handle gravity constraints which makes layouts
much more flexible across devices.
Change-Id: I64068f4eaa81ef6c464247049117d53432fcacbd
Bug 6428812
Change ResolverActivity to use a grid rather than a list, and present
buttons for "Use Always" and "Just Once". Use large launcher icons
when appropriate.
Change-Id: I177360a727cbc4b401ffbcea83d1b3dac1de5744
Added bitmaps for permission group icons. We had to pick either
icons for a dark or light background, and it had to be light for
settings, so the installer theme has gone back to dark.
Tweaked the permission groups to match the icons.
Redid the group priorities to make them correct (they were written
with higher priorities being less important).
Fixed bug where priority was not being used for system apps.
Change-Id: Ia3d3f0c1614a11b4cfd11682ce9e6c9f87d75c06
1. While a default target is very convenient, having two targets for the
widget on a phone takes too much space and the apps do not have room
to add other essential affordances to the action bar. Making the default
activity show only of the screen is large enough - the action bar
accommodates at least four targets i.e. 500dip.
2. Fixed a bug where changing the backing model of an ActivityChooserView
when the view is not shown did not remove the observer for the old
model, hence the View can get into a state where it responds to changes
of two models while presenting only one. Also in such a case the view
would leak since the singleton model will keep a handle to it.
3. Updated the documentation of share action provider to explain how a
a developer can change the backing history file and refresh the UI
based on the historical data in that file.
bug:6447692
Change-Id: Id5c9e54cd5df322ded8574ba028cb680e628243b
* commit 'cdea2a3e654543ecdf27528d505787770c1b5feb':
Add an alternate title that can be used in the overflow of a InboxStyle. Always hide contentText for BigTextStyle and InboxStyle. Style cannot be used without specialization, it should be abstract.
Always hide contentText for BigTextStyle and InboxStyle.
Style cannot be used without specialization, it should be abstract.
Bug: 6428978
Bug: 6274137
Bug: 6317471
Change-Id: I21531a94494f891a058a477805b177e736b921cf
This lets us avoid a Binder roundtrip to the system process during
volume changes. Previously volume change would be staged at key-down,
then applied at key up in tandem with playback of the sonic feedback
about volume key presses. The reason for this two-stage handling was
to defer playback of the sound [at the target volume] while the volume
key was being held for repeat.
On some devices volume is always sent as key down/up pairs rather than
down-repeat-up sequences. On these devices it is more efficient to
apply the new volume immediately during down handling, and have the
up handling be a no-op. This CL adds a configuration resource item
selecting this new fast path.
Bug 6433943
Change-Id: Icffa56e958243b841d514e2fe4609ba3a7b20f14
