am: 6dc98b9dc0
* commit '6dc98b9dc01f8e5cf5729b958f348af37e0117c6':
Simplifying view cluster by using a single int flag instead of 4 booleans
Change-Id: Id019e3ef2ec1893b51e7b55d58c648532ddd18e6
am: eb4b79935e
* commit 'eb4b79935e9f75dda72e4953f45e616e252d7b03':
Removing icon_type column Icon type is not used consistently. It is used initially during the loader. Afterwards, we save both the icon and resource to the db. Instead of changing the logic to always read the shortcut-resource first, and fallback to the bitmap if the resource is not available, always write the bitmap to DB whenever the shortcut is edited.
Change-Id: Ied43e481b22b444dc9d088f07bde98e7dffcec74
> Sending unboundX to the overlay which is the total untranslated X and not just deltaX from last frame
> Handling overlay callback and translating workspace accordingly
Change-Id: I3bd8d9efac738e9ce131758f0e5ff1b9c1d6a8fc
Icon type is not used consistently. It is used initially
during the loader. Afterwards, we save both the icon and resource to the db.
Instead of changing the logic to always read the shortcut-resource first, and fallback to the bitmap if the resource is not available,
always write the bitmap to DB whenever the shortcut is edited.
Change-Id: I0ea5e88f8904bd3250ca669220b3e5d6aeef1bfd
Overlays are supposed to use their own UI and not interfere with the
Launcher UI. If the UI needs to be put inside the Launcher, use customContent
instead.
Removing some unnecessary and unused methods related to overlays
Bug: 25993953
Change-Id: I4d715cdee04eb7b0ebef673d885a4258c521ff1f
> This used to work, but when I got rid of preloading which was
handled by linear manager to increase scrolling speed, the save
and restore instance that was being handled by the linear layout
manager created using Launcher context also went away. Hence,
bringing back custom LinearLayoutManager.
Change-Id: Ibccdf80533a5ace06cc6c6932b257c223cbac0ff
Since I62963d225e6ea5d2ec9d8ebc8a6d73099f5d6c7f, we have disabled
selection action mode in the folder-name editing mode on Launcher,
mainly because it messed up the view on phones. However that is no
longer the case in Android M and later, where floating action mode
is available.
With this CL, we start relying on the default floating action mode
in Android M and later.
Bug: 22210697
Bug: 28526978
Change-Id: Ie19e7844194acd86cdb013254a1923f0b1d78e11
(cherry picked from commit 1bd9a430ed)
am: 6b360f684d
* commit '6b360f684da3bf4d36643a4325dec2d659900da9':
Using a separate thread for logging
Change-Id: Id911cce659eeefecb33f47967ea72c3210a37c3e
b/27978139
Background: onSaveInstanceState assumes that state of the launcher
is being stored after screen is all binded. However, due to ActivityStack
bug in nyc, onCreate is called twice when the device is rotated while
the Launcher is in the background. The first onCreate fails because
our AndroidManifest is setup with nosensor field and hence doesn't support
Landscape. During this first onCreate, screen is not correctly bound
and incomplete workspace state is saved. This results in the second onCreate
to load wrong screen id.
Fix: While the workspace is still being bound, mSaveState is not reset,
which has the correct values. SaveInstance should use this state
instead of incomplete workspace state.
Change-Id: I5b80f584e55769b2a8ffa292f5daa4705c20086d
am: 462b5cca7b
* commit '462b5cca7bb1d5e24fb8277b0cfe238cc2e1e980':
Extract color for the hotseat.
Change-Id: I83fe42945ff7e32d69885040f3eb473a12141e01
- Only considers the bottom fourth of the wallpaper
- Is translucent black or white depending on how dark/light
the wallpaper is
- Hotseat extends behind the nav bar
Bug: 27230217
Change-Id: Id4ea6ee91b4dd221b4c277d22d5041cab178801d
am: 34a2d31f32
* commit '34a2d31f3208c64f6ebf403f8a0cb6ea96461747':
Adding a utility class for persistant logging.
Change-Id: Ib5ce8987d9271379165d34ff3829482b7509e732
am: ac6d3a87ae
* commit 'ac6d3a87ae9a31873a34f3eae01979910740ade1':
Fixing bug where the widget background enters into a focused state if a child calls requestFocus in xml
Change-Id: I768f13b539e4de683925f94d29d092023660c371
The logs are kept for at max 48 hours. It uses two log files and switches
between the two based on the day of the year.
Change-Id: I9a99499b3445a62f29f62a5cd13db20b1783bcd3