Age | Commit message (Collapse) | Author |
|
am: ded14cc211
Original change: https://android-review.googlesource.com/c/platform/packages/apps/Launcher3/+/2937801
Change-Id: Ic9b3be62af2271286292cfaf30bda03351c1aaf6
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
|
|
There are some more files relevant to picker, but this CL covers
directory with the primary picker UI.
Change-Id: I53e174d9cd20396b4f56acb5d9e3cc07ec475ea8
|
|
Bug: 319669529
Merged-In: I0708bf3c060ba84089722d0bd9480a4f4bd2b8e2
Change-Id: I31bb7f6aa8f71244f6e44903927f67e9d3a85642
|
|
Original change: https://android-review.googlesource.com/c/platform/packages/apps/Launcher3/+/2891611
Change-Id: I1b9beba5e4ff06b338bc10ed618f60338e6e8d3d
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
|
|
When the dark night mode switch is triggered,systemui calls binder
to the onNavigationBarSurface method in the launcher and applies the
surfaceController.
Keep switching,you will keep applying,resulting in more surface
objects. The behaviour would cause that SurfaceFlinger couldn't
remove the unnecessary navigationbar layers timely and the
navigationbar layer would leak in SF.
Actively release the SC after using the SC in the launcher.
Bug: 317336417
Test: 1.Launch the settings app
2.Click Display menu
3.click the dark theme menu multiple times
4.Check whether the surfaceController is released
adb shell "ls -l/proc/904/fd|wc -l"
Change-Id: Ic449de9dbe0c52e0053be91e67ee9081a574581b
|
|
main am: aa5a060093
Original change: https://android-review.googlesource.com/c/platform/packages/apps/Launcher3/+/2886506
Change-Id: Ib6973650c99c5d92a3548864e56fb3a977766249
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
|
|
lintable modules currently pick up files named "lint-baseline.xml" to use as the
lint baseline implicitly. This is confusing because you could end up using the
baseline files in more modules than intended. Lint also has a feature where it
requests you remove unnecessary findings from the baseline file, so something
could be necessary for one module, but unnecessary for another that accidentally
picked up the baseline.
We're removing the implicit detection of the baseline file, which requires
all modules using it to list the baseline file explicitly.
Bug: 272769514
Test: Presubmits
Change-Id: Idcd6b8c8868b05a34fe621c5c05aa21cc1f149ea
Merged-In: Idcd6b8c8868b05a34fe621c5c05aa21cc1f149ea
|
|
into main
|
|
|
|
|
|
|
|
into main
|
|
Fully reverted the change in ag/24840504, and instead make use of
prefixOrderIndex to ensure translucent overlays launch on top of
the underlying task.
Test: Swipe up from an app to Overview (phone), scroll over one
task, click on the live tile you came from; ensure animates well
Test: Open an app, launch a translucent overlay, e.g. Volume
Dialog, swipe up to Overview and relaunch the live tasks; ensure
the overlay stays on top throughout the animation
Fixes: 310765248
Flag: ACONFIG com.android.launcher3.enable_grid_only_overview TEAMFOOD
Change-Id: I0708bf3c060ba84089722d0bd9480a4f4bd2b8e2
|
|
|
|
|
|
|
|
Bug: 315847371
Test: presubmit
Flag: N/A
Change-Id: I9cf9818946de8b53edc8c44cbd9e673f3bea832f
|
|
|
|
invocation" into main
|
|
|
|
In small screen, we use 48dp for nav bar height, while it's 60dp for task bar.
Bug: 230395757
Test: manual
Change-Id: Ia7083a1b2246981466e1163404c63b645a6bf5b1
|
|
to go home." into main
|
|
Don't reinflate from LauncherAppWidgetHostView#onConfigurat#onConfigurationChanged because Launcher activity will rebind app widgets on configuraiton change. This will reduce lock contention to inflate complex widget views and reduce flicker.
Bug: 285279824
Flag: None
Test: Rotate screen and verify widget are rendered correctly
Change-Id: I69abc7f1fe0ca5704ac887142c73b8d245fead4e
|
|
So we recreate task bars when configuration is changed, if ENABLE_TASKBAR_NAVBAR_UNIFICATION = true. In order for unstashed state to propagate, we need to save STASHED_IN_APP_AUTO in TaskbarSharedState.
Fixes: 311429718
Test: Unstash the task bar in app, rotate, make sure the task bar stays unstashed
Change-Id: I7db773725ea89976612e9e91af5b6911d0ec5fc0
|
|
home.
This fixes the bug where the flag gets set when user taps on nav handle, which
results in the taskbar animation playing.
Flag: N/A
Test: open app
wait for taskbar to finish stashing*
tap on nav handle
nothing happens (desired affect)
* I will address tapping on taskbar while its animating in a separate change
Bug: 292108880
Change-Id: I75870050225bdd951c69224d272d0bd5a3d6d4ea
|
|
ConstraintLayout was causing test failures" into main
|
|
grid" into main
|
|
from All Apps" into main
|
|
|
|
amount of apps to show" into main
|
|
|
|
ConstraintLayout was causing test failures
There are test failures when using ConstraintLayout without a known solution, see https://chat.google.com/room/AAAACwktJi8/2OogGWfbLvI. Switching back to a relativelayout to resolve those issues.
Bug: 301918659
Test: WidgetPickerImageTest
Flag: ACONFIG com.android.launcher3.enable_unfolded_two_pane_picker DEVELOPMENT
Change-Id: I004c2d77ca308d85b29217d4f1e548067126556f
|
|
|
|
Bug: 313926097
Flag: N/A
Test: presubmit
Change-Id: Idd6e3383be21c2040797148817b96105a6f94fe3
|
|
TYPE_ACCESSIBLE." into main
|
|
|
|
Test: Presubmit, Manual
Bug: 308496668
Flag: NONE
Change-Id: Ib8f64e3ae51f5468b9086808551aae826636e03c
|
|
app to workspace" into main
|
|
|
|
Test: locally
Flag: N/A
Bug: 294386159
Change-Id: I810239047480090911c54dbe65a4aad8515f640c
|
|
|
|
This issue happens when restoring the data from a phone to a tablet or vice-versa. When Launcher is restoring the data, it allows the device to load a disabled or invalid grid temporarly for the migration. This leads to a crash when the responsive grid is enabled.
The hotseat spec has only WIDTH or HEIGHT specs in a certain posture. When the user restores the data from a phone to a tablet, the Launcher loads a handheld spec that doesn't have HEIGHT specs for the hotseat in landscape (spec_handheld_hotseat_[grid].xml). However, the tablet, in landscape, tries to retrieve the hotseat HEIGHT spec.
It also prevent crash when responsive grid is used with multi window mode. isVerticalBarLayout becomes false. Then, the responsive grid tries to load a hotseat spec that doesn't exist (using DimensionType.HEIGHT). Phones have hotseat specs only for DimensionType.WIDTH.
Bug: 315548992
Fix: 315069300
Fix: 315377544
Flag: ACONFIG com.android.launcher3.enable_responsive_workspace TEAMFOOD
Test: v2/android-crystalball-eng/health/microbench/systemui/main/systemui-notification-3-jank-suite
Test: atest CtsWindowManagerDeviceDisplay:android.server.wm.display.MultiDisplaySystemDecorationTests#testSendPrimaryHomeIntentActivityOnDisplayWithDecorations -- --abi x86_64
Change-Id: Ibd6537e0528868da9a1b7672c43b5455fa6a8184
|
|
|
|
|
|
|
|
-s ours am: e2d8c0c312 -s ours am: 26fa6bd719 -s ours
am skip reason: Merged-In I7f5bca7edd18631b36f2b9213e17554cf769cbc6 with SHA-1 861ce33a59 is already in history
Original change: https://android-review.googlesource.com/c/platform/packages/apps/Launcher3/+/2863559
Change-Id: I9c2ad64b29aee915aae6ba9784e32fd4f1829ace
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
3cbfd5623b -s ours am: c95f995a9e -s ours
am skip reason: Merged-In I7f5bca7edd18631b36f2b9213e17554cf769cbc6 with SHA-1 861ce33a59 is already in history
Original change: https://android-review.googlesource.com/c/platform/packages/apps/Launcher3/+/2863559
Change-Id: I3b541ffd85a0a721b27b873668ee83089c9c0efd
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|