Change Ie817b396 removed the layout transition from the main
status bar, fixing a number of weird bugs caused by the
translations on CHANGE_APPEARING and CHANGE_DISAPPEARING.
This change restores the layout transitions, but only the
alpha fade on APPEARING and DISAPPEARING. Doing this should
bring back the useful part of the status bar animations
(i.e. things fading in & out) without the buggy part (things
sliding around to make room for the things fading in & out).
Additionally, these fade-only layout transitions are now
properly applied to the clock/notification area (when
bringing up the notifications panel) and the icons within
the navigation cluster (so the legacy MENU key will fade
in).
Bug: 3503960
Bug: 3489129
Change-Id: I1ea433c41f2f930342ae2486505b0fee19709f9c
They're causing a number of unpleasant effects (see bug list
below). The root cause is a limitation of layout transitions
(http://b/3503912) that we don't have time to fix right now.
Bug: 3427414
Bug: 3489129
Bug: 3501979
Change-Id: Ie817b396f89847b105ef7b7c7007c7a1e64b8469
Allows builds to specific MINIMAL_NEWWAVE_LABS=true to reduce the number
of newwavelabs/*.ogg that are included to one for ringtones, one for notifications.
This fixes the passion-userdebug + EMMA_INSTRUMENT=true, when
MINIMAL_NEWWAVELABS=true is also specified.
Change-Id: I310e64e770c9b36af6bd01326d8606e46e34df79
Fixed in this change:
- ListView overscroll drawable was partially off screen.
- Selected item was not fading when unselected
Change-Id: Ifba86eede591c4d4f984a7966b933a77799f66f9
...at android.app.DialogFragment.dismissInternal(DialogFragment.java:264)
Don't allow a DialogFragment to be dismissed twice.
Change-Id: Id2e9e3be1046b0d7862492c57c36001d8fd44a69
Unable to destroy activity {com.android.browser/com.android.browser.BrowserActivity}:
java.lang.NullPointerException at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:2809)
Add a bunch of guards to not call on to the window callback after the
window is destroyed.
Change-Id: I66ca0705f421bafdfe953d03654c8f78d9e68249
This fixes a crash caused by clicking in the footer view
by making it not selectable.
Also, don't hide home and recents button, per request from UX.
Change-Id: Ie3348c8f5d699841aa76fd7abe889b2b329c7b0b
Well, I'm not sure it is right for onCreateDialog() to return a null
dialog, but if it does, let's not crash here.
Change-Id: I5ff49b9b3c326d9005f70a01435c01bfc7307343
This is due to the window doing a relayout after its activity is
stopped, at which point it may need to interact with the adapter
to load data.
The fix here is to tell ViewRoot about an activity being stopped
and, if in this state, hold off on doing any new measurements and
layouts of the hierarchy until it is no longer stopped.
In this case the relayout was happening due to the cursor
being deactivated, with causes the adapter to invalidate
its data. Because this is now in a dialog window, this
allows the window to actually be resized smaller (unlike when
in a full screen activity), and boom.
Change-Id: I26442b4679819b4a4e6bc56289afd3445526750b
