When launcher loads, it fetches the list of apps twice, once for
loading all-apps and again for updating icons. Instead reusing
the previously fetched apps list.
Also moving the icon loading in a separate package for further
generalization
Change-Id: Ibd2dae56e6027a31b633da030bc6b43a90b27e1b
Apparently, one platform tests starts Messages, and Messages
simply doesn't start.
This check will help to hunt down the problem.
Bug: 110103162
Test: affected tests
Change-Id: I8d781647a2e680e31e96db40d94b89e7728aaf11
- Use accent color for action
- Update font-family to use TextTitle style
- Reduce elevation to 3dp
- Inset snackbar left/right margins more, unless we need to increase the
width to fit the text
- For largest display/font size, fallback to 2 lines and smaller font if
necessary to not cut off the label
- Remove top/bottom padding on action (b/114084048)
- Allow up to 20 char for the action (b/114317987)
Change-Id: I833c102aaac3ba3db2283997c142926c3830336d
When controlling from launcher activtiy, there is no activity focus change, and rotation
lock is not required.
Bug: 114074832
Change-Id: Ia976f9daa9b0f87d3493138d12cb37a490b8b1bd
Reset the restore status for auto install icons where the activity is
installed and enabled so the item is not stuck in the auto install
state.
Bug: 112664405
Test: manual - See issue
Change-Id: I37116b6e6ecbe4215d96627f9b1ea6909d12a6c0
When using overview button, we skip the activtiy animation, which leads
to wrong state. Instead always running the animation and changing the endpoints
accordingly.
Change-Id: Id071b4e74da42c78760519aa29644621afc822e2
Bug: 113683301
Tests failures that we are trying to fix.
https://sponge.corp.google.com/invocations?searchFor=target%3Aandroid.platform.systemui.tests.jank%20label%3Ab%2Fgit_master
When the build rule is android_library, AndroidManifest.xml is pulled into
the the final apk that is being built. Hence, the platform jank and platform test
AndroidManifest.xml is extended with the one we have for Launcher3.
This causes the tests to fail due to existence of disambiguation screen.
We do not want this behavior.
Change-Id: I1a551abf37bb75b4efa8a5e5324ab1b4d8a3eb13
Previously, if a developer renamed their launcher activity, we removed
all instances of their icon from the home screen, since technically the
activity they pointed to no longer exists. However, in the vast majority
of cases, the developer simply renamed their activity and nothing should
change from a user's perspective. So instead of removing icons that no
longer point to a valid activity, we now redirect them to point to the
first activity in the manifest (or remove them if there is none).
Test:
- Install app with Activity A and place on home screen
- Rename A to B and reinstall - verify home screen icon remains
- Add new launcher activity C - verify icons still go to B
- Force stop launcher and rename B to A - verify icons go to A (same activity)
- Remove activity A - verify icons go to C
- Remove activity C - verify icons are removed
Bug: 28907647
Change-Id: If9da251bd588908c4c425e7dd32e38fcbe54bab2
This makes is simpler to control the swipe to overview UI, and ties the
transition with the state machine
Bug: 113287120
Bug: 79755195
Bug: 112203163
Change-Id: I3041dbb659b46ccea6284855addc91e370815be6
Sunny Goyal
Bill Yi
TreeHugger Robot
Vadim Tryshev
Hyunyoung Song
Tony Wickham
Tobias Dubois