Note that this does not convert any widgets what were bound when
a different global search app was installed. Thus Froyo -> Froyo
upgrades without userdata wipe will see "Problem loading widget".
Workaround: Remove the search widget and add a new one.
Change-Id: I2bcd211c10bbaba66f5f3f82b6785396d957aa25
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.
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.
Before, Launcher2 sent an intent to
com.android.settings/com.android.settings.LauncherAppWidgetBinder
to bind any converted appwidgets. That doesn't seem to work anymore,
and is not how non-converted widgets are bound. Changing to
binding the widgets directly fixes a problem where the search
widget was not bound after an upgrade from Eclair to Master.
The search widget conversion problem was introduced in
Change I85d64defe155c0cad97fafef6a3db62c6cab504a
where I got rid of the built-in search widget.
This patch may break conversion of legacy built-in
clock and photo widgets, but I believe that was already broken
because of the non-functional widget binding mechanism.
Bug: http://b/2322160
Merge commit 'bdc5a45de6708c241a414805bdec65428c9ddd88' into eclair-mr2-plus-aosp
* commit 'bdc5a45de6708c241a414805bdec65428c9ddd88':
Still trying to fix 2320348 - Launcher2 crashed: AIOOBE at com.android.launcher2.AllAppsView$RolloRS.removeApp
Merge commit '3ecbd81f99d2005172f431d2bf207b698154fe29' into eclair-mr2
* commit '3ecbd81f99d2005172f431d2bf207b698154fe29':
Still trying to fix 2320348 - Launcher2 crashed: AIOOBE at com.android.launcher2.AllAppsView$RolloRS.removeApp
Merge commit '6801766784c752609fc4a63db9038e5f64db6453'
* commit '6801766784c752609fc4a63db9038e5f64db6453':
Launcher2 - This might fix the missing app problem and the crash in removeApp.
Merge commit '15237db04c12c3bf193211a878aa69ea91e2052a' into eclair-mr2-plus-aosp
* commit '15237db04c12c3bf193211a878aa69ea91e2052a':
Launcher2 - This might fix the missing app problem and the crash in removeApp.
Merge commit '8cf34293dc2f078bf023ac77d007f5182f9b9357' into eclair-mr2
* commit '8cf34293dc2f078bf023ac77d007f5182f9b9357':
Launcher2 - This might fix the missing app problem and the crash in removeApp.
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.
Merge commit 'fd379524674a3af9d00b7df13bb2f3ed44fd4f90'
* commit 'fd379524674a3af9d00b7df13bb2f3ed44fd4f90':
fix 2315821 and 2315729 - problems caused because the apps list could become
Jason Sams
Joe Onorato
Bjorn Bringert
Romain Guy
The Android Open Source Project
Eric Fischer
Jean-Baptiste Queru
Tom Taylor
Android (Google) Code Review
android-build SharedAccount
The Android Automerger