-> workaround for platform issue related to this resource, but also
a decent code cleanup
issue 20006693
Change-Id: Iea3a2fb14be5ed78d882ddf9d970b12d177f4249
It will help reduce memory footprint of Launcher, when in background.
It is required to help deallocate images, when Google Now Launcher
goes into the background. See cl/83222937/ .
Plan after this CL:
- Generate drop CL with launcher3_drop.sh. Add empty metods to
make code compile.
- Sync the cl/83222937 and hide the code behind the feature flag.
It was previously submitted in ag/628070 and reverted in ag/630423
due to GSA release schedule.
Change-Id: I56eee618b86d518d0afc362b6cf44c3bbec1f19c
-> AppWidgetManagerCompatVL uses an IntentSender to launch the widget
config activity (to handle the case of cross profile config activities)
-> Launcher was not overriding this method, and so not capturing the fact
that we are waiting for a result.
issue 19723510
Change-Id: If5751e6d23d31c9f7b3b85f9464a93f935487cec
By not storing them in a HashMap keyed against ComponentName (which is
almost guaranteed to conflict with other widgets when managed profiles
are in play).
Bug: 19444068
Change-Id: I6ffce78e8aaf265196239670404cbdaff9fa09be
It will help reduce memory footprint of Launcher, when in background.
It is required to help deallocate images, when Google Now Launcher
goes into the background. See cl/83222937/ .
Change-Id: I6d3d4d1f0457c67abcad3ba4516c87abcf666b05
> Adding 'Remove' option to workspace items
> Adding 'Add to workspace' to all apps and widget list items, which
adds the item to the first available space, giving preference to
the current workspace screen
> Adding 'App info' and 'Uninstall' options to appropriate items
Bug: 18482913
Change-Id: Ifab7423af2d9ba502b5a2771b37bb5436b3df937
-> This change provides integration for widgets provided by
the launcher package which can run arbitrary code.
Change-Id: I6052da5c4afed7ee72e3b44d045b9c46f2d84c42
1) During migration, if launcher2 has deleted user data,
migration oes not happen
2) If Launcher3 does not has bind widget permission,
QSB would be null.
Bug: 18388507
Change-Id: Ief81f6f77ce154e7b3ecd4b77caf24239401e738
> Removing all logic related to search and voice overlays
from Launcher3
> Using the widget provided by global search provider on the
homescreen
> Removing VoiceButtonProxy, as it is not being used anymore
Change-Id: Ie8b09b44f7213c8fa11bce685914442e4884295d
-> Always dispose of widget page views when leaving the activity.
These pages hold onto many bitmaps.
-> Clear database cache when leaving the activity.
Bug: 17967108
Change-Id: I10ebaaed14e7cd86f09a9afcabd73043705f21b8
> Adding DeviceProfile information in the backup
> Removing SharedPreference backup
> Adding helper methods to abort backup in the middle
> Comparing keys against the backup journal during restore
to avoid restoring corrupt/lost entries
> Old backups are still compatible, but lost keys verification
will be ignored in that case.
Bug: 17937935
Bug: 17951775
Bug: 17260941
Change-Id: Iad48646cfdd69abaff5c163b2055f3b8a9b39b19
> Using equal weight to ensure that all items are of same width
> The total width of the panel is set in DeviceProfile#layout
Bug: 17456856
Change-Id: Ic98f5c4f7befd4d32d1b52dfe8c9f5b6c58b020a
-> When extending the Launcher Activity, instead of overriding
public and protected methods, create a proper interface
-> This helps define the interface when extending Launcher
more formally and more clearly
Change-Id: Ib38e8a376b2242d4078bf6856bb145f5b5f0da80
> Launcher was making non-trivial updates to ItemInfo objects
on UI thread. These updates were getting skipped when the
Activity gets destroyed (possibly due to onConfigurationChange)
> Unregistering SessionCallback on application onTerminate,
rather than activity onDestroy
Bug: 17941096
Change-Id: Iad4a50871fe09470f26139b44a2e9886833032f1
> changing shortcutInfo.isDisabled to be a flag based variable
> on received OnPackageUnavailable, icons are disabled from desktop
instead of being removed. Icons in all apps are removed
Bug: 15852084
Bug: 16238283
Change-Id: I126d23c709682a917d4bbb84de71032593dce8f9
-> Launcher uses a static instance of it's loader (across
multiple activities) since activities can come and go
(configuration change, eg.) but the data model and loading
is static.
-> Currently, this is not robust to a sequence of events that
looks like onCreate(instance A), onCreate(instance B),
onDestroy(instance B) -- depending on the timing of those
calls.
-> This CL addresses a symptom of the above scenario by not
allowing an older Launcher Activity cancel the loader /
clear the callbacks for a newer Activity.
Bug 17679693
Change-Id: I8ece93e288464b0d578b9669c165b67132d997ed