The original patch by motorola had another check, but the 2nd check
is wrong as in that case, there would be a nullpointer exception just
after the check for the same reason.
issue: 15518908
issue: 15516428
Change-Id: I85c5fb3541b7f837e6c5295e97e45162a4120e39
-> Early exploration of AllApps Hero transition with
circular reveal
-> Stripping a bunch of dead code from AppsCustomizeTabHost
-> Moved background scrim to DragLayer
-> Removed "SMALL" state from workspace: replaced with
NORMAL_HIDDEN and OVERVIEW_HIDDEN. This is mainly to
reduce the overall usage of the z-space model between
allapps/widgets and workspace. There are vestigial
remains of this model, mainly due to the overview
mode, and a bit for spring-loaded.
Change-Id: If2302a24394f0ec66621f01ffa2fc4934aa10c3f
Track state of promise in the info, not the view.
Fix bugs around moving promises to folders.
Fix bugs around filterign and removing promises.
Bug: 12764789
Change-Id: If5e8b6d315e463154b5bafe8aef7ef4f9889bb95
This reverts commits 01453e855f.
and 242bbe1b72.
"Add content description to bagded icons."
"Remove reflection now we are building against L"
Bug: 15833449
Change-Id: I81a5316f5619a9cd3b6ab9fd03b2ba96657b7f68
Enabled accesibility so that icons badged by the
managed profile have a content description
that is different to the non-bagdged version.
Bug: 15106236
Change-Id: Id483273173d9539916eebd59111d179087526be3
-> When the user creates a new folder
-> When the user drags an existing folder
-> The folder cling gets cut off in certain instances
and until we make it more extensible (not worth
it right now), we're disabling it in the problematic
cases. Also, in the problematic cases, the user
is demonstrating some advanced knowledge, so
it's somewhat justifiable.
issue 14491765
Change-Id: Ib15d2f097c51a9b755f04b95ed6ef468d3bacc60
Use LauncherApps API and badging APIs instead of PackageManager.
With compatability layer that uses PackageManager pre L.
Adds support to show apps from current user and any managed profiles.
Background: Managed profiles are user sandboxes that are visible from
the primary user and can be launched as if they are a part of this user.
A launcher should now be capable of listing apps from this user as well
as related profiles of this user.
Launching of activities is now via the LauncherApps interface, to allow
for cross-profile app launching. Only activities with category LAUNCHER
can be added as a shortcut on the workspace for a managed profile.
Widgets and non-application shortcuts are only supported for the
current profile. Widgets from the managed profile are not available.
Change-Id: I5f396b1bf7f91ad91a5710ea4a0fd14573972eb9
Stops the workspace from announcing incorrectly while the apps
page is open, also makes the apps announce which page on opening.
Bug: 13006306
Change-Id: I723011fc55c24b66604a24b16c17bac4f5653f84
If bounds are set on a compound drawable in a textview, drawing it into a
bitmap set to the intrinsic size of the drawable results in it being scaled
down in the top corner. Scaling it down again into the grid icon size then
gives a tiny icon.
Use the drawable bounds if any are set, otherwise use the intrinsic size.
Bug: 14103508
Change-Id: Idadd7bb891dc33d092eb9ceb3025b9a5d9e1bfd8
-> Found another path that could lead to the same issue
[add shortcut with config activity to an existing folder,
when config activity launches, kill launcher, configure
shortcut. observe crash and data loss].
-> Plugged up above, and a couple other potential holes
-> Initial fix probably took care of the main issue
Issue 12523285
Change-Id: I29db9da4af4a8bf22047eb46bd49354447d04b8d
-> This appears to be what may be causing data loss in some users during update.
A certain (seemingly) rare combination of life-cycle events and package events
seems to be the culprit (potentially why it's seen at update time).
Change-Id: Iea4f8aef012ba80b7ba568e0df264edb9284efbe
When dropping from all apps, accept drop was returning true if the item
was above a folder, however, when it came time to complete the drop,
the folder wouldn't accept the item. This can be prevented by increasing
the criteria in acceptDrop.
Change-Id: Ib644ec45984e8366c33bb674f3d3a76e22ed5160
We need to make sure the custom content is adding synchronously
while the rest of the workspace is being created. If we wait
for it to be added in a separate run task, we see a black
flash during rotation.
Also rename a few methods and remove obsolete methods.
Bug: 11802691
Change-Id: I3f6500aa1fabe68cef59ad8c764877f954986a99