Merge commit '75fd1ec46da7708bd46183da7999ec891d63140d' into eclair-plus-aosp
* commit '75fd1ec46da7708bd46183da7999ec891d63140d':
DO NOT MERGE - Use the froyo launcher2 in mr3, except for a few unbundling things that can't be merged back.
Merge commit 'b8fc9e7df69db4b1647ef780f5620836c86f70ea' into eclair-plus-aosp
* commit 'b8fc9e7df69db4b1647ef780f5620836c86f70ea':
Launcher changes to handle UTS test mode.
When in UTS test mode keys received need to be handled
by the Phone application or Contacts application to
operate properly in the test mode. When not in test mode
the search widget will handle the keys as it was before
this change.
The UTS test mode is enabled when presist.sys.uts-test-mode is 1.
bug: 2402366
Change-Id: I58e68830f9ce6905e189ecba1c04b1076799a0a0
Signed-off-by: Wink Saville <wink@google.com>
Merge commit '52ba5b08f25e031a6f717551c75abf630b92ed8b' into eclair-plus-aosp
* commit '52ba5b08f25e031a6f717551c75abf630b92ed8b':
DO NOT MERGE. Update for new RS library with ES 2.0 support.
Merge commit '999b6a5ecb36405d3697f9fb11df9a5bb0273e73' into eclair-plus-aosp
* commit '999b6a5ecb36405d3697f9fb11df9a5bb0273e73':
android-2.1_r1 snapshot
Keep banging on the launcher locks up bug. This moves the
Fix 2257802 - Screen unresponsive when you get a call while moving the shortcuts or widgets on home screen
Fix bug 2258128 - homescreen on Passion unresponsive while still not leaking the contexts.
It looks like the evil hack in 14f122bf84 to make the workspace
not animate didn't completely work. The key to reproducing this bug is to make sure the
activity is destroyed and to have last gone to an app from a screen other than the center
screen, because that causes it to get reloaded from the icicle, which makes the timing
more amenable to missing the animation, because the view isn't attached yet.
This marks the apps list as dirty by default. Usually, because of how long
it takes the loader thread to run, the apps list comes in after the surface
has been initialized. However, if the surface isn't around yet when setApps
is called, then setApps won't set mRollo.mAppsDirty because mRollo is null.
The extra null check is necessary for the normal case when mAllAppsList isn't
ready yet when the surface comes in.
Joe Onorato
Wink Saville
Jason Sams
The Android Open Source Project
android-build SharedAccount
The Android Automerger
Eric Fischer
Android (Google) Code Review
Romain Guy
Daniel Sandler