- 10 May, 2012 1 commit
-
-
Wink Saville authored
Change-Id: Ie46bba7e0ef7737a865f7efadbf963c2d14e488f
-
- 07 May, 2012 19 commits
-
-
John Reck authored
-
Daniel Sandler authored
-
Daniel Sandler authored
-
Daniel Sandler authored
-
satok authored
Change-Id: I7803d92de8f4ea399cef5c2d1ddf5396d59ef2cf
-
satok authored
Merge "DO NOT MERGE. Backport If36b8a69e7fa22e837c99d Fix the issue that the spell check doesn't start when the user changes the cursor position by touch" into jb-dev
-
satok authored
DO NOT MERGE. Backport If36b8a69e7fa22e837c99d Fix the issue that the spell check doesn't start when the user changes the cursor position by touch Change-Id: I1535eae23efc42660b9d1e6dbfba6c800b0302b2
-
Adam Powell authored
-
Adam Powell authored
Change-Id: I2c982c0b7c722ca7cad46cc23ac8d161bee3a1ff
-
Romain Guy authored
-
Adam Powell authored
-
Adam Powell authored
Bug 6449422 Overzealous action views should not be able to cause action bars to take up a huge amount of space. Fixed text alignment on action buttons Change-Id: Ic28d6dacdb6933c63b323f5ed6a6cab5d3726938
-
Dianne Hackborn authored
-
Dianne Hackborn authored
Change-Id: I29a270c7499a96718b3d2cad8c2b89783a5607f8
-
Adam Powell authored
-
Adam Powell authored
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
-
Dianne Hackborn authored
Merge "Finish up issue #6249094: Display permissions based on relevance to private data" into jb-dev
-
Dianne Hackborn authored
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
-
Svetoslav Ganov authored
-
- 06 May, 2012 18 commits
-
-
Romain Guy authored
Change-Id: If609c9ffbea800ff6409b0096a82f0b899f29343
-
Michael Jurka authored
-
Craig Mautner authored
-
Fred Quintana authored
Merge "fix expedited syncs. there were times when an expedited sync wouldn't correctly preempt non-expedited syncs" into jb-dev
-
Svetoslav Ganov authored
-
Svetoslav Ganov authored
-
Craig Mautner authored
BlackSurface transparency was tracking animation transparency causing background images to peek around the corners. Fixes bug 4998851. Change-Id: I48ac7bf5d0cc560b655c9f12faccda411985cbad
-
Romain Guy authored
-
Romain Guy authored
Bug #6436642 Change-Id: I906b9c68225683f97b9c97c153a1132cf9ac6509
-
Romain Guy authored
-
Fred Quintana authored
correctly preempt non-expedited syncs Change-Id: Ia88ce6504c06d7c8e50e40362e8bf2b85bd0934b
-
Romain Guy authored
-
Svetoslav Ganov authored
1. The dismiss implementaton in Dialog was posting a message on the main thread to perform the real dismiss work. The goal of this was to allow calling dismiss() from multiple threads. The side effect of this is that when dialog fragment is dismissed the dialog is not dimissed until the current loop on the main thread is completed. However, during rotation of the screen the current activity has to be restarted, hence all fragments whould be removed. In the destruction process the dialog grament requests from the dialog to dismiss but since this is asynchromous, the code in ActivityThread#handleDestroyActivity detects a leaking window since the dialog window is still not removed and removes that window. Now when the dialog removal message is processed on the next loop we get an exception that the window has already been removed. Now if Dialog#dismiss() is called from the main thread the call goes right though otherwise a message is posted. bug:5911682 Change-Id: I449d6dd75a84c0ff29ea13dac7d163219cc38341
-
Romain Guy authored
These allocations were frequently triggered by the home screen. This change removes dozens of allocations during page scrolls on home. Change-Id: I7289efa28ecf5bd62459042b10062aa9cf0432dd
-
Dianne Hackborn authored
The action bar now maintains separate states for the things that can impact its visibility (calls from the app, action mode, system UI) so that the changes in these won't incorrectly mix together. Also added a hack to force the status bar to be shown when showing the action bar for an action mode, when the UI is in a state where the action bar would be shown with a gap above where the status bar is. Change-Id: Ib0950a7f585c5d2c9e77d11b237ba6e150f15ebd
-
Pin Ting authored
-
Svetoslav Ganov authored
1. When performing the click and long click actions the code in View was not returning the resilt of the called method. bug:6426849 Change-Id: I0cf396a8373f622948ed436ce09f8d1dcf246acd
-
Svetoslav Ganov authored
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
-
- 05 May, 2012 2 commits
-
-
Dianne Hackborn authored
-
Dianne Hackborn authored
Start calling Surface.setActiveRect(). Change-Id: I94197059c971c6ab7820e615ea8f285482b86c75
-